Delivery management process

PDF

The process of new functionality development and delivering involves the following environments:

  • Development environment.
  • Pre-production environment.
  • Production environment.

Learn more about environments in a separate article: Environments.

To avoid irregularities in Creatio and critical errors in the production environment, follow a particular action sequence when transferring the functionality between environments. View the sequence in the figure below.

1. Develop new functionality 

We recommend developing new functionality in the development environment that has a personal database for each developer. We recommend using a version control system (Subversion, Git, etc.) to transfer changes between environments.

Attention. Do not use SVN to transfer changes to the production environment. Transfer changes with SVN only in the development environment.

2. Export the package to a *.zip archive 

You can export the package to a *.zip archive in the following ways:

3. Import the package into the pre-production environment 

You can import the package into Creatio in the following ways:

  • Using the Creatio UI. This is convenient if your pre-production environment is in the cloud. To do this, follow the guide in a separate article: Delivery in Creatio IDE.
  • Using the WorkspaceConsole utility. This is convenient if your pre-production environment is on-site and you use a continuous integration pipeline. To do this, follow the guide in a separate article: Delivery in WorkspaceConsole.

Attention. We recommend using the capabilities of Creatio UI to transfer changes to the Creatio cloud. Using WorkspaceConsole is not possible because the user does not have direct access to the cloud Creatio database.

The package import procedure is different for the environment that uses a load balancer. To import the package into the environment that uses a load balancer, follow the instructions in the user documentation article: Install a Marketplace application.

If you find errors during the testing stage, improve the functionality by eliminating them. Repeat steps 1-3 after that.

4. Back up the production environment database 

Before you delivery packages that contain the developed functionality to the Creatio production environment, back up the database. To do this, follow the instructions in a separate article: Update guide. This is a required step since the functionality developed by various third parties can affect the general operativity of Creatio.

Attention. To back up Creatio cloud database, contact support. If you use Creatio on-site, back up the database on your own.

5. Import the package into the production environment 

Import the package into the production environment similar to the pre-production environment (step 3).