Imported from previous forum
Hello,
Is it possible to do time validation to ‘Now’ in FixATDL spec? I need to validate some of strategy parameters to be later than ‘Now’.
Thanks.
Anastasia,
Thanks for the question.
I’m going to take a shot at this and also encourage others to jump in.
FIXatdl doesn’t extend the underlying FIX protocol and to best of my knowledge there is no concept of “now” in the base FIX protocol other than “assumed” as in market type order.
“Now” strikes me as something the OMS does - takes a “Now” GUI option and substitute in a current time/date stamp into a variable. VALIDATION (see xsd) in FIXatdl is considered batch oriented, to be run only AFTER all variables have been filled and the “send order” button has been pressed. A “now” would need to become a time/date variable prior to the FIXatdl VALIDATION rules being run.
FLOW (see xsd) on the other hand allows branching and work flow management during the order build process. Testing “now” in FLOW might be difficult or a problem? Especially if “now” did not result in a time/date stamp replacement until after the “send order” button was pressed (just prior to the VALIDATION rules being run). In FLOW you would likely need a “now” translated into time/date, prior to the FLOW rule running and you might later, after the “send order” button was pressed substitute in a later time/date stamp.
If you could write up a USE-CASE its highly likely people in the WG and others will be able to give you a “work around” solution or help better identify any FIXatdl structural issue.
Time/date seems to be a “hot area” with many nuances. This impacts FIX in general, and likewise FIXatdl. So, thanks for bringing it up.