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	`fromTo(value1`,`value2`,`value3)`	`fromTo(value1`;`value2`;`value3)`
any, anyOf, noneOf	`any(value1`,`value2)`	`any(value1`;`value2)`
any, anyOf, noneOf	`any(value1`,`value2`,`value3)`	`any(value1`;`value2`;`value3)`
range	`range(value1`,`value2)`	`range(value1`;`value2)`
range	`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.