Skip to content

App

The App environment is used for developing new applications. It is where you create general-purpose applications and upgrade them according to business needs and improvements. Based on the applications created in the App environment, Tenants are generated. In the generated Tenant, the separated applications are customized and implemented according to specific requirements, and then used by end users. Therefore, applications implemented in the App environment need to be written in a general-purpose manner.

The content developed in the App environment is deployed to the other three environments (Dev, Sandbox, Prod) through a process called Provisioning. During deployment, any changes to the database are extracted and deployed as DDL statements.

The provisioning process of the CALS environment involves first generating meta information from the developed content in the App environment. This meta information is first deployed to the Dev environment. If there are no issues after deployment, it is then deployed to the Sandbox environment, which includes each Tenant. Finally, it is deployed to Prod following the same process as for Sandbox.
Note 1. In the Sandbox and Prod environments, separate permissions and tasks such as Deploy and Publish are required for each Tenant.

If there are conflicts between the content developed in the App environment and the customized content in the Sandbox during the deployment process, the content developed in the Sandbox takes priority.

Note 2. This application criterion applies to storage units such as Component and Control in CALS.

When a Tenant is first created in the Sandbox, it is created based on the currently deployed application from the App environment. Newly created objects in the App environment are also applied to the Tenants in the Sandbox and are deployed with released permissions. After provisioning, each Tenant can decide whether to use the new objects and adjust the permissions accordingly to use them in the Sandbox Tenant.