Report Definitions were introduced in Pega 7 to improve Pega‘s Reporting capabilities. Report Definitions provide additional capabilities that support all functionalities previously provided by List Views, Summary Views, and Custom Database Views.
For more information about Report Definitions, see:
How to identify
To identify List Views and Summary Views, go to Application Guardrails landing page. Click Warnings Summary, and open the lists. Rules labelled "Deprecated class instance" must be replaced with Report Definitions.
To identify Views and Materialized Views, run the Database Cloud Readiness Tool. This identifies all the Custom Database Objects. Database Objects with an Object Type of View or Materialized View must be replaced with Report Definitions.
How to modernize
List Views are deprecated rules. Replace them with Report Definition rules.
Replace references to List Views in the UI with new controls that support feeding data into different controls by leveraging OOTB Pega Platform features. Data will be retrieved from the Report Definition that has replaced the existing List View.
Summary Views are deprecated rules. Replace them with Report Definition rules.
Replace drill down logic combining List Views and Summary Views with two report Definitions that provide the expected outcome.
Replace references to Summary Views in the UI with new controls that support feeding data into different controls by leveraging OOTB Pega Platform features. Data will be retrieved from the Report Definition that has replaced the existing List View.
Custom Database Views
Report Definitions also provide new joining capabilities (previously not available in List Views or Summary Views), which make this type of rule the right replacement for Custom Database Views. Moving all configuration and logic from the infrastructure layer to the Pega Platform layer, ensures better maintainability of the overall application.
Report Definition rules contain the join logic on the Data Access tab. Different table classes can be leveraged if relevant properties are exposed for reporting.
For more information, see: Joins, associations, and subreports on Pega Academy