Rhythm 2.0 Specifications

Appearance

CAP-CRM-ACT-006Review activity changes and their attribution

Markdown

CAP-CRM-ACT-006

Review activity changes and their attribution

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-CRM-ACT-01
Key concepts
CON-CRM-ACT-001
Actors
ACT-CRM-001, ACT-CRM-002
Depends on
CAP-CRM-ACT-003
Open questions
OQ-CRM-ACT-001
Proved by
ATS-CRM-ACT-006

KindCapabilityProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Review activity changes and their attribution ​

Purpose ​

Staff inspect how an interaction record changes over time.

How It Works ​

A staff member with history access opens Version History from the activity editor. Rhythm lists saved revisions from newest to oldest. Opening a revision separates the activity details, links and files. Current record names help the reader recognize related information. Historical values can fall back to their references when a label no longer exists. Creation, modification and deletion all contribute revisions. Service executions and historical imports can carry attribution other than the person currently reading. Deletion of the activity does not remove the available revision list.

Relationships ​

  • Activity correction produces the revisions staff inspect.
  • Access controls determine who can read the activity and its history.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Readable revisions with actor attributionRevision access after deletion
Surfaces
consoleapi
Intent sources
services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-49

Controls

19 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003

Permissions

KeyChecked atScope
crm.activities.readapitenant
crm.activities.historyapitenant
crm.activities.historyconsoletenant

Business Rules

6 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 1 confirmed by a product decision, the rest inheriting this capability's proposed.

IdRuleKindEnforced atProvenance
01must prove
Proposed
Viewing activity revisions requires activity read and activity history permission.
no proof recorded yet
permissionapi, consoletest
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses the history to a caller without crm.activities.history: 403
02must prove
Proposed
Creating, changing or deleting an activity records a revision attributed to the execution caller, with service and historical-import attribution supported.
no proof recorded yet
invariantdatabase, serviceobserved
services-crm:modules/activities/services/persistence/activities.ts:recordedStampsOf
03must prove
Proposed
Revision lists run newest first and remain available after activity deletion.
no proof recorded yet
policyservicetest
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#answers its history, newest first: the update and the create
04must prove
Proposed
Revision details separate the activity, linked records and attachments, resolving record, type and outcome labels from current names.
no proof recorded yet
calculationservicetest
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#shows the creation section by section, the linked records named as they are called
05must prove
Proposed
An outcome label comes from its activity type’s outcome list, falling back to the outcome reference when that entry no longer exists.
no proof recorded yet
calculationservicetest
services-crm:modules/activities/tests/integration/services/history/activity-history.integration.spec.js#presents a change of outcome by the two outcomes’ names
06
Confirmed
The activity editor exposes Version History only to users with the history permission.
origin: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-49
policyconsoletest
react-console:components/activities/__tests__/activities-explorer-and-history.test.ts#refuses a reader who does not hold crm.activities.history, as CRM does

Scenarios

IdGivenWhenThenProvenance
01A saved call has one subsequent correction.Open its revision list.The correction precedes creation and both revisions carry attribution.test
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0702.spec.ts#CRM-ACC-0702

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