Skip to content

forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-management

service-itsm-agentic-setup-incident-management

Verified

Orchestrator for Incident Management setup in Service Cloud ITSM: presents the features with live org status, and configures each — Incident preferences, Incident persona PSG assignment, Priority Matrix, SLA & Milestones, Incident dashboards, Email-to-Incident, Major Incident Management (approval group + MIM preferences), Broadcast Communications, Manage Incidents with AI, Service Management Privilege (privilege escalation), and audit tracking. Use for: set up or configure incident management, a walkthrough, what incident features can I configure; the incident preference toggles (default field validations, auto-close child incidents, auto-triage, assign with Einstein, restrict assigned group, rich text descriptions); assigning the Incident Fulfiller or Incident Manager persona PSG. DO NOT TRIGGER for: the master on/off switch alone (use the IncidentMgmt SOR), the Priority Matrix, SLA, or field history tracking alone, the Major Incident Manager PSG, creating/editing PSGs, or Problem/Change/Case Management.

references/incident-preferences.md

View on GitHub
# Feature: Incident Preferences (delegated to the `IncidentMgmt` SOR)

How the orchestrator runs the **Incident Preferences** feature: the six per-feature toggles on the ITSM
Incident Management setup page. The `IncidentMgmt` SOR's own steps and guidance decide *how* — the six
preference names and labels, the two one-way ones, and the read-back; the orchestrator runs them itself
under its **SOR hand-off protocol** and owns every user-facing gate. This file adds what is specific to the
preferences.

1. `discover` the SOR by intent (e.g. "configure ITSM incident management preferences: automatically triage
   incidents, assign incidents with Einstein") and `describe` the id `discover` returns (`IncidentMgmt`) —
   never the Service-Foundation `IncidentManagement` look-alike, whose toggles are broadcast channels.
2. Behavior step 2 already ran this SOR's IT Service Enablement and Incident Management steps, so start at
   its preference flow: read (`getOrgPref_1`), change (`updateOrgPref_2`), read back
   (`verify-update-org-pref`). Never run its `disable-itsm-incident-feature` /
   `verify-itsm-incident-feature-disabled` steps (the master switch is not part of this feature) or
   `delegate-email-to-incident` (that is the **Email-to-Incident** feature).
3. Read all six and show them with the block below, flagging the two one-way ones. Ask which to change and
   in which direction (`AskUserQuestion`) — never infer the direction from the current state, and never
   offer to turn a one-way preference off. Skip any already in the requested state.
4. Confirm the exact change and that this org is modified (explicit confirmation for production). For
   *Restrict Assigned Group to Regular Groups* or *Enable Rich Text for Incident Descriptions*, the
   confirmation must say it can't be undone. Write each chosen preference and read each back; mark the
   feature `Done` only when every read-back matches.
5. In plain language: a failed enable of *Restrict Assigned Group…* means the org already has incidents, so
   it can't be turned on now — don't retry. If *Automatically Triage Incidents* or *Assign Incidents with
   Einstein* can't be read or turned on, the org lacks that switch's license (*IT Services: Agentforce
   Features for Employees* for triage, *IT Services: Einstein Features* for Einstein assignment): say so,
   skip it, and carry on with the others.
6. *Automatically Triage Incidents* and *Assign Incidents with Einstein* are also two of the three switches
   of the **Manage Incidents with AI** feature — the same org preferences — so one set in either feature
   reads as already set in the other. That feature's third switch, *Report Incidents from Chat or Voice
   Using AI*, is not one of the six.

```text
  Default Field Validations for Incidents ...... On | Off
  Automatically Close Child Incidents .......... On | Off
  Automatically Triage Incidents ............... On | Off
  Assign Incidents with Einstein ............... On | Off
  Restrict Assigned Group to Regular Groups .... On | Off  (one-way)
  Enable Rich Text for Incident Descriptions ... On | Off  (one-way)

Changed: <label> Off → On (SUCCEEDED | ALREADY-ON | FAILED)
```
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall