Additional Fields and Attachments: Feature Acceptance Suite

What the Feature Must Do as a Whole

The suite follows additional fields and attachments 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

A condition dependency blocks archival until corrected. 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.

Regression Record

Revision	Change	Scenario	Why
1	initial	all	Establish cumulative feature acceptance from the landed capability and design obligations.

Scenarios

5 scenarios proving FEAT-PFM-MTD-02 as a whole.

01 Staff add and recover a custom property behaviour proposed

Exercises: CAP-PFM-MTD-005 CAP-PFM-MTD-006
Relies on: ATS-PFM-MTD-005-07 ATS-PFM-MTD-006-07
Preconditions: An object has a property and its own rules.
Steps: [object Object]
Expected: Archival removes the current definition surface and its rules; restoration recovers the retained definition.
Data: An object has a property and its own rules.
Source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-02-custom-fields-and-files.md

02 A condition dependency blocks archival until corrected interaction test

Exercises: CAP-PFM-MTD-005 CAP-PFM-MTD-006
Relies on: ATS-PFM-MTD-006-06 ATS-PFM-MTD-005-07
Preconditions: A rule depends on a second property.
Steps: [object Object]
Expected: The dependent rule is named and no archive is saved.
Data: A rule depends on a second property.
Bound to: TST-PFM-MTD-009
Source: react-console:acceptance/custom-objects/playwright/journeys/PLAT-M5-S09.spec.ts#PLAT-M5-S09: archiving a property another rule depends on is refused, naming the rule

03 Field lifecycle controls later file-valued inputs lifecycle proposed

Exercises: CAP-PFM-MTD-005 CAP-PFM-MTD-007
Relies on: ATS-PFM-MTD-005-07 ATS-PFM-MTD-007-03
Preconditions: A file property has valid staging and an existing saved value.
Steps: [object Object]
Expected: The property lifecycle governs the new save while the earlier value remains retained.
Data: A file property has valid staging and an existing saved value.
Source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-02-custom-fields-and-files.md

04 Upload reach does not confer field administration permissionnegative proposed

Exercises: CAP-PFM-MTD-005 CAP-PFM-MTD-007
Relies on: ATS-PFM-MTD-007-01 ATS-PFM-MTD-007-02 ATS-PFM-MTD-005-11
Preconditions: An uploader lacks definition-update permission.
Steps: [object Object]
Expected: The upload is issued and the unauthorized definition change is refused.
Data: An uploader lacks definition-update permission.
Source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-02-custom-fields-and-files.md

05 Widening preserves definitions while invalid rules preserve the preceding set regressionnegative proposed

Exercises: CAP-PFM-MTD-005 CAP-PFM-MTD-006
Relies on: ATS-PFM-MTD-005-04 ATS-PFM-MTD-006-02
Preconditions: A decimal field has rules and stored values.
Steps: [object Object]
Expected: The wider definition remains and the rejected rule request preserves the preceding rules.
Data: A decimal field has rules and stored values.
Source: specs/platform/metadata/planning/features/FEAT-PFM-MTD-02-custom-fields-and-files.md

Planning

Additional Fields and Attachments: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Additional Fields and Attachments: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record