Symptoms: 
Tasks prepared with the Custom XML (Embedded Content) Pre-Processing tool have a partial Project TM or no Project TM created, despite the fact that TM matches are applied to the SDL XLIFF file.

Explanation: 
When using the Custom XML (Embedded Content), the .sdlxliff file generated at Pre-Processing contains a specific file structure. This structure flags which segments are generated using the base processor and which are generated using the embedded processor. In the .sdlxliff file, the structure reflects blocks of segments, therefore the name "merged .sdlxliff file".

When creating the Project TM, SDL TMS writes the TM matches for each block of segments into the .tmx file. The problem was happening when going to the next block of segments within the merged .sdlxliff, as SDL TMS was then overwriting the output from the previous block of segments. As a result, only matches from the last block would remain in the Project TM, sometimes resulting in an empty TM if no matches were found in the main TM. 

Resolution: 
SDL TMS no longer overwrites matches, but incrementally adds matches to the existing .tmx file.

This hotfix has a dependency on two previously released hotfixes, which must be installed in the following order, prior to this new hotfix:

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 Hotfix for TMS-6151.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/Hotfix.

Note: 
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.