The orchestra_cm editor lets you add and remove nodes and flows, but not duplicate one. A node with several configured features (settings, routing, escalation timers, assignments) is tedious to recreate by hand, and a conditioned flow often wants a near-identical sibling.

Proposed solution: add two buttons.

  • Clone node, beside Remove node, on every node (the start included): duplicates the node with all of its current configuration (type, label, settings, routing and feature editors) under a fresh machine name, marks the label as a copy, and opens the new row. The clone is left unwired (no flow is copied), so its machine name stays editable for an immediate rename, like a newly added node.
  • Clone flow, beside Remove flow: duplicates the flow (same endpoints and condition) under a fresh id, as a starting point for a sibling branch. Offered only on a flow that has a condition, since a second always-taken edge between the same two nodes is a duplicate that could never behave differently.

Both act on the live, even unsaved, edits, so the duplicate reflects what is on screen.

Issue fork orchestra-3605375

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mably created an issue. See original summary.

mably opened merge request !197

  • mably committed 582688a9 on 1.x 
    feat: #3605375 Add Clone node and Clone flow buttons to the orchestra_cm...
mably’s picture

mably commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.