1.6.0 Deployments

Deployments and Imports

Abbreviations, used in manual:

QG - Quality Gates

EF - Execution Flow

RDA - Reference Data Administrator

FW - Form Wizard

DD - Drop Down

One of the main Best Practices suggested when working with quilliup is maintaining at least 2 working environments, for example: Development (DEV) and Production (PROD).

This way Users can implement Tests on the DEV environment without touching the PROD environment.  

After testing is complete, Users can deploy all necessary objects from DEV to PROD.

It is possible to transfer every entity (e.g.: Tests, EFs, FWs, DDs, Scripts, even whole Projects).

Pay Attention:

- It is possible to use Deploy\Import process in order to transfer entities between Projects in the same environment, but when transferring an entity from Project 1 to Project 2- the entity will be automatically removed from Project 1 (every entity has a unique ID).

- When deploying or importing, the schema name must be exactly the same in both DEV and PROD environments.

For example: the schema name in the development environment is quilliup, and similarly in the production environment.

General information on Deploying and Importing

Deployment is enabled when configured in the target environment, while Import is enabled when configured in the source environment. These tools allow users to share and reuse system elements across different environments.

All objects in the system support deployment and import functionality. As a result, deployment status and pending imports are available for each entity throughout the application (i.e. Users/Groups will be deployed and pending at the Administration module, Tests and EFs will be deployed, and pending at the QG module, etc.).

Deployments grid:

Imports grid:

Pending Imports for the module can be also accessed by choosing the import icon in the toolbar in the upper right corner:

The Deployment and import together allow the user to move packages between environments like Test, Dev, etc.

There could be two Import cases:

- Import into the same environment - the whole package will be transferred from the first/source Project into the second/target Project and will be deleted from the first/source Project.

- Import into another environment - the whole package will be transferred from the first/source environment into the second/target environment and won't be deleted from the first/source environment.

In order to perform the process, please follow the related manual:

How to implement Deploy/Import

Note: This process is identical to both QG and RDA modules.