Reporting on rules
You can report on rules of more than one type and rules that are checked out. For reporting purposes, searching all instances of the classes derived from the Rule- base class, or even all instances of the Rule-Service- class, can impact performance. To provide more efficient reporting, you can create report definitions that query the database view that corresponds to a particular class.
To report on rules of more than one type, create a report definition rule with Data-Rule-Summary as the Apply to class. The properties that you use for selection criteria must be stored as exposed columns of the PegaRULES database view that corresponds to the Data-Rule-Summary class.
To report on rules that are checked out, create a report definition rule with Data-Rule-Locking as the Apply to class.
- Viewing the heat map
You can view a heat map that shows in the number of rules in each category, broken down by rule type. The size of each box reflects the number of rules of a single rule type. Complete the following steps.
- Viewing and running inventory reports
Inventory reports are not associated with a specific application's work items, assignments, or processing. You can run reports for which the Applies To key part is a class derived from the System-, Data-, or Rule- base classes.
- Reviewing exposed properties
To enhance record selection operations for reporting, certain single value properties are stored as exposed columns in an application. You can review which properties are exposed in your appliction.