What's New in Trados GroupShare 2020 SR2: CU14 and CU15 Highlights
We've been busy. Over the past two cumulative updates for Trados GroupShare 2020 SR2, we've shipped a meaningful set of improvements — from a refreshed interface and faster project creation to stronger API capabilities and under-the-hood reliability fixes. Here's a closer look at everything that landed in CU14 and CU15.
CU14 — A Fresh Look, Faster Workflows, and a Richer API
Rebranding Update
The GroupShare interface has been refreshed to align with RWS's latest brand identity. You'll notice updated color schemes, a new logo, and polished visual enhancements throughout the UI. It's the same GroupShare you know — just looking its best.
Optimized Project Creation for Large-Scale Projects
If you regularly work with projects containing a very large number of files, CU14 brings a welcome performance improvement. We significantly reduced disk usage for the [rpt].[PredefinedTasks] table in these scenarios, resulting in faster project loading times and lower memory consumption in the Tasks report. Large projects just got a lot smoother to manage.
Real-Time TU Count on the Licensing Page
Previously, the translation unit (TU) count on the Licensing page could lag behind actual usage. That's now fixed. Whether you're importing translation memories, translating segments, or deleting TUs, the TUs in use field updates in real time — so you always have an accurate picture of your licensing consumption.
New Language Variant Support
CU14 adds support for two new language variants: Haitian Creole (Haiti) and Russian (Israel). We're continuing to expand GroupShare's language coverage to meet the needs of global teams and projects.
Richer Webhook Responses
Webhook integrations just got more informative. The response to the Finalize Operation event now includes the language code of the project file and the UTC timestamp of the event. The response to the Check In event now includes both the name and the ID of the project phase the file was in at the time of check-in. More context in your webhooks means smarter automation.
MultiTerm Server REST API v2
Third-party developers will be pleased to hear that CU14 introduces an enhanced version (v2) of the REST API for MultiTerm Server, accessible at /api/multiterm/v2. This new version lays the groundwork for more capable integrations with server termbases going forward, notably with Trados Studio 2026 Release which relies on this API.
️ Fixes and Enhancements
- TM field value retention: A new option lets you keep translation memory field values when linking or unlinking custom field templates. When linking, only values compatible with the template can be retained. (CRQ-41818)
- Security enhancement: An improvement was implemented to help protect user data. (CRQ-41914)
- TM deadlock fix: Resolved an issue where finalizing two projects sharing the same GroupShare TM simultaneously could result in a deadlock error. (CRQ-41954)
CU15 — Performance, Stability, and MultiTerm API Enhancements
MultiTerm Server REST API: Faster Concept Retrieval
Building on the v2 API foundation introduced in CU14, CU15 brings two notable improvements for developers working with server termbases:
- Improved performance when retrieving concepts (
GET /api/multiterm/v2/termbases/{termbaseGuid}/conceptxmls/{conceptId}) - A new batch endpoint that retrieves a list of concepts in a single request (
POST /api/multiterm/v2/termbases/{termbaseGuid}/conceptxmls/batch), reducing round trips and improving efficiency for integrations that need to pull multiple concepts at once
Both updates are key for the upcoming Trados Studio 2026 Release. For optimum performance, we strongly recommend to deploy GroupShare CU15 before updating any client machines to Trados Studio 2026 Release.
More Robust Project Detach Operations
Project detaches are now handled through a more reliable batch processing approach, replacing the previous timer-based synchronization mechanism. Detach operations are now processed in batches of three, with regular progress checks built in. Crucially, if a single detach operation encounters a problem, it no longer impacts the Execution Service — keeping the rest of your environment stable.
Server TM Availability Fixed
A race condition in the shared service infrastructure could previously cause server TMs to become unavailable due to TMService Host issues. This has been resolved in CU15, restoring consistent access to all server TMs. (CRQ-41890)
Deeper Tag Nesting for Translation Model Builds
For teams working with translation units (TUs) that contain deeply nested tags, CU15 significantly raises the ceiling. The maximum supported tag nesting depth has been increased from 27 to 59 levels, resolving cases where model builds would previously fail with an unhelpful Unable to build model error. Datasets that previously hit this limit can now complete their Translation Model builds successfully. (CRQ-37351)
Stay Up to Date
Both CU14 and CU15 are available now. As always, we recommend reviewing the full release notes before updating:
Changes introduced in Trados GroupShare 2020 SR2 CU14
Changes introduced in Trados GroupShare 2020 SR2 CU15
Have questions or feedback? Drop a comment below. We'd love to hear how these updates are working for you.
Translate