SpecificationsActivities, Follow-ups and Task Work
19 acceptance test sets for MOD-CRM-ACT, one per capability, holding 131 scenarios — 127 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-CRM-ACT-001 | Log one interaction for all related people and organizations | 13 | 13 | 11 | 10 api · 1 browser · 2 unit | Proposed |
ATS-CRM-ACT-002 | Create a follow-up while recording an interaction | 6 | 5 | 4 | 5 api · 1 browser | Proposed |
ATS-CRM-ACT-003 | Correct or delete an activity with protection against stale edits | 8 | 8 | 4 | 7 api · 1 browser | Proposed |
ATS-CRM-ACT-004 | Retain supporting files with an activity | 4 | 4 | 2 | 4 api | Proposed |
ATS-CRM-ACT-005 | Read past interactions and upcoming work on a record timeline | 10 | 10 | 4 | 10 api | Proposed |
ATS-CRM-ACT-006 | Review activity changes and their attribution | 3 | 3 | 1 | 3 api | Proposed |
ATS-CRM-ACT-007 | Find and open activities across the workspace | 3 | 3 | 1 | 2 api · 1 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-ACT-008 | Configure activity types and the details they collect | 9 | 9 | 8 | 8 api · 1 browser | Proposed |
ATS-CRM-ACT-009 | Preserve the baseline activity catalog without replacing customer choices | 5 | 5 | 3 | 1 browser · 4 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-ACT-010 | Record and maintain a piece of work | 12 | 12 | 8 | 10 api · 2 browser | Proposed |
ATS-CRM-ACT-011 | Complete, cancel and reopen work with clear attribution | 8 | 8 | 7 | 2 unit · 6 api | Proposed |
ATS-CRM-ACT-012 | Assign shared work and claim it from a queue | 9 | 8 | 6 | 8 api · 1 browser | Proposed |
ATS-CRM-ACT-013 | Offer work to a security role and reserve it by claim | 6 | 5 | 3 | 5 api · 1 browser | Proposed |
ATS-CRM-ACT-014 | Work from personal and shared task views | 4 | 3 | 2 | 3 unit · 1 browser | Proposed |
ATS-CRM-ACT-015 | Route overdue work to the people responsible for it | 6 | 6 | 2 | 5 api · 1 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-ACT-016 | Maintain task classifications and shared queues | 8 | 8 | 6 | 7 api · 1 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-ACT-017 | Create workflow tasks once and repeat actions according to state | 8 | 8 | 7 | 8 api | Proposed |
ATS-CRM-ACT-018 | Retain interactions and work through record deletion and merge | 3 | 3 | 1 | 1 api · 2 browser | Proposed |
ATS-CRM-ACT-019 | Apply workspace access and maintenance permissions | 6 | 6 | 6 | 6 api | Proposed |