Configure Localization Framework (LF) and Dynamic ... - ServiceNow Community

Configure Localization Framework (LF) and Dynamic Translation (DT) on instance

nilimadesai
ServiceNow Employee
ServiceNow Employee
‎10-05-2021 03:07 PM

Localization Framework (LF) and Dynamic Translation (DT) Overview:

Localization Framework helps to standardize and enhance the translation process of supported artifacts such as ServiceNow®Service Catalog items and ServiceNow®Virtual Agent topics across the platform through configurable workflows.

Dynamical translation allows to automatically translate text entered in an application, such as a user-entered text on forms for a seamless localization experience.

This blogs details how LF and DT can be activated and configured on an instance so that it can be used for applicable translation use cases such as Virtual Agent, Catalog, and NLU Model translations. 

Configure LF and DT on instance:

LF offers three different modes for content translation. Either of the below three modes can be used by the  localization fulfiller to translate the content and fulfill the localization request. 

  1. Machine Translate 
  2. Send to TMS 
  3. Send via Email 

LF and DT Plugin requirements:

  1. Platform plugin: Localization Framework Installer (com.glide.localization_framework.installer). 
  2. Platform plugin: Dynamic Translation (com.glide.dynamic_translation). 

We will first go through steps involved for configuring DT i.e; activating Translation service providers like Google Cloud and Microsoft Azure in the instance to enable machine translation of content on the instance, then discuss LF configuration settings.  

Configure DT settings:

Translation Service Providers like Microsoft, Google and IBM via spokes help to translate the content using DT. These spokes provide sub-flows and actions to dynamically detect the language of the text and translate the user-entered text using the translation services. 

Translator service spokes (Install any of the translation provider used for Machine translations): 

    • Google Cloud Translator Service spoke (sn_google_trans).
    • Microsoft Azure Translator Service Spoke plugin (com.glide.microsoft_translation_spoke).
    • IBM Watson Translator Service Spoke plugin (com.glide.ibm_translation_spoke). 

This article shows how Google Cloud Translator and Microsoft Azure Translator spokes can be configured on the instance. 

Setup Google Cloud Translation: Google Cloud Translation can dynamically translate text between thousands of language pairs. Translation lets websites and programs programmatically integrate with the translation service. Translation is offered in various editions (Basic or Advanced) with their own pricing plans.   
[ Overview ]    [ Editions ]    [ Setup ]    [ API ]     [ Pricing ] 

Store App plugin required: Google Cloud Translator Service Spoke (sn_google_trans). 

Activate Cloud Translation API in Google Cloud: 

    • Go to Navigation Menu -> APIs & Services -> Dashboard
    • Check if 'Cloud Translation API' activated, if not click on 'Enable APIs and Services'.
    • Search for 'Cloud Translation API' and select it from the search results.
    • Enable the API (Select appropriate pricing plan). 

     Set up Google Cloud Translator Service spoke in ServiceNow: Follow Set up Google Cloud Translator Service spoke (Product doc) or Integrating with Google Cloud Translator (YouTube) 

     Activate Google for DT on instance: 

    • Go to Dynamic Translation -> Translator Configurations.
    • Select Google.
    • Select the Active checkbox.
    • In the Preferences section, choose a translator as default either for translation or detection, or for both.
    • At a given time only one Translator configuration can be default. 

 

Setup Microsoft Azure Translation: 

Plugin required: Store App: Microsoft Azure Translator Service Spoke plugin (com.glide.microsoft_translation_spoke). Installed automatically with DT plugin. 

 Activate Azure Translations in Microsoft Azure and Set up Microsoft Azure Translator Service spoke in ServiceNow:  Follow Integrating with Microsoft Azure translation service (YouTube) 

 Activate Microsoft for Dynamic Translation: 

    • Go to Dynamic Translation -> Translator Configurations.
    • Select Microsoft.
    • Select the Active checkbox.
    • In the Preferences section, choose a translator as default either for translation or detection, or for both.
    • At a given time only one Translator configuration can be default. 

 

Setup a Translation service provider of your choice: We can create a custom Translation service provider to detect and translate the text dynamically. For this we need to create subflows to detect the language of the input text, and translate the input text using IntegrationHub subflows, actions, and connections and credentials.  

For creating subflows, we can refer to the existing subflows if required. For example, Detect Language (detect_language_v3) and Translate Text To Multiple Languages (translate_text_to_multiple_languages_v3). For more detailed info check Integrate with a translation service provider and Create a translator configuration. 

 

Configure LF Settings:

We can define translation and workflow preferences for one or more activated languages with Localization Framework Settings. Before we define the translation and workflow preferences, ensure to activate all the required languages in the instance to define the localization preferences. For more information, see Activate a language. 

Check below doc for help with setting up Translation and Workflow preferences for one or more activated languages where we consider the use of ‘Machine translate’ in Translation preference form. 

  • 2,837 Views
2 Comments