nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Behaviour Parallel Gateway without Join

rodolfobarbeiro

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?

parallel_gateway.png

Find more posts tagged with

Comments

ronald_van_kuij

Why don't you give it a try 😉

rodolfobarbeiro

I tested!

All tasks are executed.

trademak

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,

andregs

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.

trademak

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,