Securing OpenRules Decision Services

Release 8.4.1 of OpenRules Decision Manager is about “Securing OpenRules Decision Services” – click on this link to see the new tutorial that describes how to secure decision services using JWT Authentication and SSL communication. Release 8.4.1 also provides business users with an additional control over input and output of their decision models allowing them to validate incoming JSON requests and choose which decision variables to exclude from the produced responses. Read Release Notes

Glossary: Controlling Decision Model Input and Output

Glossary with UsedAs-properties

Being at the heart of any decision model, OpenRules Glossary uses columns “Variable Name”, “Business Concept”, “Attribute”, and “Type” to define all used decision variables. It is recommended to add the optional column “Description” with plain English descriptions of these variables.

Additionally, OpenRules 8.4.1 Glossary may include optional columns “Used As” and “Default Value” that allow you to effectively control the input and output of the decision model. It can be especially important when your decision model is deployed as a RESTful web service, and you want to validate the incoming JSON structure and decide which variables should be included in the outgoing JSON structure.

Continue reading

Glossary at the Heart of the Decision Model

Any practical decision modeling tool allows a user to represent a business glossary that specifies all decision variables and thus is at the heart of any decision model. The DMN standard does not explicitly specify a glossary letting different implementation products to compete. So, the modern digital decisioning systems use different constructs to organize their glossaries. In this post and follow-ups I will describe how OpenRules deals with its most important tables of the type “Glossary” which are always the focal point of any decision modeling process.

Continue reading