BPMN MIWG capability demo is back! Again, we will be showcasing the interoperability of BPMN diagrams. This time our capability demonstration will not be a part of the Object Management Group conference, but it will be a standalone (online) event on July 18th, 2024 at 04:00 PM CEST.
You can register at: https://streamyard.com/watch/dAGGy6KFzb9Y
What to expect from this edition of our capability demonstration? As always, we will be working together on a set of BPMN diagrams to show that different process modeling tools can work together seamlessly thanks to the BPMN XML – shared diagram interchange format.
This year, we will be covering more advanced elements of the BPMN specification:
- Boundary events
- Call Activities and
- Event Subprocesses
Our demo scenario will be based on a process of handling credit application.
The main process (Customer Onboarding) will be created by colleagues from: MID (with tool BPanda), Camunda, Software AG (ARIS), KnowProcess, and Trisotech.
As you can see, the logic is pretty clear: after the application is received, a credit score is automatically checked and business rules are used to decide how this application should be handled.
Safe applications get automatic confirmations. Very risky applications are automatically rejected. Cases that are not obvious require a manual check, which can lead to acceptance, rejection, or special handling for fraud.
In case you are wondering: originally when we planned to show automation as a part of this demonstration, there was also some DMN used in this business rule task, but finally, we decided it would take too long and participants would not be very happy.
Apart from the main flow of the process, we also have two event subprocesses used for handling timeouts and cancellation requests.
Now, it’s time to see what happens inside the “Manual check” diagram referenced from the Call Activity in the main process.
Manual Check process will be created by: Cardanit, CaseAgile, viadee, and BOC Group (with yours truly and ADONIS).
The main flow is pretty easy: the employee needs to decide on the application. If it does not happen within 7 days, there is a timeout thrown. Yes – it is the same timeout that is handled in a main process.
However, that is not all. Apart from the main flow, we also have three event subprocesses (all non-interrupting). The first one deals with requesting documents. We will return to it in a second, since this Call Activity also has its own diagram.
The second one is meant to handle situations when we need to speed up a bit.
The last one (my favorite) is about fraud handling. If fraud is detected, an error is thrown. As you may expect, we will handle it with the boundary event “Fraud detected” in our main diagram.
Last but not least, the final diagram – Document request. It is the smallest one, so there are only two vendors involved: SAP Signavio and Omnitracker.
We do not have any event subprocesses here – only boundary events. The main flow is simple: when we need the documents, they need to be requested, and then we wait for an answer. Ideally, we get the documents and the process can finish. However, some customers may not deliver them right away, so we need the boundary events: one sends a daily reminder and the other triggers a call the customer after a week (we assume optimistically that it will suffice).
As in the previous cases, after the demo I will also add more details to this post plus embed a recording.
If you want to see the diagram interchange live plus have a chance to ask questions to the members of BPMN MIWG register for the live event: https://streamyard.com/watch/dAGGy6KFzb9Y