...

It is not a best practice that each decision tables must always contain exactly one result attribute for each possible value. It could be a good starting point in design, but it should not be the ultimate goal to establish one result attribute for each possible value.To illustrate this, the example above has been redesigned to match the before named strategy. In the example above, there are only four discounts: 10%, 20%, 25% and 30%. The decision table holding a result attribute for each value will look like the one below, which in this particular case is not as legible as the two (green) decision tables above:

The use of expressions in the left column of a decision table

it is possible to use an expression in the left column of a decision table. For instance a count on instances that results in a number that is evaluated. This possibility in Blueriq offers the business engineer extensive options to create a model. The problem is that expressions are not easily readable by business users. The Blueriq platform offers two options to 

Table with reusable expressions

Image Added

Decision table or data rule?

...