Application scoping
Package your work into scoped apps with clear boundaries, namespaces and APIs.
Scoped applications are how you package custom development so it is isolated, portable and safe. Every scoped app has its own namespace (like x_acme_travel), its own tables and files, and explicit rules about what it may touch outside itself. This is the modern default, the opposite of dumping everything in the Global scope.
- Why scope matters
- Scope and the API surface
- Tie-in with delivery
- Try it Yourself
Scoped applications are how you package custom development so it is isolated, portable and safe. Every scoped app has its own namespace (like x_acme_travel), its own tables and files, and explicit rules about what it may touch outside itself. This is the modern default, the opposite of dumping everything in the Global scope.
Why scope matters
- Isolation, your app can't accidentally break another; cross-scope access is opt-in.
- Namespacing, tables and script includes are prefixed, avoiding collisions.
- Distribution, scoped apps publish to the ServiceNow Store or an internal repo.
- Governance, runtime access to other scopes is controlled by cross-scope access records.
Scope and the API surface
Tie-in with delivery
Scoped apps travel between instances via update sets or, better, source control, which is where DevOps and CI/CD pipelines take over.
▸ Press Run to execute.
Runs in a sandbox in your browser. Mock gs and GlideRecord and sample data are provided.