Release Notes - Language I/O for Salesforce Chat version 2.42.2

These are the Release Notes for version 2.42.2, released October 25th, 2023.

Improved

File Transfer can now be disabled in Chat

Certain organizations want the behaviour of their Language I/O tab to match the behaviour of the conversation tab. To that effect, Language I/O added the option to disable the File Transfer functionality in the Chat Custom Settings.

The File Transfer functionality is enabled by default. To disable it, go to the Chat Custom Settings and uncheck the "Enable File Transfer Request" option.

More precision added to Error Logs

Chat error logs now specify when a thrown error was caused by a blocked HTTPS request. This will help agents and administrators better understand or diagnose issues when they see or review thrown exceptions.

Remove dependency on Contact access to run Chat plugin

Certain organizations want to restrict agent permissions so that they only access objects that are relevant for their work. As a result, we added the option to remove unneeded permissions and their dependencies (for example, access to the "Contact" object) so that agents can still load the Language I/O Chat component even when their set of permissions is restricted compared to the default settings.

Fixed

Language detection did not display language

A bug was found where, when the customer language was the same as the agent language (for example, when both the customer and agent language were English), the "Customer: locale" field was not updated with a language code and showed "[locale]" as if no language was detected. This is now fixed and the field now correctly shows the customer language, even when it is the same as the agent's.

Related fields records limitation

A bug was found where, if you were using related fields and the related object contained more than 50,000 records, the chat window would not load. This is now fixed and the chat window loads and works as intended regardless of the number of records in the related object.

Fetching Related Language now triggers when variable is not null

The method to fetch related language now has a check implemented to run before its execution, to avoid the display of a Chat component error when agents first launch the app. The method only executes if the variable contains a value. If the variable is null, the method does not execute.

Archive Email Message Records without Attachment trigger executing

When users archive their email message records, the operation no longer executes the attachment trigger automatically. This means that archives no longer check for attachments to record them by default. It is still possible to add an attachment to an object (such as Case) manually as needed.