OpenRules supports decision tables applied to all element of collections of objects. The phrase [for each <element> in >collection>] added to the end of the decision table signature applies the rules to every <element> of the <collection>. In this post I will explain additional iteration capabilities now available to OpenRules customers.
Continue reading
Real-world decision models usually execute multiple decisioning steps in a certain order. Whether the execution order is defined manually or automatically, the good design does not need to be explicitly interrupted if, after every execution step, the decision model validates the expected results and directs the execution to the correct branches. However, sometimes you still need to interrupt the execution of your multi-hit decision table, to break your iteration loop, or even to terminate the execution of your entire decision model. This post shows how to deal with such situations using OpenRules predefined actions “ACTION-BREAK” and “ACTION-TERMINATE”..
Continue reading
DMCommunity.org Challenge May-2022 still has no submitted solutions. I knew that the problem is not as simple as it sounds because we, at OpenRules, have quite a few claim processing customers, whose decision models address similar and much more difficult problems. When I tried to create a decision model for this challenge, I quickly got a solution that still produced these errors while processing a test-claim:
[E71.313] cannot be reported together with [E72.3]
[E72.3] cannot be reported together with [E71.313]
But the challenge specifically required not to produce duplicate errors. Trying several decision modeling approaches, I built a few “tried-and-failed” decision models before I came up with two solutions which I feel comfortable enough to share here.
Continue reading
Recently I helped one of our larger customers to build a set of their business decision models. At the end I said that now they can continue to assemble new decision models themselves. Then one of their business analysts said that our decision modeling approach reminds him of LEGO. I believe this is a really good analogy and I will elaborate on it using specific examples.
OpenRules - Decision Intelligence Platform 