Validating Aggregations of Decisions or Tables - Gnorion/BizVR GitHub Wiki

VV is really very simple. It just takes whatever rules you throw at it and will apply its validation logic.

It doesn’t care if there is one rule per table or a thousand rules per table.

It doesn’t even care if you got those rules from a dozen different decisions, or whether some came from DMN and some from XLSX and some from BVR.

It just analyzes that set and tells you if there is anything wrong in three main categories:

  • Consistency: do any rules conflict?

  • Completeness: are there missing rules?

  • Redundancy: are there unnecessary rules.

Currently you have the option to send all the tables in a single decision or you can send just one table. There is a validate button at the decision level image and a different one at the table level image

The option we don’t yet have is to send in an arbitrary set of tables. They could be part of the same decision or they could be from different decisions.

At the moment, tables live inside decisions which live inside projects which live inside workspaces in a hierarchical fashion. In the future BVR will support the concept of Domains which allow arbitrary groupings of decisions or tables. So while a decision can only part of a single project it can be a member of any number of domains.

Generally a Domain would imply some meaningful relationship between its members but you can make that relationship anything you like.

For example you could have a domain for healthcare related decisions:

image

Or one for decisions that use resource allocation in different fields

image

image

image