Layout rules
Crossings, slopes and flows through a shape live only in the DI coordinates. The XML diff looks clean, the rendered diagram knots, and no structural rule sees it. These rules decide on waypoints and bounds, never on guesswork.
A flow routed through an unrelated shape
1 finding
flow_reopenSequence flow is routed through element <serviceTask_assessTicket>
A sequence flow routed through an unrelated shape's body. Read the rule
Two flows crossing
2 findings
flow_finalizedSequence flow crosses <flow_orderRevised>flow_orderRevisedSequence flow crosses <flow_finalized>
Two sequence flows whose drawn paths cross each other. Read the rule
A flow docked onto the wrong side
2 findings
flow_toDecisionSequence flow connects to <gateway_approved> on a diagonal; a gateway must connect at one of its four tipsflow_reviseSequence flow enters <userTask_reviseOrder> from the left; an activity must be entered from the right
A sequence flow docked onto the wrong side of a shape. Read the rule
A target drawn off the row
1 finding
flow_archivedSequence flow connects <subProcess_archiveOrder> to <endEvent_orderHandled> at a different height; an outgoing flow's target should sit at the same height as its source
A flow's target drawn off the row, sloping the main path. Read the rule
A flow that runs diagonally
1 finding
flow_rejectSequence flow <flow_reject> runs diagonally; use only horizontal and vertical segments
A sequence flow that runs diagonally instead of horizontal and vertical. Read the rule
All five are non-blocking layout hints at warn in both recommended presets. See Presets.