09/25/2025 |
|
|
Fixes |
Market Data |
Fixed an issue that sometimes caused stale auto-roll instruments to persist in the workspace.
(Ref 189979)
|
09/23/2025 |
10/11/2025 |
10/11/2025 |
Improvements |
ADL |
This is to address logic improvements within our Market Making Algo (MMA) suite, specific to the following globally deployed algos:
Bid Ask Theo
Direct Entry
Reference Market
Single Theo
Improvements within these MMA's are to address the following:
- Addressed a situation where initial cover orders were not sent out unless the Net Pos was >=1. Re-sequenced the "Quote Order" fills such they update the net pos block before they hit the branch block
- Improved the "fill throttle" logic to ensure "Order:price requote" discrete message is kept instead of circumventing the fill throttle.
Primary issues were within the SafeToPlace orders group block. Qty increases would set all checks true and generate a message that would ultimately place an order even when "Manual Requote" was enabled or if a fill was being throttled. Addressing these led to a number of obstacles which led to the following necessities.
- For on start generator, one path needed to have only an initial on start while another path required all subsequent starts (resumes) but must exclude the initial start message.
- This was achieved by using Value extractor "Initial start tracker" in tandem with branch block "Initial start?"
- Initial start message needed to be tagged so logic within virtualization could differentiate between initial start and subsequent start messages.
- This was achieved with value injector "Initial start tracker" injecting "1" into userfield1 and value extractor "Initial start marker" placed just inside the virtualized block.
An indication of active fill throttling was required to stop qty increases from triggering a new order.
- "fill throttled" value accumulator was added in the previous change and used in this change as well to determine whether or not there is active fill throttling.
- Logic was added to clear it when the fill throttle time elapsed, or if throttling was active when the user pauses the algo, to clear it on resume.
Within the "SafeToPlaceOrder" group the following was added:
- A formula block with the following equation to check manual requote setting, intial start marker and active fill throttle.
(!Manual Requote OR Initial start marker =1) AND fill throttled !=1
- If the above evaluates to true, then the a message that would ultimately place an order is sent.
- If the above evaluates to false, the message that would place an order will not be generated until the user hit the manual requote button.
(Ref 163092)
|
09/22/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 |
09/19/2025 |
09/19/2025 |
|
Improvements |
FIX Services |
This weekend, CME will modify the Quarter tick eligibility for options on the following products.
SR3
1YH
1YM
1YU
1YZ
2YH
2YM
2YU
2YZ
See here for details from the CME:
https://www.cmegroup.com/notices/electronic-trading/2025/09/20250915.html#ctsoqte
Customers who trade these Options via TTW must refresh their workspace after 15:30 CDT on Sunday, September 21, in order for the tick changes to take effect.
Customers trading via FIX should ensure that their weekly security definition download occurs after 15:30 CDT on Sunday, September 21.
If you need any assistance please reach out to TT Support.
(Ref 189701)
Production Release: 09/19/2025 Version: v286 |
09/19/2025 |
|
|
Fixes |
Order Book |
Fixed an issue that sometimes caused old filled orders to remain in the Order Book.
(Ref 187387)
|
09/17/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 |
09/12/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)
|
09/12/2025 |
|
|
Improvements |
Order Entry |
We have extended the current FX Spot order quantity behavior, specifically the “K”/”M” quantity modifier button, to also encompass other FX product types of NDFs, FWDs and Swaps.
(Ref 187393)
|
09/12/2025 |
|
|
Improvements |
General |
We now display a status message when the user attempts to login and exceeds the allowed concurrent login sessions.
(Ref 187379)
|
09/12/2025 |
|
|
Fixes |
General |
Added a defensive check to prevent exception errors from invalid risk updates.
(Ref 187378)
|
09/12/2025 |
|
|
Fixes |
Autospreader |
Fixed an error that sometimes occurred when using Autospreader with Aggregator leg instruments.
(Ref 187377)
|
09/12/2025 |
|
|
Fixes |
Order Entry |
Fixed an issue that prevented correctly creating a child order on a care order set with a Time-in-Force of GTDate.
(Ref 187376)
|
09/12/2025 |
|
|
Fixes |
Fills |
Fixed a memory leak that could appear when retrieving old fills from previous sessions.
(Ref 187375)
|
09/12/2025 |
|
|
Fixes |
Positions |
Fixed an issue that caused the Position widget to display margin incorrectly when using TT Premium Order Types.
(Ref 187361)
|
09/12/2025 |
|
|
Improvements |
Market Data |
The Product Grid now includes the Status column as an optional column, similar to the Market Grid.
(Ref 187360)
|
09/11/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 |
09/09/2025 |
09/13/2025 |
09/13/2025 |
Improvements |
ADL |
Further to the Release Note dated 07/28/2025 (with Ref 177412)
Addressed an issue within the existing MinVol algo logic that ensures upon recovery, the logic should never place a buy and sell child order in the same instance.
The fix has now been deployed to UAT and Production environments under its original name "MinVol". The amended version of this algo will be globally available to users within the "Shared with me" section of the algo list panes.
A copy of the MinVol ADL logic is also available from the ADL Canvas.
(Ref 189165)
|
09/05/2025 |
|
|
Plan |
FIX Services |
UAT deployment of the v291 Drop Copy, Order Routing, Market Data, Recovery and Importer FIX Services began September 4th.
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 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 |
09/04/2025 |
09/12/2025 |
|
Improvements |
Trade Surveillance |
Users now have the ability to automatically generate reports that run on a user defined schedule. This new feature is located under the “reports” tab where there is a new section entitled “reports scheduler”. Here the user can choose from the dropdown of available reports for auto generation and select the parameters and frequency of generation. All auto generated reports will be available on time in the “generated reports” section near the bottom of the page. The reports initially available for auto generation are the cluster export list, which allows for the export of all or a subset of the clusters to be exported to a csv, and the new unreviewed clusters report, which identifies all clusters left in an unreviewed state during the user defined report period.
(Ref 191153)
|
09/04/2025 |
09/12/2025 |
|
Improvements |
Trade Surveillance |
New report: This report identifies all clusters left in an unreviewed state during the user defined report period. This is available with the new automated reports in TT Trade Surveillance.
(Ref 191152)
|