Release Notes | Language IO Case for Salesforce

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

June 4, 2026: 2.36 1GP & 2.36 2GP

New

Language IO Case for Salesforce 2.36 2GP (Second-Gen Package)

Language IO recommends upgrading to benefit from the latest security improvements in Salesforce 2GP packages.For more information on Salesforce 2GP packages, see the Salesforce documentation on Second-Generation Managed Packages.

Versions 2.36 1GP & 2GP allow you to transition to 2GP if you haven't already.

If you haven't upgraded to 2.35.3 2GP yet, you must upgrade to version 2.36 1GP and then to 2.36 2GP. Please see Installing Language IO Case for Salesforce for more information.

Improved

Attachment Translation Expanded to All Case Attachments

Case attachments can now be translated regardless of origin (including internally-created, Email-to-Case, Web-to-Case, and Feed Posts). Translated attachments persist with the Case and remain accessible even if Case ownership changes.

Reporting Expanded to Include the Source Content of All Message Types

Previously, translation reports only included the source content of outbound email messages. Now, translation reports include the source content of all translated message types, so the original message and translation can be reported side-by-side.

Fixed

• When two or more different attachments with the same name were attached to the same Case, they were all unavailable for translation. This has been fixed.
• When an attachment's name contained certain special characters, translation of the attachment failed. This has been fixed.
• When Feed Posts contained an attachment, they were not available for translation. This has been fixed.
• Right-to-Left (RTL) text would render out of order when mixed with bidirectional (BiDi) content. This has been fixed.

February 24, 2026: 2.35.3 1GP & 2.35.3 2GP

New

Transitioning to SF Case 2.35.3 2GP (Salesforce Second-Generation Managed Packages)

Version 2.35.3 1GP & 2GP mark a significant milestone in Language IO's commitment to security and performance. Language IO recommends that you install this upgrade to benefit from all the latest recommended security improvements brought by Salesforce 2GP packages. For more information on 2GP managed packages, see the Salesforce documentation on Second-Generation Managed Packages.

November 25, 2025: 2.35.2

Fixed

"Draft already translated" message appears after the first attempt failed

When an agent tries to translate a draft in Salesforce Case, and the translation fails, a second attempt to translate the draft is still permitted.

A bug was found where, when the translation of a draft was requested, but there was no end user language defined, the translation would fail (as expected, due to the lack of target language), but instead of showing that it had failed, the interface would show that the draft was already translated upon the second attempt.

This is now fixed, and attempting to translate a second time works as expected.

November 18, 2025: 2.35.1

Fixed

Case word count enforcement error

A bug was found where, when a specific word count limit was set for outbound email translations and the message exceeded this limit, a warning message appeared as designed, but the agent could still click the "Confirm" button, triggering a "Null pointer" error message.

This is now fixed so that when the message exceeds the word count limit, the agent cannot click "Confirm" and must edit the message until it is within the defined length.

Blank Language IO Translation Visualforce tab and Email Feed showing HTML

A bug was found where, after upgrading to version 2.35 without having the LIO Translation Visualforce tab, and after adding the tab on the page layout, comments and incoming emails would not display.
If this happens, this can be fixed by making sure the "Only Show Translations Plugin" setting is checked in the Language UI Case Custom Settings.

July 18, 2025: 2.35

Improved

Preserving formatting styles in pasted content and translations

Now, when an agent copies and pastes content that contains styles between the sentences (for example, line spacing, margins, indentation, etc.) into the Language IO Case Translation component, this formatting is preserved in the pasted content and is also preserved after translation.

Fixed

HTML Tags Visible in Language IO component and Feed

A bug was found where, when an agent translated formatted text (for example, a case description), the translation that was delivered would show the HTML tags used in formatting in the Language IO component as well as the case feed. This did not happen with partial translations. This is now fixed, and the translations no longer show any HTML tags.

Regular expressions for description field not working

A bug was found where the regular expressions for description field was no longer working. This field allowed agents to create regular expressions in the custom settings to translate the latest email received in the thread. This version fixes this issue, so that regular expressions work again as expected.

June 20, 2025: 2.34.1

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.

April 23, 2025: 2.34

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 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 exceeds 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 exceeds maximum: 6000000".

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

Older versions

Submit a support request if you need to review older release notes for this application.