workflow-routing-usage

Workflow Routing Usage Guide

Workflow routing lets a workflow automatically choose one of several next steps from the same current step. The first supported mode is percentage routing.

Who Uses Routing

Admins and management staff configure routing while building form, task, or training workflows.

When to Use Percentage Routing

Use percentage routing when you want to randomly select one of several transitions out of a step. Common examples:

• send a small share of submissions to supervisor review
• route most submissions directly to completion
• split follow-up work across equivalent review paths

Builder Workflow

1. Open the nonlinear workflow builder.
2. Select Routes in the workflow header.
3. Add a route from the route drawer.
4. Select the route.
5. Select workflow graph transitions that start from the same step.
6. Set each transition likelihood.
7. Confirm the route total is 100%.
8. Save the workflow.

All transitions in one route must start from the same workflow step. After the first transition is selected, transitions from other steps are disabled for that route.

Runtime Behavior

When an instance enters a step with percentage routing, the server rolls the route and stores the selected transition as a routing observation on the instance. This 'roll' will never change for the lifetime of the form, task, or training.

After the observation exists:

• only the selected routed transition is available from that route
• manual transitions from the same step remain available
• retrying or reopening the same instance keeps the same selected routed path

Create Screen Restriction

Percentage routes that start from the first workflow step cannot run during initial form creation. Users must save the form first, then submit from the saved instance.

This restriction only applies to percentage routing. Future routing modes will define their own create-screen behavior.

Public Share Behavior

Public share submissions use the same routing resolver as authenticated form creation and updates. When a public share submission enters a routed step, the selected transition is stored as a routing observation on the created or updated instance.

Operational Notes

• Missing transition routing config means the transition is manual.
• A route should total exactly 100%.
• Renaming a route updates transition references in the builder.
• Removing a route clears routing from its transitions.
• Stored observations are audit data and should not be edited manually.