FIX Production Release Notes
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.
| Date |
Type |
Component |
Release Note |
10/25/2019 |
Improvements |
FIX Services |
All FIX Services for this release were initially deployed to UAT at EOD Sept. 6, 2019. *Update:* adjusted production roll-out dates.
Production deployment was completed EOD Oct. 11, 2019, in the following TT Data Centers only:
- Chicago - All FIX Services
- Sao Paulo - ALL FIX Services
Production deployment was completed EOD Oct. 18, 2019 in the following TT Data Centers only:
- Aurora - ALL FIX Services
- New York - ALL FIX Services
Production deployment will continue at EOD Oct. 25, 2019 in the following TT Data Centers only:
- Hong Kong - FIX Back Office and Order Routing Services
- Singapore - FIX Back Office and Order Routing Services
- Sydney - FIX Back Office and Order Routing Services
- Tokyo - ALL FIX Services
Production deployment in all remaining TT Data Centers will complete EOD Nov. 1, 2019.
This release includes only cosmetic changes to the FIX XML schema files. Nonetheless, clients are strongly encouraged to download and deploy the latest XML schema files from https://library.tradingtechnologies.com/tt-fix/System_Overview.html prior to release.
(Ref 104010)
Version: v73 |
10/12/2019 |
Fixes |
FIX Services |
Fixed an issue where tag 129, DeliverToSubID, could be missing on unsolicited execution reports received on a FIX order routing session.
(Ref 102823)
Version: v73 |
10/04/2019 |
Improvements |
FIX Services |
Added support for (5) vendor-defined fields to the FIX XML schema, which are reserved for future use by 3rd-party algo / FIX Out execution destinations.
Tags added:
17001: Vendor-defined Field 1
17002: Vendor-defined Field 2
17003: Vendor-defined Field 3
17004: Vendor-defined Field 4
17005: Vendor-defined Field 5
Description: Vendor-defined fields 1-5 for 3rd-party algo / FIX Out connection types. Not supported when routing to/from native TT order connections.
Type: String
Required: No
Used in message type: Execution Report, Cancel/Reject
These values are not over-rideable when submitting orders via FIX and can only be set by defining values in order tag defaults for the FIX Out connection type in TTUS.
These tags will not be supported for any TT native order connections and will also not be copied onto compliance drop copy messages.
(Ref 102828)
Version: v73 |