Deployment of processes and new versions
Once the process automation cycle has been completed, Bizagi offers the possibility to publish such processes for their execution.
Deployment of Bizagi Processes consists of promoting the processes into a Test or Production environment.
Consider that deployment is done first to a Test environment and then into a Production environment.
Bizagi promotes agile management of continuous improvement.
New process versions can be released easily when driven by business needs.
An environment in Bizagi is defined as an independent application of a Bizagi project (meaning, that it has its own Work portal, Database, and Scheduler service).
By default Bizagi presents 3 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 the Processes are modeled and their implementation detail is 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 and interfaces definitions, amongst others. This environment is worked through Bizagi Studio.
•Test: This environment is used to simulate the Production environment. It is used to carry out the user acceptance tests for the functionality of the Processes (certification of the Processes). Processes in the Test environment can be marked as "Release Candidate" so that these Processes are locked (avoiding modifications in the Development environment). It is administered through Bizagi Management Console.
•Production: This is the actual operating environment in which the client's Processes are operated by end users. Through Bizagi Management Console, management tasks and configurations can be carried out in the Productive Work Portal such as: editing business policies, users administration and authorization configuration, and administration for the SMTP server or ECM systems, amongst others.
Process Deployment options
For assisted process deployment, Bizagi promotes the One-Click Deployment.
Through the One-Click Deployment Bizagi will automatically publish the processes into an environment different than the Development environment and configure such environment.
Through this procedure, Bizagi will automatically create or update that environment (i.e., set up a production environment).
For more information about this option, refer to the One-click Deployment.
For more sophisticated scenarios, Bizagi provides an Advanced Deployment Tool. This option is useful for the following scenarios:
1. Projects requiring an Offline Deployment.
2. Projects with many developers performing specific modifications in parallel.
3. Projects with more than 3 environments.
4. Projects relying on deployment software or policies in which deployment must be done manually (i.e, apply packages).
For more information about this tool, refer to the Advanced Deployment.
Before actually getting into performing a deployment, it is important that you acknowledge previous considerations and requirements.