ATS-CRM-ACT-009Preserve the baseline activity catalog without replacing customer choices: Acceptance Test Set

ATS-CRM-ACT-009

Preserve the baseline activity catalog without replacing customer choices: Acceptance Test Set

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Preserve the baseline activity catalog without replacing customer choices: Acceptance Test Set

Coverage

Bound scenarios identify existing assertions; unbound scenarios remain proposed proof. Static inspection does not establish a passing execution.

Show evidence (sources, provenance, origins, pinned commits)

5 scenarios proving CAP-CRM-ACT-009; 5 bound to an existing test.

01 Inspect the expected baseline catalogbrowsertest

Proves: BR-CAP-CRM-ACT-009-01
Preconditions: An acceptance workspace is available for baseline inspection.
Steps: List activity types after setup.
Expected: The test expects seven built-in categories; installation across workspaces remains a Platform dependency.
Data: Each run creates and isolates the records it needs.
Bound to: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.ts#CRM-ACC-0728
Source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.ts#CRM-ACC-0728

02 Adopt a customized baseline typeapitest

Proves: BR-CAP-CRM-ACT-009-02
Preconditions: The workspace has renamed its Call type.
Steps: Apply the corresponding seed again.
Expected: The existing customized record remains unchanged.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#adopts a type the tenant already has under that id, leaving it as the tenant made it
Source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#adopts a type the tenant already has under that id, leaving it as the tenant made it

03 Prevent baseline type deletionapinegativetest

Proves: BR-CAP-CRM-ACT-009-03
Preconditions: Call is a built-in activity type.
Steps: Request its deletion.
Expected: The service conflicts and directs deactivation.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a system type, saying to deactivate it instead
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses the delete of a system type: 409
Source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a system type, saying to deactivate it instead

04 Preserve and uniquely reserve baseline codesapinegativetest

Proves: BR-CAP-CRM-ACT-009-04 BR-CAP-CRM-ACT-009-05
Preconditions: The workspace has built-in Call.
Steps: Try another code on its replacement and insert another type with the Call code.
Expected: Replacement preserves the code and the duplicate reservation fails.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#keeps a system type’s system code whatever the replacement says
services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a change of system code in the database too, whatever writes the row
services-crm:modules/activities/tests/integration/db/activities.table.integration.spec.js#refuses a second type of the tenant with the same system code
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0701.spec.ts#CRM-ACC-0701
Source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#keeps a system type’s system code whatever the replacement says

05 Keep Call direction mandatoryapinegativetest

Proves: BR-CAP-CRM-ACT-009-06
Preconditions: The workspace has built-in Call.
Steps: Make direction optional.
Expected: The refusal explains the required direction setting.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses to make the Call type’s direction anything but required, saying why
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses to make the Call type’s direction optional: 400
services-crm:modules/activities/tests/integration/db/activities.table.integration.spec.js#refuses a system call type whose direction is not required
Source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses to make the Call type’s direction anything but required, saying why