Skip to main content

Copy or Create a New Workflow from an Existing Template

Reuse an existing workflow as the starting point for a new, separate workflow.

Lauren Baird avatar
Written by Lauren Baird
Updated this week

Primary Role: Workflow Manager
Learning Focus: Apply
Where: Workflow Editor


When to Use This

Use this process when:

  • You want to create a new workflow based on an existing one

  • The new workflow should exist alongside the original

  • The workflow purpose, audience, or scope will differ

If you only need to improve or correct an existing workflow, use Updating an Existing Workflow instead.


🧭 Before You Start

  • The source workflow must already be Published

  • You should know how the new workflow will differ

  • This process creates a separate workflow template


🛠️ How to Create a New Workflow from an Existing One

  1. Open ANVL Insights

  2. Navigate to Mobilize → Editor

  3. Open Published in the left-hand menu

  4. Select the workflow you want to reuse

  5. Edit the workflow name to reflect the new purpose

  6. Click Save

    • This saves the workflow as a Draft with the new name


🛠️ Publish the New Workflow to Demonstration (UAT)

  1. Open Drafts

  2. Locate the newly named draft

  3. Click the Publish (🚀) icon

  4. IMPORTANT: When prompted, choose Create

    • This creates a new workflow template

    • DO NOT Use "Update" (default option) as this will overwrite the existing workflow.

  5. Assign:

    • The appropriate Workflow Category

    • The Demonstration / UAT site

  6. Click Publish


🔍 Verify the New Workflow in Demonstration / UAT

After publishing:

  1. Refresh the browser page

  2. Open Published

  3. In the Group Selector, select the Demonstration / UAT site

  4. Locate and open the workflow

  5. Confirm the workflow appears with the new name and expected content


🧪 What to Do Next


🔑 Key Takeaways

  • Editing the name before saving is what creates the new draft

  • Create (not Update) is required to make a new workflow template

  • Always publish new workflows to Demonstration / UAT first

  • Refresh and verify before testing

Did this answer your question?