Using Release Candidate for a deployment to Test

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Deployment of processes and new versions > One-click Deployment > Test environment deployment >

Using Release Candidate for a deployment to Test

Deployment to the Test environment presents an option to mark your Processes versions as Release Candidate.

 

Using this option will flag these Processes as Release Candidate for the Production environment, and Bizagi will give a special treatment for them in the Development environment.

 

Deployment01_ReleaseCandidateTest

 

 

 

When to mark your Processes as Release Candidate

Processes deployed to Test without being marked as Release Candidate are useful to:

 

1. Run unit tests

2. Detect possible adjustments and fine tuning.

3. Run a demo (presentation purposes).

 

When Processes deployed to Test are marked as Release Candidate, Bizagi will:

 

1. Automatically lock them in the Development environment to avoid edition.

In other words, the workflow, and other objects such as attributes, forms, etc. used by those Processes versions will not be allowed changes (until the given Release Candidate cycle has finished).

2. Keep the Release Candidate Processes "on hold", with all the necessary information of their related objects to be deployed to Production.

 

 

note_pin

if you need to do any adjustments in the Processes, canceling the Release Candidate is required.

Then, executing the Test deployment with the Release Candidate mark and with the adjustments should be repeated until Processes are certified.

 

 

How does Release Candidate work?

Processes marked as Release Candidate will have their objects locked in the Development environment as detailed at Continuous improvement and development after a deployment.

 

Once the deployment to the Test environment is done with the Release Candidate mark, users involved in the Test environment should carry out their tests to approve those Processes versions (and certify that they can be deployed to the Production environment).

 

 

Within the user acceptance tests, any flaws detected in the Processes version or any additional requirements asked for them, will need to be adjusted in the Development environment.

Therefore, to carry out these modifications it will be necessary to go to Bizagi Studio's Deploy Process option and Cancel the current Release Candidate.

 

Deployment_W10_Cancel

 

Canceling the current Release Candidate will prompt for confirmation:

 

Deployment_W12_CancelWarn

 

Once this is canceled and the necessary modifications are made in the Development environment, a new deployment to Test environment should be carried out again as Release Candidate.

This procedure should be repeated until the user acceptance test are completed and no modifications or adjustments are required for these Processes versions.

 

This way, by going into Bizagi Studio's deployment option again, you may choose to Apply the current Release Candidate in the Production environment.

Doing this, will launch a deployment to the Production environment with those Processes already approved and certified.

 

Deployment_W11_Apply

 

Summarizing this concept, when there is a current Release Candidate in the Test environment, the Deploy Process option of the Process Wizard's step 7 (Execute) will prompt to either: Apply the Release Candidate (that is, to deploy those Processes version to Production), or to Cancel it (in which case you could make changes in the Development environment for those Processes, and a new deployment to Test would be required afterwards).