Release Notes

June 2019 - UAT Environment

Date Type Component Release Note

06/25/2019

Improvements

SSE

Implemented a Time Duration algo to allow users to slice a larger quantity into smaller orders by defining the total time desired to achieve the total goal quantity.

Learn More

06/13/2019

Improvements

TT Rest API

In prior versions, a status code of 200 is returned for all requests. In this version, 400 and 500 status codes are being returned for error conditions.

Production Release: 06/28/2019

06/13/2019

Improvements

TT Rest API

Added POST /report/admin and POST /report/risk endpoints to expose the data provided by TTUS reports.

Production Release: 06/28/2019

06/11/2019

Fixes

FIX Services

FIxed an issue with FIX drop copy download of account data from TT Setup, where more data was being downloaded than was necessary, leading to long download times and session disconnects for some FIX Clients.

Version: v52

06/10/2019

Improvements

FIX Services

In order to make Instrument block usage more consistent across all supported message types, tags 107, 460, 607 and 620 will be included where applicable on FIX Market Data (35=W, 35=X), Security Definition (35=d), Security Status (35=f) and QuoteRequest (35=R) messages.

This change is available in all UAT and Production (North America only) locations as of June 7. Deployment to the remaining production locations is planned for June 21.

Production Release: 06/10/2019

Version: v52

06/10/2019

Fixes

TTSDK

The package TT.NET.SDK.ClientSide 1.4.0.4-dp was recently published on NuGet Gallery. It includes a few fixes for routing algos.

06/10/2019

Improvements

FIX Services

In order to make Instrument block usage more consistent across all supported message types, tags 107, 460, 607 and 620 may now be sent on Execution Report messages (35=8).

This change is available in all UAT and Production (North America only) locations as of June 7. Deployment to the remaining production locations is planned for June 21.

Production Release: 06/10/2019

Version: v52

06/10/2019

Improvements

FIX Services

In order to make Instrument block usage more consistent across all supported message types, tags 460, 607 and 620 may now be sent on 35=AE and 35=AR messages.

This change is available in all UAT and Production (North America only) locations as of June 7. Deployment to the remaining production locations is planned for June 21.

Production Release: 06/10/2019

Version: v52

06/10/2019

Improvements

FIX Services

When "Compliance Feed" is enabled on a FIX Drop Copy OUT session type, tags 100, 107, 207, 460, 607 and 620 will be included when applicable on 35=D, 35=G, 35=AB, 35=AC and 35=F messages. (corrected 6-10-19)

This change is available in all UAT and Production (North America only) locations as of June 7. Deployment to the remaining production locations is planned for June 21.

Production Release: 06/10/2019

Version: v52

06/07/2019

Improvements

Setup App

In the Setup App, admins will see three new fields within the Users->Custom Fields tab, labelled Billing 1, Billing 2, and Billing 3. These are optional, free-form text fields. The values entered can be used to segregate Users into separate billing groups.

06/06/2019

Improvements

Autospreader Rules

Increased the maximum allowed value for both the Inside and Outside Throttle values in the (TT) Quote Throttle Autospreader Rule.

06/04/2019

Fixes

Exchanges

Fixed an issue in ASX where the required "Account Type" field was sent as "Client" if not specified in User Setup or the FIX message. Now if account type is not specified, the order will be rejected. FIX tag 528 can also be used to populate Account Type values for FIX clients.

06/04/2019

Fixes

Orders

Fixed an issue where some fields required account settings in Setup. All required ASX fields can now be sent from a FIX connection without corresponding Setup fields.