Symptoms: 
In some cases, for segments containing locked elements, those elements would be missing when the translated strings were returned from a Machine Translation provider.

Explanation: 
A generic issue was identified. Although the source segment was sent to the Machine Translation provider, when merging the translated strings back, SDL TMS was using the old target segments rather than the source segments.
This was incorrect because the target segments are not necessarily the same as the source segments before the strings are sent to the Machine Translation provider; for example, a typical workflow may have the Apply PerfectMatch and Apply TM steps before the EMT steps.

Resolution: 
SDL TMS now maps the segments returned from the Machine Translation provider with the source segments, therefore preserving the elements present in the new target segments.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0.3 Hotfix for TMS-10698.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Pre-requisites on top of SDL TMS 11.0.3 (in this order):

- Hotfix for TMS-10122
- Hotfix for TMS-10540
- Hotfix for TMS-7295
- Hotfix for TMS-10643

Notes: 
This issue was detected in a previous version of SDL TMS.
Per SDL Engineering policy, the Engineering team provides hotfixes for the latest release of SDL TMS to encourage our customers to run the latest version of SDL TMS to benefit from the latest features and fixes.