05/29/2020

Improvements

FIX Services

FIX has added a new tag, Secondary Account Name, (FIX tag 18219), to FIX order messages, the purpose of which would be to enable customers to supply an externally defined account name to the TT system that could be used to lookup a single TT account in setup that is then assigned to Tag 1 on the order. This tag is optional an D/AB messages only and is not included on any outbound messages from TT to FIX clients.

For more information, please contact the TT FIX Integration team at: fixintegration@tradingtechnologies.com

(Ref 114026)

Production Release: 05/29/2020

Version: v105

04/29/2020

Improvements

FIX Services

All FIX Services for the v105 release were initially deployed to UAT Data Centers at EOD Apr. 25, 2020.

Production deployment will begin EOD May 29, 2020, in the following TT Data Centers only:
- Sao Paulo - ALL FIX Services
- Chicago, Aurora, New York - A single server in each cluster will be upgraded for All FIX Services

Production deployment will continue at EOD June 5, 2020 in the following TT Data Centers only:
- Chicago, Aurora, New York- All FIX Services
- London, Frankfurt - A single server in each cluster will be upgraded for all FIX Services

Production deployment will continue at EOD June 12, 2020 in the following TT Data Centers only:
- London, Frankfurt - All FIX Services
- Hong Kong, Singapore, Sydney, Tokyo - A single server in each cluster will be upgraded for all FIX Services

Production deployment in all remaining TT Data Centers will complete EOD June 19 2020.

This release includes changes to the FIX XML schema files. 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 113599)

Production Release: 05/29/2020

Version: v105

04/29/2020

Improvements

FIX Services

Added FIX tag 18227, Organization, which is a an optional "custom field" defined in TT Setup that represents the User-defined name of the trader's organization. This tag is optional in D/AB/8/9 messages. Sent only when a value is configured in Setup by a customer's admin user.

(Ref 113557)

Production Release: 05/29/2020

Version: v105

04/29/2020

Improvements

FIX Services

Support routing of Reject messages created by FIX Inbound Drop Copy to a specific Error Account, which can then be delivered via FIX drop copy or viewed in TTW Audit Trail.

Types of Rejects created by FIX Inbound Drop Copy:
* Account not found
* User not found
* Instrument not found
* Badly formed FIX message
* Order not in book

The Error Account can be assigned to the FIX Inbound Drop Copy session via the TT Setup GUI. Further documentation is available in the Setup section of TT Help.

(Ref 111988)

Production Release: 05/29/2020

Version: v105