Page Comparison

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

Project Manager

Project Exceptions Dashboard

• In order to capture targets that may have been get added to documents long after the document was first uploaded, we have modified the "Added in the past 'x' hours" tab . It now searches for all targets that have been created in the TMS rather than uploaded documentsrecently added targets regardless of how long ago the source document was uploaded.
• We have added a filter to the "Added in the past 'x' hours" tab that will show targets that were added to the document after the document was uploaded. This will make Project Managers aware of targets that have been added to already existing documents. 

Project Status Report

• We have added the Document UUID and Target UUID columns to the exported Project Status report.
• The Target Language column has been renamed to Target Locale. 
• A new Status Reason column (see Status Reasons below) has been added to the exported Project Status report (see 'Status Reasons' section below). 

Status Reasons

• Currently, users are required to enter a reason when cancelling targets and documents, as well as when phases, targets or documents are completed late. Also, when phases are skipped automatically by workflow rules, the system records the reason the phase was skipped. A new information icon will appear next to the status the TMS requires a "Reason" when one of the following terminating status changes occur:
  • Cancelling targets or documents
  • Skipping or cancelling a phase (either manually or automatically via workflow)
  • Completing a phase, target or document after its due date (i.e. Late)
• To make it easier for users to see these Status Reasons, an information icon now appears next to the Status field of any phase, target, or document if it that has a reason Reason for its status. Users can see the status reason whenever they hover over the Status Reason by hovering the cursor over the information icon. The following pages have been updated with this change:
  
  • Task List
  • Document List
  • Target Summary

Upload Document

• The Preserve white-listed in-line tags setting has been expanded to include the following tag patterns:
  • Curly brace variables. An example is: {1}
  • Square bracket variables. An example is: [Account]
  • Dollar variables where the first character after the dollar sign is a letter. An example is: $projectName
  • C-style printf codes. An example is: %2$d
• This feature can be enabled in the following places:
  • When uploading a document
  • On the Document tab of the "Setup" phase in Workflow template

Workflow

• When a callback is specified on a workflow rule, it won't be sent if it does not belong to the client organization or doesn't belong to the Vendor organization assigned to the target. 

Workbench

Track Time

• The timer in the Workbench has been updated to automatically stop timing when the task is marked complete, instead of when the phase progress reaches 100%. This allows users to account for the time it takes them to go back and review their work. 

Skipped Phases

• Any user with access to a skipped phase can now open that phase within the Workbench in view-only mode. 

Mark Tasks Complete

• We have added a button in the Workbench that will allow linguists to mark tasks complete when they have reached 100% progress on the task. 
• The progress on the Task List is automatically updated as the user makes progress in the Workbench. When the user reaches 100% progress on the task in the Workbench, the box to mark tasks complete appears on now immediately appears on the Task List (without the need to wait for, or force, a refresh of the Task List). 
• When the user closes the Workbench, the Task List will be refreshed automatically to make sure any changes are reflected in the Task List. 

Quality

• We have improved the scalability and integrity of Quality Reports. These changes resolved the issue that prevented linguists from downloading Quality Reports. 

API

• The locale_code parameter for the POST /document document call can now accept multiple locale codes to allow the user to easily create multiple targets when uploading documents via the API. 
• Any API call that creates a job in the TMS will receive a response that includes a process ID and the results of the process. This allows To allow integrators to know whether or not the job they created background job resulting from an API call has failed or was successful as well as giving them the ability to track the job., we now return the process_ID in the response for the following APIs:
  • API4

    • addDocument

    • addDocumentAsync

    • addContentDocument

    • addContentDocumentAsync

    • addDocumentWithTargets

    • addDocumentWithTargetsAsync

    • addContentDocumentWithTargetsAsync

    • addContentDocumentWithTargets

    • api/document

  • API5
    • POST /document