--- id: ATS-PFM-QRY-006 scope: CAP-PFM-QRY-006 product_area: platform module: queries revision: 2 status: proposed approved_by: null approved_at: null source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464 scenarios: - id: ATS-PFM-QRY-006-01 title: Private questions remain outside customer management level: api proves: - BR-CAP-PFM-QRY-006-01 - INV-DOM-PFM-QRY-002-02 preconditions: A private query exists beside colleague and manager contexts. steps: Read and list it using those customer contexts. expected: Both receive 404 and neither catalog lists the query. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#tells a colleague that somebody else’s private query does not exist, as 404 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#tells a manager the same thing, as 404 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#leaves a colleague’s private query out of the list - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#tells a colleague that somebody else’s private query does not exist, as 404 category: permission - id: ATS-PFM-QRY-006-02 title: Role visibility follows active membership level: api proves: - BR-CAP-PFM-QRY-006-02 preconditions: A saved question is shared with one role. steps: Read and list it as a holder and nonholder. expected: The holder can read it; the nonholder receives not found and no list entry. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#lets a holder of the selected role read the record [E2E-SQ-08] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers not found for a role the caller does not hold, and excludes the record from the list [E2E-SQ-09] - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#lets a holder of the selected role read the record [E2E-SQ-08] category: permission - id: ATS-PFM-QRY-006-03 title: Read Only consumes shared definitions without writing level: api proves: - BR-CAP-PFM-QRY-006-03 preconditions: A Read Only user can discover an organization query. steps: 'List, open and execute it, then attempt creation, replacement and deletion.' expected: Reads succeed and each attempted write returns 403. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - 'services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#lists the organization’s saved query' - 'services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#runs the organization’s saved query' - >- services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#is refused creating a saved query with 403 - >- services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#is refused replacing a saved query with 403 - >- services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#is refused deleting a saved query with 403 - TST-PFM-QRY-231 provenance: test source: 'services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#lists the organization’s saved query' category: permission - id: ATS-PFM-QRY-006-04 title: Organization sharing needs its own grant level: api proves: - BR-CAP-PFM-QRY-006-04 preconditions: Otherwise equivalent callers differ in share permission. steps: Create shared queries and attempt to make a shared query private. expected: Audience changes fail without share authority and succeed with it. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses making the query the organization’s without the power to share it as 403 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#accepts it from a caller who may share - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses the owner taking its shared query back to private without the power to share as 403 - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses making the query the organization’s without the power to share it as 403 category: permission - id: ATS-PFM-QRY-006-05 title: Shared maintenance belongs to owner or manager level: api proves: - BR-CAP-PFM-QRY-006-05 preconditions: An organization-visible question belongs to another person. steps: Edit and delete it as a colleague and manager. expected: The colleague is refused and the manager can maintain it. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a colleague editing the organization’s query as 403 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#lets a manager edit the organization’s query - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a colleague deleting the organization’s query as 403 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#lets a manager delete the organization’s query - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a colleague editing the organization’s query as 403 category: permission - id: ATS-PFM-QRY-006-06 title: Support staff have the recorded private-work exception level: unit proves: - BR-CAP-PFM-QRY-006-06 preconditions: A staff context has a workspace grant and a customer manager does not own the private question. steps: 'Evaluate read, edit and share access for both.' expected: Staff receive the private-work powers; the customer manager cannot read it. negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/unit/services/saved-queries/saved-query-access.spec.ts#shows a colleague’s private query to staff - >- services-platform:modules/queries/tests/unit/services/saved-queries/saved-query-access.spec.ts#lets staff write a colleague’s private query, which a non-staff caller may not - >- services-platform:modules/queries/tests/unit/services/saved-queries/saved-query-access.spec.ts#hides a colleague’s private query from a non-staff holder of platform.saved-queries.manage - TST-PFM-QRY-413 provenance: test source: >- services-platform:modules/queries/tests/unit/services/saved-queries/saved-query-access.spec.ts#shows a colleague’s private query to staff category: permission - id: ATS-PFM-QRY-006-07 title: Role updates replace the selected set level: api proves: - BR-CAP-PFM-QRY-006-07 preconditions: A query already has role visibility. steps: 'Replace its roles, change to organization visibility and read a private query.' expected: 'The role set is replaced, and non-role audiences expose no role selection.' negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#creates a role-shared query and answers its stored role_ids [E2E-SQ-06] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#replaces the whole selected-role set rather than appending to it [E2E-SQ-07] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers no role_ids property when an update takes a role-shared query to the whole organization [E2E-SQ-12] - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#creates a role-shared query and answers its stored role_ids [E2E-SQ-06] category: boundary - id: ATS-PFM-QRY-006-08 title: Dependent reports block audience narrowing level: api proves: - BR-CAP-PFM-QRY-006-08 - INV-DOM-PFM-QRY-002-06 preconditions: Reports and dashboards depend on questions with wider audiences. steps: Narrow their sources before and after narrowing the presentations. expected: Initial saves report blocking dependencies and write nothing; aligned audiences permit the change. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#refuses narrowing it to private with 409 saved_query_narrower_than_reports, naming the report - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#refuses dropping a role a report over it is shared with, naming that report and its roles - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#refuses narrowing it below the dashboard’s audience, naming the dashboard - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#allows the same save once the report is narrowed to private - >- services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#is refused 409 saved_query_narrower_than_reports, naming the report - TST-PFM-QRY-345 - TST-PFM-QRY-231 provenance: test source: >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#refuses narrowing it to private with 409 saved_query_narrower_than_reports, naming the report category: interaction binding_note: >- The cited suites contribute separate assertions. The complete combined example is not a single executable journey. - id: ATS-PFM-QRY-006-09 title: Omitted audiences preserve existing sharing level: api proves: - BR-CAP-PFM-QRY-006-09 preconditions: One query is role-shared and another organization-visible. steps: Save without visibility and save role visibility without new roles. expected: The existing visibility and selected roles survive. negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#keeps a role-shared query’s visibility and roles when the save states no visibility - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#keeps the roles when the save states "roles" and no roleIds - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#keeps the organization’s visibility when the save states none - >- services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js#keeps the query’s visibility when a replacement leaves it out - TST-PFM-QRY-345 - TST-PFM-QRY-231 provenance: test source: >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#keeps a role-shared query’s visibility and roles when the save states no visibility category: rule binding_note: >- The cited suites contribute separate assertions. The complete combined example is not a single executable journey. - id: ATS-PFM-QRY-006-10 title: Saves reject questions unavailable to the saver level: api proves: - BR-CAP-PFM-QRY-006-10 preconditions: Definitions include invalid criteria and a forbidden dataset. steps: Save each proposed question. expected: Definition problems return 400 and missing data access returns 403. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a body whose definition cannot be run as written as 400 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a dataset this caller may not query as 403, however the library is reached - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a body whose definition cannot be run as written as 400 category: validation - id: ATS-PFM-QRY-006-11 title: Stored values preserve intentional whitespace level: api proves: - BR-CAP-PFM-QRY-006-11 - INV-DOM-PFM-QRY-002-03 preconditions: A criterion text value has a trailing space. steps: Save the query and read its definition. expected: The value and full definition retain their submitted content. negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#leaves a criterion’s value exactly as the person typed it, spaces and all - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers the definition it stored, and the version of the definition format - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#leaves a criterion’s value exactly as the person typed it, spaces and all category: invariant - id: ATS-PFM-QRY-006-12 title: Query names normalize within one owner level: api proves: - BR-CAP-PFM-QRY-006-12 - INV-DOM-PFM-QRY-002-04 preconditions: An owner already has a question named Q3. steps: Create or rename another to the normalized name and try the same name for another owner and workspace. expected: The same-owner duplicates fail while the separate ownership contexts allow reuse. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a create whose name normalizes to one the owner already has, naming the trimmed proposed name as 400 [E2E-SQ-01] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a rename that would duplicate another of the owner’s saved queries as 400, leaving the row unrenamed [E2E-SQ-02] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#lets a different owner save the same name, with the created record answered under that owner [E2E-SQ-03] - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a create whose name normalizes to one the owner already has, naming the trimmed proposed name as 400 [E2E-SQ-01] category: validation - id: ATS-PFM-QRY-006-13 title: Query replacement requires its read version level: api proves: - BR-CAP-PFM-QRY-006-13 - INV-DOM-PFM-QRY-002-13 preconditions: A query is currently at version two. steps: Replace using version one and without a version. expected: The stale request returns 409 and the missing version returns 400. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a replacement at a version that is no longer in force as 409 - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a body that states no version at all as 400 - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses a replacement at a version that is no longer in force as 409 category: concurrency - id: ATS-PFM-QRY-006-14 title: Dependent sources cannot be deleted level: api proves: - BR-CAP-PFM-QRY-006-14 - INV-DOM-PFM-QRY-002-05 preconditions: 'Separate queries are used by reports, widgets and schedules.' steps: Attempt to remove every source query. expected: Each request reports its blocking dependency with 409 and retains the query. negative: true data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/reports.e2e.spec.js#refuses to delete a saved query a report presents as 409 saved_query_reported - >- services-platform:modules/queries/tests/e2e/reports.e2e.spec.js#refuses to delete a saved query one of its widgets draws on as 409 saved_query_reported - >- services-platform:modules/queries/tests/integration/services/schedules/query-schedule-routes.integration.spec.js#refuses to delete a saved query that schedules run (409), naming them - TST-PFM-QRY-233 - TST-PFM-QRY-349 provenance: test source: >- services-platform:modules/queries/tests/e2e/reports.e2e.spec.js#refuses to delete a saved query a report presents as 409 saved_query_reported category: interaction binding_note: >- The cited suites contribute separate assertions. The complete combined example is not a single executable journey. - id: ATS-PFM-QRY-006-15 title: Private work does not leak through library metadata level: api proves: - BR-CAP-PFM-QRY-006-15 preconditions: A colleague owns a private query and another query has lost dataset access. steps: 'Inspect pages, counts and facets, then open the problematic accessible query.' expected: >- Private work is absent from metadata; the readable query reports problems rather than rejecting its read. negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#leaves a colleague’s private query out of the numbered page too - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers how many queries each view holds - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers the record and its problems, not a refusal, when the dataset is no longer the caller’s to query - TST-PFM-QRY-234 provenance: test source: >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#leaves a colleague’s private query out of the numbered page too category: invariant - id: ATS-PFM-QRY-006-16 title: Saved-question delivery retains deletion protection level: browser proves: - AS-JNY-PFM-QRY-002-01 - AS-JNY-PFM-QRY-002-02 preconditions: A coordinator retains a membership question for recurring delivery. steps: Execute the saved-question browser journey. expected: 'The question is saved and scheduled, and its active schedule blocks deletion.' negative: false data_needs: Use the existing binding’s controlled fixture data. bound_to: - 'react-console:acceptance/reporting/playwright/journeys/schedules/RPT-ACC-0434.spec.ts#RPT-ACC-0434' - TST-PFM-QRY-149 provenance: test source: 'react-console:acceptance/reporting/playwright/journeys/schedules/RPT-ACC-0434.spec.ts#RPT-ACC-0434' category: interaction - id: ATS-PFM-QRY-006-17 title: A colleague runs a shared question with personal values category: interaction level: api exercises: - CAP-PFM-QRY-006 - CAP-PFM-QRY-007 proves: - BR-CAP-PFM-QRY-006-02 - BR-CAP-PFM-QRY-007-01 preconditions: Two users share one role and a saved personal-task question with a requested date. steps: 'Run the shared question as each user with the same date, then remove one user’s dataset grant and rerun.' expected: Each successful answer contains that runner’s tasks; the revoked runner receives no result. negative: true data_needs: >- Use an isolated workspace with the described source records, access grants and a surviving control workspace. bound_to: [] provenance: proposed source: - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers not found for a role the caller does not hold, and excludes the record from the list [E2E-SQ-09] - >- services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses to run it for a caller who may not query the dataset as 403, however it was shared - id: ATS-PFM-QRY-006-18 title: A source audience cannot strand a wider report category: interaction level: api exercises: - CAP-PFM-QRY-006 - CAP-PFM-QRY-011 proves: - BR-CAP-PFM-QRY-006-08 - BR-CAP-PFM-QRY-011-04 preconditions: A role-shared report depends on an organization-shared query. steps: 'Attempt to make the query private, then narrow the report and repeat the query change.' expected: >- The first change identifies the blocking report; compatible audience changes allow the query to become private. negative: false data_needs: >- Use an isolated workspace with the described source records, access grants and a surviving control workspace. bound_to: [] provenance: proposed source: - >- services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js#refuses narrowing it to private with 409 saved_query_narrower_than_reports, naming the report - >- services-platform:modules/queries/tests/e2e/reports.e2e.spec.js#refuses a report shared wider than its saved query as 409 ReportSharedWiderThanQuery, naming the query - id: ATS-PFM-QRY-006-19 title: Scheduling protects the retained source until removed category: interaction level: api exercises: - CAP-PFM-QRY-006 - CAP-PFM-QRY-015 proves: - BR-CAP-PFM-QRY-006-14 - BR-CAP-PFM-QRY-015-03 preconditions: A saved contact question has an enabled query schedule. steps: 'Edit the question, compare the schedule, attempt query deletion, then delete the schedule and try again.' expected: >- The schedule keeps its earlier copy and exposes the change; deletion succeeds only after the dependency is removed. negative: false data_needs: >- Use an isolated workspace with the described source records, access grants and a surviving control workspace. bound_to: [] provenance: proposed source: - >- services-platform:modules/queries/tests/e2e/reports.e2e.spec.js#refuses to delete a saved query a report presents as 409 saved_query_reported - >- services-platform:modules/queries/tests/integration/services/schedules/query-schedule-routes.integration.spec.js#flags the saved query as changed since the schedule was set up evidence: - 'Pinned reference: react-console:acceptance/reporting/playwright/journeys/schedules/RPT-ACC-0434.spec.ts' - 'Pinned reference: services-platform:modules/queries/tests/e2e/read-tier.e2e.spec.js' - 'Pinned reference: services-platform:modules/queries/tests/e2e/reports.e2e.spec.js' - 'Pinned reference: services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js' - >- Pinned reference: services-platform:modules/queries/tests/integration/services/saved-queries/saved-query-narrowing.integration.spec.js - >- Pinned reference: services-platform:modules/queries/tests/integration/services/schedules/query-schedule-routes.integration.spec.js - >- Pinned reference: services-platform:modules/queries/tests/unit/services/saved-queries/saved-query-access.spec.ts coverage_notes: transition: >- This capability has no formal lifecycle of its own. Audience and definition changes remain rule, permission and concurrency proofs; related lifecycles are exercised through interaction scenarios. coverage: rule: covered transition: not-applicable validation: covered permission: covered edge: 'gap: FND-PFM-QRY-056' failure: 'gap: FND-PFM-QRY-056' boundary: covered concurrency: covered invariant: covered interaction: covered coverage_findings: - FND-PFM-QRY-056 transition_obligations: [] unproved_rules: [] --- # Save and share reusable questions: Capability Test Specification ## Coverage | Rule | Scenario or Finding | |---|---| | `BR-CAP-PFM-QRY-006-01` | `ATS-PFM-QRY-006-01` | | `BR-CAP-PFM-QRY-006-02` | `ATS-PFM-QRY-006-02`, `ATS-PFM-QRY-006-17` | | `BR-CAP-PFM-QRY-006-03` | `ATS-PFM-QRY-006-03` | | `BR-CAP-PFM-QRY-006-04` | `ATS-PFM-QRY-006-04` | | `BR-CAP-PFM-QRY-006-05` | `ATS-PFM-QRY-006-05` | | `BR-CAP-PFM-QRY-006-06` | `ATS-PFM-QRY-006-06` | | `BR-CAP-PFM-QRY-006-07` | `ATS-PFM-QRY-006-07` | | `BR-CAP-PFM-QRY-006-08` | `ATS-PFM-QRY-006-08`, `ATS-PFM-QRY-006-18` | | `BR-CAP-PFM-QRY-006-09` | `ATS-PFM-QRY-006-09` | | `BR-CAP-PFM-QRY-006-10` | `ATS-PFM-QRY-006-10` | | `BR-CAP-PFM-QRY-006-11` | `ATS-PFM-QRY-006-11` | | `BR-CAP-PFM-QRY-006-12` | `ATS-PFM-QRY-006-12` | | `BR-CAP-PFM-QRY-006-13` | `ATS-PFM-QRY-006-13` | | `BR-CAP-PFM-QRY-006-14` | `ATS-PFM-QRY-006-14`, `ATS-PFM-QRY-006-19` | | `BR-CAP-PFM-QRY-006-15` | `ATS-PFM-QRY-006-15` | ## Interactions With Related Capabilities The combined examples change a source, its audience or its retained state before checking the dependent outcome. Unbound examples remain proposed, and the coverage finding retains design obligations that these examples do not establish. | Related Capability | Scenario | |---|---| | Journey dependency | `ATS-PFM-QRY-006-08` | | Journey dependency | `ATS-PFM-QRY-006-14` | | Journey dependency | `ATS-PFM-QRY-006-16` | | `CAP-PFM-QRY-007` | `ATS-PFM-QRY-006-17` | | `CAP-PFM-QRY-011` | `ATS-PFM-QRY-006-18` | | `CAP-PFM-QRY-015` | `ATS-PFM-QRY-006-19` | ## Evidence and Binding Limits The source revisions pin the inspected assertions. A test binding identifies written assertions, and does not establish a successful run or approval of the expected behavior.