--- id: CON-CRM-ACT-001 name: Activity 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: >- An activity retains the customer’s account of a completed, cancelled or planned interaction and connects it to the relevant people and organizations. owned_by: MOD-CRM-ACT synonyms: - interaction entry not_to_be_confused_with: - Work managed as a task - Revision history of edits facets: - name: Linked records meaning: Contacts and organizations connected to the interaction. used_for: Presenting the shared interaction in each related context. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Primary record meaning: The chosen preferred context among the activity’s links. used_for: Choosing the record landing and follow-up context. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Attendees meaning: Linked contacts other than the primary record. used_for: Representing people who participate beyond the primary context. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Status meaning: 'Completed, Scheduled or Cancelled interaction standing.' used_for: Separating upcoming entries from historical context. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Outcome meaning: The result selected from the activity type’s choices. used_for: Understanding and reporting interaction results. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Owner meaning: >- An optional user responsible for the interaction, distinct from its author. used_for: Personal activity views and ownership filtering. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Notes meaning: Formatted discussion text cleaned before retention. used_for: Preserving readable detail about the interaction. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Files meaning: Managed documents retained as attachments to the entry. used_for: Keeping supporting material beside the interaction. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Origin meaning: Source classification and an optional external matching reference. used_for: Tracing and matching imported or entered interactions. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Follow-up meaning: Ordinary task work requested during activity creation. used_for: Recording the next piece of work without another form. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts; services-crm:modules/activities/db/activity-types.table.ts - name: Field modes meaning: 'Hidden, Optional and Required settings for six entry details.' used_for: Tailoring forms and validation to the selected type. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Outcomes meaning: 'The type’s ordered result catalog, with independently retired choices.' used_for: Selecting results while preserving earlier use. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Starting status meaning: The type’s Completed or Scheduled creation default. used_for: Reducing entry effort for past or planned interactions. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Default duration meaning: 'A type-level duration suggestion between one and 1,440 minutes.' used_for: Supplying a starting duration when no value is entered. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Follow-up suggestion meaning: An optional interval proposed by the activity type. used_for: Offering follow-up creation and suggested timing. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Built-in code meaning: The stable classification code of a baseline type. used_for: Recognizing standard categories after labels change. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Appearance and order meaning: 'Configured icon, palette colour and selection position.' used_for: Helping staff recognize and choose categories. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' - name: Active switch meaning: The type’s availability for new selection. used_for: Retiring classification without losing prior interactions. provenance: observed source: 'services-crm:modules/activities/db/activity-types.table.ts' relationships: - to: CON-CRM-ACT-002 statement: >- Activity classification is retained as a facet, with the earlier concept entry superseded. provenance: observed source: >- services-crm:modules/activities/db/activities.table.ts:activities_activity_type_fk - to: CON-CRM-ACT-005 statement: Each related record can present the activity in its timeline. 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: An initial activity save can request related follow-up work. provenance: test source: >- services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#creates the follow-up task it is asked for, about the primary contact and the organization, due the type’s follow-up days after the activity lifecycle: - state: scheduled meaning: The interaction remains planned. how_it_changes: The activity save sets this status. - state: completed meaning: The interaction is recorded as finished. how_it_changes: The activity save sets this status. - state: cancelled meaning: The interaction is recorded as cancelled. how_it_changes: The activity save sets this status. acted_on_by: - CAP-CRM-ACT-001 - CAP-CRM-ACT-002 - CAP-CRM-ACT-003 - CAP-CRM-ACT-004 - CAP-CRM-ACT-006 - CAP-CRM-ACT-007 - CAP-CRM-ACT-018 - CAP-CRM-ACT-019 visible_to: - ACT-CRM-001 - ACT-CRM-002 - ACT-CRM-003 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. - >- 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: - CON-CRM-ACT-002 --- # Activity ## What It Is An activity is the customer’s account of an interaction involving a person or organization. A call, email, meeting or note gives staff something they can review before the next conversation. The record can describe something completed, cancelled or still scheduled. Its identity remains distinct from its subject, date and the names of the people involved, so later corrections do not require a new interaction record. A coordinator creates an activity from a related record, and imports can bring earlier interactions into the same collection. Each activity refers to its type and the contacts or organizations it concerns. This differs from the earlier model in which one interaction belonged to one contact or one organization: a shared meeting can now be recorded once and viewed in several contexts. ## What It Is Not An activity is separate from a task. The activity describes the interaction; a task carries work someone needs to manage. A follow-up can connect those purposes during creation, but completion of the task does not itself create another interaction. Activity history is also different from the record timeline: history explains edits to this entry, while the timeline places it beside other interactions and work. ## How It Is Used Coordinators log interactions, readers consult them, and authorized colleagues correct inaccurate details. Before calling a member, staff can review recent conversations and decide what remains to discuss. A useful entry identifies the records involved and preserves enough context for someone else to understand the interaction. Selecting the appropriate type makes that context easier to enter and interpret. A lost response can leave staff unsure whether their entry saved. The create and edit recovery behaviors address that uncertainty. Concurrent corrections can still require reconciliation, and locks can prevent an otherwise permitted edit. An activity that loses all related links remains retained but cannot open through the normal record landing. ## Its Facets **Related records and primary context.** Links identify the people and organizations involved. One primary selection supplies the preferred context, while other linked contacts can represent attendees. **Type and field modes.** Classification belongs to the activity concept. Types shape subject, direction, duration, outcome, end-time and attendee controls. A hidden attendee control does not make linked contacts invalid. **Status and outcomes.** Status places the interaction in past or upcoming work. Outcomes describe its result using the selected type’s own choices; the outcome catalog can change without discarding earlier selections. **Ownership and attribution.** An owner supports personal views and filtering. Creation and modification attribution explain who wrote the record and remain separate from ownership. Initial user creation still defaults an empty owner back to its caller, an unresolved difference from the No Owner choice. **Notes and files.** Formatted text preserves discussion detail after cleaning. Managed attachments keep supporting documents associated with the entry, although the console currently lacks upload entry. **Defaults and follow-up.** Type settings suggest initial status, duration and follow-up timing. A follow-up requested during logging becomes a separate task with its own lifecycle. **Baseline identity, presentation and retirement.** Built-in codes distinguish standard categories despite renamed labels. Icons, colours and list position help staff recognize types. Deactivation provides a way to stop offering a selection while retaining prior use. **Origin.** Source classification and external references help staff distinguish entered, imported and system-created interactions and support later source matching. ## How It Relates Contacts and organizations provide the interaction contexts. Record timelines present those links alongside tasks. Task creation owns follow-up work, Platform owns managed file storage and import orchestration, and the activity’s revision history preserves changes to its own record. ## What It Could Become The product should finish management of retained activities with no links and the recorded deletion-audit requirements. It should also choose consistent duration and follow-up limits across console and service, settle the follow-up calendar, and decide whether console users need upload support. These decisions can extend the activity without turning each setting or attachment into another broad concept.