01/23/2026 |
|
|
Improvements |
FIX Services |
A new FIX session parameter 'Send Tag 60 in Nanoseconds' has been introduced to the TT FIX Session Setup for Order Routing and Drop Copy sessions, allowing for higher granularity in tag 60 (TransactTime).
1. This parameter applies to Tag 60 in all outgoing messages for FIX Order Routing, Recovery, and Drop Copy sessions and will be unchecked by default.
2. If checked, tag 60 will be sent in nanoseconds `YYYYMMDD-HH:MM:SS.sssuuunnn`. If nanosecond precision is enabled but the exchange does not support it, the timestamp will be padded with zeros to maintain the nanosecond format.
3. If unchecked, tag 60 will be sent in microseconds `YYYYMMDD-HH:MM:SS.sssuuu`.
4. If the TrimTimestamp rule is set in the session, it will always take precedence over this new parameter and tag 60 will be sent in miliseconds `YYYYMMDD-HH:MM:SS.sss` based on the rule criteria.
(Ref 198107)
Version: v295 |
01/23/2026 |
|
|
Improvements |
Settings |
Added a new "Enable Exception Management" setting to the FIX Order Routing session configuration in TT Setup. When enabled, most inbound FIX care orders with errors will no longer result in immediate client rejections. Instead, these orders will be processed and displayed in the TT front-end within a new "Order Exceptions" widget. This widget provides "Repair" or "Reject" options for direct management of these error orders. Note that front-end users must have OMS Advanced features enabled in Setup to access this functionality. See our documentation for more details.
(Ref 198101)
|
01/22/2026 |
|
|
Improvements |
Order Entry |
Enhancement #1
Eurex and EEX are enhancing their SMP feature to add 3 new SMP types , in addition to the setting for Market wide and industry wide testing . These new SMP types will be available as a new drop down on TTUS , and the following values will be allowed :-
1. Cancel Incoming Order
2. Cancel Resting Order
3. Reduce Greater
These SMP types can be set on TTUS user configurations , and also overridable through FIX
Enhancement #2
Eurex suggests that “If the Client Identifier field is not provided for agent orders, then they will be rejected. For orders sent with TradingCapacity Proprietary or Market Making, the Client Identifier field may remain empty “ .
To support this feature, TT is adding an enhancement to reject orders internally under the below condition :-
* When the “Trading Capacity” is set to “Any other Capacity” for user , then if the order is sent with "Client ID" as blank , then the order will be rejected.
(Ref 191545)
|