Enable dynamic Translation for Virtual agent without language plugin

[Anto Alad1]

Hello All,

We are looking for options to enable Dynamic translation only for Virtual Agent without Language Plugins enabled? Is there any way that Dynamic translation can be limited only to VA and not for other applications in the Environment.  Please let us know if this is feasible, if so how can this be achieved. 

Plugins enabled as of now :

1. Virtual Agent for ITSM Plugin
2. Advanced Work Assignment Plugin
3. Agent Workspace Plugin
4.Dynamic translation Plugin

We see enabling Language plugins will bring maintenance for other custom fields (non oob fields) created in the environment. so looking for options to enable this feature only for VA.

[Victor Chen]

You can currently use dynamic translation to translate VA topics or NLU models as a configuration without language plugins. See more information here.

VA conversations do not automatically translate live. Conversations between a user and a live agent however can be automatically translated with dynamic translation in agent chat. 

[aladpereira]

Hi Victor,

Thanks for your reply. we are looking translations for Agent chat (only for agent conversation) at this moment and we have enabled DTAC. But will this work without language plugins enabled?

Regards,

Anto.

[Alex Coope - SN]

@Anto Alad 

So there's a few things to unpack here,
1. Is it possible to use DT for a language without the language pack being installed? - yes it is, there needs to be a record of that language in the [sys_language] table marked as "active=true" via a server side script
2. is this going to lead to a good user-experience for the end user? - no it likely wouldn't, because you need to consider how the end-user would be able to navigate the UI if they can't necessarily read the originating language (e.g. English).

Typically speaking, it's not considered a good practice to have a "mixed language" experience in any UI, and it nearly always hurts the adoption of the new solution by the end-users if it's not consistently available in their language. If you want to learn more about it, check out one of my previous webinars available here:

Going to the comment about maintenance for other custom fields etc, this falls under the best practice guidance with the user-experience (UX) consideration. We have a whole bunch of material available on our CSC page on how to do that available here, and our dedicated forum here,


Many thanks,
Kind regards