Repository navigation
CASE (enumeration split): no way to choose which side of the decision each outcome flow leaves from #1587
Description
mxcli 0.26.0. CASE $E WHEN A THEN … WHEN B THEN … WHEN (empty) THEN … END CASE stores the outcome flows' OriginConnectionIndex by WHEN order only: 1st = 0 (top), 2nd = 1 (right), 3rd = 2 (bottom); with 4 or more outcomes 0, 1, 1, …, 2. @position does not change it. @anchor(from: right) before the CASE (and the true:/false: forms) is accepted and ignored; @anchor(A: (from: right)) is refused with MDL092; @anchor(from: …) on the first statement of a WHEN only affects the flow out of that statement.
Studio Pro draws a line by its stored sides, so the flows leave the diamond at the top and bottom and loop around it.
Wanted: a per-outcome form, e.g. WHEN A THEN @anchor(from: right) … or @anchor(A: (from: right), (empty): (from: bottom)) on the CASE, and/or a default that is not WHEN-order based (values right, (empty) bottom).
Repro: create enum M.E (A, B), microflow M.F ($E: M.E) with the CASE above (A, B, (empty), each with a LOG), then mxcli bson dump -t microflow -o M.F and read the OriginConnectionIndex of the three CaseValues flows (0, 1, 2).
Activity
github-actions commentedon Oct 19, 2026
Issue Triage
Summary:
The user reports that mxcli incorrectly assigns OriginConnectionIndex values to CASE outcome flows based solely on WHEN order, causing the generated flows to leave the decision diamond at unintended sides.
Checklist (bug report)
mxcli 0.26.0M.E (A,B), microflow with CASE, runningmxcli bson dump -t microflow -o M.F@anchoror CASE‑level mapping) or a default that places(empty)at bottom and others at right@anchorannotations are ignored or rejectedMissing information:
mxcli diag --bundle(or at least the session log) to help reproduce the issue.Could you please add the Mendix version and share the diagnostic bundle or session log? Thanks!
Automated triage via OpenRouter — workflow source