Localization Framework: Retrieve translation from custom TMS

YevhenK
Giga Contributor

Hello, big apologies for dummy question, but it makes me crazy. I'm trying to create a spoke for external TMS and use it in Localization Framework. Have implemented Request and Retrieve translation subflows, created TMS configuration and applied it in settings. Request translation works perfectly, I get a zip file with xliffs inside as expected. But Retrieve translations subflow is not invoked (don't see any logs that are printed in the start of subflow, and don't have a rest call configured in it). Also I'm very confused that I can't find any info about conditions/triggers/buttons for invocation of retrieve subflow. So the questions are:
- Is there any button like request translation, but for retrieval? Don't see anything like that, but maybe it could be configured somewhere, or maybe some conditions should happen to make this button appear?
- When/how Retrieve thanslations subflow supposed to be invoked by the default platform rules? The only thing related to this have seen in 'enable auto-retrieve' setting, it sais that retrieve will be done daily by some schedule, but also no info on how to view/edit this schedule.
- Are there any specific requitements to launch retrieve translation? Maybe smth specific should be present in output variables of Request translation subflow?

Will be very happy if someone could point me to some documentation/guide/learning course for this topic. Have studied this https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/localization... and few introductions, but haven't find there needed details.

Big thanks for your attention and thank you very much in advance,
Yevhen

14 REPLIES 14

@User41925,

There shouldn't be a need to create separate "templates", because the idea of the LFtasks is to hold the source text with one task per Source Language <-> Target Language combination. The "setting" is just to let the Localization Framework know what is the translation mechanism for that source type ("artifact") in that given language (dependent on your settings). 

The target language of the LFtask / LRitm would be included automatically in the payload so shouldn't be needed in any additional params of the setting to the TMS in question,

Many thanks,
kind regards
 

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

JoshMartin
Tera Contributor

Hello @Alex Coope - SN ! I am also having some toruble confirgruing localization.

I am working to set up a basic configuration of Localization Framework Hub and Spoke architecture. I have the appropriate plugins installed. I have determined the instances that will act as the hub and spoke.

 

As per the documentation on how to configure localization hub and spoke architecture, from the Hub Instance, I have created a new entry in the Spoke Settings table. The area I am having trouble with is configuration from the Spoke instance. The documentation does not clearly identify what information is needed to be input in the TMS Additional Info field(s) to be able to save the new entry with no errors. Any additional insight as to what these fields should be populated with to establish the connection would be helpful, thank you! 

Hi @JoshMartin,

In theory, assuming you've followed the instructions, all that should be needed is a "setting" entry in the Localization Framework so it knows to leverage the TMS flow (so it can send the LRITM's and LFTASK's to the other instance). There shouldn't be any need to do anything in the spoke itself, you'd just be adding a credential record (aka an Admin account) to the alias that's used with the spoke,

I hope this helps,

Many thanks,
Kind regards

 

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

Hi Alex,

 

By Credential Record, did you mean Spoke’s instance credential record attached with Connection & Credential record?

Since on Hub instance, we saw that for Localization Framework Hub plugin, we didn’t have any OOB Connection & Credential record.

 

Also you mentioned to Add the credential record with the Spoke instance, can you please confirm if it will be Basic Auth type, and nothing needs to be setup on Hub instance.

 

I have included a screenshot of the errror we are receiving. 

 

Thanks! 

Hi @JoshMartin,

I'm referring to steps 3 and 4 of the "spoke" configuration.

  • Navigate to the Connection & Credential Aliases table. Find and open the record named Localization Framework Hub TMS.
  • Add the connection to the hub in the Connections tab. You can enter the URL to your hub in the Connection URL field. Set authentication and other attributes appropriate to your environment.


The credential type would depend on how your instance and accounts are set up (e.g. if you are using MFA, SSO etc, so would be worth testing and trying what works best for your specific set up),

Many thanks,
kind regards 

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization