Glossary and JSON Interface

Being at the heart of any decision model, OpenRules Glossary uses mandatory columns “Variable Name”, “Business Concept”, “Attribute”, and “Type” to define all used decision variables. It also may include many optional columns such as “Description”, “Used As”, and “Default Value” that allow you to effectively control the input and output of the decision model [read more]. The new OpenRules Release 10.4.1 adds new features to the Glossary that allow our customers to build more flexible JSON interfaces for OpenRules Decision Services.

Continue reading

Composite Decision Variables

In real-world decision models, you may want to write business rules that refer to combinations of two or more individual decision variables called composite decision variables. For example, your business concept “Department” may have a decision variable “Manager” of the type “Employee” which is another business concept with such variables as “Name”, “Salary”, “Gender”, etc.

Continue reading

Nested Attributes in OpenRules Glossary and Tests

In real-world decision models, our customers deal with complex business glossaries. In particular, it is quite common when one business concept refers to other business concept and it is not immediately clear how to define and use such references. I will explain how it’s supposed to be done in OpenRules. let’s consider a simple example “HelloNestedLocation” with the following glossary:

Continue reading