Explanation

This rule checks the default value of all attributes to verify none use a decision table. The usage of a decision table as a default value is a bad practice and support for this will be removed in a future Blueriq version. 
This functionality is a piece of Blueriq legacy, but it confuses inexperienced users who see this and think it is necessary to link the decision table to the attribute (the inference engine takes care of that).

Possible improvements

Setting up proper decision tables, ideally each attribute should only be derived in a single decision table, even if this table grows too large, in which case sub-tables are considered a best practice.

The solution is usually very easy, remove the default value from the attribute. However, depending on the model, in some cases this could lead to a change in behavior in which case the decision tables should be refactored more thoroughly. 

Example