I see your problem.
Back in the days of using just plain old Activity Diagrams for processes, we could choose a different stereotype for the ‘complicated’ Activities, and another for the simple, leaf-level ones.
I hadn’t noticed that the EA BPMN mechanism needs to use the <> stereotype for all BPMN-type activities. A truly strange implementation.
Using a stereotype in this way really makes a mess of how eaDocX tried to do things: different stuff gets different stereotypes, and different stereotypes print differently.
I’ve racked my brains for a solution to this, but I just can’t see one.
You clearly want the ‘complex’ Activities to print their child Activities, so they need to print as ‘inline’, so they can print their diagrams as well.
And this doesn’t look so good when printing the child, simple Activities, which have no diagrams or children.
So I’m afraid you’re stuck with always printing them ‘Inline’. Using ‘Compact Document’ should remove some of the useless headings etc, but I’m afraid we’ve been bowled a googly by EA.
🙁
