Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-004Retain supporting files with an activity: Capability Test Specification

Markdown

ATS-CRM-ACT-004

Retain supporting files with an activity: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-004

Design

Executed by
TST-CRM-ACT-006, TST-CRM-ACT-007

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision3

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

Retain supporting files with an activity: 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-004-01ATS-CRM-ACT-004-01
BR-CAP-CRM-ACT-004-02ATS-CRM-ACT-004-02
BR-CAP-CRM-ACT-004-03ATS-CRM-ACT-004-03, ATS-CRM-ACT-004-05
BR-CAP-CRM-ACT-004-05ATS-CRM-ACT-004-05
BR-CAP-CRM-ACT-004-06ATS-CRM-ACT-004-04
BR-CAP-CRM-ACT-004-07FND-CRM-ACT-050

An interaction has two prepared files. Remove one file through an edit, omit files in another partial edit, then delete the interaction and inspect cleanup requests.

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

Coverage

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

Test Scenarios

5 scenarios proving CAP-CRM-ACT-004; 4 bound to an existing test.

01 Reject attachment overflowboundaryapinegativetest
Proves
BR-CAP-CRM-ACT-004-01
Preconditions
An activity can accept valid managed attachments.
Steps
Submit 21 attachment entries.
Expected
The request identifies the attachment limit.
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#refuses more than 20 attachments
02 Require prepared managed file referencesvalidationapinegativetest
Proves
BR-CAP-CRM-ACT-004-02
Preconditions
A prepared upload and an unprepared address are available.
Steps
Save activities with each reference.
Expected
The prepared file becomes permanent and the unprepared reference is rejected.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#stores an uploaded file as a permanent reference of the activity, and attaches its lifecycle row
Source
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#stores an uploaded file as a permanent reference of the activity, and attaches its lifecycle row
03 Replace only the submitted attachment listruleapitest
Proves
BR-CAP-CRM-ACT-004-03
Preconditions
An activity holds two attachments.
Steps
Submit a replacement list containing one unchanged file.
Expected
Only that file remains attached.
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#keeps an attachment sent back unchanged, and removes one left out
04 Skip file copying during create replayinvariantapitest
Proves
BR-CAP-CRM-ACT-004-06
Preconditions
A managed attachment accompanies activity creation.
Steps
Repeat the create under the same identifier.
Expected
The permanent file is reused without a second copy.
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#copies nothing for the retry
05 Deletion releases the corrected attachment setinteractionapiproposed
Proves
BR-CAP-CRM-ACT-004-03 BR-CAP-CRM-ACT-004-05 BR-CAP-CRM-ACT-003-07
Preconditions
An interaction has two prepared files.
Steps
Remove one file through an edit, omit files in another partial edit, then delete the interaction and inspect cleanup requests.
Expected
The omitted list preserves the remaining attachment; deletion removes its local entry and requests cleanup for released references without claiming physical storage deletion.
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#keeps an attachment sent back unchanged, and removes one left out; services-crm:modules/activities/services/persistence/activities.ts:deleteActivity; services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#removes the activity and its links

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