Open topic with navigation
Design a decision report
A decision report is a report that can be viewed when the outcome of a goal is known, outlining the reasons for that decision. The value of every base level and intermediate attribute relevant to the final outcome is displayed in the decision report.
You may want to tailor your decision report to improve readability and to make sure the logic in the rules presents sensibly to a user. You may also choose to censor information for a particular audience.
The following steps should be undertaken when designing a decision report:
- Checking the decision reports contain enough information
to explain the answer. This may require adding intermediate conditions and
restructuring rules. See Improve the wording of a rule for more information.
- Checking the decision reports don't contain unnecessary
information. Silent and invisible operators can be added to conditions in
rules to selectively omit the inclusion of lower-level attributes in decision
reports. See Hide an attribute from a decision report for more information.
- Checking that entity instances are listed by name, rather than the generic "Instance #1, Instance #2 etc. This is done by defining an identifying attribute for the entity.
- Checking sentence construction and correcting
parsing. Sometimes this can involve rewording attributes and even restructuring
rules to reflect the reworded attribute. See Change the text of an interview question or sentence for more information.
- Reviewing decision reports to ensure they conform
with the principles
for writing rules. See Rule principles for Oracle Policy Modeling for more information.