The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/crm/contacts/{id} | Choose Meeting in Log Activity from the member record. | CAP-CRM-ACT-001 | The form uses Meeting details and initially selects the member as primary. | test |
| 2 | /console/{tenantId}/crm/contacts/{id} | Enter discussion details, times and outcome, link the colleague and organization, and request a follow-up. | CAP-CRM-ACT-002 | The follow-up controls suggest a title and seven-day interval. | test |
| 3 | createActivity | Submit the activity form. | CAP-CRM-ACT-001 | The successful transaction contains one meeting and one follow-up. | test |
| 4 | /console/{tenantId}/crm/contacts/{id} | Visit the colleague and organization activity tabs. | CAP-CRM-ACT-005 | Their timelines and summaries include the same meeting. | test |
| 5 | /console/{tenantId}/tasks | Switch to My Open Tasks. | CAP-CRM-ACT-014 | The member’s follow-up is available with the supplied seven-day due calculation. | test |
| 6 | /console/{tenantId}/crm/contacts/{id} | Correct the meeting time and select the organization as primary. | CAP-CRM-ACT-003 | Related timelines return the corrected activity. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The browser calendar day differs from the workspace day. | The form supplies a due day based on browser today. | That day can differ from the service default calculation. | test |
| alternate | 4 | The record contains a long interaction history. | Narrow the timeline, search and continue to another page. | Matching entries continue without duplication. | test |
| failure | 3 | Entry omits a required detail or supplies a prohibited hidden value. | Validation identifies the detected invalid fields. | The rejected save retains no activity or follow-up. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | One meeting record is represented once in each related timeline. | test |
02 | The initial save creates one open follow-up with the member and organization context and selected due day. | test |
03 | Correction retains a shared meeting with the updated primary selection. | test |
End-to-end policy: required: This journey combines record context, activity entry and task discovery, so browser proof is needed for the integrated staff flow.