Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform administration
Table of Contents
Choose your release version
    Home Orlando Now Platform Administration Now Platform administration Dynamic Translation Domain separation and Dynamic Translation

    Domain separation and Dynamic Translation

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Domain separation and Dynamic Translation

    Domain separation in Dynamic Translation is configured to apply to translator configurations. With domain separation you can separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

    Support level: Basic

    • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
    • The application supports domain separation at run time. This includes domain separation from the user interface, cache keys, reporting, rollups, and aggregations.
    • The owner of the instance must set up the application to function across multiple tenants.
    Use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the client must be able to see the SP's response.

    Activation information

    You should activate the Domain Support - Domain Extensions Installer plugin (com.glide.domain.msp_extensions.installer). For information on how you can request the plugin activation, see Request for domain separation in Dynamic Translation.

    How domain separation works in Dynamic Translation

    A service provider with domain separated instances can implement the Dynamic Translation framework so that users can use the translation service providers configured in the translator configurations specific to their domain. Translator configurations are process-separated in Dynamic Translation. All translation service providers configured in the translator configurations of the parent domain are available in child domains.

    A translator configuration in the global domain is visible in all other domains. In any domain, a user can only view the translator configurations configured in the following domains:
    • Current domain
    • Parent domains
    • Global domain
    Note: If there are multiple translator configurations in a domain for the same translation service provider, the translator configuration of the current domain or the closest parent domain is considered for dynamic translation.

    Also, different connections can be configured for the same connection and credential alias of a translation service provider in multiple domains. However, Credentials and Connections are data-separated. So, a connection configured in a child domain is visible in parent domains. For information on domain separation for Connections and Credentials, see Domain separation for Credentials and Connections.

    For example, consider the following scenario:

    Figure 1. Connections for a translation service provider in multiple domains
    Screenshot of connections for a translation service provider in multiple domains
    Different connections are configured for the same connection and credential alias of Google in multiple domains. When in Domain A, all the following connections are visible:
    • Connection1
    • Connection2
    • Connection3
    Note: When multiple active connections are visible for the same connection and credential alias in a domain, the connection with the highest order is given priority when the Support Multiple Active Connections check box is selected.

    Domain-separated table

    Translator Configuration [sn_dt_translator_configuration]

    Default translator configuration for a domain

    The default translator configuration of the current domain is always considered for dynamic translation. If the current domain does not have any default translator configuration, then the available default translator configuration of the nearest parent is considered.

    A domain can have multiple default translator configurations. In this case also, the default translator configuration of the current domain is considered for dynamic translation. For example, let us consider the following scenario:

    Figure 2. Domain separation in Dynamic Translation
    Screenshot for Domain separation in Dynamic Translation

    In Domain B, both TC1 and TC2 are visible. From Domain B, TC2 is first set as the default translator configuration. From Domain A, TC1 is then overridden and set as the default translator configuration. This results in multiple default translator configurations in Domain B. In this case, when in Domain B, TC2 is used as the default translator configuration for dynamic translation.

    Overriding a translator configuration

    In any domain, you can override the translator configuration of that domain or the parent domain. The overridden translator configuration of a parent domain is also visible in child domains. However, the overridden translator configuration of a child domain is not visible in the parent domain.

    After you override a translator configuration of the same domain, only the overridden translator configuration is visible in that domain.

    After you override a translator configuration of a parent domain, the following scenarios happen:
    • Only the overridden translator configuration is visible in the child domain.
    • The Overrides field of overridden translator configuration refers to the original translator configuration of the parent domain.

    For example, consider the following scenario:

    Figure 3. Domain separation in Dynamic Translation
    Screenshot for Domain separation in Dynamic Translation

    You can override a translator configuration TC1 from Domain B. After overriding, only the overridden configuration TC1 is available in Domain B and the Overrides field of TC1 refers to TC1 of the parent domain.

    Related topics
    • Domain separation

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Domain separation and Dynamic Translation

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Domain separation and Dynamic Translation

      Domain separation in Dynamic Translation is configured to apply to translator configurations. With domain separation you can separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

      Support level: Basic

      • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
      • The application supports domain separation at run time. This includes domain separation from the user interface, cache keys, reporting, rollups, and aggregations.
      • The owner of the instance must set up the application to function across multiple tenants.
      Use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the client must be able to see the SP's response.

      Activation information

      You should activate the Domain Support - Domain Extensions Installer plugin (com.glide.domain.msp_extensions.installer). For information on how you can request the plugin activation, see Request for domain separation in Dynamic Translation.

      How domain separation works in Dynamic Translation

      A service provider with domain separated instances can implement the Dynamic Translation framework so that users can use the translation service providers configured in the translator configurations specific to their domain. Translator configurations are process-separated in Dynamic Translation. All translation service providers configured in the translator configurations of the parent domain are available in child domains.

      A translator configuration in the global domain is visible in all other domains. In any domain, a user can only view the translator configurations configured in the following domains:
      • Current domain
      • Parent domains
      • Global domain
      Note: If there are multiple translator configurations in a domain for the same translation service provider, the translator configuration of the current domain or the closest parent domain is considered for dynamic translation.

      Also, different connections can be configured for the same connection and credential alias of a translation service provider in multiple domains. However, Credentials and Connections are data-separated. So, a connection configured in a child domain is visible in parent domains. For information on domain separation for Connections and Credentials, see Domain separation for Credentials and Connections.

      For example, consider the following scenario:

      Figure 1. Connections for a translation service provider in multiple domains
      Screenshot of connections for a translation service provider in multiple domains
      Different connections are configured for the same connection and credential alias of Google in multiple domains. When in Domain A, all the following connections are visible:
      • Connection1
      • Connection2
      • Connection3
      Note: When multiple active connections are visible for the same connection and credential alias in a domain, the connection with the highest order is given priority when the Support Multiple Active Connections check box is selected.

      Domain-separated table

      Translator Configuration [sn_dt_translator_configuration]

      Default translator configuration for a domain

      The default translator configuration of the current domain is always considered for dynamic translation. If the current domain does not have any default translator configuration, then the available default translator configuration of the nearest parent is considered.

      A domain can have multiple default translator configurations. In this case also, the default translator configuration of the current domain is considered for dynamic translation. For example, let us consider the following scenario:

      Figure 2. Domain separation in Dynamic Translation
      Screenshot for Domain separation in Dynamic Translation

      In Domain B, both TC1 and TC2 are visible. From Domain B, TC2 is first set as the default translator configuration. From Domain A, TC1 is then overridden and set as the default translator configuration. This results in multiple default translator configurations in Domain B. In this case, when in Domain B, TC2 is used as the default translator configuration for dynamic translation.

      Overriding a translator configuration

      In any domain, you can override the translator configuration of that domain or the parent domain. The overridden translator configuration of a parent domain is also visible in child domains. However, the overridden translator configuration of a child domain is not visible in the parent domain.

      After you override a translator configuration of the same domain, only the overridden translator configuration is visible in that domain.

      After you override a translator configuration of a parent domain, the following scenarios happen:
      • Only the overridden translator configuration is visible in the child domain.
      • The Overrides field of overridden translator configuration refers to the original translator configuration of the parent domain.

      For example, consider the following scenario:

      Figure 3. Domain separation in Dynamic Translation
      Screenshot for Domain separation in Dynamic Translation

      You can override a translator configuration TC1 from Domain B. After overriding, only the overridden configuration TC1 is available in Domain B and the Overrides field of TC1 refers to TC1 of the parent domain.

      Related topics
      • Domain separation

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login