Skip to content

Conditional Node Output Handling #1063

@matKlju

Description

@matKlju

AS A Service-Module user
I WANT the Conditional node to behave similarly to the MCQ node
SO THAT I can build and manage conditional flows consistently

Description

The Conditional node supports:

  • Multiple inputs
  • Exactly two outputs:
    • Success
    • Failure

When creating a connection:

  • If both outputs are free, a modal asks which path to use
  • If only one output is free, it is connected automatically
  • If both outputs are already connected, no additional output connection is allowed

Connections can be removed and reused.

AC checklist

  • Conditional node supports multiple incoming connections

  • Conditional node has exactly two outputs: Success and Failure

  • Unused outputs are shown as dashed connections

  • If both outputs are free, connecting opens a path selection modal

  • User can choose Success or Failure

  • If only one output is free, connection is created automatically

  • If both outputs are in use, additional output connections are blocked

  • Clicking an edge selects it

  • Pressing Delete or Backspace removes the selected connection

    • Removing a connection restores the corresponding dashed output path
    • Restored paths remain connectable
  • Edge labels/ titles/ buttons remain visible and unchanged after connect, delete, reconnect, and layout operations

    • Success and Failure labels persist after every manipulation
    • Deleting or reconnecting a path does not remove, rename, or hide its label
  • Behavior is consistent with existing MCQ path handling

Notes

  • Use MCQ connection behavior as the reference implementation.
  • Success and Failure labels are fixed and cannot be renamed.

Metadata

Metadata

Assignees

Labels

No fields configured for Feature.

Projects

Status
In Review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions