Overview
Thecontrol_flow object in our platform defines how each step in the verification process transitions based on specific conditions. It enables dynamic decision-making by supporting conditional logic, allowing the flow to branch based on predefined criteria. If control_flow is not provided for a step, the process will run sequentially to the next step.
Structure of control_flow
Each step contains a control_flow object with the following fields:
1. condition
Defines the logic for evaluating a decision. The condition consists of:
condition_operator: The operator used to compare values (e.g.,==,>,<,>=,<=,!=).condition_field: The data field being evaluated.condition_value: The expected value used for comparison.
2. if_goto
Specifies the next step to transition to if the condition evaluates to true.
3. else_goto (Optional)
Specifies the next step to transition to if the condition evaluates to false.
4. end (Optional)
If set to true, it indicates that the process terminates at this step if reached.
Execution Flow
- If a step has a
control_flow, the conditions determine the next step. - If a step does not have a
control_flow, the process continues sequentially to the next step in the list.
Example control_flow Objects
Example 1: ID Verification
- If
id_validistrue, the process moves toBACKGROUND_CHECK. - Otherwise, it moves to
manual_review.
Example 2: Credit Report
- If
credit_scoreis700or above, the process continues toBANK_CONNECT. - Otherwise, it moves to
request_credit_report_again.
Example 3: Process Completion
- This step marks the end of the process.
Operators Supported
| Operator | Meaning |
|---|---|
== | Equal to |
!= | Not equal to |
> | Greater than |
< | Less than |
>= | Greater than or equal to |
<= | Less than or equal to |