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 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:
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.
This minor version release delivers enhanced features for GDPR compliance as well as opening up the possibility for tighter integrations with custom interface types.
For more information, see the SDL Community post here.
Don't forget to subscribe to this new area to receive update notifications.
Symptoms:
Switching the workflow for a task in SDL TMS could cause a "duplicate key" database error which would send the task to recovery.
Explanation:
This occurred due to a race condition on the database procedure responsible for switching the task workflow.
Resolution:
The procedure for switching the task workflow has been amended to ensure that it does not encounter a race condition during execution.
SDL-hosted…
Symptoms:
SDL Trados Studio packages downloaded from SDL TMS would sometimes have the wrong word counts in the fuzzy match bands when the package was opened in SDL Trados Studio.
Explanation:
This error occurred when the SDL TMS database query returned the fuzzy match band word counts in the wrong order.
Resolution:
The procedure for retrieving fuzzy band word counts has been amended to ensure that the counts are always returned…
Symptoms:
After upgrading to SDL TMS 12.0, it is no longer possible to edit a user without being forced to change the username to a valid email address.
Explanation:
This feature was implemented by design to help users migrate to the new SDL ID single sign-on functionality available in SDL TMS 12.0. However, in response to a number of customers raising issues with this feature, we have released this hotfix.
Resolution:
…Symptoms:
After upgrading to SDL TMS 12.0, enabling SDL ID and configuring the integration, some implementations were failing to access the SDL TMS login screen.
Explanation:
This issue occurred when the URL for the SDL ID server contained an extra forward slash which wasn't being handled correctly when constructing the correct URL for the login page.
Resolution:
URLs are now constructed correctly regardless of the presence…
Symptoms:
When attempting to edit a configuration that is used for multiple jobs, SDL TMS was taking a long time to open the page and, in some circumstances, the page would time out.
Explanation:
The database query used when opening the page for editing a Configuration was excessively scanning a database view, therefore causing the slow performance of the query.
Resolution:
The associated query has been rewritten to ensure…
Symptoms:
When attempting to link an unverified SDL ID to an existing SDL TMS user account, SDL TMS did not provide the capability to send the verification link to the user.
Explanation:
This functionality was not considered initially for the release of SDL TMS 12.0 on the assumption that when the TMS account were linked, its corresponding SDL ID had been verified already.
Resolution:
Users attempting to link their SDL TMS…
Symptoms:
When editing an attribute, SDL TMS would sometimes stop responding and force a reboot of IIS in order to bring the website back online.
Explanation:
This occurred because editing an attribute also checked where that attribute might be in use. Attributes that are used extensively were returning a very large data set for the "in use" information, which was then causing the server to consume too much memory.…
Symptoms:
Terminology entries containing ampersand characters were not being shown in the translation editor in SDL TMS even thought the exact term was present in the text for translation.
Explanation:
This issue was caused by a mismatch in how the ampersand character was being stored within the translation segment and in the terminology cache.
Resolution:
Terms containing ampersand characters are now stored consistently…
We are pleased to announce the general availability of SDL TMS 12.0. This major version release delivers support for single sign-on with SDL ID as well as the first implementation of SDL Online Editor for SDL TMS. See below for some highlights.
Single Sign-on with SDL ID
SDL is introducing a new single identity for accessing SDL’s products and services. This new capability is called SDL ID and allows users to manage…
Translate
