Workflow Definition v2
Workflow Definition v2 is a separate, iterative copy of the workflow definition editor. It exists so the team can try out a newer designer experience without changing the stable Workflow Designer. Both work on the same workflows — v2 is an alternative editor, not a different set of processes.
How to open this screen
From the left navigation menu, open Configuration → Workflow Definition v2
(route /configuration/workflow-definition-v2). Clicking a workflow opens it in the v2 editor at
/configuration/workflow-definition-v2/<id>.
- Access required: the Manage Workflows permission (
CONFIGURATION.WORKFLOWS).
The list you land on is the same Workflow Definitions list described in Workflow Definitions — searching, filtering, creating, editing, and deleting all behave identically. The only difference is that opening a workflow takes you into the v2 editor instead of the standard designer.
How v2 differs from the standard designer
The standard Workflow Designer offers six step types in its toolbox. The v2 editor is experimental and groups a larger set of building blocks (called activities) into categories in its toolbox:
| Category | Activities offered in the v2 palette |
|---|---|
| Control Flow | If / Branch, Loop, Switch Case, Parallel Branch, Merge / Join |
| Actions | Task, Approval, RPA Bot, Script / Code |
| Communication | Send Email, Notification, Webhook |
| Integration | REST API Call, Database |
| Document | Document Task, Sign Document, Archive, Timer / Wait |
Experimental / work-in-progress: v2 is an iteration that explores a richer palette and nested branch arms. It is not the supported way to author production workflows. For live processes, use the standard Workflow Designer, where decisions use binary branches only (one Yes path and one No path). Treat the extra v2 activities as a preview that may change.
Working in v2
The v2 editor follows the same overall pattern as the standard designer:
- Open a workflow from the list.
- Use the activity toolbox (or the inline add controls) to insert steps.
- Fill in each step's Title, Description, Assigned Role, and SLA in the step dialog, exactly as in the standard designer.
- Decision-style steps capture a condition and Yes / No arms; you can add steps inside each arm.
- Changes are saved to the same shared workflow, so a workflow edited here also reflects in the standard designer.
Because v2 and the standard designer share the same underlying workflow data, avoid editing the same workflow in both at once to prevent confusion over which change "wins".
Tips
- Use v2 only to preview the newer editing experience. Keep authoring real, in-use workflows in the standard designer.
- If you experiment in v2, do it on a Draft workflow so nothing live is affected.
- Remember the supported rule for production: decisions branch into two paths only.
Troubleshooting
| Problem | Likely cause and fix |
|---|---|
| The menu item isn't visible | You don't have the Manage Workflows (CONFIGURATION.WORKFLOWS) permission. |
| Edits here also changed the standard designer | Expected — both editors read and write the same workflow. |
| An activity type behaves unexpectedly | v2 is experimental. For reliable results, edit the workflow in the standard Workflow Designer. |
| I need a guaranteed, supported workflow | Author it in the standard designer using binary-branch decisions. |