--- id: FAS-CRM-ACT-02 feature: FEAT-CRM-ACT-02 product_area: crm module: activities-tasks revision: 1 status: proposed product_intent: proposed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f rhythm-v2-docs: 18a49edf30ee6bda18b159b65a2b91e093ea713d capabilities: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 scenarios: - id: FAS-CRM-ACT-02-01 title: Maintain customer categories alongside protected baseline entries kind: behaviour exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 relies_on: - ATS-CRM-ACT-008-02 - ATS-CRM-ACT-009-03 preconditions: An administrator has the baseline catalog and a customer-defined category. steps: - do: Create a named category with result choices and reorder the complete list. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js - do: Attempt deletion of an unused built-in category. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js expected: Customer configuration and valid ordering save; the built-in entry refuses deletion. negative: false data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: - TST-CRM-ACT-002 provenance: test source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js - id: FAS-CRM-ACT-02-02 title: Retired baseline choices retain customer configuration kind: interaction exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 relies_on: - ATS-CRM-ACT-008-07 - ATS-CRM-ACT-009-02 - ATS-CRM-ACT-003-05 preconditions: A renamed baseline type has an existing interaction. steps: - do: Reapply the baseline without resetting configuration. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts - do: Retire the type, attempt a new interaction and correct its earlier entry. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts expected: Customer naming survives adoption; retirement blocks new selection while prior use remains correctable. negative: false data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: [] provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts - id: FAS-CRM-ACT-02-03 title: Retire and restore category and result availability kind: lifecycle exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 relies_on: - ATS-CRM-ACT-008-07 - ATS-CRM-ACT-001-07 - ATS-CRM-ACT-003-05 preconditions: An active customer type and outcome have existing interactions. steps: - do: Deactivate the type and result, then compare new selection and retained selection. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts - do: Reactivate both and create an interaction with the restored result. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-001 - CAP-CRM-ACT-003 provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts expected: New use follows availability and an earlier selection remains retained during correction. negative: false data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: [] provenance: proposed source: services-crm:modules/activities/services/persistence/activity-types.ts - id: FAS-CRM-ACT-02-04 title: Inspect configuration without maintaining it kind: permission exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 relies_on: - ATS-CRM-ACT-008-01 - ATS-CRM-ACT-009-01 preconditions: A caller can read activity classifications but cannot maintain them. steps: - do: Read the type list, then request creation. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js expected: The list is readable and creation returns Forbidden; baseline maintenance gains no exemption. negative: true data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: - TST-CRM-ACT-002 provenance: test source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js - id: FAS-CRM-ACT-02-05 title: Adopt an existing baseline type without overwriting it kind: regression exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 relies_on: - ATS-CRM-ACT-009-02 preconditions: A baseline identifier already has customer-edited configuration. steps: - do: Apply the matching baseline seed. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js - do: Read the adopted type. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js expected: The seed adopts the existing entry and preserves its customer values. negative: false data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: - TST-CRM-ACT-009 provenance: test source: services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js - id: FAS-CRM-ACT-02-06 title: Inspect provisioned catalogs and a renamed baseline entry kind: interaction exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-016 relies_on: - ATS-CRM-ACT-009-01 - ATS-CRM-ACT-016-08 preconditions: A run owns a disposable workspace and its lifecycle actions. steps: - do: Provision and inspect both catalogs and queues. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-016 provenance: test source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.ts - do: Rename the baseline Call entry, attempt to rerun its provisioning step and read the catalog. exercises: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-016 provenance: test source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.ts expected: Provisioning returns the expected activity and task catalogs with no queues; Call retains its new name after the re-seed attempt. negative: false data_needs: Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes. bound_to: - TST-CRM-ACT-068 provenance: test source: react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0728.spec.ts binding_note: The suite records the re-seed response without asserting its success, so this case does not prove successful participant replay. Local seed adoption has a separate regression case. evidence: - Pinned capability test specifications, related workflows and the scenario-specific code or suite sources. coverage_findings: - FND-CRM-ACT-054 - FND-CRM-ACT-055 --- # Activity Classification: Feature Acceptance Suite ## What the Feature Must Do as a Whole The feature acceptance checks connect customer configuration with baseline identity and later use. Retirement, restoration and repeated setup are checked together so catalog administration remains coherent. ## Interactions Between Capabilities Classification changes affect new selection and earlier correction differently. Baseline adoption is checked alongside those changes to expose accidental replacement of customer choices. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative acceptance across the feature and its related capabilities. |