Hi @RohanZ17012127,

The main differences between class joins, associations, and subreports in Pega lie in their scope, reusability, and purpose:

Class Join:

• Scope: Unique to each report. You configure a join specifically for a single report definition.
• Reusability: Not reusable. Other reports need their own joins defined separately.
• Purpose: Combines data from two classes based on specific criteria within a single report. Useful for displaying related data without requiring separate subreports.

Association:

• Scope: Global across the Pega Platform. A configured association rule can be used in any report.
• Reusability: Highly reusable. Saves time and effort by providing pre-defined joins that can be easily applied to many reports.
• Purpose: Similar to class joins, but offers a standardized and reusable way to connect related classes. Used for common join scenarios.

Subreport:

• Scope: Can be used within a report or as a standalone report.
• Reusability: Can be reused in other reports as well.
• Purpose: More complex than joins. Presents an entire secondary report within the main report. Useful for displaying detailed information at specific points in the main report or adding calculations and aggregations based on a separate data set.

The best choice for your specific needs depends on the complexity of your report and the relationship between the data you want to combine. Choose:

• Class Join: When you need a simple, one-time join for a specific report and don't require future reuse.
• Association: When you need a standardized and reusable join between two classes used in multiple reports.
• Subreport: When you need to embed a separate report or perform complex calculations using additional data within your main report.

Regards,

Mohd Qizer Uddin