Skip to main content

Copy a workflow

In briefCopy Workflow creates a new, independent workflow from an existing one — its settings, frequencies and, by default, its jobs. The copy is made from the last committed version, is created in the General workspace, and is not deployed anywhere until you deploy it.

WhereDesign › Workflows, open the workflow, then Copy Workflow on the workflow editor's toolbar. The button is unavailable until the workflow has been saved, or when your role does not permit it; its tooltip says which.

When

  • You need a second workflow structurally like one you already trust — another region, another institution.
  • You want one job from this workflow in another one — use Copy to Another Workflow on the job instead.
  • You want a starting point with the same build settings and frequencies but your own jobs (clear Copy jobs).

How

  1. Commit any changes you want carried across — a browser draft is not copied.
  2. Select Copy Workflow, and accept or change the suggested <name> - Copy.
  3. Leave Copy jobs and Navigate to this workflow after copy on, or clear them.
  4. Save, then review the copy's workspace, build settings and cross-workflow dependencies before deploying it. The task walkthrough is Add jobs to a workflow.
Notes
  • Workflow names are 1–40 characters and reject ' | ; % & < > ( ) [ ] { } , = ! \ ". The dialog checks the name as you type.
  • Every copied job is a new job, and dependencies on jobs in the same workflow are repointed at the copy's own jobs.
  • A name already in use is only reported when you save.
  • Copy to Another Workflow copies one saved job into another workflow's unsaved changes and opens it in the Job Editor there; commit that workflow to keep it. See Copy one job to another workflow.
Watch out
  • Dependencies on jobs in other workflows are kept, so the copy waits on the same external predecessors as the source.
  • Your role needs permission to create workflows in General, or the copy is refused.
  • Copy auto/copy privileges has no effect yet.