Major - If a boundary event is changed to common one (non-boundary), creating node using quick menu is different than creating it from other nodes (without creating it as boundary first). Outgoing connection is going from events' bottom magnet and a new created node is placed farther than it should be. See shiftedNode.png picture in the attachment. Notice, that in Explore Diagram Preview it is displayed as it should be displayed also in the canvas.
- If a boundary event on sub-process is changed to common one (non-boundary) inside this sub-process, after creating any outgoing connection, sequence flow in Explore Diagram Preview is not displayed properly. See sequenceFlow.png picture in the attachment.
Stunner - Wrong creation of nodes and flows after changing boundary events to non-boundary
-
Roger Martinez
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated: