08-20-2019

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

Project Management

Document List

We resolved an issue that kept TM from being updated when using the Approve All bulk action from the Document List.
When adding a phase to a document manually, the default "Update TM when saving segments" setting is the same as the corresponding phase when creating a new Workflow.
We deleted the duplicate "Created Date" filter that was visible in the Configure Document Filters modal.

When inviting members to your community in bulk, the system will look at the Login ID to see if that Login ID exists in other communities. If it does, it will invite that user as a guest member of your community. It no longer keys off of email addresses.

We have added a Document UUID column to the exported Analysis and Leverage reports.
The modal to run analyses and leverage reports will have the "Mark results visible to assignees" and "Search TM Vaults" options set to TRUE by default.

The email template under Assignment Groups now sends the WorkbenchLink variable as expected.
We resolved an issue where checking the task back in from the Manage Assignment Groups modal did not reset the timer that makes the task available to groups as expected.
Once a checked-out phase has been completed it can no longer be checked back in. This applies to all API calls, bulk actions, and individual actions, regardless of the role of the user.
Project Managers can check-out a task if they are not included in the Assignee pool from the Workbench.

All users in the TMS are auto-provisioned an alias that is comprised of an abbreviation of their default community and the last 8 digits of their UUID in the system.
Community Admins and Project managers will only be able to see the names or email of linguists that share the same default community in the TMS. PMs and Community Admins will not be able to see names and emails of Linguists that belong to a different community even though those linguists have been invited to work in their community.
There is a community setting that enables linguists to see each other's name and emails if they belong to the same community. The default setting is to hide linguists real names and emails from each other.
Users will be able to search by name, email, and alias everywhere in the UI.
The API also honors whether or not a user should see a real name or an alias in the response.

We added a new report in Vendor that is only accessible to Vendor communities. This report will have the real name and alias of the user in the Assignee and Responsible User column.
When running Invoice Reports, vendor managers can choose to automatically run a Linguist Report using the same parameters as their current Invoice Report or they can choose to run the Linguist Report separately.
The Linguist report does not include any cost information since that is specifically costs that will be presented to the client.

Invoice and Cost reports will only show user aliases in the Assignee and Responsible User column.

We can now provide live previews for IDML file types in the Context Viewer. This is in addition to INDD, InDesign Packages, and HTML documents.

Marketplace Extension

The following issues have been resolved:
- Search results that returned a large list of content would not display all the search results.
Performance when scrolling through a large list of content has been dramatically improved.
We have added a Clear Cache icon to the left of the refresh icon the extension. We use caching to improve performance when loading content in the extension. Occasionally users will make changes to source documents (editing, removing, or adding content) that will not appear until the cache has refreshed, which happens every 5 minutes. The new icon will allow users to manually refresh the cache if they know changes have been made.
Content that has been translated into Spanish, Latin America (ES-419) will no longer display as a source document in the extension.
Selecting the Refresh icon while loading content works as expected.
We have created a queue that will prevent Chrome from timing out when making a large number of API calls from the Marketplace extension.
Edits to a translation in the Workbench that has already been downloaded will redownload and override the current translation as expected.

Zendesk

We have added a new Host Mapping URL field in Zendesk product settings. For communities that have more than one Zendesk integration with different environments, we will use the host mapping you set up with Zendesk to differentiate them and make sure the correct integration is being used.
When you reupload a document with a changed name to the TMS, the document name in the TMS updates as expected.

Confluence

We resolved an issue that caused images on nested translated pages from being ported over correctly if the parent page was not translated first.
We updated the default Confluence FPRM filter so documents would round trip as expected. This was affecting the following:
- Translating the home page of your Confluence space.
- Inserting content into blank areas of the source page.
- Occasional errors when downloading documents.
Bulk actions have been reviewed in the Confluence connector and now work as expected.

Eloqua

We have added support for translating alt text and preview text in responsive content.
Downloading content that has been corrupted by the translation in the Project application will no longer halt the entire download.
Eloqua detects email data (name, id, etc.) as expected.
The Eloqua API does not support linking to Shared and Dynamic content. So we have disabled the links those content types. Additionally, the view option is not available in the drop-down menu.

We resolved an issue with the DELETE /document/{id}/reference-material/{reference_id} endpoint that was returning a 400 response even when the call was valid.
GET /task now properly returns tasks whose associated document has a priority set, without needing to specify a value for the 'priority' parameter when making the API call.
We resolved an issue that prevented the Responsible User from being set when using the POST /task/{id}/check-out call. This affected Cost and Invoice Reports. A migration was run to populate missing data.

Need Support?

Visit the Lingotek Support Center.