Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

XTRF 10.0 is now available only for test environments. The release for production environments is planned for September 17th. 👈

TL;DR

  • Great upgrade to Java 17 for better performance.

  • No more Velocity macros.

  • Text fields are limited to 20,000 characters.

  • PostgreSQL versions below 13 are not supported anymore.

  • The searching mechanism requires semicolons instead of commas in APIs running in the Browse pane.

Depending on the configuration and content of your instance, actions might be needed before you upgrade to v. 10.0.


Java 17 upgrade

The major change in this release isn't exactly eye-catching, as the whole work is conducted behind the curtains without affecting the user interface. However, you will certainly notice the difference, as Smart projects are now lightning-fast – up to five times faster than in XTRF v. 9.

Moreover, thanks to our switch to the next LTS Java version, the XTRF Platform is gaining:

  • Better overall performance.

  • Faster startup time.

  • Increased security.

  • Happier developers.


Other changes

Complete disabling of Velocity macros

Following the deprecation of Apache Velocity macros, you won't be able to launch them manually or through periodic jobs. Groovy will remain the only acceptable language for the XTRF macros. For details on Groovy macros, see the XTRF guide to macros.

Actions needed

Apache Velocity macros need to be rewritten in Groovy. For details, see the How to switch from Apache Velocity macros to Groovy guide.


Limited text box content

From now on, every text field in the system can contain no more than 20,000 characters. This limit will help increase system performance and prevent extensive memory consumption and potential stability issues. 

Actions needed

About 0.3 percent of all content in XTRF exceeds the limit and will be truncated. To avoid losing valuable information, please ensure your notes, comments, descriptions, and instructions are within a reasonable length.


End of support for PostgreSQL versions below 13

As XTRF already supports Postgresql 13 since v. 9.0, on-premise clients are advised to upgrade the database before upgrading XTRF.

Actions needed

Upgrade your database to PostgreSQL 13 or higher before upgrading to XTRF version 10.0.


Changes to the APIs running in the Browse pane

Actions needed:

APIs that run in the Browse pane will require your attention after upgrading to 10.0. Due to changes in the searching mechanism, all previously saved queries to the API in the Browse pane must be modified: commas must be changed to semicolons. This change is necessary for the API to continue working correctly.

If there was a practice of saving URL links to views outside the home portal (e.g., in browser favorites), then such links should also be updated.

 Click to see the examples

Example 1:

Changes to the URL for the filter parameters.

Operator

Previous syntax

Required syntax

fromTo

fromTo(value1,value2)

fromTo(value1;value2)

fromTo(value1,value2,value3)

fromTo(value1;value2;value3)

any, anyOf, noneOf

any(value1,value2)

any(value1;value2)

any(value1,value2,value3)

any(value1;value2;value3)

range

range(value1,value2)

range(value1;value2)

range(value1,value2,value3)

range(value1;value2;value3)

 

Example 2:

Changes to URL links

Previous syntax

Required syntax

http://127.0.0.1:8080/xtrf/faces/project/browse.seam?viewId=89&page=1&filters=targetLanguage:allOf(165,174,61,87,98);customFields.numberField1:range(100,120);sourceLanguage:anyOf(165,174,61,87,98);languageSpecialization:anyOf(1,13,2)&gantt=false

http://127.0.0.1:8080/xtrf/faces/project/browse.seam?viewId=89&page=1&filters=targetLanguage:allOf(165;174;61;87;98);customFields.numberField1:range(100;120);sourceLanguage:anyOf(165;174;61;87;98);languageSpecialization:anyOf(1;13;2)&gantt=false


Complete disabling of SMS notifications functionality

Following the earlier deprecation, the SMS tab will disappear from message templates.


Minor improvements and relevant bug fixes

Component

Improvement

System

Internal notes in Smart quotes and internal special instructions in Classic quotes are now transferred to the linked projects in a way that doesn’t increase the characters number.

Invoicing – Clients

Client invoice saving is now mandatory. The Do not save option has been removed from the Configuration menu > Templates > Files > File Locations > Save Client Invoices to / Save Client Pro Forma Invoices to dropdowns. If the Do not save option was previously selected, the default directory and filename expression will be selected automatically.

 

Component

Bug

Fix

System

An incorrect message was displayed when switching between the Sign-in Form and Single Sign-On (SSO) in General Configuration > Security.

The correct message is displayed.

Vendor Portal – Jobs

On some instances, an error occurred when trying to view All complete jobs in the Jobs module.

All completed jobs can be displayed without issues.

Smart projects and quotes

On some instances, selecting a specialization other than General was impossible.

All specializations can be selected.

Client Portal – API

Instructions from clients were missing in Classic projects created via the Client Portal.

Content from the Notes field is correctly transferred to the Home Portal via API.

Smart projects – Files

The Share Files popup did not display all the columns with file information if the file name was too long.

The file sharing popup displays all the necessary information regardless of the file name length.

Smart projects – Jobs,
Smart projects – Languages

In projects with a specific configuration, new languages could not be added at a certain stage.

When such an issue occurs, XTRF displays a message explaining why new languages cannot be added to a project with a specific configuration.

Filters and views

Filtering by Custom Fields in Smart views was not working correctly when the selected option's name contained a comma.

Filtering by Custom Fields is performed correctly despite commas in names.
(info) Custom Field names in the filter field should be separated by semicolons instead of commas.

Integration – CAT – Phrase

Phrase offline translation did not work for XLIFF bilingual files.

Phrase offline translation of XLIFF files is working without issues.

 

The bug related to GroupShare-integrated task creation cannot be fixed by XTRF. It is caused by an issue between Trados 2021 and some versions of GroupShare. If you have requests regarding this issue, please contact RWS support.
We are deploying the integration with Trados 2022 for Classic projects in XTRF v. 10.1, where that issue should not be present.

  • No labels