When working on a Bizagi project, sometimes you need to clean cache and temporary folders. The reason for this action is that the web application caches the content. So in this situation, all the changes you’ve made are not shown in the Work Portal. This can happen on changes you’ve made on forms, expression rules, or when you’ve changed environment parameters and many more.
Categories
Trace method
The ability to trace information in order to test your code is highly important. After many years of working with Bizagi, I have developed an quite interesting method of tracing the data.
All files are saved in the Trace folder and each case has its unique trace file. I don’t have to mention the usefulness of this approach because it’s quite obvious. Whenever you have to check something related to a particular case, you jump to the Trace folder and search using the case number.
Custom Bizagi widget
The widget works for all the below scenarios:
- I agree to terms and conditions…
- I accept the terms and conditions…
- I confirm…
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.
Bizagi code (my version)
The below code helps you trace the location of any uploaded document in Bizagi:
var uploadPath = CHelper.getParameterValue("uploadPath");
var IdEntity = CEntityManager.GetEntity("entity-name").Id;
var IdAttribute = CEntityManager.GetEntity("entity-name").Attributes["attribute-document-name"].Id;
var SurrogateKey = <entity-name.Id>;
var WholePart = (SurrogateKey - (SurrogateKey % 1000)) / 1000;
var bizagiFilePath = uploadPath + "\\" + IdEntity+"\\"+ WholePart +"\\"+ SurrogateKey +"\\"+ IdAttribute;Custom Bizagi widget
An organizational chart, also known as an organigram, or organizational breakdown structure, is a diagram that displays the structure of a company and the relationships and relative ranks of its parts and positions.
Custom widget
Recently, I had to work on a more complex widget. The requirement was to have a custom questionnaire loaded into the Bizagi form. As you know, Bizagi doesn’t have a form control for that so I had to put my mind to building one.
The challenge came when I had to understand how the widget works with Bizagi. The documentation is not great, but with whatever I found on Bizagi’s website and the source code from all the available widgets, I managed to understand a little bit.
With this knowledge and all my JS previous experience, I cracked it.
Custom widget
Out of the box, Bizagi provides a wide list of UI form controls like buttons, date pickers, text boxes, and so on. Unfortunately, the list is not complete so in this case, if you need a more complex control you can build one of your own and extend the form’s functionality using Widgets.
In my situation, I needed to use a simple HTML code to separate two sections horizontally.
Bizagi Work Portal
The Work Portal is a secure web application/portal developed by Bizagi where the business applications that have been previously designed, are presented to end-users.
By accessing the Work Portal, the business users can create new cases, work on pending activities, generate custom reports, and so on. Overall, they work with the data coming from the designed business applications.
Both elements are extensions to the BPM 2.0 standard and were introduced in Bizagi starting with version 11.0
What is a Conditional activity
As Bizagi defines it, Conditional activities are enabled or disabled during the course of a case instance depending upon a business condition. They represent a user task that when enabled is allocated to an end-user.