ATS-PFM-QRY-018 Request a portable workspace data package: Capability Test Specification
Markdown Design / Platform / Questions, record exploration and data delivery / Workspace export administration / Capability Test Specification Coverage Rule covered Transition gap: FND-PFM-QRY-068 Validation gap: FND-PFM-QRY-068 Permission covered Edge gap: FND-PFM-QRY-068 Failure covered Boundary covered Concurrency covered Invariant gap: FND-PFM-QRY-068 Interaction covered Test Scenarios 17 scenarios proving CAP-PFM-QRY-018
01 Default export authority belongs to Administrators permission api negative test
Proves BR-CAP-PFM-QRY-018-01Preconditions Built-in Power User and Administrator contexts are available. Steps Exercise the data-export routes under both. Expected Power User is refused and Administrator reaches the permitted operations. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js #refuses a Power User every data export route 02 Export keys are independently required permission api negative test
Proves BR-CAP-PFM-QRY-018-02Preconditions Each caller lacks one export key despite holding the others and administrator tier. Steps Invoke operations governed by the missing key. Expected Every such operation is refused. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js #is refused every read route when it holds the other three keys and the administrator tier 06 Admission records a single queued execution concurrency api negative test
Proves BR-CAP-PFM-QRY-018-06INV-DOM-PFM-QRY-004-09 Preconditions Settings can admit execution but another request is queued or settings are suspended. Steps Admit ordinary work, repeat it, try suspension and admit a staff-triggered execution. Expected The valid request copies its instant and settings, conflicts or suspension refuse, and staff work is marked nonconsuming. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js #answers it queued, at the request’s instant, with the definition’s switches copied and the allowance counted 08 Incomplete package actions state their limits failure api negative test
Proves BR-CAP-PFM-QRY-018-08Preconditions An execution is queued without a generated package. Steps Read its manifest and request cancellation, download, early deletion and delivery retry. Expected The manifest is missing and the unfinished actions return not implemented. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js #is answered 404 for the manifest of an execution with no package yet 09 Staff and customer export surfaces remain separate permission api negative test
Proves BR-CAP-PFM-QRY-018-09Preconditions Staff have platform and HQ export grants and a customer has administrator access. Steps Invoke customer-console and HQ operations under each context. Expected Staff are refused on console routes, HQ staff reads span workspaces and customers cannot use HQ. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js #is refused every console route, whatever it holds at platform scope (rule S1) 12 Recent authentication remains required by product intent permission api negative proposed
Proves BR-CAP-PFM-QRY-018-12Preconditions One administrator signed in twenty minutes ago and another five minutes ago. Steps Attempt destination changes and package download. Expected The proposed proof requires renewed authentication for the older session and acceptance for the recent one. Data Prepare isolated fixtures for the states described here. Source services-platform:docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md #D-11. Elevated authentication for download and destination changes: a recent-authentication check in release 1 13 Allowances remain workspace-specific product intent rule api negative proposed
Proves BR-CAP-PFM-QRY-018-13Preconditions Two workspaces share a customer and one has exhausted its allowance. Steps Request exports in both and apply a customer-level override. Expected Only the exhausted workspace should fail before override; the override should affect both. Data Prepare isolated fixtures for the states described here. Source services-platform:docs/proposals/tenant-data-export/20-risks-tradeoffs-decisions.md #D-14. Where the allowance attaches (blocks WP-5) — decided: per tenant 15 A workspace package grant does not reveal a query file interaction api proposed
Proves BR-CAP-PFM-QRY-014-07BR-CAP-PFM-QRY-018-08Preconditions One user has only workspace-package read and download powers; another owns a completed query file. Steps Request the query-file status and download as the package reader, then request the unfinished workspace package action. Expected Package powers confer no access to the other person’s query file; the unfinished package action reports its implemented limit. Data Use an isolated workspace with the described source records, access grants and a surviving control workspace. Source services-platform:modules/queries/tests/integration/services/exports/query-export-routes.integration.spec.js #answers 404 to a colleague who did not ask for it, even once the file exists,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is answered 409 not_implemented for a download, until the generation job 16 Workspace cleanup includes search and package resources interaction api proposed
Proves BR-CAP-PFM-QRY-017-11BR-CAP-PFM-QRY-018-08Preconditions An isolated workspace contains indexed contacts and export settings with a queued request. Steps Request workspace deletion, settle open index work and repeat participant cleanup until its inventory is empty. Expected Search documents and workspace export resources disappear without touching a surviving control workspace. Data Use an isolated workspace with the described source records, access grants and a surviving control workspace. Source services-platform:modules/quick-search/tests/integration/services/maintenance/tenant-participant.integration.spec.js #purges the tenant once the rebuild has settled, the job’s own three tables included,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is answered 409 not_implemented for a download, until the generation job 17 Workspace removal clears both kinds of retained history interaction api proposed
Proves BR-CAP-PFM-QRY-018-08BR-CAP-PFM-QRY-019-11Preconditions An isolated workspace has export settings and queued history plus multiple snapshot versions. Steps Run workspace deletion to completion and inspect both inventories. Expected Its package foundation records and snapshot history are removed; repeat cleanup reports nothing further. Data Use an isolated workspace with the described source records, access grants and a surviving control workspace. Source services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js #is answered 409 not_implemented for a download, until the generation job,services-platform:modules/snapshots/tests/integration/lifecycle/pipeline/snapshot-pipeline.integration.spec.js#removes every snapshot row, run and override of the purged tenants, the run's version chain included ← Previous Capability Test Specification ATS-PFM-QRY-017 · Maintain the fields and freshness of Quick Search: Capability Test Specification Next Capability Test Specification → ATS-PFM-QRY-019 · Preserve and inspect monthly data snapshots: Capability Test Specification