JNY-CRM-ACT-004 Configure interaction categories and retire old selections
Markdown Planning / CRM / Activities, Follow-ups and Task Work / Activity Classification / Journey Story An administrator adds a category for site visits and arranges it where staff can find it. A coordinator records a visit using the configured form. Later the administrator retires an outcome and an older category. An earlier interaction remains correctable without replacing its historical classification. Unsupported deletion and direction changes produce guidance instead of removing meaning from the catalog.
Show evidence (sources, provenance, origins, pinned commits)Goal Provide useful activity choices while retaining the meaning of earlier entries. Screens /console/{tenantId}/configuration/crm/types/activityTypes /console/{tenantId}/crm/contacts/{id} Steps # Surface Action Capability Expected Provenance 1 /console/{tenantId}/configuration/crm/types/activityTypesInspect the available baseline activity categories. CAP-CRM-ACT-009The catalog test expects Call, Email, Meeting, Note, Text Message, Postal Mail and Other. test 2 /console/{tenantId}/configuration/crm/types/activityTypesCreate Site visit with three outcomes, required end time and a seven-day follow-up suggestion. CAP-CRM-ACT-008The type and ordered outcome list are saved. test 3 reorderActivityTypesMove Site visit to the opening position and submit the order. CAP-CRM-ACT-008The complete valid reorder takes effect together. test 4 /console/{tenantId}/crm/contacts/{id}Log a Site visit from a member record. CAP-CRM-ACT-001The form presents the configured details. test 5 /console/{tenantId}/configuration/crm/types/activityTypesDeactivate an outcome and Postal Mail, and require Call outcome. CAP-CRM-ACT-008Retired selections stop being offered for new activities. test 6 /console/{tenantId}/crm/contacts/{id}Correct the text of an earlier postal interaction. CAP-CRM-ACT-003The saved correction retains its earlier inactive classification. test
Alternate and Failure Paths Path From step Condition Path taken Outcome Provenance alternate 5 Deletion is requested for a baseline or referenced type. The refusal directs the administrator to deactivation. The configured type remains available to prior records. test failure 5 Call direction is made optional. The service rejects the configuration with an explanation. Call retains required direction. test failure 2 A name or follow-up interval exceeds the accepted limit. The save identifies the invalid field. No invalid configuration is written. test
Assertions Id Statement Provenance 01Existing interactions retain deactivated selections during valid corrections. test 02Built-in or referenced types reject deletion. test 03The baseline catalog test expects seven activity categories after setup. test
End-to-end policy: required: Configuration must shape the entry form and preserve historical corrections, making the combined browser path necessary.
← Previous Journey JNY-CRM-ACT-003 · Claim, release and transfer shared queue work Next Journey → JNY-CRM-ACT-005 · Offer a workflow review to a role and close it through the task service