Introduction

The Conditionals within the Workflows platform play a crucial role in designing customizable and dynamic user journeys. By utilizing these tools, administrators can create sophisticated verification flows that adapt to the data collected during the verification process. This flexibility ensures that each user's experience is optimized for efficiency and effectiveness.

What are Conditionals?

Conditionals

Conditions, or Condition Nodes, are used within workflows to branch the user journey based on the outcomes evaluated by the Rule Engine. They allow for the creation of dynamic paths where different sets of modules can be presented to the user based on specific criteria or user inputs.

The Rule Engine is a powerful feature that allows for the evaluation of complex logic based on the data collected during the verification process. It supports a wide range of rules that can assess the quality of data, the outcome of verification checks, and more.

What They Enable?

The Conditionals enable:

• Dynamic User Journeys: Tailor the verification process in real-time based on user inputs and verification outcomes.

• Efficiency and Effectiveness: Direct users through the most appropriate verification path, optimizing both user experience and verification success rates.
• Custom Success Criteria: Define custom criteria for verification success, ensuring that the workflow aligns with specific business requirements.

How to Configure?

Configuring Conditionals involves several steps:

1. Create Condition Nodes: Incorporate Condition Nodes into your workflow where you want to branch the user journey based on the outcomes of the rules.

   

2. Configure Rule Expression: Choose from available information about user data, validation results to create rule expression and define comparisons. Rule Expression reads as: If Estimated age VALUE is greater than (>=) 25. Result of this expression (True/False) will allow branching the user journey. For example, only users over 25 can access your service.

   

3. Configure Logical Operators: Use logical operators (AND, OR) to combine multiple rules within a single Condition Node, if necessary.

   

4. Set Yes and No Branches: For each Condition Node, define what happens if the condition is met (Yes branch) or not met (No branch). Choose from the module, processing node, end result or even a new condition.

Best Practices

• Simplify Conditions: Instead of creating a single complex condition, link multiple Condition Nodes one after another. This approach makes the workflow easier to understand and manage and gives a better view on which path user went through
• Utilize Logical Operators: Effectively use AND and OR operators to create precise conditions that accurately reflect your requirements.
• Monitor and Adjust: Regularly review the performance of your workflows. Adjust rules and conditions based on real-world outcomes to continuously optimize the verification process.
• Plan for All Outcomes: Ensure that every possible path through the workflow leads to a clear result, avoiding any dead ends that could confuse users or disrupt the verification process.