search

bpmn-io / bpmn-auto-layout

Layout BPMN diagrams, generating missing DI information.
https://bpmn-io.github.io/bpmn-auto-layout/
52 stars 41 forks source link

Merging two boundary events causes issues with grid and connections #79

Open till-stadtler opened 1 month ago

till-stadtler commented 1 month ago

Describe the Bug

image There seems to be a serious issue when trying to merge to boundary events into an element.

Steps to Reproduce

  1. https://bpmn-io.github.io/bpmn-auto-layout/
  2. Model the process shown above.

Expected Behavior

I expect this process to be layouted cleanly.

Environment

https://bpmn-io.github.io/bpmn-auto-layout/

abdul99ahad commented 1 month ago

Adding to ready state. Just to confirm, is this the realistic use case where both the intermediate events are directed towards single end event?

till-stadtler commented 1 month ago

It does not need to be an end event. It can be any element: image

Thus, if you have two types of events (message + message, message + timer,...) that are followed by the same element, this error will occur.

This happened to our AWS colleagues while testing the BPMN co-pilot.