Reporting
What the exam tests
Reporting questions test whether you can choose the right report type, source, and aggregation for a business question, and secure and schedule the result without harming application performance.
Core rules
- A Report Definition is the reusable rule behind a report; it defines source class, columns, filters, sorting, and grouping.
- List reports return rows; summary reports group and aggregate; chart reports visualize a summary.
- Report on exposed columns or optimized data sources rather than joining large work tables at run time.
- Report Browser organizes reports by category; Insights surface metrics for case workers and managers.
- Scheduled reports and subscriptions deliver output on a cadence to named recipients.
- Report security follows access roles; a report must not expose data the viewer cannot open.
Worked example
A service manager wants monthly case volume by stage and owner. Build a summary report on the work class, group by stage and owner, count case IDs, filter resolved date to the current month, and display a stacked bar chart. Schedule it for the first business day. The reasoning: the business question is an aggregate, so summary plus chart is correct; a list report would return thousands of rows and obscure the trend.
Traps
Using a list report for an aggregate question; reporting directly on non-exposed properties at scale; scheduling without checking recipient access; duplicating a report instead of reusing a report definition; ignoring time-zone effects on date filters.