I wonder what’s the best way to handle branch merge situations.
Imagine a flow depicted in the screenshot. You start with a decision with 3 possible branches (Case 1, Case 2, Case 3). Each branch continues with case specific Task. Where Case 1, Case 2 branch flow merges and flow continue with a joint task.
[see BPMN attachment]
Modelling this in TP proves to be cumbersome;
it requires 2 x decision group + a “synthetic” branch. Where decision expression is repeated (2x) in two different places.
From modelling prospective in TP you can’t really easily merge two flow branches unless you make some common (members) container - which needs to be defined beforehand and therefore feels a lot like Polish notation. Have I overlooked something?
[see screen shot attachment]