How do you get Appian to process an OR Gateway adhering to the BPMN 2.0 standard

greggl over 8 years ago

How do you get Appian to process an OR Gateway adhering to the BPMN 2.0 standard? In BPMN 2.0, utilized by Appian, an Inclusive OR Gateway specifies that one or more of the available paths will be taken. They could all be taken, or only one of them. And when a 2nd OR Gateway is used to merge the paths, the OR gateway explicitly requires that all paths that were activated must be completed prior to continuing in the process.The behavior allows for implementing process flows where 0 to many paths may be taken and then whichever ones were taken for each process instance, they must all be completed before the process continues.

Appian adheres to the BPMN 2.0 standard for the OR Gateway split, but for the OR Gateway merge, it is not adhering to the standard and waiting for the all the instances to complete. My testing and Appian Docs at link below confirm this by stating "When multiple flows enter an OR node, the Gateway node pauses after the first in...

Discussion posts and replies are publicly visible

Parents

0 Tom Ryan
Appian Employee
over 8 years ago

I think that you should be able to achieve this requirement by adding a pv that tracks the number of optional flows that are active (coming out of the OR). Then, you can wait for that many flows to arrive at the complex gateway before proceeding.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Tom Ryan
Appian Employee
over 8 years ago

I think that you should be able to achieve this requirement by adding a pv that tracks the number of optional flows that are active (coming out of the OR). Then, you can wait for that many flows to arrive at the complex gateway before proceeding.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data