Application Scopes

Application scoping protects applications by identifying and restricting access to available files and data

Applications developed prior to application scoping are in the global scope

All custom applications have a private scope that uniquely identifies them and their associated artifacts

• App A
  • Table A
  • UI Policy A Business Rule Al
  • Business Rule A2
• App B
  • Table B
  • UI Policy B
  • Business Rule B1
  • Business Rule 82

Administrators can specify what parts of an application are accessible to other applications from the custom application record and each application table record.

For example, suppose that 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 not applications unless you give them 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, are permitted. Application developers specify an application scope when they create an application.

  The global scope is a special application scope that identifies applications developed prior to application scoping or applications intended to be accessible to all other global applications.

  The system adds a namespace identifier to the front of application artifacts such as tables scripts and configuration records.