Inheritance and Secialization of Decision Tables - Gnorion/BizVR GitHub Wiki

IDEA: INHERITANCE AND SPECIALIZATION OF DECISION TABLES

Is there any value to this concept:

Normally decision tables are created inside a decision.

But suppose we could create a table at the project level so that every new decision created automatically gets populated with any decisions defined at the project level (or workspace level)

Such "inherited" tables could be read only preventing the decision owner from modifying it, or it could be editable - meaning the user could add rules to it but not modify the inherited ones. This would be similar to the concept of inherited functions and specialization in code.

Such an inherited table could be user to impose constraints on every decision within a project both at design time and at execution time.

For example the inherited table may place an upper limit on the value of the field benefit. Within the decision itself the user could write any rules to determine benefit but the inherited table would limit the value if needed. this same limit then would automatically be applied to every decision that is created in the project by any user