Guidelines for new version of a Process

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Deployment of processes and new versions > Continuous improvement and considerations for incremental Deployments  >

Guidelines for new version of a Process

Overview

The management of Process versions offers the client the possibility to flexibly implement the improvements that result from the performance analysis of the Processes and the company’s continuous improvement process.

 

The developments and improvements of the Processes in Production must be evaluated before implementing them to define whether they require the creation of a new version of the Process in order to guarantee the compatibility of the functions in Production, that is, open cases must end with the version of the Process they were created in.

 

When to create a new version?

In-flight Process instances will keep running in the version they were created. When a new version of a Process is taken to production, new instances will be created in the new version.

 

The following table lists some common scenarios of required adjustments to Processes in Production.

 

NEW VERSION REQUIRED

NEW VERSION NOT REQUIRED

Any change in the Process flow: include or delete shapes in a Process flow, change names of shapes, change task duration, automatic notifications, etc.


To include or delete attributes (or controls in forms) that will be evaluated later in a business rule.

To include or delete attributes in forms with no relevant information, or information that will not be evaluated in a business rule.

To change rules that will be evaluated at a certain point of the Process and can produce errors for in-flight cases.

To change rules that have no impact (will not produce errors) to in-flight Processes.

Changes On Enter, On Exit, On Save actions or business rules that determine the routing of the Process workflow.

Changes On Enter, On Exit, On Save actions that do not affect the Process logic.

Sub-Process configuration


New path added to the Process after Inclusive or Exclusive Gateways.


 

Recommendations

The following steps must be performed prior the generation of a new version of the Process:

 

1. Evaluate if you need a new version of a Process according to the guidelines above and regarding what you can edit in a production environment directly, as described at Continuous improvement and development after a deployment.

 

2. Bizagi allows you to clone a Process to start a new Process based on a the existing one.

If you need to improve the last (newest) version of a Process, then create a newer version of the last version.

You may also consider cloning a process to create a different new one, but based on common things with another.

 

3. Ensure your process is not checked-out by any user before creating a new process version. For more information, refer to Process in Expert View.

 

4. It is recommended to take backups of the database before creating a new process version.

 

Considerations

1. Bizagi will duplicate the process components such as Forms, Policies, Expressions, Vocabulary, Templates and elements in every process version/copy created.

 

2. Bizagi will share the same definition for Global Vocabulary, Expressions and Policies between the different process versions/copies. Thus, they will not be copied. The existing ones will be shared.

 

3. When you clone a process with multiple versions, Bizagi will only clone the last process version; previous versions will be ignored.

 

4. During the creation of a new version or during the cloning of the process, end users cannot use the Work Portal because all services will be stopped.

 

Creating a new version of a Process

1. In the Expert View right-click on the version of the Process you want to version.

Click on the New Version.

 

Deployment06_NewVersion

 

2. A new window will display the structure of the application that contains the Processes. Select the exact version of the Process or Processes that will be generated as a new version.

 

Deployment07_NewVersion

 

3. We strongly recommend to click on the Advance button on the bottom left corner.

This will allow you to create new versions of the Sub-Processes.

The new Process version will use the new Sub-Processes and the new forms version with the purpose of preserving the previous versions intact.

 

Deployment08_NewVersion

 

4. Click on New Version to start creating the new version of the Process.

A warning message will be displayed. Click on OK

 

Deployment09_NewVersion

 

A small window will display the status of the Process.

 

Deployment10_NewVersion

 

As soon as the Process is finished you will be prompted with a message. You are now ready to work on your new version through the Wizard view.

 

note_pin

Only the objects related to the process are copied: Phases, Activities, Transitions, Intermediate Event, Forms, Rules etc. Shared objects are not copied: Entities (Attributes), Entity Forms.

 

If the Process failed to complete you will be prompted with a window displaying the messaged found. You need to correct the error and start again.