---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil ServiceNow AI Platform Administration
ft:clusterId :
- platadm
bundleId :
- platadm
workflow :
- Platform
---
# Normal values
# Normal values {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 2 minutes to read
Summarize
 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 Normal values
Normal values in ServiceNow standardize similar but ambiguous field values into a single, consistent value.
This is essential when data entries come from multiple sources such as Discovery, imports, or manual user input, which can result in multiple variations of the same value.
For example, CPU Type on a computer CI form might have many variants like "E3350 (Intel)" or "Intel Xeon 5.4.554" that represent the same CPU type.
Using normal values consolidates these into a single standard value like "Xeon," improving data quality and simplifying management.
Show full answer Show less
## Key Features
* **Aliases:** Short lists of known variant input values that map directly to a normal value. Aliases are processed first during normalization and are effective when variant values are few and well known.
* **Rules:** Conditions that define how to identify and normalize field values, especially useful for large or complex sets of variations. Rules are processed after aliases and can use expressions such as regex matching to cover many variants.
* **Combination of Aliases and Rules:** Both can be used together to comprehensively normalize field data based on your needs.
* **Normalized Queries:** Administrators can enable query normalization to apply normalization logic to list filters and queries, ensuring consistent results with normalized values while displaying original input values in filter breadcrumbs.
* **Scripting Support:** Scripts that insert or update records automatically normalize field values. Scripts querying normalized fields can be configured to return normalized values rather than raw variants, ensuring consistent data handling in automation and integrations.
## Key Outcomes
* Eliminates duplicate and ambiguous field values, improving data integrity.
* Enhances search quality and simplifies query conditions by using a single normalized value.
* Reduces complexity in business logic by consolidating multiple variants under one standard value.
* Supports automated normalization across system processes, including imports, discovery, manual entries, and scripts.
* Provides flexibility to handle normalization for both simple and complex data variations through aliases and rules.
A normal value replaces similar but ambiguous field values with one standard
value.
## Field value variations {#c_WhatFieldNormalizationDoes__section_qkk_3jw_x1b}
Records values can come from multiple sources such as:
* Automated entries made by Discovery.
* Automated entries made by importing records from external systems or files.
* Manual entries made by users.
{#c_WhatFieldNormalizationDoes__ul_vgd_k21_x1b}Each of these sources may describe the same field value in several different forms. For example, the CPU Type field on a computer CI form might display any of the following similar values:
* E3350 (Intel) 4.5.2234
* Intel Xeon 5.4.554
* Xeon L3350
* L3350
{#c_WhatFieldNormalizationDoes__ul_q4v_5kz_xp}
Without normalization, these variant field values results in:
* Duplicate CPU types
* Poor search results
* Complex queries and conditions to apply business logic
{#c_WhatFieldNormalizationDoes__ul_srv_q3w_x1b}
Creating a normal value record solves these issues by consolidating on one standard value such
as Xeon.
## Identifying variations with aliases and rules
Each Normal value record specifies how to identify variations of a normal value using a
combination of aliases and rules.
Aliases
: Aliases are known variations of an input value that normalization converts to the normal
value. Use aliases when there is a short list of variant values.
For example, you could create a normal value Xeon that has these aliases.
* E3350 (Intel) 4.5.2234
* Intel Xeon 5.4.554
* Xeon L3350
* L3350
{#c_WhatFieldNormalizationDoes__ul_jjc_2w1_x1b}
Whenever a normalization data job or normalized query sees a field value matching an alias, it automatically replaces the field value with the normal value. Normalization data jobs and queries process aliases before rules.
Note:
Aliases are logically equivalent to rules using the \[is\] operator in a condition where \[Field name\]\[is\]\[Alias value\]. For example, the sample aliases are equivalent to these rules: \[CPU Type\]\[is\]\[E3350 (Intel) 4.5.2234\] OR \[CPU Type\]\[is\]\[Intel Xeon 5.4.554\] OR \[CPU Type\]\[is\]\[Xeon L3350\] OR \[CPU Type\]\[is\]\[L3350\]
Rules
: Rules specify the conditions under which normalization replaces an input value with the
normal value. Use rules when there are a large number of possible variant values, or when you
must create complex conditions.
For example, the normal value Xeon could have this rule.
\[CPU Type\]\[matches regex\]\[.\*\\bxeon\\b.\*\]
Whenever a normalization data job or normalized query sees a field value matching a rule,
it automatically replaces the field value with the normal value. Normalization data jobs and
queries process rules after aliases.
Rules and aliases can be combined to normalize a field. Make sure to test your
normalization methods before applying them to all the existing records in the database.
## Normalized queries
An administrator can configure normalization to apply to queries issued against normalized
fields in lists. Select the Normalize query check box on the
Normalization form to enable this functionality. In a list containing normalized values, [Filters and breadcrumbs](https://www.servicenow.com/docs/access?context=c_UsingFiltersAndBreadcrumbs&version=brazil&pubname=brazil-platform-user-interface&ft:locale=en-US) using the original (raw) value for the normalized field in the query
condition.
The filtered list returns records with the normal value substituted for the raw value.
However, the breadcrumbs for the filter display the original query conditions.
## Scripting and normalization {#c_WhatFieldNormalizationDoes__section_cmg_5wp_x1b}
Scripts that update or insert records into the database (GlideRecord) are normalized
automatically when field normalization is applied. For example, if a script to insert a CI
record contains a CPU type of Xeon L3350, the script is normalized to
insert the CI with a CPU type of Xeon instead. Scripts that query the
database for normalized field values (using the conditions of equals or not equals) can be
configured to return the normal value (such as Xeon) rather than the
original (raw) value.
**Related topics**
* GlideRecord