--- id: FAS-PFM-MTD-03 title: Record Presentations Acceptance feature: FEAT-PFM-MTD-03 product_area: platform module: metadata revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-PFM-MTD-008 scenarios: - id: FAS-PFM-MTD-03-01 title: An administrator keeps a reusable contact form kind: behaviour exercises: - CAP-PFM-MTD-008 relies_on: - ATS-PFM-MTD-008-01 - ATS-PFM-MTD-008-07 preconditions: The administrator can manage contact forms. steps: - do: >- Create from the default, edit its description, clone it, rename the clone and delete the clone through the screens. provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it expected: 'Stored forms reflect the saves, versions advance and deleting the clone leaves the original intact.' negative: false data_needs: The administrator can manage contact forms. bound_to: - TST-PFM-MTD-027 provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it assertions: - expect: 'Stored forms reflect the saves, versions advance and deleting the clone leaves the original intact.' provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it - id: FAS-PFM-MTD-03-02 title: Object archival changes form consumption and record availability kind: interaction exercises: - CAP-PFM-MTD-008 - CAP-PFM-MTD-009 - CAP-PFM-MTD-012 relies_on: - ATS-PFM-MTD-008-06 - ATS-PFM-MTD-009-08 - ATS-PFM-MTD-012-01 preconditions: An active custom object has a form and a record. steps: - do: 'Archive its object, request the form and read and edit the record by identity.' provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md expected: The form becomes unavailable while the retained record remains readable and rejects edits. negative: false data_needs: An active custom object has a form and a record. bound_to: [] provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md assertions: - expect: The form becomes unavailable while the retained record remains readable and rejects edits. provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md - id: FAS-PFM-MTD-03-03 title: Removing an assignment permits later definition removal kind: lifecycle exercises: - CAP-PFM-MTD-008 relies_on: - ATS-PFM-MTD-008-08 - ATS-PFM-MTD-008-10 preconditions: A saved presentation has two referrers. steps: - do: 'Attempt deletion, clear both assignments and retry deletion.' provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md expected: The first attempt explains the uses and the unassigned definition can be removed. negative: false data_needs: A saved presentation has two referrers. bound_to: [] provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md assertions: - expect: The first attempt explains the uses and the unassigned definition can be removed. provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md - id: FAS-PFM-MTD-03-04 title: Purpose readership does not authorize form administration kind: permission exercises: - CAP-PFM-MTD-008 relies_on: - ATS-PFM-MTD-008-03 - ATS-PFM-MTD-008-04 - ATS-PFM-MTD-008-05 preconditions: A record reader can consume a purpose but lacks its administration grants. steps: - do: 'Read the form, attempt create, replacement and deletion and request a purpose outside reach.' provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md expected: Consumption succeeds; administration is refused and unavailable definitions remain hidden. negative: true data_needs: A record reader can consume a purpose but lacks its administration grants. bound_to: [] provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md assertions: - expect: Consumption succeeds; administration is refused and unavailable definitions remain hidden. provenance: proposed source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md - id: FAS-PFM-MTD-03-05 title: A stale form save preserves the current version kind: regression exercises: - CAP-PFM-MTD-008 relies_on: - ATS-PFM-MTD-008-07 preconditions: A stored form is read at its current version. steps: - do: Submit a replacement at a stale version. provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it expected: The service refuses the replacement with a conflict. negative: true data_needs: A stored form is read at its current version. bound_to: - TST-PFM-MTD-027 provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it assertions: - expect: The service refuses the replacement with a conflict. provenance: test source: >- react-console:e2e/dev/contact-forms.dev.spec.ts#creates a form from the default, edits it, clones it and deletes it evidence: - specs/platform/metadata/planning/features/FEAT-PFM-MTD-03-forms-and-page-layouts.md - >- specs/platform/metadata/planning/capabilities/CAP-PFM-MTD-008-keep-the-workspace-s-forms-and-page-layouts-governed-by-the.md --- # Record Presentations: Feature Acceptance Suite ## What the Feature Must Do as a Whole The suite follows record presentations through its customer outcomes, lifecycle actions, permission refusals and retained regression cases. Each scenario names the capabilities it exercises and the detailed outcomes it relies on. Existing executable bindings identify specific assertions, while unbound scenarios remain proposed acceptance work. ## Interactions Between Capabilities Object archival changes form consumption and record availability. The interaction case checks the joint outcome after configuration or record state changes, so separate capability checks cannot stand in for the complete feature result. Presentation management is one capability; its feature interaction therefore crosses to object lifecycle and record consumption. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative feature acceptance from the landed capability and design obligations. |