$(document).ready(function(){highlight();});

Preparing a solution to be exported

<< Click to Display Table of Contents >>

Navigation:  From Studio to Cloud >

Preparing a solution to be exported

Overview

Once you have completed the business automation cycle with Bizagi Studio, Bizagi offers you the possibility of exporting applications and deploying them in Bizagi Cloud for their test and execution in the Testing and Production environments provided in the solution.

 

Deployment00_Overview

 

Bizagi promotes agile management of continuous improvement. New application versions can be released easily to a Test and then to a Production Environment. For a full explanation of the environments in the cloud, please refer to the Project and Environment management article.

 

Export process check list

Before exporting applications you should check the following:

 

Processes to export must be checked-in

Make sure you coordinate the deployment with all team members of your project, so they are all aware and agree which Bizagi Processes versions will be deployed.

 

Ensure that the versions of the processes you plan to include in the export are all "checked in" in the Development Environment. To do so, select the Expert View in Bizagi Studio and click the Processes module. All of the processes you wish to be deployed should be checked-in.

 

Deployment03_CheckedIn

 

Review Parameter entities management

Each parameter entity has, in its advanced properties, a definition that states if that particular entity is designed to be managed in the Production Environment or the Development Environment. It is therefore recommended to review in depth which parameter entities’ values require deployment into the Cloud’s Production Environment.

 

Please note that a parameter entity cannot be managed in both Development and Production Environment; it is necessary to select one environment to manage (insert, edit or disable) the entity’s values.

 

ParameterAdministration

 

For the first deployment, all the values for the parameter entities can be taken from the Development Environment into the Production Environment (regardless of this definition).

In further deployments, when the Production Environment already exists, only the values of parameter entities which are managed in the Development Environment are updated and taken into the Production Environment.

 

For more information about defining or reviewing parameter entities managed in production, please refer to Where to Manage parameter entities.

 

Check all Environment options

In the Development Environment, you can set the values for the environment options that will apply to the Test and Production Environment.

 

Environment

 

You can modify these values directly in the Cloud by using the Environment Console.

Click here for more information about Environment configuration.

 

Check Interfaces Properties (Systems)

When defining an interface (for a web service invocation), you can define its initial property values for each environment (e.g. URL, method, authorization credentials, logging threshold).

You can modify these values directly in the Cloud using the Environment's Console.

 

Interfaces

 

 

 

 

Review authentication and LDAP settings

Update configuration for LDAP  authentication using the Security module for the Authentication options and LDAP synchronization. Initial values set in Bizagi Studio are taken to Bizagi Cloud. These can be changed using the Environment Console.

 

Security

 

Organization definition

The definition of the elements in your organization that will be involved in the project (such as areas, positions, skills, roles, user groups, etc.), is done only in the Development Environment.

User groups, can be edited directly in Testing and Production Environment, where you can include or remove users for a particular user group. In Bizagi Cloud it is not be possible to create new user groups or delete existing ones.