Is it possible to do something so that for each chosen sequence at the inclusive gateway, the process continues along that flow until it hits the join on the right side?
For those branches with two user tasks in a row, I would prefer that those tasks are actually shown one after another, rather than the breadth-first way that it is done now.
Thanks in advance
No, that would mean the engine low-level operations need to be changed. The engine cuts up the process execution into small chunks (so-called ‘operations’) that get planned on an agenda. Each parallel path will progress these chunks and plan new operations to continue, switching between branches.
What’s your use case for this? In the example above the engine will stop execution once the tasks have been all reached (and the order of creating them shouldn’t matter).