One-click Deployment

<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > Initial project configuration > Deployment of processes and new versions >

One-click Deployment


Bizagi Studio presents a friendly Deployment Wizard to publish the project's Processes in a quick and online procedure.

This procedure is assisted by means of the Process Wizard, in which one-click configurations are carried out.


A deployment's configuration involves: selecting which Processes and versions of them are to be deployed, and then, choosing the target environment (Test or Production), along with other specific options for each environment.


The One-click Deployment will automatically create (in the first deployment) the target environment's components (Work Portal, database and Scheduler service).

For the next deployments, the One-click Deployment will update the new information into the target environment.



This feature is not eligible for Automation Service.

For Automation Service or any other scenarios, in which there is no online connectivity between the development environment and a production environment, Bizagi provides:

The Advanced Deployment Tool.

For more information about this tool, refer to the Advanced Deployment.

The possibility to Export processes and Import them directly in the cloud, under a similar UI and approach as that one presented by the Advanced Deployment Tool.


The options related to the objects involved in process deployment which are available in the One-click deployment are also available when either exporting to Automation Service or using the Advanced Deployment Tool.



Executing the Deployment

The one-click deployment is executed through Bizagi Studio, and launched from Step 7 of the Process Wizard (the Execute option), by selecting the Deploy Process option.


Notice that this option becomes available once there is at least one Process for which you have clicked on the Next option for the previous Step 6.





Alternatively, the deployment window and procedure can be also launched as well from the Process module (in the Expert View) by right-clicking on a specific Process version:



What happens with the existing cases?

When a deployment is executed by Bizagi, existing cases of Processes in the Development environment are not taken to the Production environment nor to the Test environment (Bizagi does not deploy values stored in master entities).


When a deployment is carried out to an already-existing Production environment, the previous cases in the Production environment will be kept consistently in that environment:


If a new Process version is deployed to Production, the existing cases will continue to work with the version they were created with.

On the other hand, new cases created in Production from that moment on will be created under the latest deployed Process version.


You may also choose to make minor changes to a Process which is already in Production (and have the existing cases take those changes). For this scenario (e.g adding a new attribute, modifying a business rule or a performer assignation), it is required to modify the current Process version and publish this version again to the Production environment in order to update these changes.



How to make a deployment?

Deployment of Bizagi Processes should be done with previous consideration of the prerequisites, and by following the recommended deployment cycle.



To review the prerequisites for a deployment of your Bizagi project, refer to Previous considerations and requirements.


Recommended deployment Cycle

The following steps illustrate the recommended deployment cycle of Processes versions:


1. First, deployments to the Test environment are to be made in an iterative way so that required additions and modifications are detected in the Test environment and these are adjusted in the Development environment.

Note that in the Development environment you may too perform quick prototyping, workflow verification and unit tests.


These iterations should be initially done without the Release Candidate mark, so that the Test environment goes under unit tests.




2. When there are no more adjustments to be made (from what was observed in the tests carried out in the Test environment), a deployment to the Test environment should be made by specifying that the Processes versions are to be marked as Release Candidate.

Should there be any adjustments required, then it is necessary to cancel the Release Candidate and perform the adjustments in the Development environment, and repeat this step.




3. Once the Release Candidate Processes versions are approved by expected test results, then this Release Candidate is applied to the Production environment.




4. Subsequent deployments for continuous improvement of the existing Processes, or to publish new Processes, should follow this same cycle.

Click for more information about Continuous improvement and development after a deployment.


Deployment to the Test environment

It is strongly recommended to perform deployments to a Test environment prior to deployments to the Production environment.


This should be done to a Test environment with similar characteristics of the Production environment, so that user acceptance tests can certify that the Processes are ready to be taken to a Production environment (their behavior, integration points and Workflows are as expected).


Click for more information about the Deployment to the Test environment and detailed explanation about the Release Candidate option.


Deployment to the Production environment

Once the deployment to the Test environment has been repeated until the Processes versions in the Development environment do not need further additions or modifications (any fine tuning or adjustments), you may deploy your Processes to the Production environment.


Click for more information about the Deployment to the Production environment.