Navigation: » No topics above this level«
Once the process automation cycle has been completed, Bizagi Studio offers the possibility to publish such processes for their execution.
Deployment of Bizagi processes consists of promoting the processes you choose (or process versions) into a Test or Production environment.
Recall that Bizagi Studio handles all these environments directly in the cloud.
Before you continue
Keep in mind that in order to conduct successful process deployments, it is strongly recommended to:
1. Ensure you have a project leader role to drive process deployments.
It is recommended to establish a project leader role who is in charge of knowing the overall project status and which processes/versions roll along with each deployment package.
Such project leader should be able to coordinate the deployment with all involved users and for instance consider that access to the Management portal is needed when actually applying the deployment package into the test or production environment.
2. Plan process deployments accordingly within your team.
It is important that you follow well-defined procedures for these types of tasks, so that deployments are scheduled and coordinated with other communicated team members; and similarly communicated to UAT users if publishing to a test environment or to end users if publishing to a production environment.
It is recommended to perform deployments to a production environment at non-busy system hours and consider a maintenance time window.
Creating a deployment package
The first step needed to deploy, is to create a deployment package, which is a file generated by Bizagi with a .bex file extension.
To create the deployment package, go to the process wizard in Bizagi Studio and locate the 7th step named Execute.
In there, click the Export .bex file option:
In the appearing Export window, ensure you tick those process versions you want to include in the deployment package:
Note that you may: define advanced settings for this package (using the Advance button to define which Bizagi metadata objects to include exactly), force additional objects into the package through the Define process dependencies option, or include Experience design definitions (e.g stakeholders, contexts, etc) by using the Experience components button.
When done, click Export and define where to save the .bex file:
A successful file creation will prompt you when finished.
To view full detail about these above options, refer to the From Studio to PaaS document.