Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
6 subscribers
Views
4846 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
How do you get Appian to process an OR Gateway adhering to the BPMN 2.0 standard
greggl
over 9 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...
OriginalPostID-169192
OriginalPostID-169192
Discussion posts and replies are publicly visible
Parents
0
greggl
over 9 years ago
Merging multiple incoming flows with an AND Gateway would be stuck at the gateway waiting for any flows that did not occur for that process instance. I tested that as well. In theory I can put a series of XOR Gateways in front of the AND Gateway merge mimicking the conditions of the OR Gateway split. That seems like an ugly solution but perhaps would work. Does anyone know if that is what Appian recommends to achieve standard OR Gateway behavior?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
greggl
over 9 years ago
Merging multiple incoming flows with an AND Gateway would be stuck at the gateway waiting for any flows that did not occur for that process instance. I tested that as well. In theory I can put a series of XOR Gateways in front of the AND Gateway merge mimicking the conditions of the OR Gateway split. That seems like an ugly solution but perhaps would work. Does anyone know if that is what Appian recommends to achieve standard OR Gateway behavior?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data