Development process organization
Glossary Item Box
Overview
When adding a new complex custom functionality to Creatio, be sure to follow the proper development process. We recommend deploying three separate environments: development, testing and operational.
For more information on organization of the project development process, please refer to the "Project Life Cycle Methodology" documentation.
The Development Environment is a separate application (or a number of applications) where a new functionality is developed. These applications must be deployed on local computers (on-site), which gives the ability to export schemas to the file system and create a new program code using different IDE. SVN version control is also highly recommended. Use a separate application and database for developing new functions. For more information about the development Environment, please refer to the "Organizing a development environment" article.
The Pre-Production environment can be a separate application where the new functions are installed and tested. Usually, the testing is done by a system analyst from the development team or the customer who ordered the development of the new functionality. If needed, the application can be deployed in the cloud or on-site.
The production environment is a separate Creatio application, in which all current user business processes are executed. If needed, the application can be deployed in the cloud or on-site mode, on customer servers.
For more information about deployment options, please refer to the "Deploying the Creatio on-site application" and "Deploying the Creatio cloud application".
The production database must never be used for development or pre-production testing. Development activities cannot be performed in the production environment.
The general development process is shown in Fig. 1.
- All development activities are performed in the development environment.
- After development is complete, the developers prepare packages with the new functions and install them in the pre-production environment.
- The new functions are then tested in a pre-production application.
- Any errors found during testing are corrected in the development environment (stage 1). When the testing is complete and all errors are corrected, the packages with the new functionality are installed in the production environment.
Fig. 1. General workflow of the development process
It is recommended to use zip-archives to transfer packages between environments. Zip-archives can be created in the [Configuration] section or by WorkspaceConsole utility. For more information about transferring changes between applications, please refer to the "Transferring changes between the working environments" article.
