While troubleshooting an apparent error just now, I noticed that all completed instances of a relatively simple process with an AND gateway had failed to execute both of its outgoing paths. The key factor here is that the process chains (unattended) all the way to a Terminate node, presumably because after the user submits their task in this subprocess, they're expected to chain into a followup task back at the parent level.
However I never realized this constraint was in place - that is, the process executes all possible chained paths (up to and including a terminate) before it will execute the other AND gateway outputs. This seems like a bug to me - but am I wrong? Has anyone else noticed this?
I was able to recreate the behavior with this very, very simplified example process, if anyone's having trouble picturing what I'm referring to:
Discussion posts and replies are publicly visible
Not realized, but not sure if its real bug.Appians defines chaining as "If the completion of a task in a process requires the same user to complete a subsequent task, you can activity-chain the two tasks together in your process model."https://docs.appian.com/suite/help/22.1/Process_Model_Recipes.html-> This means to me, that you define a "please do these tasks in priority then the rest".second - BPMN Best practice -> each AND opening gateway shall have "closing" gateway, which would mean you should have a second AND gateway before your "end event", which would solve your issue as it waits there until all flows arrived before going to the end event.-https://www.visual-paradigm.com/guide/bpmn/bpmn-gateway-types/
Richard Michaelis said:each AND opening gateway shall have "closing" gateway, which would mean you should have a second AND gateway before your "end event",
Good point, I never realized this.