Symptoms:
SDL TMS would sometimes become unresponsive due to high CPU usage by IIS when running the SDL TMS website.
Explanation:
This issue was found to be a result of multiple requests accessing the same resource concurrently, causing conflicts which could not be resolved. The only way to solve them was resetting IIS.
Resolution:
SDL TMS now manages requests to access the same resource to prevent conflicts and allows IIS…
Symptoms:
Some users were unable to authorize tasks from the inbox even though they had sufficient permissions.
Explanation:
This issue was introduced by a previous hotfix for CRQ-6359 which related to authorizing tasks from the user's inbox. The permissions for authorization were taken from the organization where the user was created, rather than from the organization where the job was created.
Resolution:
SDL TMS will…
We are pleased to announce the General Availability of SDL TMS 11.4.
This is the next major update on the SDL TMS 11.x branch and delivers some important updates, new features, and defect fixes.
For more information, see SDL Community post here.
Don't forget to subscribe to this new area to receive updates notifications!
Symptoms:
Vendors were unable to download SDL Trados Studio packages.
Explanation:
This issue was introduced by a previous hotfix for CRQ-6359 which related to authorizing tasks from the user's inbox. The capability to download packages was affected by this fix.
Resolution:
The ability to download SDL Trados Studio packages has been restored for vendor users.
SDL-hosted customers should contact SDL Support to arrange…
Symptoms:
A vendor user was not able to submit jobs or tasks from the PJM Authorization step even if the user had the Authorize Job permission granted.
Explanation:
The issue occurred because the Submit action for Vendor Users, currently dependent on the Authorize Job permission, was not covered by the implementation from a previous fix (TMS-11738: A job is authorized by submitting). The Vendor PJM User was able to submit…
Symptoms:
When performing a concordance search in the SDL TMS search pane, the matching words were not being highlighted and, in some cases, the first letter was removed from the result.
Explanation:
The issue was related to a previous hotfix that addressed TM looking performance issues. As part of that optimization, the concordance matches were no longer highlighted.
Resolution:
The issue was fixed be re-instating the highlighting…
Symptoms:
When processing MIF files, external cross-reference text was being extracted for translation.
Explanation:
The issue was caused by new functionality introduced in the MIF filter to extract cross-reference text. However, this new functionality was not disabled by default.
Resolution:
This hotfix deploys a newer version of the MIF filter which has the new functionality disabled by default. Users can instruct the filter…
Symptoms:
When processing HTML embedded in XML files, spaces between inline tags were being removed by the filter.
Explanation:
This issue was caused by a breaking change in the version of the HTML filter that was being used by SDL TMS 11.3.1.
Resolution:
The issue had already been found and rectified in the HTML filter. This hotfix deploys a newer version of the HTML filter which is responsible for processing the embedded…
Symptoms:
When creating a Job via CTA using a Language Pair no longer supported by the Configuration that CTA uses, the Job would contain Tasks for all the Language Pairs that the Configuration supports.
Explanation:
When the Job Request was sent from CTA, there was no check in place to validate the availability of the selected Language Pair(s) in the Configuration used by CTA.
Resolution:
When a Job Request is sent from…
Symptoms:
For some XML files with embedded HTML, SDL TMS 11.3.1 failed to extract the content for translation and sent the tasks to the Recovery workflow step.
Explanation:
The issue was caused by a breaking change that was introduced in the HTML filter in SDL TMS 11.3.1.
Resolution:
The issue had already been found and rectified in the HTML filter. This hotfix deploys a newer version of the HTML filter which is responsible…
Symptoms:
Pages in SDL TMS that use the returnUrl parameter were vulnerable to cross-site scripting attacks.
Explanation:
The return URL was not being validated which allowed for injection of JavaScript code into the application resulting in a vulnerability.
Resolution:
The issue was fixed by validating the returnURL parameter to ensure that JavaScript code is not injected into the application.
SDL-hosted customers should…
Symptoms:
When downloading Studio Packages for multiple language pairs of the same job, the packages would contain the files from the target language folder and TM folder of the previously created packages.
Explanation:
When downloading multiple Studio Packages for a single job at once, the source folder where the packages are created would not remove the information about the previously created Studio Package, before creating…
Symptoms:
Users without the permission to authorize jobs are able to authorize a job by submitting the job from their SDL TMS Inbox.
Explanation:
The permission to authorize jobs was not being checked when jobs are submitted from the user's Inbox.
Resolution:
The issue was fixed by ensuring that the appropriate permissions are checked when a user submits a job from their Inbox.
SDL-hosted customers should contact SDL…
Symptoms:
On the Edit Job page in SDL TMS, the Duration appears as an editable field but for Vendor users, changes made to the field are not saved.
Explanation:
Vendors have areas of specific functionality in SDL TMS and permissions are controlled carefully. In this case, SDL TMS was incorrectly preventing Vendor users from editing the Duration field.
Resolution:
The issue was fixed by ensuring that editable fields on the…
This article is obsolete and has been superseded by the hotfix for CRQ-6278 and CRQ-6343. Please see the new article here.
Symptoms:
After installing the hotfix for CRQ-4820, CRQ-4791 and CRQ-4913, the SDL TMS TM Maintenance tool was not returning any matches when using the "Text Search" functionality.
Explanation:
The previous hotfix included an optimization to respect the number of requested matches from the…
This article is obsolete and has been superseded by the hotfix for CRQ-5468. Please see the new article here.
Symptoms:
Any of the following could have a negative impact on the performance of the Apply TM workflow step in SDL TMS:
Symptoms:
When editing the encodings on a configuration, selecting a value from the first drop down list for a file type changes the encoding of all languages to Default instead of changing everything to the selected value.
Explanation:
As part of a previous enhancement to improve the performance of the edit configuration page, this problem was introduced for the encodings.
Resolution:
The issue was fixed by ensuring that…
We are pleased to announce the General Availability of SDL TMS 11.3.1. This is the first update on the SDL TMS 11.3 branch.
We are delivering Integration updates for SDL TMS with this release providing support for the upcoming release of SDL Knowledge Center. SDL TMS 11.3.1 provides a new REST API endpoint for system integrators that allows the current workflow step for a task to be changed.
In addition, we are releasing…
Symptoms:
Some TM matches are being returned as 100% matches even though there are tagging differences between the source segment and the TM segment.
Explanation:
This happened because of an incorrect override of the tag mismatch penalty, recently introduced. Specifically, the issue was caused by the fact that the SDL TM was overriding the TM penalties. This impacted the TM Leverage and ultimately, both the cost implications…
Symptoms:
All jobs that use the sdlftsettings custom file type for processing the ‘DOCX 2007-2016' file types go into recovery.
Explanation:
The issue was caused by a breaking change that was introduced in the ‘Microsoft™ Word 2007-2016’ filter, specifically, a namespace was modified. This change would then trigger a serialization exception when working with this sdlftsettings file.
Reso…
Symptoms:
While adding or editing a configuration, when selecting more than one sdlxliff-based XML file type with the same extension, the page validation mechanism throws the following error, even if the document type is different in each XML file type:
"You cannot select two or more file types with the same file extension and document type".
Explanation:
Before TMS 11.3, the validation for sdlxliff-based…
Symptoms:
When using a configuration with the Studio-style Analysis Statistics option enabled, the following issues appeared:
1/ the AutoMatch Penalty set up on the System > Settings page would not be applied, leading to leveraging issues
2/ the Project TM provided with the tasks would contain a target translation with AutoMatch already applied, instead of providing the translation “as it is” in the main TMS translation…
We are pleased to announce the general availability of SDL TMS 11.3. This is the next major update on the SDL TMS 11.x branch and delivers some important updates, new features and defect fixes. See below for some highlights.
SDL Trados Studio Commute
SDL TMS 11.3 has a new plug-in available for both SDL Trados Studio 2017 and SDL Trados Studio 2015. The plug-in allows translators and reviewers to access their SDL TMS…
Translate
