Release Notes - Language IO for Salesforce Case

These are the Release Notes for Language IO for Salesforce Case.

Please see the installation instructions in Installing Language IO Case for Salesforce for the installation link.

v2.34.1 (2025.05.20)

Fixed

Attachment not visible when description is empty

A bug was found where, if a case only contained a subject and an attachment, but the description was empty, the attachment would not be visible for translation. This is now fixed so that attachments are visible, regardless of whether or not the description field was filled out.

v2.34 (2025.04.23)

Fixed

Line break formatting removed after translation

A bug was found, where line breaks and other formatting elements that were present in the source content sent to translation might be missing from the translation that was returned. 

This could happen in the following scenarios:

• When users would copy and paste content for translation, where "invisible" characters such as line breaks would then be removed during the translation process.
• When users requested a "partial" translation of the description field, where line breaks would then be removed from the field during the partial translation process.

This is now fixed, and formatting elements are preserved in the delivered translation as expected.

Error “String length exceed maximum: 6000000" when translating PDF attachments

A bug was found where attempting to translate PDFs with the Language IO app would fail and result in the following error message: Error “String length exceed maximum: 6000000".

This was caused by a file size limitation on the Salesforce side. The current file size limit is 11.8Mb.

v2.33 (2024.12.18)

New

Creating Translation Turn-Around Time Reports

You can now report within Salesforce for each translation:

• the time when the source text was sent for translation
  • this is the moment when the agent or or the end user sent the message.
• the time when the translation was returned 
  • this is the moment when the translation response is received in Salesforce.
• the unique identifier for each translation
  • this is typically the translation id

You can find more information about how to create this report here. 

Fixed

Displaying original and translation for outbound emails

A bug was found, where agents who translated an outbound email could no longer see the translation in the Language IO Case component. As a consequence, they could not reference what was originally written and what it was translated to. This is now fixed, with the following:

• When an agent translates an outbound email, the Language IO component shows both the original text and the translation.
• The original text is labeled as "Agent Email". The translation is labeled "Original Translation".
• The ability to Partially Translate and Translate is preserved. This is so that if another agent takes over the case, but speaks a third language, can translate the content again to their own language.

v2.32 (2024.11.19)

New

Introducing attachment translations

Agents can now translate attachments that end users send them with the new attachment translation feature. End users could already attach an image or file as reference material to the case, but agents can now translate these files to their language with the click of a button. This way, end users can now give agents much more context about their case, helping them to solve issues more quickly and efficiently than before.

For more information about supported formats and attachment translations in Salesforce Case, see this link.

For more information about the differences between, and respective benefits of, attachment translations versus the Language IO translation portal, see this link.

Older versions

Please consult your Language IO Customer Success Manager if you need to review older release notes for this application.