| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-01 An owning service registers its record definitions on each deployment so the catalogue follows the released declaration. | no | | |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-02 Registration replaces an application manifest atomically, retires omitted objects, fields and collections without deleting them, and revives declarations in their supplied order when they return. | yes | ATS-PFM-MTD-001-01, ATS-PFM-MTD-001-08 | TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-03 An invalid manifest reports its contract problems together and leaves the registration unchanged. | yes | ATS-PFM-MTD-001-02 | TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-04 Record type names use an application and a plural noun; manifests cannot name another application, use the reserved custom-object application or repeat an object. | yes | ATS-PFM-MTD-001-03 | TST-PFM-MTD-113 (not-run), TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-05 References and collection elements must resolve to registered record types, and a table already assigned to another record type causes the entire registration to be refused. | yes | ATS-PFM-MTD-001-04 | TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-06 Table columns become fields unless explicitly excluded with a reason; field declarations specify type, write classification and API requirement, and unwritable fields cannot be required. | yes | ATS-PFM-MTD-001-05 | TST-PFM-MTD-112 (not-run), TST-PFM-MTD-131 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-07 Unspecified field settings resolve to an editable, optional field with a label derived from its column name, preserving those defaults across shared-contract upgrades. | yes | ATS-PFM-MTD-001-07 | TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-08 Collections describe repeating values through labels, optional limits, write classification and an optional element record type; their keys cannot duplicate field keys. | yes | ATS-PFM-MTD-001-06 | TST-PFM-MTD-127 (not-run) |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-09 A rejected manifest returns an explanatory response instead of failing the invocation, giving the deployment a reason to report. | no | | |
| CAP-PFM-MTD-001 | BR-CAP-PFM-MTD-001-10 After the registration commits, retired fields trigger search degradation and rebuild requests in affected workspaces; logged workspace failures leave the completed registration intact. | yes | | |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-01 An object description orders live standard fields first with workspace labels and retained original labels, then unarchived custom fields by position, creation and key, and finally collections. | yes | ATS-PFM-MTD-002-01, ATS-PFM-MTD-002-07, ATS-PFM-MTD-004-07 | TST-PFM-MTD-116 (not-run) |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-02 Field descriptions report create and edit access, computed and system status, and requirement level so forms can determine which fields are writable. | yes | ATS-PFM-MTD-002-02 | TST-PFM-MTD-107 (not-run), TST-PFM-MTD-116 (not-run) |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-03 The shared catalogue distinguishes seventeen stored data types from their compatible presentations and supplies those presentations with each described field. | no | | |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-04 A reference describes its target record type and labels without recursively describing the target fields. | no | | |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-05 Unknown or retired registered types and unavailable, archived or foreign-workspace custom objects return a not-found response identifying the requested type. | yes | ATS-PFM-MTD-001-08, ATS-PFM-MTD-002-03 | TST-PFM-MTD-107 (not-run), TST-PFM-MTD-115 (not-run) |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-06 The record type list combines registered types with the workspace draft and active custom objects, showing custom origin and status while excluding archived objects. | yes | ATS-PFM-MTD-002-04 | TST-PFM-MTD-123 (not-run) |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-07 Descriptions isolate workspace fields and labels and remain identical when the underlying state does not change. | yes | ATS-PFM-MTD-002-05 | TST-PFM-MTD-116 (not-run) |
| CAP-PFM-MTD-002 | BR-CAP-PFM-MTD-002-08 Custom-object descriptions place fixed fields before ordered, grouped properties and their rules, include publication fields when applicable, and contain no collections. | yes | ATS-PFM-MTD-002-06 | TST-PFM-MTD-115 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-01 A custom-field declaration requires Product approval for that record type: contacts, organizations, committees, committee nominations, memberships, organizational units and membership applications are eligible, and other declarations are refused at registration. | yes | ATS-PFM-MTD-003-01 | TST-PFM-MTD-126 (not-run), TST-PFM-MTD-130 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-02 An automated comparison keeps the coded approval list equal to the standard classification, requiring the decision table to change alongside any newly eligible type. | yes | ATS-PFM-MTD-003-02 | TST-PFM-MTD-128 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-03 Custom fields require configurable forms and page layouts in the declaration; either presentation capability may exist independently, and omitted capability declarations remain backward-compatible. | yes | ATS-PFM-MTD-003-03 | TST-PFM-MTD-126 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-04 During the transition, an approved type with no declaration receives all three capabilities and produces a warning identifying the type. | no | | |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-05 Creating or replacing a custom field without the capability is refused, and descriptions omit existing custom definitions after that capability is removed. | yes | ATS-PFM-MTD-001-08, ATS-PFM-MTD-003-04, ATS-PFM-MTD-003-07 | TST-PFM-MTD-126 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-06 Form creation requires configurable forms and page-layout creation requires configurable page layouts; contacts, organizations and committees support both. | yes | ATS-PFM-MTD-003-05, ATS-PFM-MTD-003-07, ATS-PFM-MTD-008-12 | TST-PFM-MTD-104 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-07 A capability-filtered record type list includes only holders and their flags for the configuration screens, and rejects an unrecognized capability. | yes | ATS-PFM-MTD-003-06 | TST-PFM-MTD-107 (not-run), TST-PFM-MTD-126 (not-run) |
| CAP-PFM-MTD-003 | BR-CAP-PFM-MTD-003-08 Custom objects inherently support custom fields, configurable forms and configurable page layouts; a relationship to another type does not transfer those capabilities. | no | | |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-01 A standard-label request may change the label alone and rejects attempts to alter visibility, requirement, type or presentation. | yes | ATS-PFM-MTD-004-01 | TST-PFM-MTD-108 (not-run) |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-02 Relabelling requires a live registered standard field; custom keys, undescribed columns, missing types and retired fields return not found, while prior overrides survive field retirement. | yes | ATS-PFM-MTD-004-02 | TST-PFM-MTD-124 (not-run) |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-03 An override label contains between one and two hundred characters after trimming. | yes | ATS-PFM-MTD-004-03 | TST-PFM-MTD-124 (not-run) |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-04 Workspace relabelling changes neither the owning declaration nor labels seen in other workspaces. | yes | ATS-PFM-MTD-002-07, ATS-PFM-MTD-004-04, ATS-PFM-MTD-004-07 | TST-PFM-MTD-108 (not-run), TST-PFM-MTD-124 (not-run) |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-05 Removing an override returns the owning label, and removing an absent override succeeds while reporting that no override was removed. | yes | ATS-PFM-MTD-004-05, ATS-PFM-MTD-004-07 | TST-PFM-MTD-108 (not-run) |
| CAP-PFM-MTD-004 | BR-CAP-PFM-MTD-004-06 Setting a replacement label retains the original creator and increments the override version. | yes | ATS-PFM-MTD-004-06 | TST-PFM-MTD-124 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-01 A custom field identity combines record type and key; registered types use lowercase custom-suffixed keys, while custom objects use plain keys outside the reserved fixed-field vocabulary, with database checks backing both forms. | yes | ATS-PFM-MTD-005-01 | TST-PFM-MTD-110 (not-run), TST-PFM-MTD-117 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-02 Field keys remain reserved within their workspace and type after archival, cannot collide with standard keys, and can be used independently in another workspace. | yes | ATS-PFM-MTD-005-02 | TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-03 Replacing a field cannot change either its data type or its key. | yes | ATS-PFM-MTD-005-03, ATS-PFM-MTD-006-11 | TST-PFM-MTD-105 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-04 Configuration changes may widen accepted values but cannot narrow lengths, bounds or precision, remove options instead of archiving them, reduce selection multiplicity, change reference targets or remove media types. | yes | ATS-PFM-MTD-005-04 | TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-05 Definition validation reports all type and presentation problems together, bounds selectable ranges, fixes currency for the field lifetime and stores percentages as entered. | yes | ATS-PFM-MTD-005-05 | TST-PFM-MTD-105 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-06 Requirement levels distinguish API, console and portal, portal alone and optional; an omitted replacement level becomes optional without rewriting stored values, and the owner enforces API-required writes. | yes | ATS-PFM-MTD-005-06 | TST-PFM-MTD-105 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-07 Archival removes a field from descriptions and new-value writes while preserving its key and stored values; the definition remains unchangeable until restoration makes it available again. | yes | ATS-PFM-MTD-002-07, ATS-PFM-MTD-005-07, ATS-PFM-MTD-005-13 | TST-PFM-MTD-105 (not-run), TST-PFM-MTD-116 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-08 Indexed-field archival records search degradation and requests rebuilding in its transaction; the later rebuild removes those values from search documents. | yes | ATS-PFM-MTD-005-08, ATS-PFM-MTD-005-14 | TST-PFM-MTD-132 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-09 Custom objects have a two-hundred-property limit that counts archived properties; this service does not apply that count check to registered record types. | yes | ATS-PFM-MTD-005-09 | TST-PFM-MTD-117 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-10 New fields require a live registered type or a draft or active custom object, and references must identify one live target rather than a polymorphic target. | yes | ATS-PFM-MTD-005-10 | TST-PFM-MTD-117 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-11 Field replacement checks the supplied version and update lock; archival refuses any lock, while archival and restoration carry no expected version. | yes | ATS-PFM-MTD-005-11 | TST-PFM-MTD-105 (not-run), TST-PFM-MTD-118 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-12 Optional position and group settings affect presentation only and are cleared when omitted from a replacement. | yes | ATS-PFM-MTD-005-12 | TST-PFM-MTD-117 (not-run) |
| CAP-PFM-MTD-005 | BR-CAP-PFM-MTD-005-13 The initial property vocabulary excludes formulas, rollups and lookups; query facilities supply derived information pending the shared formula language. | no | | |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-01 Rules are replaced as a complete set of five possible kinds, with one entry per kind; omitted kinds disappear and the default staff exposure needs no stored entry. | yes | ATS-PFM-MTD-006-01 | TST-PFM-MTD-109 (not-run), TST-PFM-MTD-120 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-02 Conditions may reference other fields of the same type using compatible operators, cannot reference their own field and must fit sixteen kilobytes; rejected sets leave existing rules intact. | yes | ATS-PFM-MTD-006-02, ATS-PFM-MTD-006-11 | TST-PFM-MTD-120 (not-run), TST-PFM-MTD-129 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-03 Uniqueness rules are supported only for custom objects and are refused with a duplicate-value count until existing records satisfy uniqueness. | yes | ATS-PFM-MTD-006-03, ATS-PFM-MTD-006-10 | TST-PFM-MTD-065 (not-run), TST-PFM-MTD-120 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-04 Defaults accept a compatible literal, the workspace current date, the portal caller contact or the caller organization token, and incompatible defaults are refused. | yes | ATS-PFM-MTD-006-04 | TST-PFM-MTD-129 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-05 Exposure selects the widest permitted readership along the staff, owner, portal and public ladder, with broader levels including narrower audiences and invalid levels rejected. | yes | ATS-PFM-MTD-006-05, ATS-PFM-MTD-006-10 | TST-PFM-MTD-109 (not-run), TST-PFM-MTD-129 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-06 A custom-object property named by another property condition cannot be archived until those dependencies are changed; the refusal identifies each dependent field and rule without deleting them. | yes | ATS-PFM-MTD-005-13, ATS-PFM-MTD-006-06 | TST-PFM-MTD-009 (not-run), TST-PFM-MTD-120 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-07 Field archival deletes that field’s own rules atomically, and rule replacement is unavailable while the field is archived. | yes | ATS-PFM-MTD-005-13, ATS-PFM-MTD-006-07 | TST-PFM-MTD-120 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-08 Writing a field rule advances the workspace query-description stamp in the same transaction. | yes | ATS-PFM-MTD-006-08 | TST-PFM-MTD-109 (not-run) |
| CAP-PFM-MTD-006 | BR-CAP-PFM-MTD-006-09 The archive dependency safeguard applies to custom objects; a registered-type field can be archived despite another field condition naming it. | yes | ATS-PFM-MTD-006-09 | TST-PFM-MTD-120 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-01 Upload issuance requires the upload permission, held by Platform Administrator and User but absent from Read Only; refusal issues nothing. | yes | ATS-PFM-MTD-007-01 | TST-PFM-MTD-078 (not-run), TST-PFM-MTD-084 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-02 The signed caller context must include the workspace named in the route, and requests cannot substitute a workspace in the body or use another customer’s workspace. | yes | ATS-PFM-MTD-007-02 | TST-PFM-MTD-078 (not-run), TST-PFM-MTD-082 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-03 Upload size must be a positive whole byte count within ten mebibytes for images or twenty-five for files; oversized requests name the size problem without signing or recording an upload. | yes | ATS-PFM-MTD-007-03 | TST-PFM-MTD-082 (not-run), TST-PFM-MTD-083 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-04 Images permit JPEG, PNG, GIF and WebP but exclude SVG; files additionally permit supported document, text, spreadsheet and archive formats, while mismatched image types and executables are refused. | yes | ATS-PFM-MTD-007-04 | TST-PFM-MTD-083 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-05 Platform derives staging location from workspace, record-type folder, a fresh upload identifier and a safe filename, uses public staging for images and rejects filenames containing paths. | yes | ATS-PFM-MTD-007-05 | TST-PFM-MTD-083 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-06 The signed upload expires after fifteen minutes and binds declared type, length and uploader identity so storage rejects a changed declaration and saving can identify the uploader. | yes | ATS-PFM-MTD-007-06 | TST-PFM-MTD-078 (not-run), TST-PFM-MTD-085 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-07 Issuance records caller, object, field, location, type, size and expiry together with its security audit event. | yes | ATS-PFM-MTD-007-07 | TST-PFM-MTD-082 (not-run) |
| CAP-PFM-MTD-007 | BR-CAP-PFM-MTD-007-08 The owning save checks and copies uploaded or web-address files into managed storage and must refuse staging files issued to a different saving person. | yes | ATS-PFM-MTD-007-08 | |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-01 A presentation definition stores a trimmed name of one to two hundred characters, optional description, fixed purpose and an opaque JSON object of at most 256 kibibytes that is returned without interpretation. | yes | ATS-PFM-MTD-008-01 | TST-PFM-MTD-098 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-02 A replacement or patch cannot change the purpose and reports the stored and requested purposes when they differ. | yes | ATS-PFM-MTD-008-02 | TST-PFM-MTD-087 (not-run), TST-PFM-MTD-098 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-03 Reading accepts the purpose administration read key or record consumption key, while writes require the appropriate purpose administration key defined by the record owner. | yes | ATS-PFM-MTD-008-03 | TST-PFM-MTD-087 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-04 Unreachable definitions return not found for reads and writes, disappear from lists and produce an empty purpose-filtered list. | yes | ATS-PFM-MTD-008-04 | TST-PFM-MTD-087 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-05 Creation rejects an unregistered purpose before purpose permission evaluation, and a Platform staff wildcard cannot substitute for the purpose owner keys. | yes | ATS-PFM-MTD-008-05 | TST-PFM-MTD-087 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-06 Custom-object purposes use shared definition administration and record-read keys, require a draft or active object in the workspace and become unreadable when that object is archived. | yes | ATS-PFM-MTD-008-06, ATS-PFM-MTD-008-12 | TST-PFM-MTD-088 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-07 Replacement and patch require the current version, update locks block modifications and delete locks block removal. | yes | ATS-PFM-MTD-008-07 | TST-PFM-MTD-098 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-08 Definition lists default to fifty entries, cap at two hundred, order by name and use a cursor that is rejected when malformed. | yes | ATS-PFM-MTD-008-11 | TST-PFM-MTD-087 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-09 The owning save registers presentation use in five assignment slots, whose database references reject missing definitions or mismatched workspace, kind or purpose. | yes | ATS-PFM-MTD-008-08 | TST-PFM-MTD-093 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-10 Create and edit assignments may select either two different console forms or the same console form. | yes | ATS-PFM-MTD-008-09 | TST-PFM-MTD-093 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-11 An assigned definition cannot be deleted until its referring records or settings are changed, and concurrent assignment and deletion cannot leave an invalid reference. | yes | ATS-PFM-MTD-008-10 | TST-PFM-MTD-087 (not-run), TST-PFM-MTD-093 (not-run), TST-PFM-MTD-098 (not-run) |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-12 The contact form designer persists console forms in Platform and reports unsupported content when opening a stored form rather than discarding it. | no | | |
| CAP-PFM-MTD-008 | BR-CAP-PFM-MTD-008-13 The contact page-layout designer stores drafts and published layouts in browser storage instead of Platform presentation storage. | no | | |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-01 A custom object starts in draft with permanent configuration and derived record-type identities; its plural key uses lowercase underscore-separated words within fifty-five characters, and archived identities remain reserved. | yes | ATS-PFM-MTD-009-01 | TST-PFM-MTD-052 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-02 A workspace may define fifty custom objects, with a further create refused. | yes | ATS-PFM-MTD-009-02 | TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-03 Object replacement supplies all mutable settings at the current version, cannot alter identities or status and is refused while the object is archived. | yes | ATS-PFM-MTD-009-03 | TST-PFM-MTD-052 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-04 Activation accepts only a draft with a live display property of a supported name-like type and up to three live secondary properties, reporting incomplete definitions without activating them. | yes | ATS-PFM-MTD-005-13, ATS-PFM-MTD-009-04, ATS-PFM-MTD-009-14 | TST-PFM-MTD-002 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-05 An owner setting names an active relationship ending at the object with one-to-one or one-to-many cardinality; because draft endpoints cannot form relationship types, ownership is configured after activation. | yes | ATS-PFM-MTD-009-05, ATS-PFM-MTD-009-13, ATS-PFM-MTD-009-14 | TST-PFM-MTD-067 (not-run), TST-PFM-MTD-077 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-06 Publication may be enabled freely but cannot be disabled while any object record is published. | yes | ATS-PFM-MTD-009-06 | TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-07 Object saves validate portal operation and rule vocabularies, duplicate kinds, ownership and publication prerequisites, workspace roles and bindings, and related relationship-type references. | yes | ATS-PFM-MTD-009-07 | TST-PFM-MTD-067 (not-run), TST-PFM-MTD-075 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-08 Object archival preserves data while making its records readable by identity and unwriteable; restoration returns a draft that needs activation checks again. | yes | ATS-PFM-MTD-008-12, ATS-PFM-MTD-009-08, ATS-PFM-MTD-010-07, ATS-PFM-MTD-016-08 | TST-PFM-MTD-010 (not-run), TST-PFM-MTD-052 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-09 Each definition mutation writes a security event containing changed field names rather than their values. | yes | ATS-PFM-MTD-009-09 | TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-10 Reset preserves custom-object definitions and empties records, but removes properties and rules with the other custom-field definitions until configuration reloads them. | yes | ATS-PFM-MTD-009-10 | TST-PFM-MTD-139 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-11 Object settings accept per-owner record and per-record link limits without enforcing either limit in record storage. | yes | ATS-PFM-MTD-009-11 | TST-PFM-MTD-138 (not-run) |
| CAP-PFM-MTD-009 | BR-CAP-PFM-MTD-009-12 Activation writes reusable Explorer query recipes; object archival changes status without a recipe retirement call in this operation. | yes | ATS-PFM-MTD-009-12 | |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-01 Placement accepts the seventeen console navigation apps or a workspace unarchived custom app and an optional trimmed group of one to one hundred characters, rejecting unknown apps. | yes | ATS-PFM-MTD-010-01 | TST-PFM-MTD-067 (not-run), TST-PFM-MTD-074 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-02 An object can be created, activated and used without placement or ownership, remaining accessible through links and queries. | yes | ATS-PFM-MTD-010-02 | TST-PFM-MTD-013 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-03 A custom app has a permanent nonreserved key, bounded label, icon and order from zero to ten thousand, supports archival and restoration instead of deletion and uses versioned replacement. | yes | ATS-PFM-MTD-010-03 | TST-PFM-MTD-049 (not-run), TST-PFM-MTD-060 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-04 App archival is refused while draft or active objects are placed there, naming those objects; archived objects may retain the placement. | yes | ATS-PFM-MTD-010-04, ATS-PFM-MTD-010-07 | TST-PFM-MTD-049 (not-run), TST-PFM-MTD-060 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-05 An archived app rejects new placements and replacements until it is restored. | yes | ATS-PFM-MTD-010-05 | TST-PFM-MTD-060 (not-run), TST-PFM-MTD-067 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-06 Custom-app counts remain unrestricted pending the product-wide limits mechanism. | no | | |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-07 App reads include placed active objects with their groups and staff access and omit draft or archived objects. | no | | |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-08 Navigation includes only readable active objects and apps containing them, respects object-scoped roles and refuses callers with no record-read reach. | yes | ATS-PFM-MTD-009-13, ATS-PFM-MTD-010-06, ATS-PFM-MTD-010-07 | TST-PFM-MTD-051 (not-run) |
| CAP-PFM-MTD-010 | BR-CAP-PFM-MTD-010-09 Reset preserves custom apps and object placements, whereas workspace deletion removes them. | yes | | |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-01 Shared record permissions support assignments scoped to one custom object, hiding other object records behind a not-found response. | yes | ATS-PFM-MTD-011-01 | TST-PFM-MTD-051 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-02 Roles-only objects require an active object-specific assignment in addition to permission reach; built-in, workspace-wide and customer-wide grants alone do not expose them. | yes | ATS-PFM-MTD-010-07, ATS-PFM-MTD-011-02, ATS-PFM-MTD-011-08 | TST-PFM-MTD-014 (not-run), TST-PFM-MTD-051 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-03 Platform Administrator receives every definition and record key, User receives definition reads plus record read, query, create, update and history, and Read Only receives definition reads plus record read, query and history. | yes | ATS-PFM-MTD-011-03 | TST-PFM-MTD-072 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-04 Record archival and restoration require the separately granted delete permission and support object-specific scope. | yes | ATS-PFM-MTD-011-04, ATS-PFM-MTD-011-08 | TST-PFM-MTD-072 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-05 Record export is marked sensitive and reserved to administrators, but no current route requires its dedicated key. | no | | |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-06 Audience projection shows all properties to staff, owner-or-broader properties to owners, portal-or-public properties to members and only public properties to anonymous readers; portal links exclude staff-only types. | yes | ATS-PFM-MTD-006-10, ATS-PFM-MTD-011-05 | TST-PFM-MTD-073 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-07 Data-layer portal predicates combine ownership, organizational roles, links, publication and eligibility, exclude archived records and limit members without contacts to publication or eligibility; portal routes remain absent. | yes | ATS-PFM-MTD-011-06 | TST-PFM-MTD-069 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-08 Console action visibility follows permissions, leaving readers without edit controls and hiding inaccessible object navigation and cards. | yes | ATS-PFM-MTD-011-07 | TST-PFM-MTD-008 (not-run) |
| CAP-PFM-MTD-011 | BR-CAP-PFM-MTD-011-09 System execution without a permission slice can reach every custom object in its workspace. | no | | |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-01 Record writes require an active object; records of draft or archived objects remain readable by identity with their links, reject writes and cannot be reached through another object path. | yes | ATS-PFM-MTD-008-12, ATS-PFM-MTD-012-01 | TST-PFM-MTD-051 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-02 Property validation uses live definitions and typed conversion, names invalid or unavailable properties without disclosing rejected values and uses the object label in its refusal. | yes | ATS-PFM-MTD-012-02 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-03 API-required properties need a value at creation and reject attempts to clear them. | yes | ATS-PFM-MTD-012-03 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-04 Visibility validation rejects non-null submitted changes to hidden properties while retaining untouched stored values; conditional requirement checks resulting visible values, and unknown evaluations neither require nor hide. | yes | ATS-PFM-MTD-012-04, ATS-PFM-MTD-012-15 | TST-PFM-MTD-004 (not-run), TST-PFM-MTD-065 (not-run), TST-PFM-MTD-076 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-05 Creation fills omitted, empty or null properties from compatible defaults using literals, workspace dates or caller contact, while supplied values override defaults. | yes | ATS-PFM-MTD-012-05 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-06 References must resolve to a record of their target type in the workspace, with custom-object targets requiring unarchived records of the specified object. | yes | ATS-PFM-MTD-012-06 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-07 Unique-property reservations reject duplicate values without saving, name the holder, normalize text case and surrounding whitespace and release a reservation when its value changes. | yes | ATS-PFM-MTD-006-10, ATS-PFM-MTD-012-07 | TST-PFM-MTD-005 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-08 Display properties reject internal line breaks by property name, trim boundary line breaks and leave unrelated properties unaffected. | yes | ATS-PFM-MTD-012-08 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-09 Each save derives the name from the primary display value or prefixed record number plus populated secondary values, limits it to five hundred characters and assigns numbers from the object sequence. | yes | ATS-PFM-MTD-012-09 | TST-PFM-MTD-065 (not-run), TST-PFM-MTD-076 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-10 Patches affect named properties and use null to clear them, while replacements clear omitted live properties and accept a complete record representation. | yes | ATS-PFM-MTD-012-10, ATS-PFM-MTD-012-19 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-11 Updates require the read version and respect update locks; archived records reject editing and publication but remain deletable when the object is active and deletion safeguards allow it. | yes | ATS-PFM-MTD-012-11, ATS-PFM-MTD-012-16 | TST-PFM-MTD-006 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-12 Caller-supplied external identifiers are unique within the object and reject conflicting creation or patch requests. | yes | ATS-PFM-MTD-012-12 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-13 New image and file values pass through managed asset preparation before saving, with unavailable or unsavable sources reported at the property without exposing the address. | yes | ATS-PFM-MTD-007-08, ATS-PFM-MTD-012-13, ATS-PFM-MTD-012-18 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-14 Record lists default to unarchived entries ordered by name, offer bounded pages and publication, archive and prefix filters, while reads include grouped links and write view audits and mutations audit actions without values. | yes | ATS-PFM-MTD-012-14 | TST-PFM-MTD-051 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-012 | BR-CAP-PFM-MTD-012-15 Decimal, currency and percent storage also records an exact precision-scaled integer, leaving that shadow empty when the value exceeds the supported safe integer range. | yes | ATS-PFM-MTD-012-17 | TST-PFM-MTD-065 (not-run), TST-PFM-MTD-076 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-01 Publishable records begin in draft and accept draft, pending-review, published or unpublished states; entering publication sets its time, leaving it clears the time and nonpublishable objects reject publication. | yes | ATS-PFM-MTD-013-01, ATS-PFM-MTD-013-11 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-02 Record archival retains values, files and links while excluding ordinary-list entries and refusing edits, publication and repeated archival until restoration; deletion remains available for an active object. | yes | ATS-PFM-MTD-013-02 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-03 Permanent deletion requires the current version, removes record and owned value reservations and detaches files for retirement. | yes | ATS-PFM-MTD-013-03 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-04 A restricting link in force prevents deletion without removing anything, including a link whose end date is still current or future. | yes | ATS-PFM-MTD-013-04 | TST-PFM-MTD-037 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-05 Cascading deletion follows linked custom records through the same safeguards to a maximum depth of ten and rolls back the entire deletion when any member is refused. | yes | ATS-PFM-MTD-013-05, ATS-PFM-MTD-013-10 | TST-PFM-MTD-022 (not-run), TST-PFM-MTD-037 (not-run), TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-06 Deletion announcements order link removals first, cascaded records from deepest to shallowest next and the originating record last. | yes | ATS-PFM-MTD-013-06, ATS-PFM-MTD-015-08, ATS-PFM-MTD-019-10 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-07 Owner cascades still delete records of archived or draft objects even though direct deletion from those objects is refused. | yes | ATS-PFM-MTD-013-07 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-08 Publication, archival, restoration and deletion record audit events in their transaction, including the chosen publication state. | yes | ATS-PFM-MTD-013-08 | TST-PFM-MTD-065 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-09 Authorized record-page actions offer publication, unpublication, archival, restoration and confirmed deletion, explaining restricting links in a refused deletion confirmation. | yes | ATS-PFM-MTD-013-09 | TST-PFM-MTD-007 (not-run), TST-PFM-MTD-022 (not-run) |
| CAP-PFM-MTD-013 | BR-CAP-PFM-MTD-013-10 Direct store deletion consults an optional external deletion check, but no integration registers it and cross-service deletion does not consult it. | no | | |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-01 Committed record, value and relationship changes capture author, time, source and before-and-after fields in transactional history, while unchanged business values create no revision. | yes | ATS-PFM-MTD-012-18, ATS-PFM-MTD-013-10, ATS-PFM-MTD-014-01, ATS-PFM-MTD-014-06, ATS-PFM-MTD-019-10 | TST-PFM-MTD-007 (not-run), TST-PFM-MTD-057 (not-run), TST-PFM-MTD-070 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-02 Revision presentation follows form sections and property labels, resolves option labels, includes composed names and labels relationship changes from the relevant side. | yes | ATS-PFM-MTD-014-02 | TST-PFM-MTD-057 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-03 History requires its own permission and object reach, additionally checks record read access while the record exists and permits deleted-record history under history access. | yes | ATS-PFM-MTD-011-08, ATS-PFM-MTD-014-03, ATS-PFM-MTD-014-07 | TST-PFM-MTD-057 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-04 Archived object records retain readable timelines, individual revisions and actor lists. | yes | ATS-PFM-MTD-014-04 | TST-PFM-MTD-057 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-05 Link changes enter the starting record history and the other endpoint history when it is a custom record; CRM endpoint revisions are stored in Platform and remain absent from the CRM drawer. | yes | ATS-PFM-MTD-014-06, ATS-PFM-MTD-018-13 | TST-PFM-MTD-070 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-06 CRM merge changes to custom records capture one revision per transaction, including reference values before the move and the surviving contact afterwards. | yes | ATS-PFM-MTD-014-05, ATS-PFM-MTD-014-07 | TST-PFM-MTD-053 (not-run) |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-07 History supports actor, operation, source and date filters, rejects unsupported parameters and remains until authorized workspace lifecycle purging removes it. | yes | | |
| CAP-PFM-MTD-014 | BR-CAP-PFM-MTD-014-08 Revision presentation includes only properties available in the current description and admitted by the caller’s audience, so archived property values remain retained but undisplayed. | yes | | |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-01 Record lifecycle and property mutations and link creation, ending or deletion append their event in the mutation transaction, while refused or rolled-back writes append nothing. | yes | ATS-PFM-MTD-012-18, ATS-PFM-MTD-013-10, ATS-PFM-MTD-015-01, ATS-PFM-MTD-015-08, ATS-PFM-MTD-018-13 | TST-PFM-MTD-043 (not-run), TST-PFM-MTD-048 (not-run), TST-PFM-MTD-064 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-02 Record events identify the object, record, prefixed number, name, publication state and author, with update events listing changed property keys in sorted order. | yes | ATS-PFM-MTD-015-02 | TST-PFM-MTD-048 (not-run), TST-PFM-MTD-064 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-03 Unchanged property values, external-identifier-only changes, repeated publication states and link updates that do not end the link produce no business event. | yes | ATS-PFM-MTD-015-03 | TST-PFM-MTD-043 (not-run), TST-PFM-MTD-064 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-04 Events retain a ledger entry and waiting work until dispatch destinations accept their messages; any refused destination leaves work for another run without removing the ledger fact. | yes | ATS-PFM-MTD-015-04 | TST-PFM-MTD-056 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-05 Consumption sends the event to native subscribers or its versioned external-router contract to the router and reports only failed messages for redelivery. | yes | ATS-PFM-MTD-015-05 | TST-PFM-MTD-056 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-06 The nightly ninety-day sweep retains events still referenced by waiting queue rows; workspace reset or deletion purges the workspace events. | yes | | |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-07 Deletions announce link removals and cascaded records before the records they depend on. | yes | ATS-PFM-MTD-015-06, ATS-PFM-MTD-015-08, ATS-PFM-MTD-019-10 | TST-PFM-MTD-064 (not-run) |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-08 Platform has no native subscribers yet, and CRM merge moves or endings of links produce no business event. | no | | |
| CAP-PFM-MTD-015 | BR-CAP-PFM-MTD-015-09 Retention sweeps refuse durations below one day or durations that are not whole numbers. | yes | ATS-PFM-MTD-015-07 | TST-PFM-MTD-058 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-01 Producer keys identify load lines within their object and become external identifiers; new crosswalk keys can adopt matching records, known keys patch only differing supplied properties and identical reloads make no changes. | yes | ATS-PFM-MTD-016-01 | TST-PFM-MTD-135 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-02 Preflight validates object state, property contracts, references, requirements, conditions, uniqueness within storage and the file, and caller reach, reporting rejected lines and properties without values. | yes | ATS-PFM-MTD-016-02 | TST-PFM-MTD-134 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-03 Validation computes impact without writing records, and apply refuses a mismatched impact digest while keeping the job validated. | yes | ATS-PFM-MTD-016-03 | TST-PFM-MTD-134 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-04 Loaded records use normal write behaviour for numbering, names, unique values, assets and audits and reject archived targets until restoration. | yes | ATS-PFM-MTD-016-04, ATS-PFM-MTD-016-08 | TST-PFM-MTD-134 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-05 Link loads resolve type and endpoint keys or identities, validate type state, endpoint kind, dates, attributes and cardinality, and refuse changes to known link endpoints before applying. | yes | ATS-PFM-MTD-016-05, ATS-PFM-MTD-016-08 | TST-PFM-MTD-136 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-06 A known-link correction replaces all link attributes, clears omitted dates, position and notes and reopens an ended link when its end date is omitted, without warning. | yes | ATS-PFM-MTD-016-06 | TST-PFM-MTD-136 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-07 Link-load submission requires create permission and each line needs create or update according to whether it is new, while results remain limited to the submitter and workspace. | yes | ATS-PFM-MTD-016-07 | TST-PFM-MTD-137 (not-run) |
| CAP-PFM-MTD-016 | BR-CAP-PFM-MTD-016-08 Load controls support pause, resume, cancel and retry, and resubmission of an idempotency key returns its original job. | no | | |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-01 A relationship type has a permanent bounded key, labels from both sides, one-to-one, one-to-many or many-to-many cardinality, dating and primary settings and detach, cascade or restrict rules for each side, rejecting invalid choices. | yes | ATS-PFM-MTD-017-01 | TST-PFM-MTD-036 (not-run), TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-02 Endpoints may be contacts, organizations or active custom objects of the workspace, including two sides of the same type, but not draft custom objects. | yes | ATS-PFM-MTD-017-02 | TST-PFM-MTD-036 (not-run), TST-PFM-MTD-041 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-03 A relationship type cannot define a cascade that would delete a contact or organization. | yes | ATS-PFM-MTD-017-03 | TST-PFM-MTD-016 (not-run), TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-04 Endpoint types, cardinality and dating are immutable; versioned changes may alter labels and policies, and primary support cannot be disabled while an in-force primary remains. | yes | ATS-PFM-MTD-017-04 | TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-05 Removal deletes an unused type or deactivates a used type, preserving links and blocking new ones while allowing subsequent revival. | yes | ATS-PFM-MTD-017-05 | TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-06 A relationship named as an object owner cannot be deleted or deactivated regardless of object status, and the refusal names the affected objects and required owner change. | yes | ATS-PFM-MTD-009-13, ATS-PFM-MTD-017-06, ATS-PFM-MTD-017-09 | TST-PFM-MTD-023 (not-run), TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-07 Required-link flags can be stored on a type but have no enforcement in record or link writes. | yes | | |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-08 The approved relationship limits are one hundred types per workspace and twenty touching an object, but current code enforces neither limit. | yes | | |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-09 Type mutations audit changed field names and advance the workspace query description so relationship changes become available to queries. | yes | ATS-PFM-MTD-017-07 | TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-017 | BR-CAP-PFM-MTD-017-10 The relationship-type editor explains choices and validation issues, saves no invalid definition and remains unavailable to standard users. | yes | ATS-PFM-MTD-017-03, ATS-PFM-MTD-017-08 | TST-PFM-MTD-016 (not-run), TST-PFM-MTD-026 (not-run), TST-PFM-MTD-041 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-01 Creating a link requires an active workspace type and two existing compatible endpoints, rejects self-links and fills an omitted endpoint from the record route. | yes | ATS-PFM-MTD-012-18, ATS-PFM-MTD-012-19, ATS-PFM-MTD-017-09, ATS-PFM-MTD-018-01 | TST-PFM-MTD-036 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-02 A link remains in force through its inclusive end date in the workspace calendar, or indefinitely when no end date exists. | yes | ATS-PFM-MTD-018-02 | TST-PFM-MTD-020 (not-run), TST-PFM-MTD-044 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-03 Overlapping date spans cannot occupy a duplicate pair, a cardinality-limited endpoint or the primary place of a record and type; unbounded ends and inclusive dates determine conflicts while adjacent spans are allowed. | yes | ATS-PFM-MTD-018-02, ATS-PFM-MTD-018-03 | TST-PFM-MTD-018 (not-run), TST-PFM-MTD-020 (not-run), TST-PFM-MTD-044 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-04 Concurrent writers cannot both occupy a conflicting relationship place, and the losing write receives a conflict refusal. | yes | ATS-PFM-MTD-018-04 | TST-PFM-MTD-044 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-05 Only dated types accept calendar dates, an end cannot precede its start and only primary-enabled types accept primary links. | yes | ATS-PFM-MTD-018-05 | TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-06 Type and endpoint identities remain fixed, while versioned replacements can change dates, primary designation, position and notes bounded to four thousand characters. | yes | ATS-PFM-MTD-018-06 | TST-PFM-MTD-036 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-07 Ending a dated link uses a supplied day or the workspace today and refuses already-ended, invalid or conflicting spans; ending an undated link is refused in favour of removal. | yes | ATS-PFM-MTD-018-07, ATS-PFM-MTD-018-13 | TST-PFM-MTD-019 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-08 Removing a dated link without an end date ends it today, removing a dated link with an end date deletes it as a correction, and undated links are deleted. | yes | ATS-PFM-MTD-018-08 | TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-09 Creation permits one thousand links per record and type on each side, counting current and ended links together, while merge can exceed that limit. | yes | ATS-PFM-MTD-018-09 | TST-PFM-MTD-044 (not-run), TST-PFM-MTD-045 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-10 Link lists use the current endpoint label and opposite record name, default to in-force links, offer ended history when requested and isolate workspaces. | yes | ATS-PFM-MTD-018-10 | TST-PFM-MTD-017 (not-run), TST-PFM-MTD-024 (not-run), TST-PFM-MTD-036 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-11 Relationship cards on custom, contact and organization pages expose permitted link actions and ended history, allowing standard users to maintain links while readers receive no actions. | yes | ATS-PFM-MTD-018-11 | TST-PFM-MTD-026 (not-run), TST-PFM-MTD-036 (not-run) |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-12 General relationships leave contact-to-organization affiliations under the separate CRM model. | no | | |
| CAP-PFM-MTD-018 | BR-CAP-PFM-MTD-018-13 Update locks refuse edits and ending, any lock refuses removal, and deactivation does not prevent maintenance of existing unlocked links. | yes | ATS-PFM-MTD-018-12 | |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-01 Endpoint deletion applies the configured side rule: detach removes links, cascade also deletes the opposite custom record, restrict refuses in-force links and ended links are removed regardless of policy. | yes | ATS-PFM-MTD-017-09, ATS-PFM-MTD-018-13, ATS-PFM-MTD-019-01 | TST-PFM-MTD-037 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-02 Cascades cannot delete contacts or organizations, stop at a depth of ten and roll back when the depth or a record lock prevents deletion. | yes | ATS-PFM-MTD-019-02 | TST-PFM-MTD-037 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-03 CRM endpoint deletion invokes relationship rules within its own transaction and reports restricting types while rolling back all resulting changes on refusal. | yes | ATS-PFM-MTD-019-03 | TST-PFM-MTD-037 (not-run), TST-PFM-MTD-133 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-04 CRM-originated cascades perform the same value cleanup, asset detachment, audit, history and event work as direct custom-record deletion. | yes | ATS-PFM-MTD-013-10, ATS-PFM-MTD-019-04, ATS-PFM-MTD-019-10 | TST-PFM-MTD-037 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-05 Deletion functions operate only within the transaction workspace and are executable only by the authorized CRM and Platform service roles. | yes | ATS-PFM-MTD-019-05 | TST-PFM-MTD-037 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-06 Owner policies continue to apply when the owned object is draft or archived, including cascades and restricting links. | yes | ATS-PFM-MTD-019-06 | TST-PFM-MTD-037 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-07 Merging CRM duplicates moves current and ended links to the survivor, ends overlapping duplicate or self-links on the merge day and clears an additional primary flag. | yes | ATS-PFM-MTD-019-07 | TST-PFM-MTD-025 (not-run), TST-PFM-MTD-039 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-08 Merge also redirects custom-record reference values from merged contacts or organizations to the survivor and captures prior values in history. | yes | ATS-PFM-MTD-014-07, ATS-PFM-MTD-019-08 | TST-PFM-MTD-053 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-09 Merge planning counts moved links, redirected references and endings, application follows those counts, repeat application moves nothing and per-record limits do not block a merge. | yes | ATS-PFM-MTD-019-09 | TST-PFM-MTD-039 (not-run), TST-PFM-MTD-053 (not-run) |
| CAP-PFM-MTD-019 | BR-CAP-PFM-MTD-019-10 Workspace deletion clears relationships before their types, and reset empties both collections. | yes | | |