---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Attribute Mapping references

# Attribute Mapping references {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Attribute Mapping References

Attribute Mapping allows ServiceNow users to define relationships between SCIM attributes and ServiceNow table fields, streamlining resource management.
This functionality is crucial for ensuring accurate data synchronization between different systems.
Show full answer Show less  

## Key Features

* **Attribute and Sub-Attribute:** Define attributes like userName and complex types like name.familyName, with sub-attributes being optional for complex types.
* **Filter Condition:** Specify conditions for multi-valued attributes using options derived from SCIM Provider schemas, e.g., filtering phoneNumbers by type (mobile or work).
* **Database Field Name:** Map SCIM attributes directly to ServiceNow fields, allowing for dot-walking through nested structures to ensure data is correctly aligned.
* **Default Value:** Set default values for fields that return null or use hard-coded values when necessary.
* **Script:** Implement scripts to fetch attribute values, ensuring the output is formatted as a string or a JSON string, particularly for multi-valued attributes.

## Key Outcomes

By utilizing Attribute Mapping, ServiceNow customers can enhance data integrity, enable efficient resource management, and customize data synchronization processes to meet specific organizational needs. This results in improved system interoperability and user experience across integrated platforms.  
The attribute mappings enables you to use the attributes as a single source of resource
to the ServiceNow table fields.

## Attribute {#attribute-mapping-references__section_sbw_3jm_htb}

The attribute for which mapping
needs to be defined. For example, userName.

## Sub-Attribute {#attribute-mapping-references__section_o4h_cmm_htb}

Select the sub-attribute, if
any, for which a mapping needs to be defined.

For example, if there is a complex type
attribute like name.familyName, then the attribute is
name and the sub-attribute is
familyName.

For simple attributes like user name, the
Sub-Attribute value would be None.

## Filter Condition {#attribute-mapping-references__section_gfm_ymm_htb}

A multi-valued attribute can
have additional information that can be specified by using a Filter Condition. The choices
for the filter condition are populated using the schemas defined by the SCIM
Provider.

For example, the phoneNumbers attribute has multiple
types like work, mobile, home, and so on.

You can specify a Filter Condition from a
set of possible values. For example, the phoneNumber attribute can have
the Filter Condition as type eq "mobile".

The phoneNumber attribute can instead have a Filter Condition
as type eq "work".

## Database Field Name {#attribute-mapping-references__section_a1t_4sm_htb}

If the direct attribute
mapping option is chosen, then this attribute needs to be defined. The Database Field Name field represents the ServiceNow field name
that is mapped with the SCIM Attribute.

For example, the username
SCIM Attribute can be mapped to a user as the Database Table Name
field, and to the user ID field as the Database Field Name
field.

<br />

You can also dot-walk using the Database Field Name. For
example, the department SCIM Attribute can be mapped to the
Department Name field.

Here the Database Table is User and the Database field Name
is Department Name.

## Default Value {#attribute-mapping-references__section_e2t_zvm_htb}

The default value is passed to
the SCIM Provider if direct attribute mapping of that field returns null. The default value
can also be used to return a hard-coded value.

In the case of a hard-coded value, the
database table name and field name should be None.

For example,
the primary sub-attribute value of work email can be hard coded as
true.

## Script {#attribute-mapping-references__section_hpd_1wm_htb}

The script is used to fetch the
attribute value. The return type of the script should be always a string, or a JSON
converted as a string. The output of the script should be in the proper format as expected
by the provider for that attribute.

The following is a sample script for a
multi-valued attribute.

The output of the script should have a stringified JSON Array.

The following
is a sample Script of a simple-valued Attribute.

The output of the script should be a string.