Release Notes - Language I/O for Salesforce Article version 1.19
These are the Release Notes for version 1.19, released June 15th, 2023.
Please see the installation instructions in Setting up Language I/O Article in Salesforce (admin guide) for the installation link.
Improved
Improved clarity with Project Management
When a user kicks off a translation project, they will no longer see old options such as “Rush Start” or “Detailed Quote” in the “Translation Cost Estimate” page. These options came from legacy versions and no longer fit with current projects. We removed these obsolete listings to improve the clarity of the process and make sure users are not misled when it comes to what options are available.
The window is now set so that only the “Auto Start” option is visible. It is checked by default and cannot be unchecked.
In addition, we also removed mentions of additional "Project Management Fee". We updated the app to reflect the fact that Language I/O plans are all-inclusive, and there are no longer additional fees for Project Management.
"Quote" is now optional for project approval
It is now possible for organizations to submit a project for translation directly, without requesting or approving a quote first. To allow this, admins can toggle off a new option called "Enable Quote" in the Language I/O plugin's Custom Settings. This removes the "Request Quote" step and replaces it it with "Submit Project", and moves the project directly to "Translation in Progress".
Sending additional information when "Quote" is disabled
Because the "Quote" process is now optional (see the previous note), we inserted the possibility for users to send a note when they submit a project and the quote feature is disabled, so that they can communicate any special requests or requirements for the project to the localization project manager.
Fixed
Recurring "fr-fr" error when submitting a translation project
A bug was found where, when a user submitted a project for translation, the system returned an error about French (fr-fr) not being supported, regardless of the actual target language of the project:
This is now fixed and the project submission process no longer shows this error.
Comments
0 comments
Please sign in to leave a comment.