Documentation Center

Web/App/Db server

Web/App/Db server have been improved in this version.

Added TMS username/password authentication to Translation Organizer

TMS versions 12.1 and later prefers a username and a password (instead of apikey and secret). Content Manager Translation Organizer has been adapted accordingly.

A new configuration option is available in the TMS integration set: authenticationMode. Possible values: ApiSecret (the SDL TMS legacy authentication mode), UserCredentials (the current SDL TMS authentication mode). The default value is ApiSecret.

The Resolutions to export property

A new property has been added to the Output Format form in order to be able to use the list of image resolutions, specified in Resolutions, as a fallback list: Resolutions to export. This property has an effect only when there is more than one resolution specified in Resolutions.

Resolutions to export has two values:
  • All Resolutions: no fallback behavior. This is the default publishing behavior.
  • First Matching Resolution Only: the first resolution in the list is preferred and the others are used as fallback.

The list of resolutions is used for choosing the image resolutions to export at the early stage of publishing, and is part of the criteria needed for a publication output to acquire a Release Candidate status.

  • Export: by default all resolutions are exported, and only the first one is linked to topics in the publication, while the other resolutions are used in custom processes. With First Matching Resolution Only, only the first resolution in the list is exported. The other ones are used as fallback. For example, with resolutions "Low, High":
    • By default Low and High resolutions are exported for each image, or replaced by a missing object if they don't exist.
    • With First Matching Resolution Only, the Low resolution is exported for each image. The High resolution is exported only if the Low resolution does not exist. If none exist, the image is replaced by a missing object.
  • Release Candidate status: by default all the resolutions must be released in order to acquire the status, as all resolutions are exported. With First Matching Resolution Only, the exported resolution must be released in order to acquire the status. For example, with resolutions "Low, High:
    • By default Low and High resolutions must be released to acquire the status (considering there is no missing object exported).
    • With First Matching Resolution Only, if Low has been exported, then it needs to be released in order to acquire the status (considering there is no missing object exported). If High has been exported, then that resolution needs to be released.

InstallTool input parameter ps_java_home is now a mandatory parameter

Following the adoption of the new Java module Eclipse Temurin OpenJDK, the value of ps_java_home is no longer calculated: it must be manually set at installation. ps_java_home is therefore now part of the list of "mandatory" parameters.

We also added ps_java_jvmdll to the list of optional parameters. It has a default value (<ps_java_home value>\bin\server\jvm.dll).

Translation Jobs of type 'File System' can be cancelled

When you submit a translation job using the file system, you can now cancel it after all the objects to translate acquired the status In translation, that is, after all the files have been compressed and exported.

After a delay, the translation job will acquire the status Cancelled, and the objects will be set back to the To be translated status.

Tridion Sites Taxonomy Connector supports TLS 1.2

The taxonomy connector that imports a Tridion Sites taxonomy (IMetadataBinding) in Tridion Docs has been upgraded to be fully compatible with TLS1.2, making the taxonomy accessible again with that version.

Enhanced Publishing plugin to start DITA-OT

The IshRunDITAOT publish plugin has been upgraded to provide better control of the way DITA-OT files are managed, with two new parameters:
  • AntHomeFolder: lets you set a new location for ANT_HOME. The default value is the current DITA-OT\InfoShare folder.
  • BuildDITAOTFiles: lets you skip the automatic generation of the DITA-OT build files. By default set to yes (automatically generates the files).