SpecificationsMetadata and Organization-defined Records
19 acceptance test sets for MOD-PFM-MTD, one per capability, holding 188 scenarios — 160 of them already bound to an existing test. A scenario names the rules and journey assertions it proves; it never restates them.
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-001 | Keep the Record Catalogue Current | 8 | 7 | 5 | 8 api | Proposed |
ATS-PFM-MTD-002 | Describe Records for Shared Clients | 7 | 6 | 2 | 7 api | Proposed |
ATS-PFM-MTD-003 | Keep Configurability Within Product Scope | 7 | 6 | 4 | 6 api · 1 unit | Proposed |
ATS-PFM-MTD-004 | Use Workspace Labels for Standard Fields | 7 | 6 | 3 | 7 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-005 | Extend Records With Durable Custom Fields | 14 | 12 | 11 | 13 api · 1 browser | Proposed |
ATS-PFM-MTD-006 | Configure Field Requirements and Exposure | 11 | 9 | 7 | 7 api · 2 unit · 2 browser | Proposed |
ATS-PFM-MTD-007 | Prepare Image and File Uploads | 8 | 7 | 5 | 3 api · 4 unit · 1 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-008 | Manage Shared Forms and Record Layouts | 12 | 11 | 10 | 12 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-009 | Bring a Custom Record Type Into Use | 14 | 11 | 9 | 10 api · 3 browser · 1 unit | Proposed |
ATS-PFM-MTD-010 | Make Custom Records Discoverable | 7 | 6 | 5 | 6 api · 1 browser | Proposed |
ATS-PFM-MTD-011 | Control Custom Record Audiences | 8 | 7 | 4 | 3 api · 2 browser · 3 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-012 | Maintain Valid Custom Records | 19 | 15 | 11 | 14 api · 4 browser · 1 unit | Proposed |
ATS-PFM-MTD-013 | Retire or Publish Custom Records | 11 | 9 | 7 | 9 api · 2 browser | Proposed |
ATS-PFM-MTD-014 | Explain Custom Record Changes | 7 | 6 | 1 | 1 browser · 6 api | Proposed |
ATS-PFM-MTD-015 | Deliver Committed Record and Link Events | 8 | 7 | 4 | 8 api | Proposed |
ATS-PFM-MTD-016 | Load and Reconcile Record Files | 8 | 7 | 4 | 8 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-MTD-017 | Define Meaningful Record Relationships | 9 | 8 | 7 | 6 api · 3 browser | Proposed |
ATS-PFM-MTD-018 | Maintain Dated Links Between Records | 13 | 11 | 10 | 8 api · 5 browser | Proposed |
ATS-PFM-MTD-019 | Preserve Relationships Through Deletion and Merge | 10 | 9 | 4 | 9 api · 1 browser | Proposed |