The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/configuration/crm/taskQueues | Create Membership services and Events queues as an administrator. | CAP-CRM-ACT-016 | Both entries appear in configuration and selection lists. | test |
| 2 | createTask | Create two unassigned tasks in Membership services at different times. | CAP-CRM-ACT-012 | The records retain their queue arrival instants. | test |
| 3 | /console/{tenantId}/tasks | Open the queue view and claim the earlier task. | CAP-CRM-ACT-014 | The claimant becomes holder without removing queue membership. | test |
| 4 | releaseTask | Release the task. | CAP-CRM-ACT-012 | The holder clears while the earlier arrival position remains. | test |
| 5 | assignTask | Claim again and transfer the task to Events. | CAP-CRM-ACT-012 | The new queue receives a new arrival instant. | test |
| 6 | crm.tasks_overdue | Allow unclaimed queued work to pass its due day. | CAP-CRM-ACT-015 | When publishing is enabled, the item names queue responsibility and scope; Home delivery is beyond this test. | test services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#addresses a queued task nobody holds to the task queue responsibility at its queue |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | Several workers claim the same task together. | The reservation permits one winner. | Other attempts identify the successful holder. | test |
| failure | 1 | An administrator deletes a queue still referenced by a task. | The service rejects deletion of the used queue. | Queue and task references remain. | test |
| failure | 3 | The queue is inactive when a worker claims. | Current claim behavior still permits reservation. | Deactivation has not stopped queue work. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | Release retains the task’s prior queue position. | test |
02 | Concurrent claims leave exactly one holder. | test |
03 | A queue referenced by work cannot be deleted. | test |
End-to-end policy: required: Queue views and action controls need browser proof in addition to service concurrency and configuration assertions.