Create a custom translator configuration

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read

    • Configure Dynamic Translation for a third-party machine translation provider of your choice.

    Before you begin

    Ensure that the Dynamic Translation plugin (com.glide.dynamic_translation) is activated.

    Create subflows for your custom translation provider. See Integrate with a translation service provider.

    Create language code mappings as needed. For more information see Language Code Mapping in Dynamic Translation.

    Role required: admin

    About this task

    By default, Google and Microsoft translator configurations are available and ready for you to add your account details. Also by default the ServiceNow translator configuration, for language detection only, is available and active.

    However, you can also configure a custom translator with the following procedure.

    Procedure

    1. Complete the prerequisites and confirm your application scope, then navigate to All > Dynamic Translation > Translator Configurations.
    2. Select New.
    3. On the form, fill in the fields.
      Table 1. Translator Configuration form fields
      Field Description
      Name Identifier of the translator configuration.
      Active Option to activate the translator configuration.
      Version Version of the contract used in subflows.

      Version v3 is used in releases before Xanadu Patch 3. Version v4 is used in releases from Xanadu Patch 3.
      Preferences
      Choose a translate subflow Workflow Studio subflow that interacts with the translation service provider to translate the input text. Search for the subflow that you created in the previous procedure (Integrate with a translation service provider).
      Mark as default for translation Option to mark the translator configuration as the default configuration for translation.

      When no translator configuration is specified while translating the text, the default configuration is used.

      The ServiceNow translator configuration is for language detection only, so this check box is not available on that record.

      • The translator configuration must be active to be marked as default.
      • You can select only one translator configuration as default for translation.
      Choose a detect subflow Workflow Studio subflow that interacts with the machine translation provider to detect the language of the input text. Search for the subflow that you created in the previous procedure (Integrate with a translation service provider).
      Mark as default for detection Option to mark the translator configuration as the default configuration for detection (determining the language of the submitted text).

      When no translator configuration is specified while detecting the text, the default configuration is used.

      • The translator configuration must be active to be marked as default.
      • You can select only one translator configuration as default for detection.
      Language Code Mappings
      Language code mappings Mapping codes for languages to associate with the translator configuration record.
      Associate with the translator configuration record by selecting the magnifying glass icon ( Magnifying glass icon), then selecting the language code mapping.
      • Only languages for which the language code mapping was created are available for selection.
      • You can select only one language code mapping per language.

      For more information, see Create a language code mapping.
    4. Select Submit.

    What to do next

    If you are on Xanadu Patch 3 or above, and want to use Exclusion Framework in Dynamic Translation, add your translation provider's exclusion tags. For more information, see Add an Exclusion Provider Pattern.