Strategy Building

How to build and manage decision strategies.

Overview

Within the Decision Engine, there are four key elements to understand when building decision processes:

  1. Strategies are the highest-level element and are intended to contain all of the logic for a specific decision.
  2. Modules are placed within Strategies and contain groups of similar Rules.
  3. Branches are sub-components of Modules and allow for decision trees to be built. They allow different Rules to be run in different situations.
  4. Rules are the granular logic that determines the outcome of the decision. These are built using the Variables that are set up in the system (See Data Structure for more information on Variables).

📘

Personal Lending Example

Here are simple examples that illustrate the above structure:

  • Strategy Example: Personal Loan Underwriting
  • Module Example: Minimum Credit Requirements
  • Branch Example: New Customers
  • Rule Example: Credit Score >= 660

Creating A Strategy

To create a new Strategy:

  • Navigate to the Decision Engine > Strategies page.
  • Click the NEW STRATEGY button.
  • You will automatically be redirected to the first version of the Strategy, where you can update the name and begin adding logic.

Decision Flow ("Modules")

Once you have created a Strategy, you will see a blank workflow appear for the decision process. From here you can implement a multi-step decision workflow by adding Modules.

Add a Module to the Strategy by clicking on the "+" button between "Start Process" and "End Process". This will bring up the Module selection screen.

You can select from seven Module types:

Type

Description

Requirements Rules

The Requirements Rules Module allows you to add a set of rules that must all pass for a decision to pass. Assigns a user-defined decline reason for any rule that fails.

Rule-Based Outputs

The Rule-Based Outputs Module allows you to add rules which, if they pass, cause outputs to be set.

Scoring Model

The Scoring Model Module allows for easy implementation of a typical credit scorecard that runs rules, adds weights and produces a resulting score.

Calculation Scripts

The Calculations Scripts Module allows you to write simple calculations to generate outputs.

Simple Outputs

The Simple Outputs Module assigns outputs (without any rules needing to pass). This can be useful tasks such as initializing values.

External Integration

The External Integrations Module allows you to put integrations with data sources and predictive models directly inside decision flows.

Import Existing Module

Duplicates an existing Module from this or another Strategy.

After you add the Module, it will immediately appear within your Strategy. You can repeat this process to build the structure for your full decision process. To reorder the modules, simply click and hold the module to drag-and-drop it into another position.

👍

Create Complex Processes

The outputs of each Module can be used by subsequent Modules, allowing you to build complex decisioning processes. For instance, you could run a Scoring Model Module to create a custom credit risk score and then run a Requirements Rules Module to test if the score is high enough to pass underwriting.


Adding Logic ("Rules")

After you have added Module(s) to your Strategy, you can implement business logic by adding Rules.

To add a Rule:

  • Click the Edit Rules button within a Module. The Rules view will open.
  • Click the Add Rule button on this page.

The resulting popup provides five options:

  1. Simple Rules consist of a single comparative condition. If that condition passes, the Rule passes.
  2. Complex Rule: and rules consist of multiple comparative conditions. If all of the comparative conditions pass, the Rule passes.
  3. Complex Rule: or rules consist of multiple comparative conditions. If any of the comparative conditions pass, the Rule passes.
  4. Upload Entire Rule Set allows you to upload a CSV file with Rules to simultaneously implement many Rules. This will replace all current Rules. We suggest first downloading the CSV on the Rules page, since it provides the format required for that Module type.
  5. Import Entire Rule Set allows you to copy an entire set of Rules from another Strategy in the system. This will replace all current Rules.

The next page will allow you to build a Rule, which typically follows the logic of:

  • A condition that must pass
  • An output or result if it passes
  • An output or result if it fails

The specifics will vary based on the type of Module you're implementing. Please refer to the Module descriptions above for more information.

Repeat this process to add Rules to each Module in your Strategy.

Rule Comparison Types

DigiFi Decision Engine offers the following comparison types within Rules:

Comparison

Description

=

Equals

<>

Does not equal

>

Greater than

>=

Greater than or equal to

<

Less than

<=

Less than or equal to

Between

Between a range of numbers (inclusive of both ends)

In

In a list

Not In

Not in a list

Is Null

Is null

Is Not Null

Is not null

📘

Comparisons Depend On Variable Type

Certain comparison options are only available for variables with a specific data type. For example, a Between comparison cannot be performed on a Variable with the data type of Text or List and therefore this is not an available option (however it can be performed on Variables with a Number, Monetary or Percentage data type).

Assigning Dynamic Values

Rules includes the ability to use and assign dynamic values. Within fields that require a specified value, you have the option to provide either a Value or a Variable. You can toggle between these options using the drop-down.

  • If you select Value, you must provide a specific value.
  • If you select Variable, you must select a Variable.

📘

Note On Calculation Scripts

Calculation Scripts Modules operate differently than other Modules and allow you to enter JavaScript directly. This enables you to access all of the mathematical capabilities of JavaScript and create more complex calculations.


Implementing Decision Trees ("Branches")

You have the option to build decision tree logic within each Module by adding additional Branches. This option is available from the main Modules view, and can be added by clicking the "+ Branch" button and providing a name for the additional Branch.

Once your Module has multiple Branches, you need to add Branch Rules to each Branch, which will determine the conditions under which the Branch will run.

To add Branch Rules:

  • Click the Edit Rules button within a Branch. The Rules view will open.
  • Click the Add Branch Rule button on this page.

A very similar Rule-building popup will appear to the one discussed above. You can add multiple Branch Rules to distinguish between paths in your decision tree.

🚧

Branches Must Be Unique

A decision will only enter one Branch (if it passes all Branch Rules in that Branch). Ensure that your Branch rules are mutually exclusive so that multiple Branches do not apply to any decision. If multiple Branches are triggered, the Decision Engine will give a message that the decision cannot be processed.