Bizagi Tips and Tricks

How to update an entity not related to the data model

An easy way to update an entity which is not related to the data model is to use the CEntityManager method called GetEntity. This comes in handy when the SOA layer is not accessible as this is the only way you can perform this operation.

Best Practices Bizagi

How to Keep Track of Deployments (Bizagi)

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.

Bizagi Tips and Tricks

Date, DateTime data types

Convert Date or DateTime to String data type

var sDateTimeFormatted = dDateTime.ToString("MM/dd/yyyy hh:mm");
var sDateFormatted = dDate.ToString("MM/dd/yyyy");

Or you could use String.Format

var sDateFormatted = System.String.Format("{0:d}",DateTime.Now);

Use this to convert it for XML

var dTransactionDate = DateTime.Now;
var sTransactionDate = XmlConvert.ToString(dTransactionDate, XmlDateTimeSerializationMode.Unspecified);

Dates as filters for entities

[dDateDelivered != null AND dDateDelivered >= '08/22/2019 12:00:00 AM']

Bizagi’s way

Bizagi Tips and Tricks

Escape Character in Bizagi

Use backslash (\) for string escape. See the following examples:

var sAttribute = "test";
var xCollection= Me.getXPath("entity-list(\"mEntity\", \"sAttribute = '"+ sAttribute +"' AND bActive = 1\")");
var xCollection= Me.getXPath("entity-list('mEntity','sAttribute = \"test\" ')");

Working with Excel

Conditional formatting

This can be found on the Home > Style > Conditional Formatting.

Excel Conditional Formatting

Whenever you want to want to use a formula, I found it easier to do this trick. Create the formula next to the column you want to apply the formatting. In the case below, I want to check if the value is greater than 100 (=A2>100, =A2>100 etc)

AI Resources

Free AI Training Course (Microsoft)


Microsoft and LinkedIn have joined forces to address the increasing demand for artificial intelligence (AI) skills in the workforce. With the launch of the AI Skills Initiative, Microsoft aims to provide individuals with the necessary knowledge and tools to effectively leverage AI technology. Emphasizing the importance of responsible and ethical AI use, this initiative is designed to equip participants with the skills needed for the future of work.

Bizagi Tips and Tricks

Error Could not generate assembly for

Web portal error in Bizagi

Error Type: BaseException

Error Message: Unable to process control: _. Control type: ContentPanel. Unable to process property: _. Error processing Rule = _; Error: Error Evaluating Rule _ -Error Could not generate assembly for [C:\home\site\wwwroot\App_Data\Temporary\ComponentLibrary\BizAgi.ComponentLibrary.CRuleContextJS.js]: Errors: Error Line,Column:596,26 Error Description: ‘get’ is a new reserved word and should not be used as an identifier

Best Practices Bizagi Tips and Tricks

Avoid private processes in Bizagi

Why private processes are not good?

I present two important reasons why you should not use private processes within Bizagi:

  1. Reporting Challenges: One significant problem I have encountered is related to reporting. When cases are marked as private, the information displayed in reports depends on the user running the report. If the user has access to the case, the related information will be included in the report. However, if the user does not have access, the information will be excluded. This can create complications when you have a Manager role specifically designated for reporting purposes only. In such cases, the manager needs to be granted permission to view case details in the reports using commands like “CHelper.GrantCaseAccess(Me.Case.Id, iUserId).” But what happens when a new manager is added to the role? Do you have to run the same command for all the existing cases? While it is technically possible, it would be more convenient if this process was simplified.
  2. Access Management Challenges: The second issue with private processes is related to the constant changes in personnel who require access to the cases. As roles change or new people are assigned to a particular role, the access to cases should be dynamic. However, when using private processes, manually managing these access changes can become cumbersome. It becomes necessary to constantly update permissions and ensure that the right individuals have access to the appropriate cases. This can be time-consuming and prone to errors.

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.

What should I use instead?

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.

Bizagi Tips and Tricks

Collections in Bizagi

Case Scenario: The Peer Review process

The Peer Review process in Bizagi

Process Description: The Peer Review process is a collaborative approach that involves two key participants: the Reviewer and the Developer. In this process, the Developer examines and evaluates the code created by the Reviewer. The purpose of this examination is to ensure the code meets certain standards and to identify any potential issues or areas for improvement.

Working with collections

To illustrate how easy is to work with collections I will describe the technical functionalities using the process called Peer Review.

When you must fill in a form and then save the content into a collection I suggest the following solution:

Data model: You have 2 entities Main Process entity called mPER and an entity mPERFinding. The latter has 2 relations with the former: these two are one-to-one (Finding) and one-to-many(Findings) as seen in the picture below.

Data model

The first relation is used to create the form where the user inputs the data.

The second one is to store the data each time the user completes the form.

<mPER.kmPERFinding.mPER> = <mPER>;
Peer Review workflow

Learning React

Setting up the Dev environment

npm i -g create-react-app@1.5.2

Download and install visual studio code (set the Oceanic Next theme or Ayu Mirage)

Add the extensions:

  • Simple React Snippets (developed by Burke Holland)
  • Prettier – Code formatter (developed by Esben Petersen) – File > Preferences > Settings > set this to format on save

Create your first React application

npx create-react-app <name of the app>

then from within the console navigate to the application’s folder

cd <name of the app>

and run the following command as it will ask you a series of questions. The provided answers will be used to create the package.json file.

npm init
visual studio code - learning react
npm start
react application compiled successfully
my first react application