Deployment of processes and new versions
Once the process automation cycle has been completed, Bizagi lets you publish processes for use.
Deployment of Bizagi processes involve promoting the processes into a Test or Production environment.
Deployment should be done first to a Test environment, then optionally into a Staging environment, before moving into a Production environment.
Bizagi promotes agile management of continuous improvement.
New process versions can be released easily to respond to business needs.
An environment in Bizagi is an independent application of a Bizagi project (it has its own Work portal, Database, and Scheduler service).
By default Bizagi presents three different environments, each with its own major objective: a Development, Test and Production environment for a same project.
When using the Deployment feature it is strongly recommended to use these three environments.
•Development: The Authoring environment. This is the only environment in which processes are modeled and their implementation details are specified. Design and construction stages take part in this environment, in which the data model, the forms and the business rules are created, along with the performers, interfaces definitions and others specifications. Work in this environment takes place through Bizagi Studio.
•Test: This environment simulates the Production environment. The development team carries carry out user acceptance tests for the functionality and certification of processes. Processes in the Test environment can be marked as "Release Candidate" and locked to avoid modifications in the Development environment until the release candidate version has been promoted to Production. The target enviroment is administered through the Bizagi Management Console.
•Production: This is the actual operating environment in which the client's processes are available to end users. Through the Bizagi Management Console, management tasks and configurations can be carried out in the Production Work Portal such as editing business policies, user administration and authorization configuration, and administration for the SMTP server or ECM systems.
Process Deployment options
For assisted process deployment, Bizagi provides One-Click Deployment.
Through One-Click Deployment Bizagi automatically publishes processes into an environment different than the Development environment, and configures that environment.
Through this procedure, Bizagi automatically creates or updates that environment (i.e., sets up a production environment).
For more information about this option, refer to One-Click Deployment.
For more sophisticated scenarios, Bizagi provides an Advanced Deployment Tool. This option is useful for the following scenarios:
1. Projects requiring offline deployment.
2. Projects with many developers performing specific modifications in parallel.
3. Projects with more than three environments.
4. Projects relying on deployment software or policies in which deployment must be done manually (applying packages).
For more information about this tool, refer to the Advanced Deployment.
Before actually performing a deployment, it is important that you review Preconditions and requirements.