Translations Add-On Release Notes

Bloomreach offers Enterprise support for this feature to Bloomreach Experience customers. The release cycle of this feature may differ from our core product release cycle. 
Using this feature requires an additional license. Please contact your account manager or sales person for more information.


See here for the release notes for versions 6.x on Bloomreach Experience Manager 15.


Released: 20 October 2022


Released: 22 August 2022

    Star Connector: introduce extension point (protected method) to the StarTranslationConnector on behalf of subclasses being able add a custom attribute to the XML that is sent out:
    protected processXML(byte[] documentXml, TranslationJobItem jobItem)
    Fix for the "Enable compound configuration" functionality (since 5.8.0), where fields of compounds aren't sent anymore if not explicitly configured.


Released: 24 June 2022


Released: 18 May 2022

    Recreate the settings panel (which worked on XM 14.0 only), as custom configuration perspective, for 14.1 and higher.
    The dependency on the Settings Management GitHub plugin is no longer present, so implementation projects should remove those Maven dependencies. Please revisit the installation page.
    See also the configuration page.
    Add a new feature to the above configuration perspective, to be able to select the compound types that are enabled for translations, plus the fields inside compounds. The feature must be enabled in the same perspective, using "Enable compound configuration" checkbox.
    Fix a filtering bug in the Requests Overview, where selecting multple Status values lead to wrong results. 


Released: 14 March 2022

    Better feedback when requesting translations from the Document Search.
    Add a filter to the Document Search to easier find documents that are translated to other languages.
    This release will add a Groovy script MarkTranslatedDocuments to the updater registry. For the correct working of the new feature, the script has to be run once on every environment, so that existing documents will get the correct metadata. 
    Note: the script queries all documents so can be heavy on resources, so please use the script carefully, maybe change query, throttle, batch size. After this task, the metadata will be kept in sync when a translation is added or when a document is deleted.


Released: 31 January 2022


Released: 8 December 2021

    Filters were added to the Requests Overview, to better find translation requests.
    FTP connector:
    A) add module 'localserver' for local testing
    B) add new configuration options:
    ftp.ftpServerPort: 0 by default, meaning none used
    ftp.ftpChannelType: "sftp" by default
    ftp.connectTimeoutMillis: 0 by default, meaning no timeout.


Released: 25 October 2021

    FTP connector: clean up empty folders.
    Fix NullPointerException in the search-based dialog.
    Improve dependency management: notably scope 'provided' on spring-web and on Globallink's stax-api, to not pull in XM 14.0 dependencies in a 14.6 project.
    Improve error handling when invoking translation workflow.
    Internal refactoring: in UI, use existing services rather then reading JCR nodes/properties.


Released: 29 March 2021

    Prevent FTP connector from leaving open connections when retrieving results.


Released: 11 March 2021

  • STAR connector: when processing results fails, add the exception to the error log statements to show the underlying reason.


Released: 5 February 2021


Released: 25 January 2021

    FTP connector: fix for cancellations to remove FTP files again.
    STAR connector: log any exception per incoming result, then continue processing additional results.


Released: 20 January 2021

    Request dialog: remove confirmation message that didn't account for send failures, to be followed up by TRANSLATIONS-309.
    Request dialog: avoid scrollbar and move connector dropdown to the bottom.
    Translations overview: better handling when connector property is missing.
    Bootstrap default values of these new settings in 5.4.10:
    "Overwrite open documents": false
    "Preselect translation targets": true
    Please revisit the settings after upgrade if needed.


Released: 14 January 2021


Released: 11 January 2021


Released: 30 December 2020

  • TRANSLATIONS-300 Various bug fixes:
    • Missing wicket label 'submission-name' causing the input field for the project name to not appear.
    • XTM backend does not accept certain characters as project name, such as "™, ’".
    • A bug in advanced search side of the plugin: When multiple documents are selected for translation the document names would not be visible in the XTM UI although the content would be correct.


Released: 18 December 2020


Released: 15 December 2020


Released: 1 December 2020


Released: 6 November 2020


Released: 2 November 2020

    Added support for translation window dialog extension. Globallink now allows setting of project, submission name, priority, due date and notes per translation request.
    Added support for multiple translation connectors.
This might require some upgrade steps, please see below!

Upgrade steps for 5.3.0

The configuration for multiple connectors is different. The new configuratIon will be bootstrapped automatically. However, if you have bootstrap data in your project that assumes the old configation, you might need to change this to match the new configuration.

The connector config has moved from
/hippo:configuration/hippo:modules/translation-services-daemon/hippo:moduleconfig/translationsaddon:connector to .../translationsaddon:connector-{connector name}, such as translationsaddon:connector-livewords or translationsaddon:connector-globallink

Existing translation jobs should be updated. All nodes of type translationsaddon:job have a property translationsaddon:connector (String) with a value matching the connector class name (LivewordsTranslationConnector, TesterTranslationConnector, GlobalLinkTranslationConnector, etc). This property can be added manually in the console or created by a simple Groovy Updater Script.

In order to upgrade, please follow the steps below:

  1. Change all references of /hippo:configuration/hippo:modules/translation-services-daemon/hippo:moduleconfig/translationsaddon:connector
    in your bootstrap yaml files to /hippo:configuration/hippo:modules/translation-services-daemon/hippo:moduleconfig/translationsaddon:connector-{connector name}.
    Make sure that any configurations that are not in bootstrap yaml files are moved on the various environments as well. Think URLs and passwords, environment-specific subnodes.
  2. Remove any connector configurations you do not wish to use.
  3. Update all nodes of type translationsaddon:job, add the property translationsaddon:connector (String) if it does not exist with a value matching the connector class name (LivewordsTranslationConnector, TesterTranslationConnector, GlobalLinkTranslationConnector, etc). 
    Note: from version 5.4.11 upwards, the overview dashboard is more robust against any missing property.


Released: 1 July 2020

    In the Star connector, add a star.jobGroups configuration property. It specifies a comma-separated list of job group names to accept when polling for ready jobs.


Released: 7 May 2020


Released: 3 April 2020

    Improvement in the STAR connector: the sent file name is now the document name instead of the id.
    Improvement in the STAR connector: the mapping from standard ISO locales to Microsoft LDIC locales is moved from a coded utility to the connector property star.localesMap, see also the Star connector.
    In the yaml bootstrapping of the advanced search UI part,  use "add" operation instead of overriding property /hippo:configuration/hippo:frontend/cms/cms-advanced-search/workflowPlugin/workflow.categories.


Released: 6 February 2020


See here for the release notes for versions 4.x on Bloomreach Experience Manager 13.


See here for the release notes for versions 3.x on Bloomreach Experience Manager 12.


See here for the release notes for versions 2.x on Bloomreach Experience Manager 11.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close