---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Exclusion Framework in Dynamic Translation

# Exclusion Framework in Dynamic Translation {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Exclusion Framework in Dynamic Translation

The Exclusion Framework in Dynamic Translation allows you to preserve specific text, such as product names and technical terms, during the machine translation process.
By specifying words and patterns that should remain unchanged, you ensure clarity in the translated output.
Show full answer Show less  

## Key Features

* **Rule Types:** Supports Exact Match (specific terms) and Pattern Match (regex) rules for exclusions.
* **Default Activation:** Automatically activated with an upgrade to Xanadu Patch 3 or higher when Dynamic Translation is enabled.
* **Configuration Options:** You can add custom exclusion rules and review existing records in the Exclusion Rules table.
* **Domain Separation:** Each domain can have its own exclusion rules, allowing for tailored translation management.

## Key Outcomes

With the Exclusion Framework, you can expect that specified terms will be shielded from translation, appearing in their original form within the translated text. This ensures that critical terminology remains intact, enhancing communication clarity across multilingual environments.

To configure this feature, check the Exclusion Provider Pattern table for your translation service's tags, and test your exclusion rules for effectiveness.  
Preserve text such as product names or technical terms during machine translation. With Exclusion Framework in Dynamic Translation, you can specify words and patterns that should not be translated.


Exclusion Framework is a set of rules ensuring that your designated text bypasses the machine translation process and appears unchanged in the resulting output. Dynamic Translation applies Exclusion Framework rules to
your text before submitting the request to your machine translation provider. Two types of rules are supported: Exact Match (specific terms) and Pattern Match (regex).

## Examples of text to consider for exclusion from machine translation {#dyn-translation-exclusion-framework__section_uxl_xjv_bdc}

In response to your organization's business requirements, you can create Exclusion Framework rules for text strings such as the following. {#dyn-translation-exclusion-framework__table_cqf_zfy_cdc__entry__2}

| Rule type | Examples |
|-|-|
| Exact match | * Product or company names * Acronyms, stock ticker symbols * Technical terms or identifiers * Terminology that has unique meaning in your organization {#dyn-translation-exclusion-framework__ul_vzb_bgy_cdc} |
| Pattern match | * Case numbers, incident numbers * KB article numbers * Sys IDs {#dyn-translation-exclusion-framework__ul_slr_fgy_cdc} |
[Table 1. Exclusion rule examples]

{#dyn-translation-exclusion-framework__table_cqf_zfy_cdc}Review your organization's glossaries and taxonomies to identify candidates for exclusion.

## Activating Exclusion Framework {#dyn-translation-exclusion-framework__section_en2_2vv_bdc}

An upgrade to Xanadu Patch 3 or higher, when Dynamic Translation is active, includes activation of Exclusion Framework by default.  
Note:  
Dynamic Translation requires a Professional or above subscription. For information see [Activate Dynamic Translation](https://servicenow-prod.fluidtopics.net/CS81kgEsj8nkdwmGh4U5Lg "Activate the Dynamic Translation plugin (com.glide.dynamic_translation) to enable all the required APIs.").

An upgrade to Xanadu Patch 3 or higher also converts the Dynamic Translation flows from v3 to v4. The v4 flows contain subflows for working with Exclusion Framework. Translator configurations available by default are automatically upgraded to v4. For more information, see [Migrate customized Translator Configurations to v4 flows](https://servicenow-prod.fluidtopics.net/TUwO2W2HyaN3a0F2a3Whhw "Migrate your customized translator configurations to v4 flows. Version 4 flows for Dynamic Translation are available from the Xanadu Patch 3 release.").

A system property in AllDynamic TranslationProperties enables you to activate or deactivate Exclusion Framework: sn_dt.dynamic_framework.enable_exclusion_framework.  
Exclusion Framework appears as a module under Dynamic Translation.Figure 1. The Exclusion Framework module

By default Exclusion Framework provides several exclusion rules, and you can add your own rules during configuration.

## Configuring Exclusion Framework {#dyn-translation-exclusion-framework__section_njh_qrc_cdc}

Because Exclusion Framework is activated by default you can complete its configuration as follows.

1. Ensure that your third-party machine translation service has an active record in the Exclusion Provider Pattern \[sn_dt_provider_exclusion_pattern\] table. If you have chosen a custom translator service you must input their exclusion tags. For information see [Add an Exclusion Provider Pattern](https://servicenow-prod.fluidtopics.net/_2Lm7KD6hP~nBT7ZEtEP5Q "As part of the configuration of Exclusion Framework in Dynamic Translation, enter the tags used by your translation provider to mark text that should not be machine translated.").
2. Review any existing records in the Exclusion Rules \[sn_dt_exclusion_rules\] table to check whether they are appropriate for your needs. Rules that are provided by default can be deactivated by clearing the Active check box, but they can't be edited.
3. Add more exclusion rules according to your organizational requirements. For information see [Add new rules to Exclusion Framework](https://servicenow-prod.fluidtopics.net/qkvSE8RhximveAffB~zUcA "Add terms and patterns that shouldn't be machine translated to the Exclusion Rules table. You can create either exact match rules or pattern match rules, and you can edit your rules later.").
{#dyn-translation-exclusion-framework__ol_nbp_wkx_cdc}

## Exclusion Framework's operational process {#dyn-translation-exclusion-framework__section_uc3_f4w_cdc}

After configuration, Exclusion Framework's subflows operate within Dynamic Translation. The Exclusion Framework process is outlined as follows.

1. Exclusion Framework searches the original text (before translation) to find any matches to terms and patterns that are active in the Exclusion Rules table.
2. Any matches are wrapped in exclusion tags. These tags are pulled from the relevant record in the Exclusion Provider Pattern table.
3. The tagged text is submitted to your machine translation provider.
{#dyn-translation-exclusion-framework__ol_y54_n4w_cdc}Text that is wrapped in the exclusion tags is shielded from translation. It is written into the translation results in its original language, so the output contains unmodified text embedded in translated text.

## Domain separation support in Exclusion Framework {#dyn-translation-exclusion-framework__section_hkh_lsv_bdc}

Exclusion Framework supports domain separation. Each domain on an instance can have its own set of Exclusion Framework rules, so the rules apply at the domain level. Within a domain, each rule must be unique. Create rules in the domain where you want them to operate.

When multiple domains exist on one instance, Exclusion Framework is activated on all domains. Deactivating Exclusion Framework on a per-domain basis isn't supported. As an alternative, deactivate every rule in a domain where you want Exclusion Framework to be inactive.
* **[Add new rules to Exclusion Framework](https://servicenow-prod.fluidtopics.net/qkvSE8RhximveAffB~zUcA)**   
  Add terms and patterns that shouldn't be machine translated to the Exclusion Rules table. You can create either exact match rules or pattern match rules, and you can edit your rules later.
* **[Test Exclusion Rule](https://servicenow-prod.fluidtopics.net/HZOP1BaVUj~nJ3Dr9hhqVA)**   
  Test Exclusion Rule in Dynamic Translation enables you to test your exclusion pattern manually. You can check whether the pattern accurately excludes a text string from translation.
* **[Add an Exclusion Provider Pattern](https://servicenow-prod.fluidtopics.net/_2Lm7KD6hP~nBT7ZEtEP5Q)**   
  As part of the configuration of Exclusion Framework in Dynamic Translation, enter the tags used by your translation provider to mark text that should not be machine translated.

*[\>]: and then