Behaviour Parallel Gateway without Join
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2011 02:08 PM
See the BPMN diagram in attachment:
[attachment=0]parallel_gateway.png[/attachment]
Note that the execution flow is divided by a parallel gateway and each path finish in a "EndEvent."
What is the execution behavior of this flow?
Only runs the "Service Task 1"?
Only run the "Service Task 2" and "Service Task 3"?
Or all tasks are executed?
Or error occurs on deployment?
[attachment=0]parallel_gateway.png[/attachment]
Note that the execution flow is divided by a parallel gateway and each path finish in a "EndEvent."
What is the execution behavior of this flow?
Only runs the "Service Task 1"?
Only run the "Service Task 2" and "Service Task 3"?
Or all tasks are executed?
Or error occurs on deployment?
Labels:
- Labels:
-
Archive
parallel_gateway.png
13 KB
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2011 02:23 PM
Why don't you give it a try 😉
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2011 03:19 PM
I tested!
All tasks are executed.
All tasks are executed.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-17-2011 04:58 AM
This is not really valid BPMN.
When you are using a parallel gateway to start multiple sequence flows I would also expect a parallel gateway to join these sequence flows.
I your example all tasks are executed because each sequence flow runs in its own process execution scope.
Best regards,
When you are using a parallel gateway to start multiple sequence flows I would also expect a parallel gateway to join these sequence flows.
I your example all tasks are executed because each sequence flow runs in its own process execution scope.
Best regards,

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2012 02:24 PM
According to BPMN Method & Style (Bruce Silver, page 29):
Each outgoing path thus represents a parallel (concurrent) thread of process activity. Parallel paths may be joined downstream or may lead to separate end events. Each parallel path must reach an end event in order for the process or subprocess complete.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2012 07:14 AM
Hi,
Right, you CAN do it like this, but then all tasks are executed and the two execution paths eventually end in their own end event.
Best regard,
Right, you CAN do it like this, but then all tasks are executed and the two execution paths eventually end in their own end event.
Best regard,
