--- id: CON-PFM-QRY-003 name: Report feature: FEAT-PFM-QRY-04 product_area: platform module: queries revision: 1 status: draft product_intent: confirmed implementation_evidence: observed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- A report retains a named presentation over saved questions, including dashboards, with an owner and audience that remain separate from data-execution authority. owned_by: MOD-PFM-QRY synonyms: - Dashboard (a report of its own kind) not_to_be_confused_with: - The saved question supplying result data - The file produced by rendering a presentation - The earlier batch-report system replaced by coded presentations facets: - name: Kind meaning: 'Coded, table, designed and dashboard forms describe different presentations.' used_for: Selecting a viewer and compatible output formats. source: 'services-platform:docs/queries/reports.md' provenance: documented - name: Audience meaning: 'The owner chooses private, selected-role or organization visibility within source limits.' used_for: Determining where the presentation is discoverable. source: 'services-platform:docs/queries/reports.md' provenance: documented - name: Sources meaning: Saved questions supply the report’s data and remain recorded dependencies. used_for: Protecting against deletion and tracking definition changes. source: 'services-platform:docs/queries/reports.md' provenance: documented - name: System reports meaning: Rhythm distributes built-in presentations with the console. used_for: Providing standard entries from which staff can save copies. source: 'services-platform:docs/queries/reports.md' provenance: documented - name: Widgets meaning: 'Dashboard elements present individual figures, charts, tables or text.' used_for: Combining several questions in one view. source: 'services-platform:docs/queries/reports.md' provenance: documented - name: Rendered file meaning: A rendering execution produces a PDF or eligible Excel file under requester access. used_for: Preparing a downloadable presentation. source: 'services-platform:docs/queries/report-rendering.md' provenance: documented relationships: - to: CON-PFM-QRY-002 statement: Report visibility cannot exceed the visibility of its saved-question sources. provenance: documented source: 'services-platform:docs/queries/reports.md#2. Who may do what' - to: CON-PFM-QRY-004 statement: 'Rendering produces a downloadable file, and a schedule can deliver it repeatedly.' provenance: documented source: >- services-platform:docs/queries/report-rendering.md#Report rendering: PDF and Excel exports of reports, as built lifecycle: - state: private meaning: The new presentation or copy belongs privately to its creator. how_it_changes: Its owner or a manager applies an authorized wider audience. - state: shared meaning: Selected colleagues can discover the presentation subject to source checks. how_it_changes: Its owner or manager narrows the audience or removes the record. - state: deleted meaning: The presentation is removed while source questions and completed files remain separate. how_it_changes: Deletion releases dependencies and pauses the associated schedules; there is no report restore action. acted_on_by: - CAP-PFM-QRY-011 - CAP-PFM-QRY-012 - CAP-PFM-QRY-013 - CAP-PFM-QRY-015 visible_to: - ACT-PFM-013 - ACT-PFM-014 - ACT-PFM-007 - ACT-PFM-015 evidence: - 'Pinned reference: services-platform:docs/queries/report-rendering.md' - 'Pinned reference: services-platform:docs/queries/reports.md' supersedes: [] origin: 'services-platform:docs/milestones/plans/RPT-M1-plan.md#D1' intent_sources: - 'services-platform:docs/milestones/plans/RPT-M1-plan.md#D1' --- # Report ## What It Is A report is the presentation staff return to when they need a recognizable view of their data. A financial listing, a table of records and a dashboard can all serve that purpose. The report retains a name, owner, audience and layout. Its saved questions remain separate sources, so the presentation can be maintained without taking ownership of the business records it shows. The catalog brings customer reports together with Rhythm’s built-in entries. Customer reports are stored records. Built-in reports are delivered with the console and can serve as starting points for a saved copy. A person allowed to create reports owns the copy they make; it begins as their private work. Report identity remains separate from the name and from the data returned today. Names distinguish an owner’s reports, while the saved layout describes how later executions are presented. A source change can therefore require review even when the report’s own layout has not changed. ## What It Is Not A report does not grant the data permissions needed to run its sources. A saved question describes what to ask, while the report describes how to present it. A rendered file is a separate completed execution that can outlive the report record. A dashboard belongs to the report family, rather than creating a second catalog or a separate audience system. ## How It Is Used Staff browse their own, shared and built-in entries, open a useful presentation and save a copy when they need their own arrangement. Authors share with selected roles or the organization. Platform checks source audiences before accepting that share. Readers run the data with their own access. Read Only colleagues can consume shared reports without acquiring create or copy powers. Managers maintain stored reports across owners. Version checks prevent an older editing session from silently replacing a later change. Catalog filtering checks visible source questions and their base datasets; it does not validate the complete source query. A report can consequently appear in the catalog and still fail during execution because another part of its question is unavailable. Product should treat discovery and successful execution as separate assurances. ## Its Facets **Kind.** Coded, table, designed and dashboard presentations use the same retained report structure while supporting different viewing and file behaviours. **Audience.** Private, selected-role and organization sharing control discovery. The source audience limits how far sharing can extend. **Sources.** Ordinary reports identify one saved question. Dashboards record their distinct widget sources. Dependencies block source deletion and explain changed-definition warnings. **System reports.** Built-in entries ship with the console. Their visibility is a console responsibility rather than the stored-report catalog’s responsibility. **Widgets.** Each dashboard element obtains its own source result. One unavailable source can fail independently of the remaining widgets. **Rendered file.** Exporting creates a separate rendering request evaluated as the person who asked for it. Supported formats depend on the report kind. ## How It Relates Queries supply data definitions and datasets supply their vocabulary. Export records preserve rendered files; schedules arrange repeated delivery. Deleting a report releases its query dependencies and pauses its schedules while completed files follow their own retention. Accounting remains responsible for accounting figures and business interpretations. ## What It Could Become The product should settle ownership handover and whether report history or catalog pins deserve supported user flows. Reporting’s approved plan confirms selected decisions while product acceptance remains pending. Later reporting work should resolve the gap between catalog readability checks and complete query execution.