Bizagi is a very peculiar tool when it comes to deployments and if you are not well organized, things can go south pretty quickly.
In my current project, the production environment is in use 24/7 and the opportunities for a new release window are slim to none. So, imagine having issues in production just because you forgot to import the values of a new parameter entity.
To avoid all this trouble, plus to keep track of all the objects that were deployed (what, when, where – the holy trinity), I’ve come up with an easy solution, all in an Excel file.
The Excel Template
|Package Name||Enter the name of the package. As a best practice, name the package as follows: [acronym of the project]_[project name]_[release version]|
The release version is built as follows: [major release].[minor release]
The minor release gets incremented every time the package is pushed to TEST.
The major release gets incremented every time the package is pushed to PROD.
|Date Create||The date when the package was created|
|Deployed to Test||Yes/No|
|Date Deployed (Test)||The date when the package was deployed to Test|
|Deployed to Prod||Yes/No|
|Date Deployed (Prod)||The date when the package was deployed to Prod|
|Object Type||This is related to the next column (Objects to export/import). For any release, in Bizagi you might need to import the values of a parameter entity managed in prod or to set the value of a business policy.|
|Objects to export/import||The name of the object|
|Items to check||The list of things you must check. E.g set the security for xyz, check the job scheduler etc.|