Source: Blume ( Steffen)
Please excuse that i ask this question by opening this bug report. SInce i wasn't able to find a definite answer to the given question in the specification, it may more be a bug in terms of an missing clarification, which seem to lead to the situation, that certain software providers handle the use of a XOR Join Gateway in a way, that seem to be redundant, from a strictly logical perspective, by stating the use of a XOR Gateway without the following mandatory use of a XOR Join Gateway as an error.
There seem to be two different understandings of the handling of the XOR Join gateway. The Majority seems to state, that using this in general would be the best practise, whereas I think, that the logical aspect should be paramount. (Form follows function). That is why I was starting to research for an official explanation.
So, could the OMG point out:
A: Which possible Situation could logically justify the existance of this element?
B: What a desired best practice in the use of this element would be?
Thank you very much for your help
Reported: BPMN 2.0.2 — Wed, 26 Feb 2020 09:28 GMT
Updated: Wed, 26 Feb 2020 17:34 GMT
BPMN21 — Is there a definite reason to exist for a XOR join gateway?
- Key: BPMN21-426
- OMG Task Force: BPMN 2.1 RTF