Tenant Developer

A Tenant developer in the CALS Tenant environment primarily works in the Sandbox environment, where all configurations must be done. Content developed in the Sandbox environment is deployed through Check-in and Deploy, and the implemented content is verified in the Sandbox Application.

Tenant developers mainly customize applications to meet customer's requirements. When adding screens, components, controls, menus, etc., that are not present in the App Application, it is recommended to use Extension Columns or Extension Tables if possible, or request the application developer to add the necessary tables or columns to the database.

Similar to the App environment, business functions can be implemented using CALS Extensions (refer to the CALS Extension documentation).

INFO

Unlike Application Lambda, Server Scripts can only be written with the following restrictions: They must be based on the Business Objects created in the current Tenant. They can only be selected for use before or after the three common lambdas (CommonSelect, CommonSave, CommonDelete) are executed.

After provisioning to the Sandbox is complete, a separate deployment must be carried out to complete the deployment to the Tenant Sandbox. Similarly, since automatic deployment does not occur in the Prod environment, publishing must be done from the Sandbox Studio after provisioning to the operational environment is complete to finish the deployment to Prod.

The customized content in the Sandbox can be verified after Check-in and Deploy. If there are no issues in the Sandbox Application, it can be deployed to the Prod environment through Publish.