Application Scope

• Every application has a scope
• Determines which of its resources are available to other applications
• Once scope is assigned to an application, it cannot be changed!

• Scope protects an application and its artifacts from damage to, or from other

  applications

• Must be configured to grant other applications the ability to act on its

  records

Baseline applications provided by ServiceNow (e.g. Incident, Service Catalog, Service Portal, etc...), as well as any custom application built prior to the Fuji release are in the Global scope. It is difficult to protect/isolate application data in the Global scope.

There is no migration path to a custom or different scope.

TIP FROM THE FIELD

Turn on the Show application picker in header developer setting so you can easily switch between application scopes using a drop-down on the Header bar.

1. Select the Settings icon located on the right-side of the banner.
2. Select Developer.
3. Select Show application picker in header.
4. Use the Application drop-down list to switch between application scopes.

Artifacts

Artifacts are the application files in an application. Examples include, but are not limited to, Tables, Access Controls, Email Notifications, Data Policies, Client Scripts, Business Rules, Script Includes, etc...

Application developers specify an application scope when they create a new application. They can also specify what parts of an application are accessible to other applications from:

1. The Custom application record.
2. Each application Table record.

For example, suppose you create a Travel & Expanse Management application. By default, the application can access and change its own tables and business logic, but other applications in the platform cannot unless you grant them explicit permission to do so.

Application scope ensures

1. The application does not interrupt core business services.
2. Other applications do not interfere with its normal functioning.

Scope Namespace Identifier

• The system automatically prefixes a namespace identifier to scoped application artifacts (including scripts)
• Cannot be changed or removed to ensure they are always associated with the proper application

Example of namespace identifier: x_cld_traveI_ExpensesReqBy

The application scope prevents naming conflicts and allows the contextual development environment to determine what changes, if any, are permitted.

Applications in the Global scope do not append a unique namespace iden fier to the application name.

Updating Scripts in Another Scope

1. Out-of-scope scripts are read-only
2. Select the here link to temporarily switch scopes

Built-in limitations prevent developers from updating artifacts while in a different scope. This protects the application from inadvertent modifications.