10/15/2025 |
Improvements |
FIX Services |
Updates on the FIX XML file
1. The newly introduced tag 18233 will appear in the TT XML files with the name “BrokerRoute” and not “Route” as stated in the previous RN (Ref: 190796). It is included in the NewOrderSingle (35=D), NewOrderMultileg (35=AB), OrderCancelRequest (35=F), OrderCancelReplaceRequest (35=G), MultilegOrderCancelReplace (AC), ExecutionReport (35=8) and OrderCancelReject (35=9) messages.
2. Enum values 125:ORDER_PASSING_REQUEST_INITIATE and 126:ORDER_PASSING_REQUEST_UNDO under tag 378 (ExecRestatementReason) are now available in the v295 XML.
(Ref 191472)
Version: v295 |
10/15/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 |
10/14/2025 |
Improvements |
FIX Services |
Updates on the FIX XML file
1. The newly introduced tag 16762 will appear in the TT XML files with the name “DefSecuritySubTypeID” and not “SecuritySubTypeID” as stated in the previous RN (Ref: 188541).
2. The NestedParties component, previously part of the LegsGrp component in the FIX XML file, was removed because it was only used by TT internally and not exposed on client FIX messages. This change does not impact TT FIX client applications.
3. Enum values 125:ORDER_PASSING_REQUEST_INITIATE and 126:ORDER_PASSING_REQUEST_UNDO, which had been previously added to tag 378, were removed from the v291 XML. These enums will be added in an upcoming TT release, along with the new Order Passing functionality.
(Ref 191167)
Production Release: 10/14/2025 Version: v291 |
10/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.
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.
If the exchange rejects the request, the order will be rejected.
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.
When FIX OR receives the PDS notification, it routes the order to the exchange.
If FIX OR does not receive the PDS notification within (60) seconds, the order will be rejected.
(Ref 190798)
Version: v295 |
10/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.
(Ref 190796)
Version: v295 |
10/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 |
10/14/2025 |
Plan |
FIX Services |
UAT deployment of the v295 Drop Copy, Order Routing, Market Data, Recovery and Inbound Drop Copy FIX Services began Oct 14th.
Production deployment of all services will begin in 4-5 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 |
10/14/2025 |
Improvements |
Orders |
We have implemented significant improvements to the workflow for brokers and execution desk traders, enabling more efficient management and resolution of FIX care order rejections. Previously, errors in inbound FIX care orders resulted in immediate rejections to the client. Going forward, the majority of these orders will be processed and displayed in the TT front-end within a new "Order Exceptions" widget. FIX care orders with exceptions will not appear in the standard Order Book widget or the Orders and Fills Widget (OFW); instead, they will be displayed in this new widget, which provides "Repair" or "Reject" action options for direct management of these error orders.
Exception orders will be routed through the regular TT account specified on the order, unless the error pertains to the account indicated on the order. In such instances, the exception order will be routed through the "error account" associated with the FIX session. Companies should map these error accounts to the users who will be utilizing the exception management functionalities. Please note that users must have OMS Advanced features enabled within Setup to access this new functionality. More detailed information will be forthcoming in our documentation.
(Ref 187369)
|
10/09/2025 |
Improvements |
Blocktrader |
Blocktrader now supports reporting OTC trades on New Zealand's Exchange (NZX) with two trade types: (1) Block and (2) Exchange for Physical.
(Ref 189985)
|
10/09/2025 |
Improvements |
Blocktrader |
Per a change in Euronext exchange behavior, Blocktrader now supports submitting Request for Cross (RFC) on Commodity Option Strategies without the need to specify the individual leg prices.
(Ref 189983)
|
10/02/2025 |
Improvements |
General |
The TT titlebar has been updated as follows:
1) Added "Home". This option opens the customer portal in a new tab.
2) Updated the behavior of "Trade". Instead of opening the workspace management page, this option now opens the last opened workspace, or a blank workspace if there in no workspace created yet. To access the workspace management page, click "Home" and open it from the customer portal.
(Ref 188563)
|
10/01/2025 |
Improvements |
General |
Starting October 5, the naming convention for FIX Order Routing Send/Recv logs will change slightly. The new naming convention will include the data center from which the collection was processed. This change is part of an effort to reduce the amount of time needed to collect these files.
This change also means that customers might receive several FIX Order Routing Send/Recv zip files per day and these files might be delivered at slightly different times. The number of files will depend on FIX Order Routing activity in each data center.
For example, a customer who had FIX Order Routing sessions running in several data centers might having been receiving a single file named like fix_order_routing_service_tt_send_recv_logs_999_2022_03_01.zip might now receive two files named like fix_order_routing_service_tt_send_recv_logs_999_singapore_2022_10_10.zip and fix_order_routing_service_tt_send_recv_logs_999_frankfurt_2022_10_10.zip.
A similar change was made to FIX Drop Copy Send/Recv logs in October 2022.
(Ref 190404)
Learn More |