Custom Dynamic Translation build

[ganapati2]

We are trying to build a custom dynamic translation. Currently we are using IBM as our dynamic translator which is a OOB translator. We would like to understand how we could build a custom flow where we are going utilize a third party as a Dynamic Translation service provider. I would like to understand the detailed steps how we could achieve it. Has anyone done this before? Any leads would be much appreciated.

Thanks

Ganapati

[Tom Sienkiewicz]

I'm not sure how to do that within the OOTB "Dynamic Translation" product but I if you want to do this from scratch....

We've built a custom app for the Store which works with Azure/Google translators. Some high-level pointers would be:

• what should trigger the interface? Should you limit who/when can do that? (remember, messages sent = cost)
• what fields' values should be translatable?
• How do you detect source language? Azure/Google do this automatically in their API (there's no need to use a separate API for language detection) - perhaps your custom API does that too.
• How do you detect target language? Based on language in user profile or something else?
• What types of content should be translatable? Plain text or also HTML (HTML may require extra logic/parsing, depending on the API).
• Once you know all of this, you basically trigger the REST API of your translation service(I guess), where you pass the source text and the target language, and you get the translated text back. You also need to authenticate etc.
• How will you display the translation to the user? This depends on where this is used. A flow/subflow is flexible enough to be used in multiple places.

The REST interface is the easiest part of all this.

[ganapati2]

Hello Tomasz,

Thanks for your response. We are trying to build this custom translation in Virtual Agent product for the agent chat experience. OOB logic seems to be bit complex to understand the flow. I am trying to understand if we can utilize any of the OOB code and update the code to make it work for our new Translation service provider

Thanks

Ganapati

[Tom Sienkiewicz]

If you want to go with OOTB dynamic translation as much as possible, then according to the docs, you need to create your own Subflows:

https://docs.servicenow.com/bundle/quebec-platform-administration/page/administer/dynamic-translatio...

In the subflows, you need to use the REST step operation to send payloads to your API of choice, the inputs and outputs from the subflow need to adhere to the standard ones.

Then you create  a new translator configuration and add your subflows there. Meaning you should get all the capabilities the OOTB provides, it is just that your API would be triggered instead of one of the defaults.

[avivs]

Hi @ganapati2 

Did you handle it? I'd like to discuss if so, we are in same situation.