Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-002Create a follow-up while recording an interaction: Capability Test Specification

Markdown

ATS-CRM-ACT-002

Create a follow-up while recording an interaction: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-002

Design

Executed by
TST-CRM-ACT-002, TST-CRM-ACT-006, TST-CRM-ACT-007, TST-CRM-ACT-034, TST-CRM-ACT-049, TST-CRM-ACT-050

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision3

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

Create a follow-up while recording an interaction: Capability Test Specification ​

Coverage ​

Category coverage counts specified proof. Unbound cases remain proposed; registered assertions do not establish a passing run.

RuleProof Scenario Or Finding
BR-CAP-CRM-ACT-002-01ATS-CRM-ACT-002-01
BR-CAP-CRM-ACT-002-03ATS-CRM-ACT-002-02
BR-CAP-CRM-ACT-002-04ATS-CRM-ACT-002-03
BR-CAP-CRM-ACT-002-05ATS-CRM-ACT-002-03, ATS-CRM-ACT-002-07
BR-CAP-CRM-ACT-002-06ATS-CRM-ACT-002-04
BR-CAP-CRM-ACT-002-07FND-CRM-ACT-069
BR-CAP-CRM-ACT-002-08ATS-CRM-ACT-002-07
BR-CAP-CRM-ACT-002-09ATS-CRM-ACT-002-05
BR-CAP-CRM-ACT-002-10ATS-CRM-ACT-002-06

A type suggests seven days and an earlier interaction already has a follow-up. Change its suggestion to two days, log another interaction through the API without an explicit due day, and inspect both tasks.

The interaction scenario names the capabilities and rules it exercises. The coverage finding retains incomplete permission combinations and failure variants.

Coverage

  • Rule gap: FND-CRM-ACT-069
  • Transition gap: FND-CRM-ACT-069
  • Validation covered
  • Permission covered
  • Edge gap: FND-CRM-ACT-069
  • Failure covered
  • Boundary covered
  • Concurrency gap: FND-CRM-ACT-069
  • Invariant covered
  • Interaction covered

Test Scenarios

7 scenarios proving CAP-CRM-ACT-002; 5 bound to an existing test.

01 Require task creation authority for follow-uppermissionapinegativetest
Proves
BR-CAP-CRM-ACT-002-01
Preconditions
The caller may create activities but not tasks.
Steps
Submit an activity asking for a follow-up.
Expected
The API returns Forbidden without retaining either record.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses a follow-up task to a caller without crm.tasks.create: 403
Source
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses a follow-up task to a caller without crm.tasks.create: 403
02 Reject invalid follow-up titlesvalidationapinegativeproposed
Proves
BR-CAP-CRM-ACT-002-03
Preconditions
The activity type is active.
Steps
Request follow-ups with blank and 501-character titles.
Expected
The title fails validation before either record is committed.
Data
Each run creates and isolates the records it needs.
Source
services-crm:modules/activities/aws/api/activities.schemas.ts:followUpTaskSchema
03 Create a follow-up for the selected record contextinteractionapitest
Proves
BR-CAP-CRM-ACT-002-04 BR-CAP-CRM-ACT-002-05
Preconditions
A seven-day suggestion accompanies two contacts and an organization.
Steps
Log an activity requesting a follow-up without an explicit due day.
Expected
The task uses the primary contact, organization and activity workspace date plus seven days.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#creates the follow-up task it is asked for, about the primary contact and the organization, due the type’s follow-up days after the activity
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#creates the follow-up task it is asked for, about the primary contact and the organization, due the type’s follow-up days after the activity
04 Compare browser and workspace follow-up datesboundarybrowsertest
Proves
BR-CAP-CRM-ACT-002-06
Preconditions
The browser day differs from the workspace day.
Steps
Create a late-evening meeting with a seven-day follow-up through the form and API.
Expected
The test records each calculation and demonstrates their possible day difference.
Data
Each run creates and isolates the records it needs.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0705.spec.ts#CRM-ACC-0705
05 Roll back an invalid follow-up transactionfailureapinegativetest
Proves
BR-CAP-CRM-ACT-002-09
Preconditions
The requested task type is missing.
Steps
Submit activity creation with that follow-up type.
Expected
Neither activity nor follow-up remains after refusal.
Data
Each run creates and isolates the records it needs.
Bound to
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#writes nothing when the follow-up task is refused
06 Avoid duplicate follow-ups on replayinvariantapinegativetest
Proves
BR-CAP-CRM-ACT-002-10
Preconditions
A client-selected activity identifier accompanies a follow-up.
Steps
Deliver the identical create twice.
Expected
Exactly one follow-up task remains.
Data
Each run creates and isolates the records it needs.
Bound to
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js#makes one follow-up task
07 A changed follow-up suggestion affects only a new saveinteractionapiproposed
Proves
BR-CAP-CRM-ACT-002-05 BR-CAP-CRM-ACT-002-08 BR-CAP-CRM-ACT-008-07
Preconditions
A type suggests seven days and an earlier interaction already has a follow-up.
Steps
Change its suggestion to two days, log another interaction through the API without an explicit due day, and inspect both tasks.
Expected
The new task uses the revised suggestion; earlier work retains its due day and editing the earlier interaction adds no task.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#creates the follow-up task it is asked for, about the primary contact and the organization, due the type’s follow-up days after the activity; react-console:components/activities/log-activity-sheet.tsx:offersFollowUp; services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses to remove an outcome an activity has, saying to deactivate it instead

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