Rhythm 2.0 Specifications

Appearance

FAS-CRM-ACT-05Workflow Delegation and Record Safeguards: Feature Acceptance Suite

Markdown

FAS-CRM-ACT-05

Workflow Delegation and Record Safeguards: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ACT-05
Capabilities
CAP-CRM-ACT-017, CAP-CRM-ACT-018, CAP-CRM-ACT-019
Executed by
TST-CRM-ACT-014, TST-CRM-ACT-028, TST-CRM-ACT-062, TST-CRM-ACT-063, TST-CRM-ACT-064

Product areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3rhythm-v2-docs 18a49edf

Workflow Delegation and Record Safeguards: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The feature acceptance checks connect trusted delegation, related-record changes and workspace access. They examine the same retained work across retries, consolidation and authorized claims.

Interactions Between Capabilities ​

A delegated task can outlive its original related record and still remain subject to role and workspace checks. Merge acceptance checks retained links and task context separately from the precise absorbed-record response.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative acceptance across the feature and its related capabilities.

Scenarios

6 scenarios proving FEAT-CRM-ACT-05 as a whole.

01 Delegate one task through a trusted service entry behaviour test
Exercises
CAP-CRM-ACT-017 CAP-CRM-ACT-013 CAP-CRM-ACT-019
Relies on
ATS-CRM-ACT-017-01 ATS-CRM-ACT-017-02 ATS-CRM-ACT-013-01
Preconditions
A registered service can create work for a role held by a local user.
Steps
[object Object], [object Object]
Expected
The same service-attributed task is returned on replay and the authorized holder claims it.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/e2e/tasks-service.e2e.spec.js
02 Carry delegated work through consolidation and access boundaries interaction proposed
Exercises
CAP-CRM-ACT-017 CAP-CRM-ACT-018 CAP-CRM-ACT-019 CAP-CRM-ACT-013
Relies on
ATS-CRM-ACT-017-02 ATS-CRM-ACT-018-03 ATS-CRM-ACT-019-01
Preconditions
A workflow task concerns a duplicate contact and is offered to a role.
Steps
[object Object], [object Object]
Expected
The single task references the survivor; foreign reads reveal no record and local role eligibility controls the claim.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Source
services-crm:modules/tasks/services/persistence/tasks.ts; services-crm:modules/activities/services/persistence/activities.ts
03 Keep shared interaction and work context after record deletion lifecycle test
Exercises
CAP-CRM-ACT-018 CAP-CRM-ACT-005 CAP-CRM-ACT-010
Relies on
ATS-CRM-ACT-018-01 ATS-CRM-ACT-010-08
Preconditions
One interaction links two contacts; a task concerns the contact selected for deletion.
Steps
[object Object], [object Object]
Expected
The interaction remains once in the surviving context and the task remains with its deleted-record reference cleared.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0719.spec.ts
04 Keep foreign-workspace data absent across both record kinds permissionnegative test
Exercises
CAP-CRM-ACT-019 CAP-CRM-ACT-017 CAP-CRM-ACT-018
Relies on
ATS-CRM-ACT-019-01 ATS-CRM-ACT-019-02
Preconditions
Two isolated workspaces own separate interactions and tasks.
Steps
[object Object], [object Object]
Expected
Cross-workspace records remain absent, mismatched contexts are forbidden and original records remain intact.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0718.spec.ts
05 Consolidate shared links without duplicating related work regression test
Exercises
CAP-CRM-ACT-018 CAP-CRM-ACT-005 CAP-CRM-ACT-010
Relies on
ATS-CRM-ACT-018-03 ATS-CRM-ACT-005-04
Preconditions
Duplicate records share an interaction and one owns another activity and a task.
Steps
[object Object], [object Object]
Expected
Duplicate links collapse with primary preserved; the timeline counts each activity once and work follows the survivor.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0720.spec.ts
06 Distinguish trusted command replay from public closing interaction test
Exercises
CAP-CRM-ACT-017 CAP-CRM-ACT-019 CAP-CRM-ACT-011
Relies on
ATS-CRM-ACT-017-03 ATS-CRM-ACT-011-05
Preconditions
A registered service has completed a task.
Steps
[object Object], [object Object]
Expected
The service repeat returns unchanged while the person repeat conflicts.
Data
Run-owned records, classifications and users; isolated workspace for lifecycle or calendar changes.
Bound to
Source
services-crm:modules/tasks/tests/integration/services/persistence/tasks.workflow-actions.integration.spec.js

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software