Manage Reporting Packs

A reporting pack defines reusable reports from registered capabilities. Use Admin → Reporting Packs to edit a draft and inspect its preview before publishing a candidate.

Before you start

Sign in as a tenant administrator. You need an existing registered draft or template and data that matches its capabilities. Your tenant supplies the preview context; you do not need storage credentials or platform access.

If the list says No registered template is available yet, Create pack draft is disabled. This screen cannot create the missing capability from scratch. Keep that missing prerequisite separate from an empty data preview.

Edit and validate a draft

1. Open Admin → Reporting Packs. Find the pack by its name, key and Registered template; note its Revision.
2. Choose Edit mapping for that row. Start with a small change to the existing definition. For example, open Advanced contract fields and change Display name to Daily activity while keeping the pack key and existing capability mappings.
3. Review the report fields and mappings that the editor exposes. Use only capabilities and data labels available to your tenant.
4. Choose Validate draft. Continue when the editor reports Definition is valid. Correct the labeled fields if validation fails.
5. Choose Save draft. Close the editor and check the row's saved name and revision before publishing. Validation alone does not save your changes.

Create pack draft starts from the first available draft's definition. To make a separate pack, give it a new Pack key and Display name under Advanced contract fields, then inspect all inherited mappings before saving. A new draft starts with Enabled when the candidate activates off; select it when the new pack should serve after activation.

Preview the result

Reopen the saved row with Edit mapping, choose the editor's Preview and publish step, then Preview executive report. Close the editor to inspect the resulting preview below the table. This selects the intended pack; the page-level preview button otherwise uses the first draft when no editor is open.

The preview uses a one-day range and is capped at the registered template's limit or 100 rows, whichever is smaller. It renders aggregates, not raw event payloads or subject records.

Read Candidate executive report, Data state, Trust, and any warnings together. A partial result is not complete coverage. Check that the result's label, unit and meaning match the change you intended; a successful preview does not prove that a candidate is active.

Publish and check serving state

1. Save and close the editor, then choose Publish candidate on the intended draft row.
2. Review Publish reporting pack candidate and select Confirm publish. This creates an immutable candidate generation; it does not bypass runtime acknowledgement or immediately activate a new query path.
3. Inspect the published generation's state and consumer acknowledgements. Pending or rejected acknowledgement needs resolution before claiming the report is serving.
4. Check Serving pack health and Authorized dashboards. Open the authorized report and confirm its result after activation.

For a correction, edit and validate the draft, then publish a new generation. Published generations are immutable. Use this forward-correction workflow if an older Request rollback control is visible.

When something fails

What you see	What to do
Drafts could not load	Reload the section after service access returns; do not assume the list is empty.
Draft could not be saved or validated	Correct the labeled fields. If someone else edited it, reload the draft and review its latest revision before retrying.
Preview failed	Check the registered capability and tenant context, then retry. The candidate remains unchanged.
Candidate publishing failed	Keep the error and draft identity; resolve the failure before retrying. Existing runtime configuration remains in place.
A serving pack cannot be used	Correct the affected definition and publish a new generation. Its reports are not being produced while it fails validation.

If a section is missing or access is denied, have your tenant administrator check your role. Do not switch tenant identifiers to work around authorization.