Is it possible to change the scope of an application after it is created?

Is it possible to change the scope of an application after it is created?

• A. True
• B. False
• C. Only during development
• D. Only when the app is deactivated

Answer: (B)

The scope of an application is the unique namespace that isolates all of its artifacts in ServiceNow. This scope is created with the app and is effectively fixed after that point because it determines how tables, scripts, and other components are named and resolved, as well as how security and packaging are handled. Changing the scope would mean renaming and re-linking every artifact and dependency, which the platform does not support. Therefore, once an app is created, its scope cannot be changed. If you need a different scope, you must create a new app with the desired scope and migrate the elements into it using appropriate transfer methods (export/import, update sets, etc.). The idea that you can change the scope during development or only when the app is deactivated isn’t supported.

The scope of an application is the unique namespace that isolates all of its artifacts in ServiceNow. This scope is created with the app and is effectively fixed after that point because it determines how tables, scripts, and other components are named and resolved, as well as how security and packaging are handled. Changing the scope would mean renaming and re-linking every artifact and dependency, which the platform does not support. Therefore, once an app is created, its scope cannot be changed. If you need a different scope, you must create a new app with the desired scope and migrate the elements into it using appropriate transfer methods (export/import, update sets, etc.). The idea that you can change the scope during development or only when the app is deactivated isn’t supported.