I try to figure out how I have to model a message flow to a task within a sub process. I want to have two different views of the same process:
(a) a detailed view where the sub process is expanded
(b) an overview diagram, where my sub process is collapsed
I came up wit the following solution:
I’m unsure if the collapsed version is semantically right. I fear that there will be two instances of the sub process invoked, which are not correlated. I didn’t find any clues in the spec how to draw a message flow to a collapsed sub process correctly.
Can anyone help me with this? Thanks