BPMN modeling elements
This section gives an overview of the BPMN modeling elements (source: BPMN 2.0 specification) that are used in the example in the next section.
BPMN modeling elements plotted on Blueriq concepts
The following table shows the BPMN modeling elements plotted on Blueriq concepts.
| BPMN | Blueriq |
|---|---|
| Event | Event |
| Task | Task |
| Collapsed Sub-Process | Process |
| Normal flow | Process line |
| Message flow | Message event |
| Pool | Case |
| Lanes | Roles |
BPMN example
The example shows a collaboration with two pools. The two pools communicate through message flows with each other.
Blueriq example process cases
The collaboration is split in two process cases that still talk to each other via message events.
Researcher
Subsidy party
Blueriq message event
So the BPMN specifies that message flows must not connect between two objects within the same pool. A pool is a process case in Blueriq concepts and a message flow is a massage event in Blueriq concepts.
So it is not allowed to send a message event from within a process case to a process case with the same type.
Known issues
| Issue number | Issue | Expected fix version |
|---|---|---|
BQ-3171 | It is possible to use the AQ_ThrowMessageEvent service in a task to send a message to a process with the same type. Studio doesn't give a validation error on this | R11 |
| BQ-3219 | Throwing a message event to a process with a started task that doesn't apply case locking leads to a double tasks in the database. | R10 |
| BQ-3220 | User ends a task, without case locking, while other user has a task, without case locking, started. This leads to a double task in the database. | R10 |
Overview
Content Tools