--- id: JNY-PFM-QRY-006 title: Configure and admit a workspace export feature: FEAT-PFM-QRY-07 product_area: platform module: queries revision: 1 status: draft product_intent: confirmed implementation_evidence: partially-observed supersedes: [] source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f actor: ACT-PFM-007 goal: 'Set export options and destinations, then request and inspect an execution.' capabilities: - CAP-PFM-QRY-018 screens: - '/console/{tenantId}/dataManagement/dataExportSettings' - '/console/{tenantId}/dataManagement/dataExports' - '/console/{tenantId}/dataManagement/dataExports/{executionId}' steps: - 'n': 1 surface: '/console/{tenantId}/dataManagement/dataExportSettings' action: Open the export settings and submit retention and recipient changes with the current version. capability: CAP-PFM-QRY-018 expected: The proposed screen receives the updated definition when its version matches. provenance: inferred source: >- services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#changes the definition at the version it read note: >- The cited evidence supports a service result or a related interaction. This screen sequence requires its own browser proof. - 'n': 2 surface: '/console/{tenantId}/dataManagement/dataExportSettings' action: Add the organization’s storage connection as a destination. capability: CAP-PFM-QRY-018 expected: The proposed screen can show the destination; its addition has a widening security event. provenance: inferred source: >- services-platform:modules/data-exports/tests/integration/services/persistence/destinations.integration.spec.js#records destination.add in the security trail as widening note: >- The cited evidence supports a service result or a related interaction. This screen sequence requires its own browser proof. - 'n': 3 surface: '/console/{tenantId}/dataManagement/dataExports' action: Request an export now. capability: CAP-PFM-QRY-018 expected: The proposed screen receives a queued execution for inspection. provenance: inferred source: >- services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#exports now: 202 with the execution queued note: >- The cited evidence supports a service result or a related interaction. This screen sequence requires its own browser proof. - 'n': 4 surface: '/console/{tenantId}/dataManagement/dataExports/{executionId}' action: Open that execution’s detail. capability: CAP-PFM-QRY-018 expected: The evidenced response lists no produced items at this stage. provenance: inferred source: >- services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#reads an execution with what it produced, nothing yet note: >- The cited evidence supports a service result or a related interaction. This screen sequence requires its own browser proof. alternates: - from_step: 3 condition: The workspace is a sandbox. path: Refuse access to export settings as ineligible. outcome: Export settings cannot be configured for that workspace. provenance: test source: >- services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#refuses a sandbox its settings with 403 tenant_not_eligible failures: - from_step: 3 condition: Another execution is already queued. path: Reject a second admission request. outcome: The existing queued execution remains the only admitted request. provenance: test source: >- services-platform:modules/data-exports/tests/integration/services/executions/admit-execution.integration.spec.js#refuses while another execution is queued, creating nothing more - from_step: 1 condition: A caller has the Power User policy without export authorization. path: Reject the export routes for that caller. outcome: The caller cannot read or change the export settings. provenance: test source: >- services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#refuses a Power User every data export route rules_in_play: - BR-CAP-PFM-QRY-018-01 - BR-CAP-PFM-QRY-018-03 - BR-CAP-PFM-QRY-018-05 - BR-CAP-PFM-QRY-018-06 - BR-CAP-PFM-QRY-018-08 assertions: - id: AS-JNY-PFM-QRY-006-01 statement: Admitting an execution records the execute event as a widening action in the security trail. provenance: test source: >- services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js#records the data export event: execute, widening, in its own transaction - id: AS-JNY-PFM-QRY-006-02 statement: Admission refuses a second request while an execution is already queued. provenance: test source: >- services-platform:modules/data-exports/tests/integration/services/executions/admit-execution.integration.spec.js#refuses while another execution is queued, creating nothing more e2e_policy: optional e2e_reason: >- 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. evidence: - 'Pinned reference: services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js' - >- Pinned reference: services-platform:modules/data-exports/tests/integration/services/executions/admit-execution.integration.spec.js - >- Pinned reference: services-platform:modules/data-exports/tests/integration/services/persistence/destinations.integration.spec.js - >- Pinned reference: services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js origin: 'services-platform:docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md#1. Decisions' intent_sources: - 'services-platform:docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md#1. Decisions' proved_by: [] --- # Configure and admit a workspace export ## Story An administrator updates export settings, adds a storage destination and requests an execution. The current service admits a queued record and exposes its detail, with no produced package yet. A concurrent request is refused. The walkthrough proposes the console sequence around those backend responses and keeps the unimplemented generation and delivery stages visible.