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}/dataManagement/dataExportSettings | Open the export settings and submit retention and recipient changes with the current version. | CAP-PFM-QRY-018 | The proposed screen receives the updated definition when its version matches. | inferred services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#changes the definition at the version it read |
| 2 | /console/{tenantId}/dataManagement/dataExportSettings | Add the organization’s storage connection as a destination. | CAP-PFM-QRY-018 | The proposed screen can show the destination; its addition has a widening security event. | inferred services-platform:modules/data-exports/tests/integration/services/persistence/destinations.integration.spec.js#records destination.add in the security trail as widening |
| 3 | /console/{tenantId}/dataManagement/dataExports | Request an export now. | CAP-PFM-QRY-018 | The proposed screen receives a queued execution for inspection. | inferred services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#exports now: 202 with the execution queued |
| 4 | /console/{tenantId}/dataManagement/dataExports/{executionId} | Open that execution’s detail. | CAP-PFM-QRY-018 | The evidenced response lists no produced items at this stage. | inferred services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#reads an execution with what it produced, nothing yet |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | The workspace is a sandbox. | Refuse access to export settings as ineligible. | Export settings cannot be configured for that workspace. | test services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#refuses a sandbox its settings with 403 tenant_not_eligible |
| failure | 3 | Another execution is already queued. | Reject a second admission request. | The existing queued execution remains the only admitted request. | test services-platform:modules/data-exports/tests/integration/services/executions/admit-execution.integration.spec.js#refuses while another execution is queued, creating nothing more |
| failure | 1 | A caller has the Power User policy without export authorization. | Reject the export routes for that caller. | The caller cannot read or change the export settings. | test services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#refuses a Power User every data export route |
| Id | Statement | Provenance |
|---|---|---|
01 | Admitting an execution records the execute event as a widening action in the security trail. | test services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js#records the data export event: execute, widening, in its own transaction |
02 | Admission refuses a second request while an execution is already queued. | test services-platform:modules/data-exports/tests/integration/services/executions/admit-execution.integration.spec.js#refuses while another execution is queued, creating nothing more |
End-to-end policy: optional: Backend tests prove the configuration and admission responses. The proposed screens can be examined once package generation and delivery exist; a complete package journey is not established by this foundation.