<< Click to Display Table of Contents >>

Navigation:  From Studio to Automation Service >



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.




Bizagi promotes agile management of continuous improvement so you can apply changes easily on your target environment.


Bizagi Environments

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. The target environment is administered through the Bizagi Management Console Web.


Production: This is the actual operating environment in which the client's processes are available to end users. Through the Bizagi Management Console Web, 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.


Deployment Steps

Make sure that your processes are ready and then you deploy as follows:


1. Generate the deployment package: Select the processes or elements to deploy, and generate the package.

2. Apply the deployment package: Apply the package in your target environment.