Issues resolved in Trados Studio 2019 SR1

The current list details the issues that were resolved in Trados Studio 2019 SR1.

Main application issues

Context matches saved into a TM in a version lower than Trados Studio 2017 SR1 do not become 100% matches anymore
The changes required for introducing upLIFT for Japanese and Chinese TMs in Trados Studio 2017 SR1 affected the way Trados Studio handles these TMs. Context matches from TMs used in a previous Trados Studio version used to become 100% matches in Trados Studio 2017 SR1 and later.
This is not happening anymore, as Trados Studio 2019 SR1 preserves context matches added in a TM before updating to Trados Studio 2017 SR1.

Integration issues

Changes made to project settings by users who have the "Edit Project" permission no longer resets the target language for different users
Users who have the "Edit Project" permission in SDL Trados GroupShare (Project Managers, typically) could make changes to a project's settings, thus resetting the target language for all translators working on a particular target language translation. This is now fixed, and translators working on a particular target language can continue working on their designated source language-target language combination, even when changes are made to the project settings during the project lifecycle.
Performance is restored when working with a large number of active server-based TMs from SDL Trados GroupShare 2017
When opening a document or accessing the Translation Memory and Automated Translation settings page, the TMs would display poor performance in the case of a very large number of active TMs from SDL Trados GroupShare 2017. This is now fixed, and the number of active server-based TMs is no longer a blocker when accessing project settings.
TM matches from Machine Translation (MT) providers are correctly retrieved
When the list of active TMs contained a TM from an MT provider, but the TM would not be first in the TM list, Trados Studio would not retrieve matches from it. Users would have to revert the order of active TMs in the list and place the MT one at the top of the list, for matches to be generated during translation. This is now fixed, and the order in which TMs are listed no longer affects match retrieval irrespective of the placement and nature of the TMs provided.