A first step in analyzing results of executing Decision Services is to gain visibility to the rules that fired. With rule tracing, you can see what rules and Rulesheets fired in processing a work document. Rule tracing can be used during development time in the Studio Tester or with deployed Decision Services. The following example uses the Advanced Tutorial's Ruleflow as the test subject. The Ruleflow has three Rulesheets, each with conditional and non-conditional rules.
Figure 256. Rule messages when metadata is enabled in Studio
The metadata can be expressed in natural language, such as, for line 1: "In Rulesheet Checks.ers, rule 2 generated this statement", and, for line 4 "In Rulesheet coupons.ers, line B's non-conditional (column 0) action generated this statement."
To enable this function, add a line to thebrms.properties as:
Note: For Decision Service deployments, set this property where the Deployment Console runs, and then regenerate each ESD file in the Deployment Console. For CDD deployments, set this property on the Server, and then regenerate and compile each Decision Service.
