Preparing processes to be exported

<< Click to Display Table of Contents >>

Navigation:  From Studio to Cloud >

Preparing processes to be exported

Overview

The following section is step number 2 to accomplish a process deployment, as described at From Studio to Cloud.

 

Check list

Before exporting processes, double check the following aspects:

 

1. 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 of, and agree which exact processes (and their versions) are to be deployed.

Ensure that the versions of these processes are all "checked in" within the development environment.

Notice that a process under a check-in status will indicates that it is not at the moment being edited, and that its implementation is completed.

Therefore, a process check-in needs to be done by the same user who was editing it last (did a previous check-out).

 

To review that a process is checked-in, go to the Expert View and into the Processes module.

Checked-in process versions should have no special marking, and just in case, right-clicking on them should present its Check-out option:

 

Deployment03_CheckedIn

 

 

Otherwise, a process which is not checked-in shows the following icon and you may right-click on it to use its Check-in option:

 

ProcessCheckIn

 

For more information about check-in, check-out options, properties and treatment, refer to http://help.bizagi.com/bpm-suite/en/index.html?processes_in_modules_view.htm.

 

2. Initial deployment parameters and records.

The following is applicable only to the very first time you deploy processes into a blank Bizagi environment.

This is so because only for a first deployment to a production environment, Bizagi will allow you to import certain definitions from your development environment as a starting point to populate data. Such definitions which are automatically included in a first deployment are:

Environment options.

Records in parameter entities.

External systems connectivity parameters.

LDAP integration connectivity parameters.

End users.

 

Therefore, consider that in a first-time deployment, you should review the settings as configured throughout the different Bizagi Studio features.

For instance, review options set for your testing and production environments so that these start off consistently to your target environment's expectations as described below:

 

2.1. Environment options.

These options consider: E-mail server settings, the  use of E-mail integration to complete activities, activation of Bizagi's web services API, custom values, and others such as the default location of attached documents:

 

Environment

 

Recall that these are set in order for the first deployment to automatically set your target environment with such values.

However, after the first deployment or at any time while that environment is live, you may modify such values by using the Management console.

To learn about more on how to modify them, refer to Environment configuration.

 

2.2. Records in parameter entities.

Records created in parameter entities will always be deployed from the development environment if such entities are not set to be manageable in the production environment.

However, for those which are manageable in the production environment, you may choose to initially populate data in the production environment by taking the same records existing in the development environment.

It is recommended to review if records being used in the development environment will be helpful as well to initially populate the production environment, by going into the Entities module:

 

 

ParameterAdministration

 

To learn more about defining or reviewing which parameter entities will be managed in production, refer to http://help.bizagi.com/bpm-suite/en/index.html?Where_to_manage_parameter_enti.htm.

 

2.3. External systems connectivity parameters.

Connectivity settings such as URLs, servers location, or credentials, can be set for any of the systems integrated by Bizagi.

Systems integrated by Bizagi include: ECMs, web services, connectors, SAP, or data repositories connected via Data Virtualization or Replication.

 

These are all configured and reviewed from the External systems module by going into details of the specific type of system:

 

ParamsExternalSystems

 

 

For example, configure or review connectivity parameters for a web service interface as shown below:

 

Interfaces

 

Recall that these are set in order for the first deployment to automatically set your target environment with such values.

However, after the first deployment or at any time while that environment is live, you may modify such values by using the Management console.

To learn about more on how to modify them, refer to Environment configuration.

 

2.4. LDAP integration connectivity parameters.

Similarly as with integrated external systems, connectivity and mapping settings regarding the LDAP user import module, can be set for testing or production environments.

This is configured and reviewed from the Security module:

 

ParamsLDAP

 

To learn about more on the LDAP import module, refer to LDAP authentication.

 

2.5. End users

A first deployment will automatically include the end users you have created in your development environment.

It is strongly recommended to review if those will be wanted in your target environment as well (i.e testing environment).

If a given user should not be wanted in the deployment, then you may disable such user:

 

DisableUsers

 

To learn more about managing end users, refer to http://help.bizagi.com/bpm-suite/en/index.html?users_administration.htm.

 

note_pin

Recall that the domain\admon user is the internal system user employed by Bizagi.
You should never disable such user, even though you may choose to limit the access rights for this account so that not all menu options are available in the Work portal for this account.

 

What should I do next?

Once you have acknowledged what you will deploy to the cloud, proceed to start a deployment process.

For information about the next step, refer to Exporting processes.