Application scope

Each application has an application scope that determines which of its resources are available to other parts of the system.

Application scoping ensures that one application does not impact another application. You can specify what parts of the application other applications can access by setting application access settings.

For example, suppose you create a conference room booking application in its own application scope. By default, the application can access and change its own tables and business logic but other applications such as incident management cannot make changes to it without explicit permission. The application scope ensures:

  • The conference room booking application does not interrupt core business services.
  • Other applications do not interfere with its normal functioning.

By default, all custom applications have a private scope that uniquely identifies them and their associated artifacts with a namespace identifier. The application scope prevents naming conflicts and allows the contextual development environment to determine what changes, if any, an application developer or an API call can make to an application artifact. Application developers specify an application's scope when they create it.