We are pleased to announce the availability of these hotfixes that contain fixes for various reported issues on SDL TMS 12.1:
CRQ-11564
Symptoms:
When re-assigning a task for a language, all users assigned to other tasks for that language will get a notification.
Explanation:
SDL TMS incorrectly assumed that other tasks in the same language had also been re-assigned.
Resolution:
Notifications are now only sent for the tasks…
Symptoms:
Using the SDL TMS API through CTA, multiple L10NComplete messages for the same task causes a silent failure and doesn't move the job on in the workflow.
Explanation:
The duplicate messages were not handled correctly and threw a silent error which terminated processing of all subsequent messages.
Resolution:
Duplicate messages are now ignored.
SDL-hosted customers should contact SDL Support to arrange for this…
Symptoms:
When returning a fuzzy match segment from a translation memory that contains more tags than the original segment, the extra formatting tags are not removed from the translation.
Explanation:
The hotfix for CRQ-11178 introduced this issue.
Resolution:
Extra tags in the translation are now removed when returning a fuzzy match from the translation memory.
SDL-hosted customers should contact SDL Support to arrange…
Symptoms:
During the ApplyTM stage, some files are failing to recovery because of a database PRIMARY KEY error.
Explanation:
This happened as part of a "race condition" which caused the file to have two simultaneous workflows in the database.
Resolution:
When a file has multiple workflows in the database, the stored procedure has been amended to use only the live workflow.
SDL-hosted customers should contact SDL…
Symptoms:
Files that fail in the pre-processing stage of SDL TMS can report a zero word count even though the file is successfully re-processed.
Explanation:
The failed processing was not being accurately detected and resubmitting the file did not update the word count.
Resolution:
Failures in the pre-processing stage are now identified correctly and a second attempt to process the file, if successful, will correctly update…
We are pleased to announce the general availability of SDL TMS 12.2.
For more information, see the SDL Community post here.
Don't forget to subscribe to this new area to receive update notifications.
Symptoms:
Downloading or uploading SDL Trados Studio packages in SDL TMS 12.1 impacted the performance of the system and the website appeared to become unresponsive.
Explanation:
Package download and upload was putting an extra message on the SDL TMS queue which was taking a long time to process. This extra message is not required in the majority of cases.
Resolution:
SDL TMS now checks whether the extra message is necessary…
Symptoms:
If a job fails to create due to a database deadlock, the database retry strategy attempts to create the job a second time but this results in a job error as the attributes for the job already exist.
Explanation:
As above, this happens when the database procedure that creates the job fails to execute due to a deadlock and, when the procedure is executed a second time, the attributes for the job already exist which…
Symptoms:
After the installation of the hotfix for CRQ-10419, some users were still being assigned incorrectly to the Translation step.
Explanation:
This issue occurs when the job is authorized from the Authorization page and the same issue exists for other vendor-assigned workflow steps. The previous hotfix did not cover all cases of assignment.
Resolution:
The provided hotfix remedies the issue and the workflow steps are…
Symptoms:
When editing a segment in the browser-based editor in SDL TMS, these two characters, "<" and ">" , are not encoded correctly when the translation is saved. Instead of being stored using their encoded versions (< and >), they were being stored as literal characters. These characters would then be removed during the rebuild translation stage.
Explanation:
The browser-based editor…
Symptoms:
When batch submitting multiple tasks from the user's Inbox, some tasks were getting stuck at the "Moving to Next" step of the workflow.
Explanation:
This issue occurred because the system was timing out when trying to process all the tasks in the batch. The root cause was discovered to be an inefficient database stored procedure which was taking too long to execute.
Resolution:
The provided hotfix…
Symptoms:
When the Translation step is assigned to a vendor group and the job is authorized, the step is assigned randomly to a member of the group instead of being assigned to the group itself.
Explanation:
This issue occurs when the job is authorized from the Authorization page and the same issue exists for other vendor-assigned workflow steps.
Resolution:
The provided hotfix remedies the issue and the workflow steps are…
Symptoms:
Running terminology analysis as a background task in SDL TMS could take a long time and cause the connection to SDL MultiTerm to time out.
Explanation:
The stored procedure used to identify the segments for analysis was inefficient and could take up to ten minutes to execute.
Resolution:
The stored procedure has been re-written to be much quicker. In addition, the connection to SDL MultiTerm is now more robust…
Symptoms:
Installing the security update for Microsoft Windows Server 2012 R2 (KB4338419, KB4338420) can prevent users from being able to access the SDL TMS user interface. Despite being able to log in normally, subsequent pages result in a server-side error. On some servers, the incompatibility is seen when starting the web site in which case the entire UI is inaccessible.
Explanation:
The security update is a remediation…
We are pleased to announce the general availability of SDL TMS 12.1. See below for some highlights of this minor version release.
GDPR
To make it easier for our customers to adhere to GDPR, SDL TMS 12.1 includes two improvements which ensure that data is removed permanently when it is no longer needed. These two features are:
Both settings are configurable…
Translate
