Documentation Center

Fixed Issues

The following list details the issues that were resolved in the Trados GroupShare 2020 SR1 CU10 release.

General

  • Trados GroupShare no longer allows creating projects with identical names within the same folder. (LTGS-10047)
  • When an incomplete date format is entered in the Create New Language Processing Rule window, Trados GroupShare no longer mistakenly indicates an issue with the name format. Instead, it displays a more appropriate error message about incorrect data within the Language Processing Rule.
  • Trados GroupShare now correctly displays phase names in selected languages from the Project details view. (LTGS-11854)
  • Fixed an issue where Trados GroupShare would throw an 'Failed to save project template. An internal server error occurred. There is already a project template with the same name in the server's error when editing Project templates with duplicate names in different organizations. (LTGS-11834)
  • Trados GroupShare would inaccurately sort task reports. The issue is now fixed. (LTGS-11851)
  • The Project templates grid could not be correctly sorted by name if the name contained accented characters, spaces, numbers, or symbols in ascending and descending order. The issue is now fixed. (LTGS-11119)
  • Adding a language pair to an existing GroupShare project from Studio failed to include the project files for the new languages. The issue is now fixed. (LTGS-11782)
  • Trados GroupShare would ignore specific language pair settings from the project template for any files added using the Update Project Files option. The issue is now fixed. (LTGS-11106)
  • Adding native files to a GroupShare project using Studio, the Upload and check in files step failed to complete. The issue is now fixed. (LTGS-11825)
  • The TM Service Agent would incorrectly listen on port 5000. The issue has been fixed. (CRQ-35496)
  • GroupShare would fail to create projects that included server-based translation memories from organizations named with an ampersand or plus sign. The issue is now fixed. (CRQ-35205)
  • GroupShare now handles correctly straight apostrophes (') in the search field under Resources > Translation Memories. (CRQ-34473)
  • The Custom Field page of the New Project wizard would not automatically display the default custom fields coming from the project template. This issue has been fixed. (LTGS-6873)
  • Fixed an issue that sometimes occurred when creating new server-based translation memory on servers hosting an extensive number of existing TMs. (CRQ-34073)
  • In certain scenarios, the Update Translation Memories API would insert duplicate translation unit context entries in the updated translation memories. This issue is now fixed. (CRQ-34111)
  • When performing an Advanced Import or Quick Import to update translation memories with newly aligned content, the date of import was recorded incorrectly as either 1900 or 1989 instead of the actual import date. This issue occurred when the GroupShare server was set to a UTC-X time zone and is now fixed. (CRQ-28962)
  • Uploading a project template would sometimes fail due to a case-sensitive source language code check. The issue is now fixed. (CRQ-19085)
  • Creating a project with multiple target languages and a termbase would fail when the termbase language was not mapped to one of the target languages in the project. The issue is now fixed. (CRQ-13995)
  • Fixed an issue within the WebHooks Service that occurred after finalizing a project file, causing the lack of Finalize operation event. (LTGS-9513)
  • Fixed an issue in WebHook notifications where the user was displayed as 'System' instead of their name when performing a phase change. (CRQ-33739)
  • When using GroupShare translation memories in Trados Studio, segments generated by Machine Translation providers were mistakenly labeled as 100% matches instead of Automatic Translation (AT) matches. This issue is now fixed. (CRQ-35092)
  • Improved performance when running the Analyze or Pre-translate tasks from Trados Studio with Trados GroupShare translation memories. (CRQ-33309)
  • Users with Delete TU permission but lacking the Batch delete TU one could still batch delete translation units in GroupShare translation memories. This issue has been fixed. (CRQ-34781)
  • In specific scenarios, exporting translation memories would fail and the corresponding tasks on the Background tasks page would not be accessible for more information about the issue. (LCC-14528)
  • We optimized SQL queries responsible for retrieving file details and improved the logic that generates emails for Overdue files and Files Due Soon. (LTGS-2552)

GroupShare API

  • Fixed an issue that prevented sending API requests via GroupShare Swagger's "Try it out!" button when a custom port was configured for the website during installation. (LTGS-12304)
  • Fixed an issue where using the 'PUT /updateWithProcessedFiles' endpoint would create duplicate file versions with different files. (LTGS-11902)
  • The Logging service failed to start when installing GroupShare MultiTerm Server only without Erlang/OTP and RabbitMQ. The issue is now fixed. (CRQ-35342)
  • Creating a project via the [POST] api/projectserver/v2/projects endpoint experienced a long response time when the template included multiple termbases. We've substantially improved the endpoint's response time by eliminating unnecessary details. (CRQ-32816)

MultiTerm Online

  • Opening termbases created with specific definition files failed with a 'NullPointerException' error message. The issue is now fixed. (LTGS-11775)
  • Changing the language direction impacted only the default termbase, resulting in an error when manually selecting terms from the second termbase. The issue is now fixed. (CRQ-16700)
  • The option Multimedia file field type was not visible in the drop-down menu when creating a termbase in MultiTerm Online. The issue is now fixed. (CRQ-26159)