In earlier posts, we discussed that there are many ways of modeling business rules. If you do it in a decision table form, the benefit is that you can check for correctness and completeness of the business rules within the table, which would be a way of validating business rules.
Let's consider the following decision table:
This is a very simple table that calculates the discount percentage for a person based on their family status:
- The age range of the person (Child, Adult)
- Whether they have kids or not? (Married, Single)
- If they are married or not (Kids, No Kids)
As you see in the above table, all the possible values are shown in the table header (3rd line of the table).
This decision table is very simple and just looks fine, right? Well, let's try to run validation and examine the results.
After running validation you get the following results:
More Complex Conditions
Business rules conditions are not always options from lists or simple values. They might be partial expressions. For example, checking for value ranges as part of the rule conditions.
The validation should also be able to validate these complex expressions:
We had couple of requests in LinkedIn discussion groups to provide more complex rulesets (i.e., decision table in this case). So, we updated this post to provide a more complex example that involves partial expressions and range values validation.
As you see the decision table is not as innocent as is it looked! Validating the decision table reveals all these issues.
From now on, make sure you don't forget to validate business rules in order to identify missing and conflicting issues. Correctness and completeness are important and these ensure you have covered all possible scenarios in your decision table when it comes to all of the possible combinations of business rules conditions.
Learn Decision Table
To learn more about how to model decision tables in detail, please check the Resource Hub at https://resource.flexrule.com/knowledge-base/decision-table-101/
- XBRL and Standard Business Reporting
- Import DMN models – XML 1.1
- Edit Business Rules on Web
- Validating Business Rules
- Decision model and Notation – Policy Example
- Decision Table Web Component
- Reuse Business Decision as a Function
- Business Rule to Identify Duplicates
Last updated September 22nd, 2020 at 11:30 am, Published March 15th, 2016 at 11:30 am
CEO and the founder of FlexRule – He is an expert in architecture, design, and implementation of operational decisions, business rules, and process automation. Created Decision-Centric Approach, a methodology that brings People, Data, Rules, and Processes together to automate operational business decisions.
This approach is recognized by Gartner as the missing link to provide business value to organizations.