Loading...
Loading...
When using dynamic translation with agent chat, and when an agent's preferred language uses special characters, punctuation characters are encoded when displayed to the end user.
Steps to reproduce: 1. On an instance that has the dynamic translation, AWA, agent chat and internationalization plugins installed impersonate a user that is configured for a chat queue (System Administrator, for example) - com.glide.dynamic_translation.va_async - com.glide.dynamic_translation - com.glide.cs.dynamic.translation.agent.chat - com.glide.i18n 2. Verify dynamic translation is configured for agent chat with a translation service, such as Google 3. For the chat agent being used, navigate to their sys_user record and change their preferred language to 'Chinese'. 4. In a private window, begin a chat and request to speak with a live agent 5. From the chat agent window, accept the chat and send a message containing punctuation (i.e: "I'm testing & you're testing, right?" 6. In the end user window, note how the message is displaying encoded characters. Actual behavior: The message displayed to the end user should be decoded after translation Expected behavior: The message displayed to the end user contains encoded punctuation characters.
This issue is fixed in Rome. There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.
PRB1497112
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.