After the Task 1 is completed, we need to spawn an optional task, based on a condition. The process completion does not depend on this optional task completion.
What is the correct way to design this model ?
There are basically three BPMN activity types: BPMN Task. BPMN Sub-Process. BPMN Call Activity.
The BPMN standard allows for multiple start and end events to be used at the same process level. There a few reasons why the business analyst may use multiple start or end events, but caution must be used to avoid mistakes.
In BPMN, a sub-process is a compound activity that represents a collection of other tasks and sub-processes. Generally, we create BPMN diagrams to communicate processes with others. To facilitate effective communications, we really do not want to make a business process diagram too complex.
An intermediate event is any event that occurs between a start and an end event. The intermediate event circle has a double line, and the event can catch or throw information. Connecting objects indicate the directional flow, determining whether the event is catching or throwing.
the desired behaviour can be modeled like this:
After Task1 completes Task2 is triggered, if the optional Condition is true, the optional Task is triggered as well. The Instance is terminated after Task2 is finished. If the optional Task was still active it will be terminated.
You should use conditional marker for the optional flow. Exclusive gateway in your diagram will always execute mandatory Task 2, optional task will always be ignored even when the condition for its execution is true.
Parallel gateway can not be used as it will wait for the optional task to complete for successful merge.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With