Views:

Overview

North52's business rules engine for Microsoft Dynamics 365 is excellent for eligibility rules. In this scenario we demonstrate how to quickly and easily set up a Decision Table that determines eligibility for a particular type of Credit Card.

For this article it is assumed that you have at least basic familiarity with Decision Tables and/or have read the following articles:

We will use the following custom fields on the Contact entity to decide if a customer is entitled to a Platinum Credit card:

  • Annual Income
  • Total Assets of Applicant
  • Credit Score

This is a part one of a two part series. You can see this example extended here.

 

 

Eligibility Rules for a Platinum Credit Card

If a customer matches any of the scenarios below then they are entitled to a Platinum credit card. As you can see there are 12 possible combinations each with 3 variables to check which means 36 data points to check.

Rule # Annual Income
Total Assets
Credit Score
1

< 100000

< 500000

> 188

2

< 100000

Between 50000 and 100000 > 180
3

< 100000

> 1000000

> 172

4

Between 100000 and 150000

< 500000

> 164

5

Between 100000 and 150000

Between 50000 and 100000

> 159

6

Between 100000 and 150000

> 1000000

> 151

7

Between 150000 and 200000

< 500000

> 145

8

Between 150000 and 200000

Between 50000 and 100000

> 134

9

Between 150000 and 200000

> 1000000

> 131

10

> 200000

< 500000

> 124

11

> 200000

Between 50000 and 100000

> 120

12

> 200000

> 1000000

> 112


The easiest and fastest way to achieve the desired functionality is with a North52 Decision Table.

North52 Decision Suite Solution

The North52 Decision Suite solution works like this:

  • A new North52 Formula of type Save - Perform Action is created on the Contact entity
  • The Source Properties for this Formula are Annual Income,  Total Assets of Applicant and Credit Score
  • Set the Event to be Create & Update
  • Add 2 additional Condition Columns and set the 3 Columns to check against the Annual Income, Total Assets and Credit Score
  • Set the Action Column to update the Credit Card field.


                                                                                        

  • Finally we add the condition values to the to Decision Table editor and save



 

Note: The ((150000, 200000)) syntax is inclusive of 150000 and 200000.

Testing the Decision Table

We open a Contact record and set the following fields and values:

  • Annual Income to $120,000
  • Total Assets of Application to $440,000
  • Credit Score to 174

When we click Save the Decision Table updates the Credit Card Type accordingly to Platinum

Did you know?

xCache helps you manage environment specific configuration

North52's Decision Suite component xCache allows you to set up environment specific data to allow you to use different values for different instances. Your advanced business rules logic could be the same, however you need to use specific reference values for a particular instance.

For example, credentials for a web service used in your Formula - you will likely use different keys/URLs for your Dev, Test and Production instances. Store these in xCache and let the North52 business rules engine apply the correct ones at runtime! 

Learn more and see examples of xCache