The suite follows an administrator’s classification and form changes through their later use on CRM records. It checks the configuration alongside what a coordinator sees and saves. Lifecycle, permission and regression cases retain the distinction between configuration authority and authority to maintain records.
The open-form case spans classification maintenance, effective form resolution and person creation. It compares the already-open form with subsequent openings so that the suite checks the interaction rather than only the configuration save.
An administrator has run-owned role, affiliation, contact and contact-point classifications and a fitting form definition.
Steps
Set the affiliation default, order the contact-point purposes and assign the contact form; read the catalogues and effective definitions.
Expected
Saved configuration is readable and the person form resolves through the selected classification and workspace defaults.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
One coordinator has opened a new-person form while an administrator can change its classification and form assignment.
Steps
Rename and deactivate the selected classification and assign a form; save the already-open person; reactivate and reopen creation; unassign the form and reopen again.
Expected
The open creation keeps its chosen classification. Later openings reflect the changed active choices and assigned form, then the built-in fallback.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
A used affiliation type is also the workspace default and existing people retain it.
Steps
Deactivate the type, inspect its held relationships and change the default; attempt deletion while relationships still reference it.
Expected
Existing relationships retain their type and the new default is readable; deletion remains blocked by actual use.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
A caller has contact-layout read and update grants but no affiliation-default or address-type write grants.
Steps
Read and update its layout section; try changing the affiliation default and reordering address purposes.
Expected
The layout work succeeds within its section; independent catalogue changes are refused with stored settings and order intact.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
A classification holds five presentation assignments and the workspace has an explicit affiliation default.
Steps
Replace the classification’s ordinary fields without presentation properties; read effective definitions and the workspace default.
Expected
The assignments survive and the affiliation default remains unchanged by unrelated catalogue editing.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.