Conditional Routing for Advanced Workflows

Preview Date: 2026-10-16. Production Date: 2026-11-20.

With this release, you can define conditional routing rules in advanced workflow definitions. Submit and approve paths can change based on planning data values at runtime.

Note: Conditional routing is only available under certain Adaptive Planning SKUs.

Business Benefits

You can automate approval routing in planning workflows instead of using fixed approval chains or manual workarounds. Approvers receive tasks only when their review is required. This reduces unnecessary approvals and helps you run planning cycles more efficiently.

Changes

We now support conditional routing in advanced workflows. You define rules in workflow definitions. At runtime, the system evaluates an account value for each participating level and routes the level to the matching approval path, a system-approved path, or a mandatory fallback path.

Workflow Definition Builder

In the workflow definition builder, you can add these new task types under

Logic

and

System Tasks

Conditional Rule

. This task type introduces a branching point after a submit task or between approve tasks within a submit/approve task group.

System-Approved Task

. This task type marks a submit or approve step as system-approved without a human approver.

When you add a

Conditional Rule

task, we create a conditional routing group with a default routing rule and a mandatory fallback branch. You configure the rule in the Conditional Rule modal. You add approve or

System-Approved Task

tasks under each branch in the workflow builder.

We display submit, approve, and conditional rule tasks together in a submit/approve task group. This layout shows how tasks relate within the group.

You can place a

Conditional Rule

task only after a submit task or between approve tasks. You can't place it before a submit task, between to-do tasks, or inside an existing conditional routing block. You can add only 1

Conditional Rule

task per submit/approve group. Nested conditions aren't supported.

Conditional Rule Modal

In the Conditional Rule modal, you configure the account and routing rules that determine which branch runs for each level:

Enter a

Conditional Rule Name

Select an

Account

. All account types available in web reports are supported. For more complex logic, select a custom calculation account.

Under

Routing Rules for Account

, define 1 or more routing rules. We evaluate the rules in order and apply the first matching rule.

Configure a mandatory

Fallback

. This branch runs when no routing rules match or when a level-specific computation error occurs. You add fallback steps in the workflow builder. We recommend that you assign an administrator to the fallback branch. That way, they're aware of any submissions that didn't meet a routing rule.

You can't publish a workflow definition until every routing rule and the fallback branch have complete configuration and valid approval paths.

Workflow Launch

When you launch a workflow from a definition that contains conditional routing, the

Launch New Workflow

dialog adds these new options:

Time

. This field displays after you select a

Plan Version

. Select the time period used to evaluate the conditional account for that workflow. Options reflect the selected plan version and automatically default to the highest time stratum. You can expand to more granular periods.

Participating Levels

. The participating levels functionality works like it does for advanced workflows without conditional routing. We automatically validate that participating levels have associations for approve tasks on all conditional branches before launch.

After launch, the

Edit Details

dialog displays the selected

Time

as read-only.

Runtime Routing

When a user submits or approves data for a level and the next step is conditional routing, we now evaluate the configured account against real-time planning data for that level and time period:

Each participating level is evaluated independently. Different levels can take different branches.

We activate only the matching branch. Branches that don't apply for a level aren't triggered.

If a branch uses a

System-Approved Task

, we mark the level approved without creating a human approval task. We then advance the workflow.

If no rule matches or a level-specific computation error occurs, we route the level to the fallback branch for human review.

If the account formula is invalid for the workflow, we put the workflow in Error
status. We notify the workflow launcher when the launcher still has the Manage Workflows
permission.

When an approver sends back a submission and the submitter resubmits, we re-evaluate the condition. If the resubmission routes to a different approver, we notify the original approver that the path changed.

End-User Experience

For workflow participants:

Conditional approval tasks don't display in

My Tasks

until the prior step completes and the condition is evaluated for that level.

If a level is routed away from a branch, tasks for skipped branches never display in the assignee's

My Tasks

On the workflow path, we hide the conditional steps that haven't been evaluated yet. An info icon indicates that additional steps might display after evaluation.

After evaluation, only the activated branch's next task display on the workflow path.

Workflow Monitoring

On workflow monitoring pages, you can now see how conditional routing affected a workflow:

Approval tasks on a conditional branch display the conditional rule step name.

Branches that weren't taken for any level display a Not Met status.

For

System-Approved Task

tasks, the drill-down displays

Approver: System Approved

and

Due Date: N/A

For levels on a taken conditional branch, the monitoring detail view includes an

Account Details

column with

Explore Cell

. Selecting

Explore Cell

opens the cell explorer filtered to the level, account, version, and time period from the workflow. The value shown is the current account value. It may differ from the value used at evaluation time if data changed after submission.

When you export monitoring data for a workflow with conditional routing, the export includes

Conditional Rule Name

and

Routing Rule Name

columns for triggered paths. Untriggered conditional paths don't display in the export.

Guardrails

We increase these workflow definition limits to support conditional routing:

Maximum tasks per workflow definition increases from 20 to 30.

Maximum approve and

System-Approved Task

tasks per submit/approve task group increases from 5 to 10.

System-Approved Task

tasks count toward this limit.

Limitations

Conditional routing supports sequential if/else routing only. Parallel routing to multiple approval groups isn't supported.

You can add only 1

Conditional Rule

task per submit/approve task group. Nested conditions aren't supported.

Routing rules support numerical comparisons on a single selected account. An AI assistant for building expressions isn't included in this release.

What Happens if I do Nothing?

If you don't update your workflow definitions, existing workflows continue to use fixed submit and approve paths. No conditional routing runs until you publish and launch workflows from definitions that include conditional routing.