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 |
---|---|---|---|---|
06/24/2022 |
07/22/2022 |
Fixes |
FIX Services |
FIxed an issue where a BlockTrade submitted via FIX Order Router was not able to be cancelled via FIX. (Ref 141765) |
06/24/2022 |
07/22/2022 |
Improvements |
FIX Services |
Added FIX tags for EchoDC_1 - EchoDC_20 to TraderCaptureReport (AE) and TradeCaptureReportAck (AR) messages. (Ref 141764) |
06/24/2022 |
06/24/2022 |
Fixes |
Market Data |
Expiry Date on JPX products has been corrected to match Maturity Date instead of LTD. (Ref 141619) |
06/24/2022 |
07/22/2022 |
Improvements |
FIX Services |
A number of tags have been added to the TT FIX XML schema files s to support custom parameters for use by TT Score customers. These parameters are available for use on execution reports submitted from clients inbound to TT via a TT FIX Inbound Drop Copy sessions *only*. These tags will not be present on ERs received on outbound Drop Copy or Order Routing sessions. (Ref 140761) |
06/24/2022 |
07/22/2022 |
Plan |
FIX Services |
Limited Production deployment of the v187 FIX Services began June 24, 2022 in Aurora and Sao Paolo only and will deploy incrementally to all TT Data Centers over the next 4-6 weeks. (Ref 140760) |
06/17/2022 |
06/17/2022 |
Fixes |
Setup App |
Fixed an issue where the Save button was not activated when only changing a user's Trade Mode in Setup. The workaround was to change another user setting value in order to get the Save button to activate. (Ref 141907) |
06/17/2022 |
Improvements |
Score |
Dual ladder replay: Score users can now add a second ladder for a user defined instrument to view in parallel with the ladder from any Score cluster. What this means is that users can view the traders activity in the cluster specific instrument and also pull up a second ladder for any instrument that will sync in time to the first ladder. This is helpful in reviewing the potential market impact of the traders activity in a related product, or demonstrating that the users activity in the cluster was due to a change in market conditions in a separate instrument. This second ladder can be added from controls area of market ladder replay. (Ref 139626) |
|
06/16/2022 |
06/16/2022 |
Fixes |
TT Core SDK |
Fixed an issue where a conflict could occur if a user cancelled a remaining algo position reserve order at the same time as our automatic cleanup process. (Ref 141922) |
06/15/2022 |
06/15/2022 |
Improvements |
TT .NET SDK |
Added support for the Sniper and Reload options for ASE orders. (v3.1.2.2) (Ref 141758) |
06/15/2022 |
06/15/2022 |
Fixes |
TT .NET SDK |
Fixed an issue with the processing of order fill updates during bursts of activity. (v3.1.2.2) (Ref 141755) |
06/10/2022 |
06/10/2022 |
Fixes |
Setup App |
On June 3, two new columns relating to KRM22 were added to the User Settings report. These fields are not needed on that report and have been removed. (Ref 141741) |
06/09/2022 |
Improvements |
TT .NET SDK |
Add support for RFQ. (v3.1.2.1) (Ref 141573) |
|
06/09/2022 |
Improvements |
TT .NET SDK |
Enhanced the API to trigger a FillBookDownloadEnd callback when all markets are finished downloading historical fills. (v3.1.2.1) (Ref 141572) |
|
06/09/2022 |
Improvements |
TT .NET SDK |
Optimized the access line health check process to start the API faster. (v3.1.2.1) (Ref 141571) |