Application Basics & Scope Concepts

ServiceNow application scope allows admins to create simple packaged files that are easy to transfer and manage. 

In this topic, we will highlight the importance of an application and its scope. We will also highlight the different global and scoped applications. By the end, we will explore the reasons why scoped applications are secure and a better option for admins. 

What is an Application?

Application in ServiceNow is a distributable package of configurations. Meaning, for an admin, it helps move multiple changes in forms, scripts, or ACLs as a single file instead of update sets. 

Applications are also called deployment containers. These are used to install, upgrade, and uninstall large feature sets in an atomic manner (either all files move or none). It is an admin’s responsibility to check that all important fields are associated with the correct application scope to avoid application failure. 

For example, a customer needs a new contract management system. Instead of using 15 update sets to move the changes, the admin will publish the contract management app to the app repository. 

These applications are like ZIP files: you do not have to manage each file; instead, you move the entire ZIP file. 

Now that we understand the ServiceNow application, it is time to move on to the application scope and how it differs from global applications. 

What is an Application Scope?

Application scope is like a workspace boundary. For admins, the scope picker helps in choosing where new records go and what can be edited. Whenever you are creating something new, it is important to check the application picker. It has to be set to the scoped app, not Global. 

If the table is created with the wrong scope, it will not be packaged with the correct application, breaking the deployment strategy. 

In the application Scope, there are two major points to remember:

1. Always confirm the custom table name; it must start with the right scope prefix. 
2. Always use the application picker while working in the main UI. 

It is obviously important to choose the right scope as it determines the application lifecycle. The main options are global and scoped applications. 

Global vs Scoped Applications

The ServiceNow environment offers two primary zones: Global Scope, which is the default for applications like ITSM, and a scoped application, which is a custom-built application. 

1. Global Scope Application: It is a default area for base applications. At a global scale, applications can generally see everything that exists. It is like a shared environment that increases the risk factor. 
2. Scoped Application: An isolated environment that helps create custom-built applications with their own private namespace. These applications are protected from changes made in the system.

Scoped applications are more secure than global applications. Let us move forward and understand why.

Why are Scoped Apps more secure?

As scoped applications are isolated and custom-built, data is secured within their respective namespace boundaries. Apart from these, there are a few more reasons that make scoped applications safer, like: 

1. Cross-Scoping Access: It is available on the application access tab. It blocks attempts to modify data through external scripts. 
2. Data Isolation: For all application scopes, the settings can have read and write access. It prevents all other applications from reading confidential data. 
3. Delegated Development: In application administration, non-admin users can be given permissions to do small tasks. It helps reduce the workload for admins and also avoids the risk. 
4. IP Protection: When publishing to the app repository, source code is obfuscated/protected. It prevents customers from modifying or stealing the core application logic. 

What’s Next? 

As we understand the applications so well, it is time to get practical. In the next topic, we will focus on the steps to create a new application from scratch and the naming convention for ServiceNow scopes.