Navigation: » No topics above this level«
Continuous improvement and incremental deployments
As part of continuous process improvement, Bizagi enables flexibility and evolution of your processes as your business evolves.
Sometimes this involves making changes to business data, business rules, interfaces or even changing the flow of the processes themselves.
It is strictly required that all objects in the development environment that have been already deployed to a production environment, are not deleted.
Objects being used in a production environment should not be deleted or have their name edited (the object's name is different from its display name), otherwise whenever attempting a deployment to production, Bizagi will indicate that the deployment package is not adequate (in order to guarantee data integrity in the production environment).
If you wish to stop using a certain object, such as a process, in a production environment, the proper way to do so is by disabling such object. But never delete such object in the development environment, as this will NOT mean that it will be no longer in production.
For the scenario of wanting to deprecate an entity or attribute, you will need to create a new process version which in turns, uses a different entity or attribute than the ones used before.
When to create versions for processes?
Depending on the necessary changes, it is recommended to generate new versions of processes when they have been already deployed to a production environment.
This is a safe way to make changes without compromising the information of the current cases being executed in the production environment.
When deploying a new process version, live existing cases will continue to be worked on the process version they were originally created.
However, publishing minor modifications to existing processes is also possible, in which case you may perform improvements right in the same deployed process version, so that the current cases can take those changes and adjustments.
Creating new versions
It is recommended as a good practice to version your processes when changes are made.
To do so, go into the Processes module and right-click on a specific process version to select New Version:
To view a detailed guide on when it is recommended to create new process versions, refer to http://help.bizagi.com/bpm-suite/en/index.html?guidelines_for_new_version_of_.htm
Regarding incremental deployments, it is important to note that when deploying new processes or new process versions, existing cases will continue to follow their workflow at the target environment.
This means that depending on the nature of your changes, you will need to decide if you want to employ a staging environment to validate how these existing cases will behave.
To perform incremental deployments, simply follow the same procedure as when deploying processes for the first time, even though there are some differences (mainly about certain objects which are only deployed from the development environment for a first deployment).
For information on the steps involved in a deployment, refer back to this chapter's main section at From Studio to PaaS.
Quick facts on incremental deployments
Consider these when planning your deployments to Bizagi PaaS:
•Incremental deployments to either testing or production environment will not delete existing cases.
•It is strictly required that objects in the Development Environment are not deleted (when being used in production already), and that you always create new versions of processes whenever you need to make adjustments to processes.
•We recommend scheduling and performing package Deployment during non-working hours. This promotes any contingency measure towards restoring a version, should the Deployment results not be as expected.