Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-007Find and open activities across the workspace: Capability Test Specification

Markdown

ATS-CRM-ACT-007

Find and open activities across the workspace: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-007

Design

Executed by
TST-CRM-ACT-004, TST-CRM-ACT-065, TST-CRM-ACT-066

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision3

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

Find and open activities across the workspace: 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-007-01ATS-CRM-ACT-007-01
BR-CAP-CRM-ACT-007-04FND-CRM-ACT-053
BR-CAP-CRM-ACT-007-05ATS-CRM-ACT-007-02, ATS-CRM-ACT-007-04
BR-CAP-CRM-ACT-007-07ATS-CRM-ACT-007-03
BR-CAP-CRM-ACT-007-08ATS-CRM-ACT-007-01

An interaction links a primary organization and a contact. Find it through a permitted workspace query and follow its direct link, then compare the timeline entry with the query result.

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-053
  • Validation gap: FND-CRM-ACT-053
  • Permission covered
  • Edge gap: FND-CRM-ACT-053
  • Failure gap: FND-CRM-ACT-053
  • Boundary gap: FND-CRM-ACT-053
  • Concurrency gap: FND-CRM-ACT-053
  • Invariant gap: FND-CRM-ACT-053
  • Interaction covered

Test Scenarios

4 scenarios proving CAP-CRM-ACT-007; 3 bound to an existing test.

01 Evaluate activity query authoritypermissionapinegativetest
Proves
BR-CAP-CRM-ACT-007-01 BR-CAP-CRM-ACT-007-08
Preconditions
A customer administrator and Rhythm staff caller are available.
Steps
Run All activities as each.
Expected
Requests follow query authority and record any customer-policy gap.
Data
Each run creates and isolates the records it needs.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0721.spec.ts#CRM-ACC-0721
02 Open a direct activity link in its record contextinteractionbrowsertest
Proves
BR-CAP-CRM-ACT-007-05
Preconditions
Activities have a primary contact or only an organization.
Steps
Navigate to each activity link.
Expected
The related timeline opens with the activity selected.
Data
Each run creates and isolates the records it needs.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0722.spec.ts#CRM-ACC-0722
03 Compute activity summaries on related recordsruleapitest
Proves
BR-CAP-CRM-ACT-007-07
Preconditions
Contacts and organizations have completed, scheduled or no activity links.
Steps
Read their query-view summary fields.
Expected
Latest completed time and total count match the links, with empty time and zero count for no activities.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers the newest completed activity and every linked one for a contact
services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers no last activity and a count of 0 for a contact with none
Source
services-crm:modules/activities/tests/integration/db/activity-summaries.view.integration.spec.js#answers the newest completed activity and every linked one for a contact
04 Discovery lands on the selected record timelineinteractionapiproposed
Proves
BR-CAP-CRM-ACT-007-05 BR-CAP-CRM-ACT-005-05
Preconditions
An interaction links a primary organization and a contact.
Steps
Find it through a permitted workspace query and follow its direct link, then compare the timeline entry with the query result.
Expected
The contact timeline opens at the same interaction; sharing does not duplicate the selected entry.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Source
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0722.spec.ts#CRM-ACC-0722; services-crm:modules/activities/tests/integration/services/persistence/activities.queries.integration.spec.js#shows the activity linked to three contacts and an organization once on each of the four timelines

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