1.3.7 Environments

Environment settings are essential for configuring the system to deploy and import application objects.

We recommend maintaining separate environments for testing (Development) and production use (Production). This architecture can be expanded to align with your organization's database and ETL environment structure, ensuring consistency across systems.

The environment is a path/location where Deployment packages are created, as well as the definition of which operations (Deploy/Import) are allowed within this environment.

Defining Environment

Adding target environments that can be used for Deploy from the current environment.

The number of environments that can be created is unlimited.

click "Add Environment" button and fill in the details:

Name - environment name.

Description - a short text describing the purpose of the target environment.

Path to Deploy - the path to the target folder in which the deploy package(s) will be created.

Allow Deploy - if marked the current environment can be used for Deploy.

Allow Import - if marked the current environment can be used for Import.

Note: an environment can be used for both Deployment and Import by using the same mounted folder or using separate/different folders and operating a manual/scheduled move procedure (usually relevant when the Production environment is completely separated and cannot be accessed).

For detailed information about Deploy/Import, please refer to the related manual: How to implement Deploy/Import