SDL TMS 12.1 - Product Updates

SDL TMS 12.1 | New Hotfixes

David Pooley — Wed, 20 Mar 2019 09:23:00 GMT

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 that have been re-assigned.

CRQ-12639
Symptoms:
Overlapping terms are not correctly highlighted in the online editor.

Explanation:
SDL TMS was attempting to highlight all terms in the source text but overlapping terms were not being handled correctly.

Resolution:
Terms are now highlighted and hyperlinked correctly in the source text in the online editor.

CRQ-13789
Symptoms:
For SDLXLIFF file types, the project translation memory did not record any times after 12:00.

Explanation:
When writing the creation and modified dates for a segment in the translation memory, the application code was only writing the hours as 00-11 instead of 00-23.

Resolution:
Dates and times in the project translation memory are now recorded correctly.

SDL-hosted customers should contact SDL Support to arrange for these hotfixes to be deployed.

Customers who host SDL TMS themselves should download the installers from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-11562 | Duplicate L10NComplete messages causes a silent failure

David Pooley — Mon, 04 Feb 2019 15:48:00 GMT

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 hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS12.1 Hotfix for CRQ-11562.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-12016 | Formatting tags generated in SDL Trados Studio are not converted for fuzzy matched segments

David Pooley — Tue, 08 Jan 2019 13:49:00 GMT

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 for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS12.1 Hotfix for CRQ-12016.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-9830 | Tasks going to recovery during ApplyTM due to PRIMARY KEY error

David Pooley — Thu, 13 Dec 2018 11:51:00 GMT

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 Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS12.1 Hotfix for CRQ-9830.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-6444 | Pre-processing stage sometimes generates a zero word count

David Pooley — Tue, 11 Dec 2018 10:40:00 GMT

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 the word count of the file.

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 SDLTMS12.0 Hotfix for CRQ-6444.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.2 - General Availability

David Pooley — Tue, 20 Nov 2018 17:18:00 GMT

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.

SDL TMS 12.1 | CRQ-12047 | Slow performance when downloading and uploading packages

David Pooley — Fri, 02 Nov 2018 12:03:00 GMT

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 and, if not, the message is not posted to the queue and the package uploads and downloads can continue working efficiently.

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 SDLTMS12.0 Hotfix for CRQ-12047.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-4829 | Job error when executing database retry strategy

David Pooley — Fri, 12 Oct 2018 14:29:00 GMT

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 results in an error.

Resolution:
The provided hotfix remedies the issue by ensuring that the job attributes are not created when the job creation procedure executes a second time.

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 SDLTMS12.0 Hotfix for CRQ-4829.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-11540 | Vendor user incorrectly assigned to the Translation step

David Pooley — Fri, 12 Oct 2018 13:59:00 GMT

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 assigned to the correct group or user.

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 SDLTMS12.0 Hotfix for CRQ-11540.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-11178 | Characters "<" and ">" not encoded correctly after using the browser-based editor

David Pooley — Thu, 04 Oct 2018 12:48:00 GMT

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 uses the "<" and ">" characters to represent tags in the translation segment. As such, these characters were not encoded when storing the translation, regardless of whether they were being used to represent a tag or not.

Resolution:
Tags in the translation that are not part of the source segment are now encoded correctly when the segment is saved in SDL TMS.

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 SDLTMS12.1 Hotfix for CRQ-11178.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-10184 | Tasks stuck at "Moving to Next" status after batch submitting multiple tasks

David Pooley — Fri, 28 Sep 2018 14:29:00 GMT

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 remedies the issue with a new version of the stored procedure which executes much quicker.

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 SDLTMS12.1 Hotfix for CRQ-10184.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-10419 | When Translation is assigned to a vendor group, the step is assigned randomly to a member of the group

David Pooley — Fri, 17 Aug 2018 09:50:00 GMT

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 assigned to the vendor group rather than an individual user.

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 SDLTMS12.1 Hotfix for CRQ-10419.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-10512 | Poor performance of terminology analysis

David Pooley — Thu, 09 Aug 2018 13:33:00 GMT

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 and will not drop if the query takes a long time to execute.

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 SDLTMS12.1 Hotfix for CRQ-10512.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | CRQ-10641 | Installing Microsoft security updates may prevent SDL TMS from working

David Pooley — Thu, 09 Aug 2018 13:31:00 GMT

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 for an "elevation of privilege" vulnerability in the .NET Framework which could allow an attacker to elevate their user rights level. To exploit the vulnerability, an attacker would first have to access the local computer, and then run a malicious program. This update addresses the vulnerability by correcting how .NET Framework enables COM objects. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8202. Changing the way in which COM objects are invoked has a direct impact on the SDL TMS user interface.

Resolution:
The provided hotfix changes the way in which the SDL TMS application pools are configured in IIS which, in turn, allows SDL TMS to continue working on all servers that have the security update applied.

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 SDLTMS12.1 Hotfix for CRQ-10641.exe from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1/Hotfix/

SDL TMS 12.1 | SDL TMS 12.1 Release Announcement (July 2018)

David Pooley — Thu, 19 Jul 2018 10:45:00 GMT

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:

Automatic deletion of archived files
Automatic deletion of log files

Both settings are configurable in the system settings page where you can specify the period for retention of this data. When the files are no longer required, they will be permanently deleted from the filing system.

Support for Passolo 2018
SDL Passolo 2018 was released earlier this year and introduced a new format for the bundles that are exported. This new format of bundle was not compatible with SDL TMS 12.0 or any other earlier version. SDL TMS 12.1 introduces support for this new bundle format so that translation of SDL Passolo 2018 bundles can be handled through SDL TMS.

Custom Interface types
The extensibility of SDL TMS 12.1 has been improved through the introduction of custom workflow step interface types. The interface type governs the behaviour of the workflow step and facilitate the following scenarios:

Linking an interface type to a custom page in SDL TMS
Determining the types of emails to be sent at each workflow stage
Avoiding having to refer to explicit workflow step unique identifiers
Accessing SDL Online Editor from stages other than the default translation and review stages

Custom requirements can now be implemented completely separately to the core SDL TMS product and dependencies are alleviated making it easier to future-proof these customisations. The new custom interface types also allow extensibility for other key focus areas such as in-context review.

For more information on custom interface types, contact your SDL representative who will put you in touch with our Professional Services team.

Cloud Terminology
Although the feature will be switched off in the initial release, SDL TMS 12.1 allows for configuration of cloud terminology sequences for those organisations that are connected to SDL Language Cloud through an API Key. These sequences can then be referenced in a configuration and will be available to jobs created using the relevant configurations. Opening files in SDL Online Editor that belong to one of these jobs will allow the translator and reviewer to reference the correct terminology in real time. Later in the year, SDL Trados Studio will also include connectivity to the cloud terminology for packages downloaded from SDL TMS 12.1. Stay up-to-date with SDL TMS news by subscribing to the community group to hear more about cloud terminology as it continues to be rolled out across other products this year.

For full information on these new features please refer to the detailed Release Notes available on https://docs.sdl.com/SDLTMS12.1/ReleaseNotes

Customers who host SDL TMS should download the installer for Sdl_Tms_12.1.25057.0.iso from the following FTP site: ftp://ftp-emea.sdlproducts.com/SDL TMS/12.1

Users are advised to refresh their browser cache after every SDL TMS upgrade.