10-26-2020

Owned by Aaron Sakievich (Unlicensed)
Last updated: Nov 10, 2020
3 min read

We are pleased to announce that version 15.33.0 of the Lingotek Translation Management System was released today.

Project Management

Workflows

  • Rules on the Project Completion workflow step using a progress condition (i.g. “When project progress reaches 55%, then call default project callback URL“) did not work as expected if the user chose any percentage other than 100%.

Global Search

  • All resources can be searched using their UUID in the global search bar. Previously, only documents could be searched using their UUID. Note that you must have the necessary permissions to access the resources you are searching for.

Project Settings

  • Projects have a new “Disable Inheritance in Update Document” setting in the Document Options panel. If set to “Yes,” updated documents will ignore the workflow(s) and filter configuration files of the previous document version and instead use the project workflow and matching importer templates as long as the API doesn’t specify otherwise (see the API release notes).

  • By default, this setting is set to “No,” which means the filter configuration files =and workflow(s) will be inherited from the previous document version if the API call doesn’t specify otherwise.

Project Callbacks

  • Our document import failure callback was improved, so it always includes document metadata in the response.

Workbench

Context Improvements

  • When the source URL is opened in a new window, the context viewer is closed in the Workbench. When the new context window is closed, the context viewer is re-opened.

  • Users can configure their context settings, so a separate window is opened automatically whenever a source URL is found.

Resolved Issues

  • All Terminology matches returned in the sidebar are also underlined in the source segment.

  • When text is cut from or pasted into a target segment, the character count is updated accordingly.

Vendor Management

Cost and Invoice Reports

  • Running a vendor report from the Project app would fail if the user selected all the project documents.

  • We have increased the time-out limit and made other improvements to keep larger reports from failing.

API

API5

  • We have added additional parameters to the PATCH /document/{id} call to give integrators the ability to override the previous document’s settings. If these parameters are not set, the document will inherit the previous document’s settings or the project default settings based on the “Disable Inheritance in Update Document“ project setting.

    • project_id – Upload the new document version to a specific project. Leave the parameter blank if you want the new version to be added to the previous version’s project.

      • The specified project must be in the same community as the previous document version.

    • translation_locale_code – Use the parameter for each target you want to specify a workflow for. You must have at least one translation_locale_code parameter to use the translation_workflow_id parameter.

    • translation_workflow_id – Specify the workflow that should be used for the new document’s targets. You can use the translation_workflow_id with the translation_locale_code parameter in the following ways:

      • Leave it blank – The targets of the new version will inherit the previous document’s target workflows or the Project Workflow based on the project setting.

      • Use the parameter once – The workflow will be used for all the locales specified by the translation_locale_code parameters.

      • Use the parameter the same number of times translation_locale_code is used – The workflows will be applied to the targets in the order they were added in API call.

API4

  • We have added the project_id parameter to the following API4 calls to allow you to upload new versions of a document to a different project than the previous version.

    • updateDocument

    • updateDocumentAsync

    • updateContentDocument

    • updateContentDocumentAsync

  • The specified project must be in the same community as the previous document version.