Prevent Boundary / Intermediate Event Confusion

Hey guys,

just a quick suggestion about boundary events - or more accurately intermediate events that might look like boundary events. In the example below I’ve attached an intermediate event really close to the edge of the event sub-process, which makes it look like it’s a boundary event. Someone modeling might not know that it’s not allowed.

So can i suggest that you snap elements like this so that they’re inside the bounds of the event sup-process that would reduce confusion. It would also be true of pools - where you also shouldn’t have boundary events.

We have got an open issue on automatically expanding these containers to avoid this kind of situation:

Feel free to comment on the issue or create a new topic to continue discussing.