Articles in this section
Category / Section

Different Types of Branching in Workflows

Published: Apr 08, 2025
New

Branching allows workflows to follow different paths based on user input or predefined rules. Selecting the right branching method helps maintain efficiency, improve user experience, and adapt to different workflow needs.

In the Workflow Designer, open the context menu and select Branching to choose from the following options:

  1. Branch via Buttons
  2. Branch via Conditions
    BrachingContextMenu

Branching Using Buttons

This approach provides users with clickable options to manually direct the workflow. You can add these options in the designer. For more details refer to step 6 in Branch Via Buttons

When to Use

User-Driven Decisions – Suitable when explicit user input is required (e.g., Approve/Reject, Yes/No).
Limited & Predefined Choices – Ideal when options are straightforward and limited (e.g., “Escalate to Manager” or “Resolve Independently”).
Immediate Action Needed – Applicable when workflow progression depends on user selection.

Example Use Cases

  • Approval processes (e.g., “Approve Request” or “Request Changes”).

  • Customer support triage (e.g., “Mark as Resolved” or “Escalate to Tier 2”).

  • Collecting feedback (e.g., “Satisfied” or “Need Assistance”).

    ButtonBranchingWorkflow

Branching Using Conditions

This method relies on automated decisions based on predefined rules, system data, or variables. You can add these conditions in the designer. For more details refer to step 14 in Branch Via Conditions

When to Use

Data-Driven Decisions – Appropriate when decisions depend on system data (e.g., status, priority, or user role).
Complex Logic – Suitable for scenarios requiring multiple conditions to be evaluated (e.g., “If priority = ‘High’ and department = ‘Finance’, notify CFO”).
No User Input Required – Best when workflows need to advance automatically without user intervention.

Example Use Cases

  • Processing orders differently based on customer tier (e.g., VIP vs. standard).

  • Automatically approve expenses based on predefined rules (e.g., approval required only for amounts above $500).

    ConditionBranchingWorkflow

By selecting the most suitable branching method, you can enhance workflow efficiency, minimize manual intervention, and elevate the overall user experience.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Please  to leave a comment
Access denied
Access denied