--- id: CON-CRM-ACT-002 name: Activity Type feature: FEAT-CRM-ACT-02 product_area: crm module: activities-tasks revision: 2 status: superseded product_intent: proposed implementation_evidence: observed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- Activity type is the classification facet that shapes interaction entry; this superseded concept is retained for historical references. owned_by: MOD-CRM-ACT synonyms: - interaction category not_to_be_confused_with: - An interaction entry - A classification for task work facets: - 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-001 statement: The activity uses this classification and its result choices. provenance: test source: >- services-crm:modules/activities/tests/integration/services/persistence/activity-types.integration.spec.js#refuses a type an activity has, saying to deactivate it instead lifecycle: - state: active meaning: The classification or routing choice is available for selection. how_it_changes: An administrator creates or reactivates it. - state: inactive meaning: The choice is retired from selection while prior use remains. how_it_changes: An administrator deactivates it; task routing can still accept work. acted_on_by: - CAP-CRM-ACT-008 - CAP-CRM-ACT-009 - CAP-CRM-ACT-001 - 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. supersedes: [] superseded_by: CON-CRM-ACT-001 --- # Activity Type ## What It Is Activity type is a classification facet of Activity. This earlier concept entry is superseded so the planning layer has one broad home for the interaction and the configuration that shapes it. Its permanent identity remains available for tracing earlier references. The active Activity concept now explains the classification together with ownership, linked records, content and follow-up context. For customer staff, a type gives a familiar category to an interaction. An administrator might organize calls, meetings, notes or a customer-specific category. The category helps an editor understand what sort of information belongs in the form and helps a reader interpret an entry later. It is configured once and reused across interaction records rather than created separately for every conversation. ## What It Is Not A type is not another interaction and is not a task category. A task type organizes work, whereas an activity type organizes the customer’s account of an interaction. Its outcomes are choices within that classification, rather than separate broad concepts. An icon or colour helps recognition but does not establish a new record kind or permission boundary. ## How It Is Used Administrators maintain the activity catalog and staff select from it when logging interactions. Readers encounter the chosen category on timelines and workspace views. The configuration capability remains part of the planning layer even though classification is folded into its parent concept; the examination changes the conceptual grain rather than removing supported customer work. Retirement requires attention to existing use. Staff need to understand an earlier interaction even when its category is no longer offered for new entries. A classification therefore has both a current selection purpose and a historical interpretation purpose. Its owning capability describes the supported maintenance behavior and evidence. ## Its Facets Field modes describe the details a classification presents. Outcomes describe possible results within it. Starting status and duration supply entry defaults. Follow-up suggestions connect an interaction to subsequent work. Built-in identity distinguishes standard categories from the customer’s additions. Presentation and order make selection easier, while the active setting supports retirement. These are all facets of Activity in the active concept model. Their configuration values remain part of the implementation evidence, but the planning layer does not promote each setting or list entry into another noun alongside the activity itself. ## How It Relates The configuration feature groups maintenance and baseline-catalog capabilities. Activity remains the concept those capabilities act on. Contacts, organizations and timelines provide the surrounding record context, and Task owns resulting follow-up work. Platform workspace lifecycle remains responsible for orchestration of the declared baseline participant. ## What It Could Become The product should evaluate classification extensions within Activity rather than reopening a separate concept for each new control. The existing questions concern consistent limits, follow-up dates and integration of baseline installation. A future setting can be considered in that context while this entry remains superseded and its identifier remains reserved.