Bizagi generates new versions periodically which include great new features.
It is strongly recommended to upgrade your project to the newest release, so that you can enjoy all the benefits of Bizagi new features, enhancements, major improvements and bug fixes.
The newest versions for all Bizagi editions are available for download directly at www.bizagi.com.
You may also get Bizagi Studio prompt about the new version release (if your installation settings are configured to check for updates).
Development Environment - Bizagi Studio upgrade
To upgrade your project to the newest release, you will need to first upgrade your Bizagi Studio installation.
This procedure is as simple as uninstalling first Bizagi, regularly through the control panel options:
And then, installing the newest version.
Take into account that after upgrading the Bizagi Studio version, you should always reboot the server.
For doubts regarding the installation process, refer to Quick start installation and setup.
If the project is configured for multiple users (in a teamwork collaboration setup), you need to perform the Bizagi Studio and project upgrade in the central Bizagi Server (where the project is hosted).
Upgrading a Bizagi Studio project is a really simple procedure, which mainly involves an upgrade to the database and some other steps to upgrade other involved components as well (such as the Work portal).
These steps are all assisted by Bizagi Studio.
Before you continue, consider the following:
The project upgrade considered in the next steps apply for a version upgrade.
If you have a Bizagi 11.0.x version, follow the next steps.
Otherwise and if you have a 10.x Bizagi version or an older one, please read about Upgrading to Bizagi version 11.0.x.
2. Processes deployment on same Bizagi versions
If you have not yet deployed your project into a Production environment, you may disregard this consideration.
Otherwise and if your project has been already published into a Production environment, then acknowledge that upgrading your project in the Development environment will eventually require that you also upgrade your project in the Test and in the Production environment (required just before you perform a deployment).
The upgrade procedure is done separately for each environment, but always carried out first in the Development environment.
Do not upgrade your version if you have a pending Release Candidate to deploy into Production.
You will need to have first applied that Release Candidate or to cancel it.
If you have doubts on this consideration, please contact our support team.
3. Taking backups
We recommend taking a backup of the current project files and its database.
Even though Bizagi automatically generates a backup before upgrading a project, you may create your own backups for these components: the Database, the complete folder structure where the project files are installed (i.e, the Work portal files).
Project files involved are those in the WebApplication and Scheduler folder at the project root (by default at C:\Bizagi\Projects\[your_project]).
•If using a local SQL Server instance, the database files will be stored at this same root, under the Database folder.
•If a SQL Server instance is involved but it is set in a database server (remotely), then the backup is stored at that SQL Server's instance backup path (usually a path similar to this one: C:\Program Files\Microsoft SQL Server\[SQL_version_id]\MSSQL\Backup).
•If an Oracle database is used, the backup will be stored at the path defined as BA_BACKUP_PATH, set when configuring Oracle to work with Bizagi.
In case you need the automatic backup files of the project, they will be stored at the Backups folder inside of the project's root:
Upgrading the project
Once you have installed the latest release of Bizagi Studio at the machine hosting your Bizagi project, follow the next steps.
1. Open Bizagi Studio and open the project.
You may directly do this from the list of projects initially displayed in the window:
If the project is not listed, then you may use the All Projects option:
2. Confirm by clicking Yes when prompted about the project's upgrade:
Make sure you coordinate with any team member and notify that you will be upgrading the project.
In this way you also ensure that no other team member is currently working on the project or has Bizagi Studio opened.
3. When the upgrade is finished your project will open in Bizagi Studio.
At this point your project has been upgraded to the new version.
4. Afterward, and if you have any other team members working on this same project, you may have them upgrade their Bizagi Studio installation.
Only when you have verified that your Development environment processes behave as expected, you may then upgrade your Test environment to deploy your processes into tests.
Test and Production Environments - Upgrading Bizagi Management Console
Once you have successfully verified that your processes behave as expected in the development environment, you may upgrade your other environments (first test, then the production replica environment if you use it, and finally, production).
For the test and production environments, the upgrade is done by following a similar procedure to that one carried out in development, and under the same recommendations.
The overall procedure would be:
•Take backups and plan the upgrade previously.
•First install Bizagi Management Console in its release that matches the Bizagi Studio used by your development environment.
Take into account that after upgrading the Bizagi Management Console version, you should always reboot the server.
•Upgrade the project by using Bizagi Management Console.
•Verify that the processes behave as expected.
If you have manually installed and configured Bizagi in a test or production environment (as described at Configuring Bizagi operating environment), then you should contact our support team to carry out your version upgrade (which will be a manual procedure).