Decision Strategies

How to build and manage decision and integration strategies.

Overview Of Decision Strategies

DigiFi's platform empowers lenders to fully automate data integrations, underwriting, verification and other lending decisions - without needing to write any code. This is done by building and running decision strategies.

Decision strategies are the central element of decisioning within DigiFi and are fully-automated single-step or multi-step execution paths that can include integrations, rules, models, calculations and more. Decision strategies let you build and control complex decisioning through a no-code, drag-and-drop interface. Your lending process can include as many decision strategies as you need.

Within a decision strategy, there are three major sub-elements:

  1. Modules are placed within decision strategies and contain a group logic (e.g. an integration. eligibility rules, a scorecard, etc.)
  2. Branches are sub-components of modules and allow for decision trees to be built. They allow different logic to run based on conditions you set.
  3. Rules contain specific business logic and can include basic value assignments, simple conditions and complex calculations. Rules are built using variables.


For Example:

Here's simple example of each level in a decision strategy:

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

Creating A Decision Strategy

To create a new decision strategy:

  • Click the New Strategy button.
  • You will automatically be redirected to the first version of the decision strategy
  • Update the decision strategy's name by clicking on it and editing it directly.

You can then begin adding modules to the decision strategy.


Setting Up A Decision Process

Once you have created a decision strategy, you will see a blank workflow for the decision process. From here you can begin implementing a multi-step integration and decisioning process by adding modules.


Add a module to the decision strategy by clicking on the "+" button between "Start Process" and "End Process". This will bring up a module selection screen with seven options:

Requirements RulesLets you add a set of rules that must all pass for a decision to pass. Outputs a user-defined decline reason for any rule that fails.
Rule-Based OutputsLets you to add rules which, if they pass, cause outputs to be set.
Scoring ModelLets you implement a typical credit scorecard that runs rules, adds weights and produces a resulting score.
Calculation ScriptsLets you to write Excel-like formulas that generate outputs during decision processes.
Simple OutputsLets you assigns outputs (without any rules needing to pass). This can be useful tasks such as initializing values.
External IntegrationLets you integrate data sources and predictive models.
Import Existing ModuleDuplicates an existing module from this or another decision strategy.

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


Create Complex Processes

The outputs of each module can be used by subsequent modules in your decision flow, 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.

Implementing Business Rules

After you have added module(s) to your decision 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 decision strategy. This will replace all current rules.

If you select "Simple Rule", "Complex Rule: and" or "Complex Rule: or", then 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 decision strategy.

Rule Comparison Types

DigiFi's decision engine offers the following comparison types within rules:

<>Does not equal
>Greater than
>=Greater than or equal to
<Less than
<=Less than or equal to
BetweenBetween a range of numbers (inclusive of both ends)
InIn a list
Not InNot in a list
Is NullIs null
Is Not NullIs 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.

Implementing Data Integrations

Integrations with data sources and predictive models can be implemented within decision strategies using the "External Integrations" module type. Before a data integration can be added to a decision strategy, it must be set up in the Data Integrations section.

When you add data integrations to a decision strategy, you'll also need to set up the following:

  • Selected Integration, which gives you the option to change the integration that will run in this module.
  • Error Handling, which lets you select how integration-related errors will impact the overall execution process.
  • Variables Required For Integration, which lets you select which variables will be used as inputs.
  • Variables Received From Integration, which lets you select which variables will have outputs assigned to them.
  • Branch Conditions, which let you run the integration only if specific condition(s) pass.

Implementing Calculation Scripts

Calculation Scripts modules operate differently than other modules and allow you to enter Excel-like formulas. This enables you to implement more complex logic than IF-THEN rules allow.

For information on how to write formulas in the DigiFi platform, please refer to DigiFi's formula language documentation.

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 decision flow view, and can be added by clicking the "+ Branch" button and providing a name for the new branch.

If 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 will be unable to process.

Versions & Change Management

Decision strategies offer a robust change management process that includes versioning. Each strategy has a version number, which is set to 1 when the decision strategy is created and incremented by +1 each time a new version is created. You can create an unlimited number of versions for each decision strategy.

Create New Version

You can create a new, unlocked version of a decision strategy by clicking the Create New Version button.


If you would like to view and navigate between different versions of a decision strategy, you can do so from the "Versions" tab.



Create New Version From Any Prior Version

Creating a new version creates an exact copy of the prior version. Typically you'll create new versions based on the latest version, but if you want to create a new version based on a previous version, simply select "Create New Version" from that version of the decision strategy (either from the list of decision strategies or from the detailed decision strategy view).

View Update History

Tracking updates helps users understand historical changes and ensure compliance. Every time a change is made to a decision strategy, DigiFi records which user made the change and when the change was made. A record of historical changes can be viewed on the Update History tab.

Locking Versions

If you set a version of a strategy to Active, this version becomes locked. You can see if a version is locked based on the lock icon that appears near the strategy name.

Locked versions cannot be edited or unlocked. This has a number of key benefits:

  • You can edit decision strategies without worrying that it will cause any production-related issues, since "Active" versions can't be edited.
  • If you want to understand how a prior automated process executed, you can refer to the version of the decision strategy that was used. Since this version will be locked, the exact details are preserved.