FIX Production Release Notes
New features are production released in a phased rollout to our globally distributed system. Therefore, a feature may be listed here which has not yet reached your workspace(s). However all of these features are available at uat.trade.tt.
| Date | Type | Component | Release Note |
|---|
11/14/2025 | Improvements | FIX Services | Introduced on-the-fly strategy creation through AB/D order messages for both DMA & staged order types through FIX OR.
1. If FIX OR does not find the strategy combination in PDS based on the legs in the order, a request will be sent to the exchange to get the strategy created.
2. If the exchange rejects the request, the order will be rejected.
3. If the exchange accepts the request, FIX OR holds on to the order until it receives a notification from PDS that the instrument is available in TT.
4. When FIX OR receives the PDS notification, it routes the order to the exchange.
5. If FIX OR does not receive the PDS notification within (60) seconds, the order will be rejected. (Ref 190798) Version: v295 |
11/14/2025 | Improvements | FIX Services | Updates on the FIX XML file
1. Introduced a new optional tag, 'BrokerRoute' (18233), to the ExecutionReport (35=8), OrderCancelReplaceRequest (35=G), OrderCancelRequest (35=F), OrderCancelReject (35=9), MultilegOrderCancelReplace (AC), NewOrderMultileg (35=AB), and NewOrderSingle (35=D) messages. The 'BrokerRoute' (18233) tag is now available in the TT XML file. This tag will be populated only on FIX Order Gateway orders, and only if a value is defined for the 'Route' parameter under a FIX Order Gateway connection in TTUS. This feature will be available in an upcoming TT release.
2. Enum values 125:ORDER_PASSING_REQUEST_INITIATE and 126:ORDER_PASSING_REQUEST_UNDO under tag 378 (ExecRestatementReason) are available in the v295 XML.
3. Introduced a new optional tag 'OneOffSharedKey' (20000) in the TradeCaptureReport (35=AE) message. This tag must be included in TradeCaptureReports (35=AE) sent through TT FIX Order Routing sessions for GFO-X block trades. It is used to define the common text between the two parties of the block trade that confirms the match. (Ref 190796) Version: v295 |
11/14/2025 | Improvements | FIX Services | For tag 456 (SecurityAltIDSource) = 92, tag 455 (SecurityAltID) in the SecurityDefinition (35=d) message will contain the 'Family Name' as displayed in PDS instead of the numeric PDS ID. (Ref 190194) Version: v295 |
11/14/2025 | Plan | FIX Services | Limited production deployment of the v295 Drop Copy, Order Routing, Market Data, Recovery and Inbound Drop Copy FIX Services began Nov 14th.
Production deployment of the services will be completed over the following five weeks.
This release includes changes to the FIX XML schema files. Clients are strongly encouraged to download and deploy the latest XML schema files from the URL below prior to release: [https://library.tradingtechnologies.com/tt-fix/general/System_Overview.html]
Release Notes for FIX v295 and prior releases can be reviewed at any time by going to [https://library.tradingtechnologies.com/release_notes/]
All TT FIX clients are strongly encouraged to subscribe to the weekly TT System Admin News and Updates email newsletter here: [https://www.tradingtechnologies.com/support-updates/] (Ref 188884) Version: v295 Learn More |
11/14/2025 | Improvements | FIX Services | Care orders with some untranslatable FIX tags ( instrument, account, user parameters, price, quantity, order type, side) will route to TT and remain in repair mode.
This allows users to review and correct the data before resubmission through the 'Order Exception' widget in TTW. Users can also review and reject the order in this mode.
When a care order is placed in repair mode, an Execution Report (39=0/150=0) will be sent through FIXOR but there will be no messages through the FIX drop copy session (if configured).
When a care order is corrected and resubmitted successfully from repair mode, a restated Execution Report (39=0/150=D) will be sent through FIXOR and a new Execution Report (39=0/150=0) will be sent through FIX drop copy session (if configured).
If the care order is rejected while in repair mode, a rejected Execution Report (39=8/150=8) will be sent through FIXOR and FIX drop copy session (if configured).
Please note that users must have OMS Advanced features enabled in TTUS to access this new functionality. (Ref 187977) Version: v295 |