The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Dynamic Translation, custom translator, Unable to translate

Jugmaz
Kilo Sage

Hi community,

we have configured custom Translator due to Customer demand.

Configurations are done, they are working as expected.

One note there is that while subflow is translating anything, it needs to create file for anything to be translated, send it to vendor system and then query whether it is ready.

SubFlow for this is created based on OOB translation SF (SubFlow always WORKS, returns success and translated text)

Worknote translation is enabled

When translation is requested for any Work note - it always returns "Unable to translate. Try again"

 

We got error of course, that is basicly:
The current execution is in the waiting state: org.mozilla.javascript.Context.makeJavaScriptException(Context.java:2080)

 

Error is longer but it just contains the normal org.mozilla.javascript stuff in it.

 

Now, we have of course contacted also ServiceNow in this case, but seems that this is a bit more challenging case as there is no answer - like any technical yet - of course normal check and try for basic DynTra configurations were suggested. 
Now multiple person in there has been studying the instance but without success.

 

Just trying to understand if anyone else has same kind of experience or even any suggestion to try!?

 

Translation service is Phrase.com - but we need to use file sending there for a reason that is not available - maybe later that might change - AND I'm 100% confident that the error is related to this as the flow is always taking more time than 1 second as it has to have wait there. 

Normally it is run through within 2 seconds. in the second try to get the file out. Doesn't help to just have a timer there.

 

Added flow context and error message for reference.

 

Any help is welcome!

3 REPLIES 3

Jonathan Demeu1
Tera Expert

 Did you ever manage to make this work? I have the same requirement

Jugmaz
Kilo Sage

Not really, unfortunately ServiceNow didn't support (fully at least or phrase.com) outer translation service.
We did try all possible things - but problem persists!
Problem btw is that when Translation flow is executed - it for some reason doesn't like waiting for flow or subflow to translate it - then it timeouts EVEN the translation is valid and everything there ok.

Not sure how it was then done or where it went as I moved already to new challenges.

I was suggesting on doing the translations in a custom way - mimicking the Now translation but with own process as the external Translation service work totally ok!

Thanks for getting back to me so quickly! Unfortunate to hear it didn't work out.