Overview
Branching allows wizards to take different paths based on user input. For example:- Skip benefits selection for part-time employees
- Show additional questions for international applicants
- Route to different review steps based on request type
Creating a Branch Step
- In the Wizard Builder, click Add Step
- Select Branch as the step type
- Configure the branching conditions
Anatomy of a Branch
A branch step consists of:Configuring Conditions
Each condition has three parts:- Field - The form field to evaluate
- Operator - The comparison type
- Value - What to compare against (if applicable)
Available Operators
Operator Availability by Field Type
Multiple Conditions
You can add multiple conditions to a single branch step:- Click Add Condition
- Configure each condition
- Conditions are evaluated in order
- The first matching condition determines the path
Setting the Default Target
The default target is required and handles cases where no conditions match:- Select a step from the Default Target dropdown
- This is the “fallback” path
- Always test your default path
Validation & Warnings
The Wizard Builder validates your branches:Errors (Must Fix)
- ❌ Missing default target - Every branch needs a fallback
- ❌ Non-existent target - Target step doesn’t exist
- ❌ Self-referencing - Branch points to itself (infinite loop)
- ❌ Cycle detected - A → B → A (infinite loop)
Warnings
- ⚠️ Unreachable step - A step that no path leads to
- ⚠️ Missing field - Condition references field not in previous steps
Branch Execution
When a user reaches a branch step:- Conditions are evaluated in order
- First matching condition’s target is used
- If no match, default target is used
- User is automatically navigated to the target step
Note: Branch steps are invisible to users—they’re evaluated instantly.
Best Practices
Keep It Simple
- Limit branching depth to 2-3 levels
- Use clear, descriptive step names
- Document complex logic in step descriptions
Test All Paths
Before publishing:- Use the Preview mode with test data
- Walk through each possible path
- Verify the review step shows correct data
Handle Edge Cases
- Always set a sensible default
- Consider what happens with empty values
- Test with unexpected inputs
Example: Employee Onboarding
Troubleshooting
Branch Not Working as Expected
- Check condition order (first match wins)
- Verify field names match exactly
- Check for typos in comparison values
- Use the Path Validator tool
Unreachable Step Warning
This means a step exists but no path leads to it:- Add a condition that targets the step
- Set it as the default target
- Or remove the orphaned step
Cycle Detected Error
You have a loop in your branching:- Review all branch configurations
- Ensure no step eventually leads back to itself
- Use the visual path diagram to trace routes