09-22-2020
Version 15.31.0 of the Lingotek TMS was released today! With this release, we expose more details in the Workbench's segment history tab and import the most common file types using our latest importer version.Â
Project ManagementÂ
Document Import
Importer Version m40 is now the default for these file types:
APPLE_STRINGS
DITAMAP
DOXYGEN
DTD
HTML
JAVA_PROPERTIES (JAVA_PROPERTIES_OKAPI)
JSON
REGEX
RESX
TS
WIKI (WIKI_OKAPI)
XLIFF (XLIFF_OKAPI)
XML (XML_OKAPI)
XML_ITS
Workflows
The workflow couldn't create new phases if a language pair was assigned to a deleted team.
Deleted language pairs would still display if assignments were still associated with the language pair. Â
Workbench
We improved segment history to provide more detailed information about changes to a segment. With the new Segment History, users can see:
When a segment was created, edited, or approved.Â
The number of unapplied tags.Â
The top TM Unit UUID and it match strength.Â
If the segment was unlocked by the user when the translation is saved.
Whether the TM unit was supposed to be marked reviewed.Â
The Update TM setting when the translation was saved.
The Lingotek System is credited when segments are changed using a system action like Copy Translations or Leverage TM.Â
Segment Notes
Collapsing the Segment Notes panel no longer interferes with other panels in the sidebar.Â
Vendor Management
Cost and Invoice Reports
We have improved failure detection for cost and invoice reports to prevent them from appearing "stuck" to the user.
Marketplace
Eloqua
We have improved how we handle the "Invalid Element" error from Eloqua.Â
Zendesk
If the Zendesk connector receives a 403 response, we will immediately fail the download the process. This error can occur if the token the connector is using has insufficient permissions or if the content we are trying to create is using content blocks. Â
API
TheÂ
hours_worked
parameter is returned as expected for the/document/{id}/cost
,/document/{id}/cost/{locale}
.TheÂ
time_spent
parameter is returned as expected for the/phase/{id}
endpoint.The TMS erroneously sent Callbacks with the target status set to
IN-PROGRESS
instead ofÂCOMPLETE
when users manually skipped the final phase in the workflow.
Â