Delivery using the Configuration section
Creatio provides various functionality delivery tools.
The delivery management tools are as follows:
- Creatio IDE
- WorkspaceConsole utility
This article covers the feature delivery using Creatio IDE.
The functionality transfer options in Creatio IDE depend on the stage of the delivery process.
In general, the ways to transfer solutions using Creatio IDE are as follows:
- Transfer packages as archives if you need to transfer complete functionality between the environments.
- Transfer packages using the SVN version control system if you need to transfer functionality that is incomplete or under development.
- Transfer configuration element schemas if you need to transfer functionality that is incomplete or being refined.
Transfer the package
To transfer a custom package, export the functionality as a package from a development environment and import the package into another development environment. You can also transfer the package between development environments in multi-user development mode.
Export packages in the Configuration section of the System Designer. The package is downloaded as a *.zip archive that contains the *.gz package archive.
Import packages in the Installed applications section of the System Designer. The import procedure is similar to installing Transfer your first application.
You cannot transfer the Custom package between Creatio instances.
You can also download the *.gz package archive from the database or SVN repository using the WorkspaceConsole utility.
Do not create packages in a production environment, then create a development environment based on the production environment, refine the functionality of the packages in the new environment, and transfer them back to the production environment.
Transfer a package using SVN
The version control system is an optional Creatio component. Use a version control system if you need to develop custom configuration in parallel with running Creatio normally. Version control system is required for multi-user development.
Creatio IDE supports the SVN version control system. SVN lets you transfer changes between development environments.
The special aspects of using SVN to transfer changes are as follows:
- You can transfer both packages and configuration element schemas between development environments.
- You can transfer the bound package data. For example, the lookup content, new system settings, demo section records, etc.
- You do not need to install the dependent packages manually. Creatio will install them automatically from SVN.
- You do not need to contact support when transferring changes in Creatio on-site.
Use the SVN version control system only to transfer changes between development environments. Do not use SVN in a preproduction or production environment. This may negatively affect Creatio performance or render the application inoperable. Learn more: Version control in Subversion.
Back up the database before updating Creatio from SVN. If you use Creatio in the cloud, contact support and ask them to back up the database for you.
Transfer the configuration element schema
To transfer schemas, export a schema from a development environment and import it into a pre-production environment. You can also transfer schemas between development environments in multi-user development mode.
You can transfer configuration element schemas:
- To pass an incomplete schema from between developers since committing unfinished functionality to the version control system is not practical.
- To save intermediate development results when a version control system is not used or has a malfunction.
- To transfer the schema between development environments quickly.
The special aspects of transferring configuration element schemas are as follows:
- You can replace the contents of a single schema.
- You can only export and import schemas. Follow this procedure to transfer packages: Transfer packages.
- You must have Creatio administrator permissions.
- You can only upload one schema at a time.