The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/queries/new | Design a contact question with a date supplied when it runs. | CAP-PFM-QRY-002 | Executing the question returns contacts that meet its date condition. | inferred |
| 2 | /console/{tenantId}/queries/{id} | Keep the question under a recognizable name. | CAP-PFM-QRY-006 | Its saved definition retains the requested date value and starts private. | inferred |
| 3 | startQueryExport | Request a CSV with technical field names. | CAP-PFM-QRY-014 | The headings follow the selected output fields in their declared order. | test services-platform:modules/queries/tests/integration/services/exports/run-query-export.integration.spec.js#heads the file with the technical names in the query’s output order |
| 4 | /console/{tenantId}/queries/schedules/new | Create a daily morning schedule with the execution day as the date value and skipping enabled for empty results. | CAP-PFM-QRY-015 | The schedule retains the selected time zone, CSV options and recipient. | test |
| 5 | /console/{tenantId}/queries/schedules/{id} | Request an immediate run while the question matches no contacts. | CAP-PFM-QRY-015 | The history records an empty-result skip and contains no delivery. | test |
| 6 | /console/{tenantId}/queries/schedules/{id} | Add a matching contact, run again and open the delivered link. | CAP-PFM-QRY-015 | A single message provides a CSV containing the new contact. | test |
| 7 | /console/{tenantId}/queries | Attempt to remove the question while its schedule exists. | CAP-PFM-QRY-006 | The refusal identifies the schedule that depends on the question. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 4 | The recipient list includes an external address. | Apply the external-recipient permission check. | A caller without that permission cannot retain the external recipient. | test |
| failure | 7 | The coordinator first removes the schedule. | Remove the unused saved question after its dependencies are gone. | The schedule and saved-query definitions no longer exist. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | The schedule supplies its execution day to the date parameter and skips delivery when the result is empty. | test |
02 | A schedule dependency prevents deletion of its saved query. | test |
End-to-end policy: required: Browser coverage connects the query’s Schedule action, parameter display, run history and delivered file; backend coverage supplies the export-format checks.