CMMN MVP Backlog

This backlog captures CMMN editor improvements discovered while exercising the MVP.

Layout And Diagram Editing

  • Manual resize for expanded Stage and CasePlanModel elements.

    Current behavior: Stage and CasePlanModel auto-resize when child elements are added, but the user cannot manually drag resize handles.

    Desired behavior: users can manually resize expanded Stage and CasePlanModel elements, and the updated bounds persist after save and reopen.

    Priority: backlog, not blocking Session 2 learning.

Runtime State And Debugging

  • Highlight CMMN runtime state on the diagram.

    Status: implemented for ready and completed CMMN Human Tasks.

    Current behavior: CMMN Human Tasks use BPMN Ed-style diagram markers to show ready and completed runtime state. Disabled/unavailable task shading still depends on sentry and criterion enforcement being added to the CMMN runtime path.

    Remaining work: when sentries are modeled and enforced, unavailable tasks should be visually muted.

  • Add an explicit CMMN Human Task completion flow.

    Status: implemented for pending CMMN Human Tasks.

    Current behavior: when a CMMN Human Task is pending, the control panel exposes an enabled Complete Task action. Completing the task advances the case, refreshes the debugger panel, and updates diagram highlighting.

    CMMN note: unlike BPMN, a case may have multiple available Human Tasks at once. The UI should support selecting which pending task to complete instead of assuming a single linear next step.

  • Execute DMN decisions from CMMN DecisionTasks.

    Status: backlog.

    Spec context: CMMN 1.1 defines DecisionTask and DMN compatibility behavior. A CMMN DecisionTask can reference a Decision and use parameter mappings to pass case data into the decision and store outputs back into the case.

    Desired behavior: users can model a CMMN DecisionTask that references an Ed DMN file or decision id. When the DecisionTask becomes active, Ed evaluates the DMN decision with current case data, stores the result in case data, refreshes runtime state, and allows sentries to use the decision output.

    Dependencies: meaningful support needs CMMN case data handling, DecisionTask reference editing, input/output mapping, and sentry/criterion enforcement. Until those pieces exist, Session 4 should treat CMMN-to-DMN execution as conceptual and use BPMN/DMN separately for executable DMN practice.