Release Notes - Language I/O for Salesforce Article version 1.18

These are the Release Notes for version 1.18, released January 4th, 2023.

Please see the installation instructions in Setting up Language I/O Article in Salesforce (admin guide) for the installation link.

New

New permissions in User Settings for the review and approval of quotes

Salesforce Article admins can now configure permissions for users to view and approve quotes for requested translations. Previously, all users could view and approve quotes, which could lead to agents approving quotes without being authorized to do so by their organization.

Users with the permissions will see the Quote and Cost links in blue:

(Click to enlarge)

Users who do not have the permission will see the links deactivated and greyed out:

(Click to enlarge)

With this new permission setting, admins now have an additional layer of safety and control. This will make it easier for admins, managers and agents to clarify who can review and approve expenses for their article translations.  

For more information about how to set up this feature, see [link to Help Center article]

New "Auto-Publish" setting

Salesforce admins can now configure their Language I/O Salesforce Article to publish the translated articles automatically by default upon creation of the translation project.

When enabled, the Publish toggle on the project creation page is automatically toggled by default:

(Click to enlarge)

For more information about how to set up this feature, see [link to Help Center article]

New export tool for record/article types and related fields

We created a new extraction tool to help admins configure their Language I/O Salesforce Article plugin in the best conditions. The new tool, once set up, automatically extracts all the article types and fields in your Salesforce Article instance and exports them to a CSV file. Admins can then easily specify for each field if they are to be included in future translations or not. Finally, when they finish their review, they simply send the file to their Language I/O Client Support representative to finish the configuration of the plugin.

Before, the extraction process was manual, which was time-consuming and could lead to human error. Now, this new automatic extract tool greatly reduces the amount of time needed to configure the Language I/O Salesforce Article plugin.

For more information about the Article Extract tool, see [Setting up Article Type Extraction] and [Using Article Type Extraction] in the Help Center.

Improved

Search now available for blank record types

Lightning users can now expand their search in the Language I/O Salesforce Article plugin to include blank records. This improves user experience as users can now send articles to translation even when no Record Types exist on their org. Previously, a Record Type was needed to request a translation. 

Fixed

Deleting draft translations in queue after a project is cancelled

When you cancel a project, this deletes the XTM project and all the draft translations in the Translation Queue as well. Before, cancellation of the project deleted the project in XTM, but sometimes did not delete the queued drafts. This bug affected projects in Absaroka Classic version 1.12. This is now fixed.

Error message when requesting an unsupported locale

When you create a project with a locale that is not supported in your account, the system now returns the correct error message:

Error: Your account isn't set up to support the locale(s) 'xx' requested

Before, the system returned a generic server error 400. This affected version 1.15 of the plugin. This is now fixed.

Error message when requesting an unsupported language pair

When you create a project with language pairs that are not supported in your account, the system now returns the correct error message:

Error: No vendors support the language pair for the given translation type HUMAN, source locale [XX], and target locales [YY]. Please contact support@languageio.com with error code 508:XXXXXXXXXXXXX

Before, the system returned a generic server error 500. This affected version 1.15 of the plugin. This is now fixed.