Release Notes

August 2024 - 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

08/28/2024

08/28/2024

Fixes

TT Core SDK

Fixed an issue that resulted in specific order parameters being dropped after a restart. (v2.0.0.1)

(Ref 169929)

08/28/2024

08/28/2024

Improvements

TT Core SDK

Created a new package with the GCC v9 compiler and C++17 / boost 1.78. TT will continue support for the existing package with GCC v7 compiler and C++14 / boost 1.69 until December 31, 2025. Clients are encouraged to migrate as early as possible to ensure continuity in their trading. (v2.0.0.1)

(Ref 169928)

08/23/2024

Fixes

Market Data

All Weekly Options on HKEX are being changed so that Maturity = Last Trade Date.
This change is being done to ensure successful instrument lookup when using FIX tag 541 or FIX tags 200 and 205.

(Ref 169069)

08/23/2024

08/31/2024

Improvements

Market Data

As of September 1, the CME will update their market Data Subscription Agreement. - From August 11, users in UAT have been prompted to sign a new agreement in order to allow continued access to CME market data - Deployment of the new Agreement will occur in Production on August 26, 2024, and all users will be required to accept the agreement prior to October 1, 2024 in order to allow access to CME market data - API users will need to access TT Setup to sign the new agreement

(Ref 168781)

08/21/2024

Plan

Order Entry

IMPORTANT NOTE: UPDATED
TT will be migrating to the SAIL B4 version this weekend. Starting on August 26, TT will adopt the SAIL B4 version. Clients will have until August 25 to link their session IDs and complete testing in UAT. Failure to do so will result in the denial of order entry session login by the exchange.
On the MX Axis portal (https://www.tmx.com/axis/login/), link the session ID to 'Order Connector v255 - B4'.
This upgrade introduces new fields for regulatory compliance. While MX does not require these fields to be populated until March 31, 2024, TT will send them to MX if they are filled in. These fields will be configurable in TT User Setup under Accounts. Please use the corresponding TT fields to set the compliance fields: 1. Unique ID: <Investment Decision ID> Alphanumeric field, max 10 characters 2. Sponsored Access Flag: <Direct Electronic Access (DEA)> Yes/ No drop -down on accounts 3. Client Short Code: <Client ID> Numeric only field, max 10 characters 4. Algo Trading Flag: <Investment Decision Qualifier> Yes/ No drop -down on accounts
Note: 1. When none of the new fields are set, the order will not be denied by MX. 2. When the “Instrument Decision ID” or “Client ID” fields are configured with more than 10 characters, the order will be denied internally by TT. The denial message will state: “Exchange does not support UniqueID or ShortCode greater than 10.” 3. The “Client ID” must be numeric only. If it is configured as an alphanumeric value, such as “Client123”, the order will be denied internally by TT with the message: “Exchange does not support negative or invalid short code.”
FIX clients can override all these fields with the following tags: Investment Decision ID (tag 448), PartyRole (tag 452), Investment Decision Qualifier (tag 2376), Client ID (tag 448), and Direct Electronic Access (tag 1724).
For additional information, please refer to: https://www.tradingtechnologies.com/support-updates/ (UPDATED: MX: API Upgrade: Client Identifiers).
https://reg.m-x.ca/en/requirements/client-and-order-identifiers

(Ref 169786)

08/09/2024

Plan

Market Data

Implemented a change to support a new SecuritySubType (92) in the market data feed for B3 market

(Ref 169091)

08/05/2024

Plan

Order Entry

The MX SAIL B4 API upgrade has been deferred to later this month in order to allow TT to ensure correct configurations are in place for all customers. We will announce the new date of the upgrade in due course.

(Ref 169061)

08/02/2024

08/03/2024

Fixes

FIX Services

DigiCert Certificate Expiration @ Saturday, August 3 - 19:30 UTC
At approximately 23:30 UTC on July 29 DigiCert publicly announced that they will be revoking their certificates at 19:30 UTC on July 30 that do not meet the CA/Browser Forum (CABF) rules. As stated on the DigiCert website “Recently, we learned that we (DigiCert) did not include the underscore prefix with the random value used in some CNAME-based validation cases.” (https://www.digicert.com/support/certificate-revocation-incident)
For customers whose FIX engine natively supports SSL encryption, or who have implemented FIX session encryption using STunnel with certificate pinning, TT provides a TTFIX.crt file.
TT updated the stunnel.zip file located in the Download Center in order to update the soon-to-be-revoked certs in the TTFIX.crt bundle.
Customers still using the old stunnel.zip file after Saturday, August 3 at 19:30 UTC will not be able to connect to the respective TT environments if they are configured to verify the certificate.
Please follow the instructions for configuring a STunnel with TTFIX.crt and download the updated stunnel.zip here: https://library.tradingtechnologies.com/tt-fix/general/Managing_FIX_Sessions.html#connecting-to-tt-fix.

(Ref 168998)

Version: v252

Learn More