You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some attributes are not GUI related and also not linked to the values of a standard FIX tag. Parameter/@definedByFIX is an option to reference a standard FIX tag within the 1-5000 range. Should this connection be made explicit to avoid valid values drifting apart?
Relevant attributes:
Strategy/@objective (has some values from StrategyType(2141) as well as TrdType(828), and a mention in SecuritySubType(762))
SecurityType/@name (reference SecurityType(167) in the description)
Strategy/@fixMsgType (references MsgType(35) in the description)
The text was updated successfully, but these errors were encountered:
These are mostly hints given to the OMS as how to behave. For example, @objective = "Pairs" my allow the OMS to bring up it's "Pairs" screen (if it has one). @definedByFIX = true lets the OMS know the parameter is in the 1-5000 range.
@fixMsgType is more prescriptive, it instructs the OMS to use a specific messages when sending a multi-leg order to the Broker-Dealer.
These were not intended to define the data model for the orders. But I can see your point on how they may drift and may benefit from using the existing values for, say, StrategyType. So instead of @objective we can have @strategyType.
I think this is best left for RC2.
Some attributes are not GUI related and also not linked to the values of a standard FIX tag. Parameter/@definedByFIX is an option to reference a standard FIX tag within the 1-5000 range. Should this connection be made explicit to avoid valid values drifting apart?
Relevant attributes:
The text was updated successfully, but these errors were encountered: