SoftOne ConsultancyBizagi 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.
I present two important reasons why you should not use private processes within Bizagi:
Considering these challenges, I strongly recommend avoiding the use of private processes in Bizagi. Instead, it is advisable to explore the following alternative approach that offers more efficient and dynamic ways of managing reporting and access permissions within the system.
I strongly recommend utilizing visibility rules on the summary form instead. By implementing simple expressions that evaluate whether a user’s role matches certain criteria, you can determine whether they should have access to the summary page. For example, if a user has the role of Manager, you can allow access to the summary page. On the other hand, if the user has a different role that shouldn’t have access to the case, you can restrict their access.
Visibility rules based on user roles are straightforward to manage and modify in the future if needed. If there are changes to the roles or access requirements, you can easily update the expressions without extensive manual adjustments. This flexibility ensures that the access permissions remain aligned with the evolving needs of your organization.
By utilizing visibility rules, you can simplify the process of controlling access to the summary page in Bizagi. It provides a more efficient and dynamic approach compared to using private processes.
In Bizagi, we refer to process instances as cases and present them to end users. By default, we assign an internal sequence for numbering each case and display it as the “Case Number”. This ensures that each case is uniquely identified and eliminates the possibility of duplication or conflicts. However, you can customize the numbering sequence to meet your specific needs. We also recommend using prefixes when using sequences to prevent duplication in case numbering. We allow you to define customized sequences, including prefixes and suffixes, for all or some of your processes.
There are many definitions for best practices, but the one that I like the most is the following:
A best practice is a method or technique that has been generally accepted as superior to any alternatives because it produces results that are superior to those achieved by other means or because it has become a standard way of doing things […]
Wikipedia
Have you ever wondered what is the proper way to cancel a case in Bizagi? When I first started working as a technical BPM consultant, I learned to cancel the case using the following workflow pattern:
At the beginning of the process, you add a parallel gateway. One path takes the normal flow, while the other one goes into this cancel logic: an Intermediate event followed by a Terminate event.