Phrase TMS Releases 2025

As a deprecation process, customers not actively using the earlier version of APC will no longer have access to that version (button removed).

An APC can now be cloned from the Automated project creation list page.

When opening a Price list from the Settings, Price list page, the URL has /web instead of the /tms URL triggering a 404 error. This has been fixed.

The Custom fields page is visible to PM users in Settings even if not accessible. This has been fixed.

When the DOCTYPE in the xml does not contain any entity declaration .XML files were failing on import. This has been fixed.

An invalid regexp expression error message was being displayed in the UI. This has been fixed.

It was not possible to disable or edit the MT engine in projects in the staging environment. This has been fixed.

It was not possible to remove providers from a batch of jobs at once with the edit job wizard. This has been fixed.

Target columns were not appearing in File Import Settings. This has been fixed.

Custom field data was retained when switching settings sections. However, if returning to the Project Details section before project creation, the data was lost. This has been fixed.

Segmentation rules were not displayed in the job creation wizard. This has been fixed.

It was not possible to upload a multilingual .CSV file via the job creation wizard.

Removing target languages during project creation for multilingual .XLSX, did not remove them from File Import Settings and created a INVALID_REQUEST: Different number of source and target columns error. This has been fixed.

PM users were not able to open project templates if not given modify rights. This has been fixed.

Whenever a line in an .ASCIIDOC ended with a + and the next line started with endif::[], the + was removed from the completed file. This has been fixed.

A new table called JOB_PART_DATE_DUE_CHANGE_V2 has been added to Phrase Data. The table displays the history of due date changes for each individual job part, indicating when the changes were made and who made them.

As of June 11, 2025, legacy SSO logins will no longer be supported in Phrase. Users will no longer be able to access Phrase TMS in web browsers or the CAT Desktop Editor using SSO configurations set up directly in TMS. To continue logging in, organizations must set up Platform SSO or use alternative methods such as email/password or supported social logins (Google, Microsoft, GitHub). This change improves security and enables a unified login experience across the Phrase Platform.

An Access Denied pop-up was appearing when a vendor accessed a project with a shared job or attempted to change a due date. This has been fixed.

Email notifications were not arriving to providers when sent from the new job creation UI or when using a project template in which they are defined. This has been fixed.

Pop-up text was being displayed in plain text affecting the appearance of links and apostrophes. This has been fixed.

File properties from .DOCX files were occasionally imported to the job, but not exported back to the file. This has been fixed.

Names of files imported in .ZIP folders did not have the correct set of characters defined in Encoding of zipped file names. This has been fixed.

The Mongolian locale mn-MN was not being displayed consistently across the UI. This has been fixed.

QA custom checks now supports named capturing groups within regular expressions (regexp).

There is a new logic to Resident and Visitor status in Identity Management. Users that are Residents of Customer 1 will have a Visitor status when joining Customer 2'ss organizations.

User provisioning now allows for changing default TMS, Strings and IDM roles for the users provisioned via SCIM or SAML. Default product access can also now be set by user.

Due date calculation functionality has been added to APC v2.

There was no highlighting of found texts in target segments, broken navigation to the segment with the next/previous occurrence and no replacement of found occurrences. This has been fixed.

Service selection drop-down in the the Submitter Portal was misplaced. This has been fixed.

In some cases, it was not possible to create a service. This has been fixed.

The MS Word Import document properties option was disabled in the job creation wizard even if enabled in the project template. This has been fixed.

In some cases, LQA scores were not generated and failing with a 500 Error. This has been fixed.

The {JobInfo} parameter was causing repetitions in emails sent from created templates. This has been fixed.

The email template macro for {recipient.firstName} was not working in custom email templates used in Submitter Portals. This has been fixed.

Adding a new workflow step was triggering the creation of an extra invalid job. This has been fixed.

Update source was not updating the word count in the Jobs view. This has been fixed.

When a job is created, the imported file data and progress was not correctly displayed. This has been fixed.

It was not possible to change machine translation setting within projects. This has been fixed.

Unpinned notifications older than 30 days will be automatically deleted.

Another set of new languages/locales has been added:

To improve system performance, emails are now grouped by project with a maximum of 1,000 emails per group.

Custom fields could not be removed from project templates. This has been fixed.

A 404 error page was displayed after archiving a project. This has been fixed.

The selected MT engine is lost if the language is unchecked during project creation. This has been fixed.

An incorrect warning about missing nontranslatable parts was shown during file import when using regular expressions (regexp). This has been fixed.

Top-up purchasing has been simplified.

Due to potential abuse, new organizations are no longer allowed to send customizable emails via cc/bcc.

A new interface for creating jobs has been introduced.

Custom metadata fields can now be added to jobs upon creation.

Submitter portal: It was not possible to add a file from an online repository. This has been fixed.

Price lists originally configured with currencies other than USD, EUR and GBP were being automatically changed to EUR with no other currencies being available when editing or creating a price list. This has been fixed.

When adding a new language to a price list, after searching for a given language, selecting the specified checkbox didn't work. This has been fixed.

There was a issue with details in the URL affecting how a customer can return to a previous page in TMS. This has been fixed.

Assignment via project template wasn't triggering an email notification or changing job status despite the template’s settings. This has been fixed.

When the language was unchecked, even briefly, in the project creation page, the MT settings for that languages were lost. This has been fixed.

PMs with client restricted access to a submitter portal couldn't access client-related SP anymore if the Authorize user to access widget URL option was enabled. This has been fixed.

It was not possible to set the include tags parameter for the Globalese Cloud Text Translation engine. This has been fixed.

Using a line break was causing translation to fail in Phrase Portal. This has been fixed.

Some MT pre-translations were failing for 3rd party engines. This has been fixed.

Adding a new language to an existing MT glossary was triggering an error. This has been fixed.

Language mapping was incorrect when using the Amazon Translate engine and the pt-pt locale. This has been fixed.

Custom workflow steps and related prices were being removed from the price list after it was saved. This has been fixed.

When a project was created via APC, manually adding a job into the project was triggering an error. This has been fixed.

Some error messages in the UI contained placeholders and not the actual text value. This has been fixed.

If the Forbidden term is checked, QA check was failing. This has been fixed.

If hidden rows are used in an .XLSM file (.XLSX with enabled macros), the file could not be exported after translation. This has been fixed.

Encoding type was not being correctly detected when using iOS Strings files. This has been fixed.

Profiles with multiple engines were incorrectly selecting Widn.AI when it didn't support the target language. This has been fixed.

The TM Threshold dashboard includes additional filters on project metadata:

These filters are designed to help users narrow down information more effectively and capture the data that matters most to support better-informed decisions.

When using an ampersand in the Add naming rules for projects created via automated project creation field of a project template, the & was converted to & in the project name. This has been fixed.

In the Users page, it was not possible to right-click on a user to open a new tab, or to click on a user and have a new tab open automatically. This has been fixed.

In the Project templates page, long text without spaces did not wrap within the column. This has been fixed.

Restored jobs could not be edited. This has been fixed.

The Run Auto LQA option was not visible to Project Manager users. This has been fixed.

When running quality assurance checks on XML files, the XLIFF tags error type was incorrectly displayed. This has been fixed.

The {sender.email} macro was replaced by the current user’s email address when viewing the CC field in email templates. This has been fixed.

An error was displayed when attaching glossaries to MT profiles. This has been fixed.

Default analysis with Include QPS option could not be launched, resulting in an error. This has been fixed.

Spellchecker was not working in Norwegian Bokmal (nb). This has been fixed.

A QPS insights dashboard has been launched to help identify the optimal QPS threshold; striking the right balance between cost savings and quality risks. The dashboard includes filters that help determine the best values for different content categories as technical, legal, and marketing texts may have distinct quality requirements (available from March 19).

Phrase Portal improvements (available from March 19):

Phrase Next GenMT is now able to translate multiple segments per request, allowing to preserve context for higher-quality translations (available from March 19).

New Generative AI machine translation (MT) engines are now available (available from March 19):

Instant QA was highlighting a false error for a custom check and the error was unintelligible when the custom check name is in Japanese. This has been fixed.

When created an APC, only the Create a new project every time option was available. This has been fixed.

After logging in, users were redirected to the default landing page for that role instead of the last accessed project. This has been fixed.

Project template file import settings were not applied to jobs created via APC. This has been fixed.

LQA scorecards were disappearing some time after being created. This has been fixed.

Post-editing analysis on jobs with ZH as the source language has an incorrect wordcount. This has been fixed.

When importing a .YAML file with the HTML subfilter enabled, <mem:tgroup/> tags were inserted in place of the translations. These were also seen in the in-context preview. This has been fixed.

Accessing some organizations with IDM Admin was resulting in a 500 error. This has been fixed.

Bilingual .DOCX was only displaying original scores. This has been fixed and the score/origin column in bilingual .DOCX is now updated after changes are made in the editor.

A new dashboard with a focus on platform usage is released and can be accessed by clicking on the Analytics button on the Subscription overview tab in Organization settings.

The Log in with SSO button has been removed from the legacy login page. Accessing the legacy login page will result in an automatic redirect to the Platform login page after a short delay. Users from organizations without a Platform SSO setup can gain access by:

PM users with Modify global server settings disabled were not able to access the new user list. This has been fixed.

Vendor's adminsitrators were not able to open shared jobs. This has been fixed.

Some filters were not working correctly on the Users page. This has been fixed.

Some checkboxes were not saved when enabled in the TM match context and optimization section of project or project template settings. This has been fixed.

The older project templates view was being displayed after saving a template. This has been fixed.

Not all of a buyer's project metadata was visible to vendors in shared projects. This has been fixed.

The pt-pt language code was not correctly mapped for use in Language Weaver. This has been fixed.

IDM invitations were not able to be accepted by SSO. This has been fixed.

Phrase Next GenMT: some MT glossary terms were being replaced by a tag. This has been fixed.

The import progress bar was not being displayed when importing from some third-party systems. This has been fixed.

The Submitter portal due date displayed during and after submission did not always match. This has been fixed.

It was not possible to open a template in a new tab from the new project templates view. This has been fixed.

Users invited to an organization that requires SSO only for specific domains were not able to accept the invitation without the SSO requirement if they were not from a required domain. This has been fixed.

There is a new {targetLangJavaResourceBundle} macro.

The MTU consumption dashboard within Phrase Language AI, MT usage tab, will now include the split of MT units across the TMS MT origins:

This information applies as of the 1st of December 2024 onwards. This means that any TMS MT units consumed prior to the 1st of December 2024 will be marked as Uncategorized.

The TMS MT origin is added to the MT consumption by project table and as a dashboard filter. The TMS MT origin filter should only be used with the Phrase TMS. Filtering on Portal or Language AI via API, Uncategorized is presented as the TMS MT origin, since the categories are only applicable to the TMS product.

The Submitter Portal page waas broken. This has been fixed.

The Project Status Automation term was not aligned through application pages. This has been fixed.

Buyers could not unassign a shared job if the Vendor creates and assigns analysis to another Vendor. This has been fixed.

Vendors were able to see a buyer’s metadata (client, business unit, cost center). This has been fixed.

When exporting segmentation rules to .XLSX, the file was corrupt. This has been fixed.

As of January 22, Phrase portal supports the .idml, .srt, and .vtt file formats.

An Access denied message was displayed to PM users without the right to Modify global server settings when importing/exporting files via online repositories, even though the files were imported/exported correctly. This has been fixed.

The Created By filter shows PMs Instead of actual submitters in the new Project List view. This has been fixed.

The Download sample file (.xlsx) link on the portal page was incorrect. This has been fixed.

Customers can now give specified external collaborators access to Phrase from outside SSO.