--- id: CON-CRM-ACT-005 name: Record Timeline feature: FEAT-CRM-ACT-01 product_area: crm module: activities-tasks revision: 2 status: draft product_intent: proposed implementation_evidence: observed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- A record timeline presents one contact’s or organization’s related interactions and tasks as upcoming and historical context. owned_by: MOD-CRM-ACT synonyms: - relationship context not_to_be_confused_with: - A revision log - Workspace activity queries facets: - name: Upcoming meaning: Scheduled interactions and open tasks ordered earliest first. used_for: Preparing for the next interaction or outstanding work. provenance: observed source: 'services-crm:modules/activities/services/persistence/timelines.ts' - name: History meaning: Completed or cancelled interactions and closed tasks ordered latest first. used_for: Reviewing earlier relationship context. provenance: observed source: 'services-crm:modules/activities/services/persistence/timelines.ts' - name: Filters and search meaning: Structured filtering and text matching insensitive to case and accents. used_for: Finding relevant entries within a busy record. provenance: observed source: 'services-crm:modules/activities/services/persistence/timelines.ts' - name: Summary meaning: 'Whole-stream type and status counts, actor choices and upcoming totals.' used_for: Providing overview without reading every page. provenance: observed source: 'services-crm:modules/activities/services/persistence/timelines.ts' - name: Editability meaning: Reported update authority without a record-lock check. used_for: >- Offering actions consistent with permission while recognizing later lock refusals. provenance: observed source: 'services-crm:modules/activities/services/persistence/timelines.ts' relationships: - to: CON-CRM-ACT-001 statement: The timeline includes each linked interaction once. provenance: test source: >- 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 - to: CON-CRM-ACT-003 statement: The timeline includes related tasks when task read authority permits. provenance: test source: >- services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#leaves the tasks out for a caller who may not read tasks lifecycle: [] acted_on_by: - CAP-CRM-ACT-005 - CAP-CRM-ACT-018 visible_to: - ACT-CRM-001 - ACT-CRM-002 - ACT-CRM-006 evidence: - >- The pinned service sources cited by the concept’s relationships, facets and acting capabilities supply its observed context. - >- The pinned console sources cited by the concept’s relationships, facets and acting capabilities supply its observed context. supersedes: [] --- # Record Timeline ## What It Is A record timeline is the contact or organization view that brings interactions and related work into one stream. It lets staff understand the relationship before a call, prepare for planned activity and see what remains to be done. The Activity tab provides that context without requiring a separate search through all workspace activities and tasks. The stream is assembled from the record’s activity links and related tasks when read. It does not duplicate those records or become their owner. Upcoming presents scheduled interactions and work still in progress, while History presents completed or cancelled interactions and closed work. The summary describes the whole record context rather than only the page currently visible. ## What It Is Not The timeline is different from revision history. Changing a contact’s name or correcting an activity produces history for that record; it does not itself describe another interaction. A workspace activity list serves a broader search purpose and uses the query layer. The timeline instead stays anchored to one contact or organization. It is also not a guarantee that every application event about the person appears. The examined stream covers activities and tasks. Registrations, payments and other application records need their own integration and product decisions before they can be assumed part of this view. ## How It Is Used A coordinator opens a member or organization record and reviews the recent context. Filters narrow the entries to a relevant kind, owner, status or period. Text search helps find discussion details even when letter case or accents differ. More pages continue the same combined stream, and a task entry opens its drawer on Tasks. Read authority matters at this point. A reader who cannot read tasks receives activity content without task rows or counts. Editing authority is reported separately, and an offered edit can still encounter a record lock. Losing the final activity link removes its timeline context even though the activity itself remains retained. ## Its Facets **Upcoming.** Planned interactions and open work give staff a forward-looking view, with past-due conditions marked. **History.** Past interaction and closed-work entries provide context for later conversations and decisions. **Filtering and search.** Structured choices and visible-text matching make a long relationship readable without scanning every page. **Summary.** Whole-stream counts and actor choices support overview and filtering independently of pagination. **Editability.** The reported flag describes update permission. It does not include the record’s lock state, which can still prevent a save. ## How It Relates Contacts and organizations own the record context and host the Activity tab. Activity links determine which interactions belong there, and task references determine which work appears. Merge transfers those relationships to the survivor and the former record’s timeline identifies that surviving context. ## What It Could Become The product should decide which additional application events belong in relationship context and how retained activities with no links are managed. It should also align editing signals with actual save eligibility. Those extensions need explicit sources and ownership so the timeline remains a view of existing facts rather than another competing home for them.