Since the introduction of Application scopes in the Fuji release, the new paradigm has introduced more contemporary application development features into the tool, making development on the platform more attractive. It started with facilitating integration with GitHub and advanced with features like delegated administration and facilitating containerisation and intellectual property protection when delivered via the ServiceNow store. It also enables protection from other applications through scoped privileges and can help package products for easy deployment neatly.

As application scopes become the norm across the platform, it is not uncommon to be working across multiple scopes to change the configuration. Take setting up the Employee Centre, for example. To modify the Service Portal record, you need to be in the Employee Center Core application scope. Want to modify the theme? Better get into the Employee Center scope. Time to create your taxonomy? You'll need to change to the Employee Center Core scope. You may also encounter similar problems when working with ETL's and Service Graph Connectors.

We do our best to make sure we are in the correct scope, but sometimes, somehow, updates from other scopes end up in Update sets where they do not belong.