---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Application properties

# Domain separation application properties {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

The Domain Separation plugin has two new tables to give service providers more
flexibility in customizing their applications that use domain separation. These tables are the
System Application Property table \[sys_application_property\] and the System Application Property
Value table \[sys_application_property_value\].

## New tables offer more options {#ds-application-properties__section_jd4_mmq_jlb}

With service provider (SP) applications, certain actions can vary depending on the domain.
However, the ServiceNow® base system System Properties \[sys_properties\]
table is not domain-separated, so it doesn't satisfy the requirements for applications that
use domain separation.

Each SP customer may want to customize their applications differently. Previously, features
that could be customized were defined as only one global value. Application developers need
a more flexible table. Now you can modify your application without having to create code
every time you want to add or change the functionality.

## How overrides work in the new tables {#ds-application-properties__section_cvt_bly_llb}

Developers typically use the ServiceNow System Property
\[sys_properties\] table to create various functions in applications. If you wanted to develop
an application to behave differently in different domains, you'd have to customize it
yourself.

In the Paris release, the new Application Property \[sys_application_property\] table
simplifies that customization. Instead of going directly to the System Property table for a
value, the application property table goes to the System Application table first. This new
table now stores the logic that you require to configure your application. If it finds a
property in the new table, it uses that content. If there is no information in that table,
it moves on to the base system properties table.

When you configure support for domain separation, you can add domain logic to this new
Application Properties table. This table can contain properties that don't exist in the
System Properties table. Or you can add properties to the configuration table that can
override any property that you select in the System Properties table.

For example, let's say that you want to configure an application with a First day of the
week feature. Sometimes, you might want the first day of the week to be Sunday. In other
cases, you might want the first day of the week to be Monday. In the base system table,
there might be only one Day 1 option, which is Sunday. With the new table, you can store
another property, making Day 1, Sunday, and a child domain, Monday.

This figure shows how the system draws properties from the Application Property table
before going to the System Property \[sys_properties\] table.

## How scoped apps work in the new table {#ds-application-properties__section_b5m_bpy_llb}

The new
Application Properties table is supported from scoped applications. The application property
name, similar to the system property name, is unique, which means that it is prefixed with
the scope name if it is not global. The scope of an application impacts your configuration.
The scope may determine which Day 1 is defined as Sunday and which as Monday. You can use
the same property but customize it so that Day 1, Sunday is the parent domain and Day 1,
Monday is the child domain. In the new table, there is both a domain column and a scope
column, so you can set these properties for each.

You can use the Expand Domain Scope
view in the sys_application_property_value table to show all overrides, as shown in the
following image.  
Hinweis:  
If those tables are not available, make sure that you have activated the Domain Extension
Installer (com.glide.domain.msp_extensions.installer) plugin.

## New application property tables {#ds-application-properties__section_j3c_smq_jlb}

The new System Application Property \[sys_application_property\] table contains these
fields:  
* name
* description
* type (choice of string, true\|false, integer, time zone, color, and so on)
* default_value
* property (reference to sys_properties)
* usage_notes
* read_roles
* write_roles
* unique key: (name)
{#ds-application-properties__ul_w4h_k4j_nsb}  
The new System Application Property Value \[sys_application_property_value\] table contains these fields:

* sys_application_property (ref to sys_application_property)
* sys_domain
* sys_overrides
* value
* unique key: (sys_application_property, sys_domain)
{#ds-application-properties__ul_ynp_h4q_jlb}

## New APIs {#ds-application-properties__section_ijt_mrq_jlb}

The new APIs are also supported in scoped apps. Domain-separated application properties
have distinct APIs. The GlideApplicationProperty API has two new scriptable methods,
available in both global and scoped applications. See [GlideApplicationProperty - Scoped, Global](https://www.servicenow.com/docs/access?context=GlideApplicationProperty&version=australia&pubname=australia-api-reference&ft:locale=en-US) to learn more about these new APIs.
**Zugehörige Konzepte**   

* [Use domain selection menus](https://servicenow-prod.fluidtopics.net/5lq_NwJ8EP4zYUSLwjSUnA "The instance offers domain selection via two menu formats.")  
**Zugehörige Verweise**   

* [Domain separation recommended practices for service providers](https://servicenow-prod.fluidtopics.net/PFPBfqQYeA_4Q9vVvFyyvw "You can create, implement, and maintain domain separation for your applications and services.")