Decision Rules Step

The Decision Rules step combines the functionality of the Condition, Decision, and Manual Review steps into a single, streamlined component.

This step allows you to configure rule-based logic that can:

• Apply a final decision (Accept, Reject, Resubmit, Cancel, or Manual Review).
• Terminate the workflow once a decision is made.
• Allow the workflow to continue to subsequent steps if no rule applies.

📘

The Decision Rules step is the only workflow step that can both issue a final decision or continue execution via a fallback path.

Use cases

• Automatically Reject consumers located in New York.
• Automatically Accept consumers who do not reside in New York and were born before 01/01/2007.
• Send to Manual Review if none of the above criteria are met.

Configure a Decision Rules step

You can place a Decision Rules step anywhere in a workflow where you need to evaluate conditions and apply decisions. It does not need to directly follow an Enrichment step, although enrichment outputs are often used as inputs.

To configure the step:

1. Select the step in the workflow to open the side panel.
2. Define your first decision rule:
   • Enter a descriptive name for the rule.
   • Select a decision outcome (Accept, Reject, Resubmit, Cancel, or Manual Review).
   • (Optional) Assign a tag for categorization or downstream logic.
   • Define the conditions that must be met for the rule to evaluate as True.
     • See Build Your Workflow for details on condition groups and operators.
3. Add more rules by clicking Add New Decision Rule. Rules are evaluated in order, and the first matching rule is applied.
4. Configure the Fallback (Else):
   • Toggle Continue without making a Decision → The workflow proceeds to later steps.
   • OR select a fallback decision (Accept, Reject, Resubmit, Cancel, or Manual Review) and assign a tag.
5. Click Close to save your configuration.

Best practices

• Order matters: Rules are evaluated top-to-bottom; place the most restrictive rules first.
• Be explicit: Always configure a fallback (Else) to avoid undefined outcomes.
• Use tags: Attach tags to provide clarity in API responses and assist downstream systems.
• Keep rules maintainable: Use descriptive names and comments so rule logic is easy to understand and update.
• Validate thoroughly: Test rules with representative cases to ensure correct outcomes.

API response

The outcome of a Decision Rules step appears in the evaluation API response under the decision field.

• If a rule applies, the configured decision (Accept, Reject, Resubmit, Cancel, or Manual Review) is returned.
• If Continue without making a Decision is selected, no decision is applied at that point, and the workflow continues.