Page Comparison

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

Project Management

Workflows

• Percentage based conditions Rules on the Project Completion step using a percentage progress condition (i.e. “When project progress reaches 55%, then….“ then call default project callback URL“) would not work as expected if the percentage user did not equal choose 100% progress.

Global Search

• Now all All resources can be searched using the resource’s their UUID in the global search bar, previously only documents could be search with their UUID.

Project Settings

• Projects have a new “Disable Inheritance in Update Document?” setting in the Document Options panel. If this is set to “Yes” updated documents will ignore the workflow and filter of the previous document version and instead use the project workflow and matching importer templates unless the integration updated the document with specific when it is updated if the API doesn’t specify those settings. By default, this setting is set to FALSE which means filters and workflows will be inherited from the previous document if the API call doesn’t specify those settings.

Workbench

Context Improvements

• When the context viewer 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 launched.

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 documents in the project.

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

API

API5

• We have also the inheritance logic for updated documents. In the past, new versions of documents would use every setting of the previous document unless otherwise specified in the PATCH call. We have expanded the number of settings you can override (projects and workflows, see below) but we have added a project setting that will make the document use all the project defaults if it is set to TRUE and there aren’t any conflicting parameters in the PATCH call.

• We have added new parameters to the PATCH /document/{id} to allow new document versions to be uploaded using different workflows, filters, and projects than the previous version.

  • 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.

  • 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 in order to use the translation_workflow_id parameter.

  • translation_workflow_id – Specify the workflow that should be used for the new document’s targets.

    If

    You can use the translation_workflow_id with the translation_locale_code

    is blank then the workflow specified will be applied to all documents. If you are specifying more than one

    parameter in the following ways:

    • Leave it blank – The workflows on the matching targets of the previous document version will be used for their corresponding targets.

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

    • Use the parameter the same number of times the 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 push new versions of a document to a new project.

  • updateDocument

  • updateDocumentAsync

  • updateContentDocument

  • updateContentDocumentAsync