Extending BizVR To Handle Complex Expressions - Gnorion/BizVR GitHub Wiki

EXTENDING BIZVR TO HANDLE EXPRESSIONS

BizVR will allow you to put ANYTHING in any cell (meaningful or not)

Currently BizVR and VV can easily handle simple tables of this form

image

Basically attribute names in the left column and literal values in the rules

You can enter a complex expression like sum(A,B) but both BizVR and VV behave as if  sum(A,B) is the name of an attribute.

This currently prevents BizVR and VV from detecting the dependencies and do the connecting arrows don't show.   As we move forward we'll need to be able to handle rule sheets that have complex expressions in ANY cell (except the cell that names the attribute whose value is being set by the rule. That can NEVER be an expression - it has to be an attribute name or the keyword RETURN (for function tables).  A DT with complex expressions might look like this

image

So we will need BizVR and VV to be able to access the names of the attributes that embedded in the expressions   ADDITIONAL PARSING OF EXPRESSIONS USED IN DECISION TABLES (bizVR style and Feel style) At some point we (BizVR and VV export) will need to know the various variables that are in an expression.

BizVR needs it for the dependency diagram and VV also needs it.

We should have a discussion about how to do that. Here are some ideas on what the export file might look like - just a few added properties to handle the attributes used in expressions

https://github.com/Gnorion/BizVR/wiki/Thoughts-on-extracting-the-variable-names-and-types-from-conditions-and-actions  

Some examples of complex expressions