Activities and Tasks Identifier Registry
Markdown Planning / CRM / Activities, Follow-ups and Task Work / Id Registry Activities and Tasks Identifier Registry This ledger preserves all module allocations and the next available number in each series. CRM actor numbers belong to the shared product-area series. Earlier inventory references retain their source qualification and do not extend this numbering.
Series Series Allocated Next free MOD-CRM-ACTCharter allocation — FEAT-CRM-ACT-01 to 05 06 CON-CRM-ACT-001 to 005 006 ACT-CRM-006 and 007 added here; earlier actor allocations belong to the shared CRM ledger 008 CAP-CRM-ACT-001 to 019 020 JNY-CRM-ACT-001 to 006 007 ATS-CRM-ACT-001 to 019, matching capability suffixes 020 FND-CRM-ACT-001 to 049 050 OQ-CRM-ACT-001 to 006 (005 added by the design draft; 006 allocated by examination) 007 DOM-CRM-ACT-001, 003 and 005, matching the active Key Concepts (002 and 004 are superseded concepts and have no Domain Object) — STATE-CRM-ACT-001 to 005 006 WF-CRM-ACT-001 to 008 009 SVC-CRM-ACT-activities, tasks (one per source module)— SCR-CRM-ACT-001 to 009 010 ADR-CRM-ACT-001 to 016 017 IOP-CRM-ACT-none: the module asks no model a question 001
Rows Inside Artifacts Capability Title Rules (BR-…-NN) Scenarios and edge cases (SC-…-NN) Next free BR Next free SC CAP-CRM-ACT-001Log one interaction for all related people and organizations 01 to 17 01 to 03 18 04 CAP-CRM-ACT-002Create a follow-up while recording an interaction 01 to 10 01 to 03 11 04 CAP-CRM-ACT-003Correct or delete an activity with protection against stale edits 01 to 11 01 to 02 12 03 CAP-CRM-ACT-004Retain supporting files with an activity 01 to 07 01 to 01 08 02 CAP-CRM-ACT-005Read past interactions and upcoming work on a record timeline 01 to 14 01 to 03 15 04 CAP-CRM-ACT-006Review activity changes and their attribution 01 to 06 01 to 01 07 02 CAP-CRM-ACT-007Find and open activities across the workspace 01 to 08 01 to 02 09 03 CAP-CRM-ACT-008Configure activity types and the details they collect 01 to 12 01 to 02 13 03 CAP-CRM-ACT-009Preserve the baseline activity catalog without replacing customer choices 01 to 08 01 to 02 09 03 CAP-CRM-ACT-010Record and maintain a piece of work 01 to 13 01 to 02 14 03 CAP-CRM-ACT-011Complete, cancel and reopen work with clear attribution 01 to 12 01 to 02 13 03 CAP-CRM-ACT-012Assign shared work and claim it from a queue 01 to 13 01 to 03 14 04 CAP-CRM-ACT-013Offer work to a security role and reserve it by claim 01 to 12 01 to 02 13 03 CAP-CRM-ACT-014Work from personal and shared task views 01 to 09 01 to 01 10 02 CAP-CRM-ACT-015Route overdue work to the people responsible for it 01 to 08 01 to 02 09 03 CAP-CRM-ACT-016Maintain task classifications and shared queues 01 to 10 01 to 02 11 03 CAP-CRM-ACT-017Create workflow tasks once and repeat actions according to state 01 to 12 01 to 02 13 03 CAP-CRM-ACT-018Retain interactions and work through record deletion and merge 01 to 08 01 to 02 09 03 CAP-CRM-ACT-019Apply workspace access and maintenance permissions 01 to 10 01 to 02 11 03
Journey Title Assertions (AS-…-NN) Next free AS JNY-CRM-ACT-001Log a shared meeting and create its follow-up 01 to 03 04 JNY-CRM-ACT-002Take a task through completion, reopening and cancellation 01 to 03 04 JNY-CRM-ACT-003Claim, release and transfer shared queue work 01 to 03 04 JNY-CRM-ACT-004Configure interaction categories and retire old selections 01 to 03 04 JNY-CRM-ACT-005Offer a workflow review to a role and close it through the task service 01 to 03 04 JNY-CRM-ACT-006Merge duplicate records while retaining related interactions and work 01 to 03 04
Examination Allocations Existing assertions cover the hidden-attendee rule. The other newly reserved rules remain named in the proof-gap finding until dedicated scenarios exist.
Design Allocations The design draft allocated these before writing. Invariant rows (INV-<DOM id>-NN) are numbered inside each Domain Object.
Independent Design Examination Allocations Id Reserved Purpose FND-CRM-ACT-041Link-count and primary-link guarantees do not survive related-record deletion FND-CRM-ACT-042State tables omit supported transitions and model derived routing incompletely FND-CRM-ACT-043Sweep reads and publishes in separate transactions without a task recheck FND-CRM-ACT-044External orchestration, standards and publication evidence have limited local proof FND-CRM-ACT-045Screen action and refresh claims differ from the built console
Examination Identifier Reserved Purpose FND-CRM-ACT-046History access differs for live and deleted interactions; shared history presentation owner correction OQ-CRM-ACT-006Attention freshness and bounded repair expectations under reconciliation races
Control Backfill Allocations Id Purpose FND-CRM-ACT-047The service’s internal-use classification does not identify the personal class of interaction content, related people and assigned work held by this module. FND-CRM-ACT-048Task assignment accepts an omitted version and permits the later writer to replace assignment without a stale-write refusal. FND-CRM-ACT-049Task edits retain current assignment and closing stamps but no revision stream; earlier edits cannot be reconstructed as an append-only task history. Ordinary module lock edits likewise lack dedicated audited transitions.