--- id: JNY-CRM-ACT-001 title: Log a shared meeting and create its follow-up feature: FEAT-CRM-ACT-01 product_area: crm module: activities-tasks revision: 2 status: draft product_intent: proposed implementation_evidence: inconsistent supersedes: - CRM-ACC-0690 - CRM-ACC-0691 - CRM-ACC-0696 - CRM-ACC-0705 - CRM-ACC-0706 source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f actor: ACT-CRM-001 goal: >- Capture the meeting in each related record context and record the promised next action. capabilities: - CAP-CRM-ACT-001 - CAP-CRM-ACT-002 - CAP-CRM-ACT-005 - CAP-CRM-ACT-003 - CAP-CRM-ACT-014 screens: - '/console/{tenantId}/crm/contacts/{id}' - '/console/{tenantId}/crm/organizations/{id}' - '/console/{tenantId}/tasks' steps: - 'n': 1 surface: '/console/{tenantId}/crm/contacts/{id}' action: Choose Meeting in Log Activity from the member record. capability: CAP-CRM-ACT-001 expected: The form uses Meeting details and initially selects the member as primary. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - 'n': 2 surface: '/console/{tenantId}/crm/contacts/{id}' action: >- Enter discussion details, times and outcome, link the colleague and organization, and request a follow-up. capability: CAP-CRM-ACT-002 expected: The follow-up controls suggest a title and seven-day interval. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - 'n': 3 surface: createActivity action: Submit the activity form. capability: CAP-CRM-ACT-001 expected: The successful transaction contains one meeting and one follow-up. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - 'n': 4 surface: '/console/{tenantId}/crm/contacts/{id}' action: Visit the colleague and organization activity tabs. capability: CAP-CRM-ACT-005 expected: Their timelines and summaries include the same meeting. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - 'n': 5 surface: '/console/{tenantId}/tasks' action: Switch to My Open Tasks. capability: CAP-CRM-ACT-014 expected: >- The member’s follow-up is available with the supplied seven-day due calculation. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - 'n': 6 surface: '/console/{tenantId}/crm/contacts/{id}' action: Correct the meeting time and select the organization as primary. capability: CAP-CRM-ACT-003 expected: Related timelines return the corrected activity. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts#CRM-ACC-0691 alternates: - from_step: 2 condition: The browser calendar day differs from the workspace day. path: The form supplies a due day based on browser today. outcome: That day can differ from the service default calculation. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0705.spec.ts#CRM-ACC-0705 - from_step: 4 condition: The record contains a long interaction history. path: 'Narrow the timeline, search and continue to another page.' outcome: Matching entries continue without duplication. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0696.spec.ts#CRM-ACC-0696 failures: - from_step: 3 condition: Entry omits a required detail or supplies a prohibited hidden value. path: Validation identifies the detected invalid fields. outcome: The rejected save retains no activity or follow-up. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0694.spec.ts#CRM-ACC-0694 rules_in_play: - BR-CAP-CRM-ACT-001-01 - BR-CAP-CRM-ACT-001-02 - BR-CAP-CRM-ACT-001-04 - BR-CAP-CRM-ACT-002-04 - BR-CAP-CRM-ACT-002-05 - BR-CAP-CRM-ACT-002-06 - BR-CAP-CRM-ACT-005-05 - BR-CAP-CRM-ACT-003-01 assertions: - id: AS-JNY-CRM-ACT-001-01 statement: One meeting record is represented once in each related timeline. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - id: AS-JNY-CRM-ACT-001-02 statement: >- The initial save creates one open follow-up with the member and organization context and selected due day. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0690.spec.ts#CRM-ACC-0690 - id: AS-JNY-CRM-ACT-001-03 statement: Correction retains a shared meeting with the updated primary selection. provenance: test source: >- react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0691.spec.ts#CRM-ACC-0691 e2e_policy: required e2e_reason: >- This journey combines record context, activity entry and task discovery, so browser proof is needed for the integrated staff flow. evidence: - >- Pinned browser evidence is identified by each journey step, alternate, failure and assertion. - >- Pinned service evidence is identified by each journey step, alternate, failure and assertion. --- # Log a shared meeting and create its follow-up ## Story A coordinator finishes a meeting with a member and colleague, then records the discussion from the member’s record. The organization is linked so other staff can find the same context. The coordinator requests a follow-up before saving and checks the resulting task in personal work. Later, correcting the meeting and its primary context updates the shared entry rather than creating another account of the discussion.