Release Notes

October 2025 - Production Environment

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.


Production Start Production Complete Type Component Release Note

10/03/2025

Improvements

FIX Services

LSEG: Eurex - RIC rename for 2 digit year code

On October 6th of this year, Refinitiv (LSEG) will rename Eurex RICs representing Futures and Spread contracts both on Real-time and Reference Data Products to support two-digit year codes. Underlying Futures contracts for Options on Futures will be displayed with a 2 digit year code. This change will also be applicable for Market by Price data, Level 2 RICs and delayed data.

TT will deploy the required changes to Production before the Refinitiv planned changes in production. These changes are now available for testing in UAT.

All currently deployed versions of TT FIX services are compatible with this change. TT customers using RICs for FIX Order Routing, Drop Copy or Market Data are encouraged to test their FIX applications in UAT prior to go-live.

(Ref 189790)

Version: v291

10/03/2025

10/04/2025

Improvements

Exchanges

TT has added support for the optional field of Liquidity Provider ID, that has been introduced by Euronext, on the order messages. This field will be available for configuration on TTUS under account settings.
FIX users can use FIX parties block Tag 448 for specifying this ID, with Tag 452 = 35.

Note that the existing field of LP Role will be set as 1 (Liquidity Provider and Market Maker) by TT, when the Account Type is specified as Market Maker, as that is the only value allowed by Euronext on the derivatives market. No value needs to be specified by customers for the LP Role field.
The Liquidity Provider ID field is now available in the TT UAT environment for customer testing.

(Ref 189114)

10/03/2025

Improvements

FIX Services

Added a new enum value, ‘X', Series Key, to SecurityAltIDSource (tag 456) for Security Definition messages. When present, the associated SecurityAltId (455) will contain the value of the PDS Series Key field for the current instrument.

The new enum is supported for Security Definition messages only (not in SecurityAltId group for other message types), and only when tag 58 on the SecurityDefinitionRequest(c) contains “456=X”.

(Ref 188542)

Version: v291

10/03/2025

Improvements

FIX Services

Introduced (2) new FIX tags in TT FIX Security Definition 35=d message.
* Tag 1227, “ProductComplex”; type String
* Tag 16762, “SecuritySubTypeID”, type Int

The values in TT FIX tags 1227 and 16762 will be as provided by the exchange. TT will not modify or normalize these values.

The new tags will be present in Security Definition 35=d messages anytime the values are available in PDS. Only Eurex products are currently supported.

(Ref 188541)

Version: v291

10/03/2025

Plan

FIX Services

Production deployment of the v291 Drop Copy, Order Routing, Market Data, Recovery and Importer FIX Services began October 3rd.

Production deployment of all services will complete in 4-5 weeks.

v291 FIX Services have been deployed to UAT since September 4th.

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 v291 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 187963)

Version: v291

Learn More

10/02/2025

10/02/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

10/02/2025

10/02/2025

Fixes

Market Data

Fixed an issue that sometimes caused stale auto-roll instruments to persist in the workspace.

(Ref 189979)