forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-sla-configure
service-itsm-agentic-setup-incident-sla-configure
UnverifiedEnd-to-end Incident SLA setup for Service Cloud ITSM — the policy's Business Hours (reuse a named schedule, or create one from described hours or a time zone), MilestoneTypes, an Incident-scoped SLA Policy (SlaProcess), Milestones with criteria, and the Entitlement so Incidents get an EntityMilestone with a computed TargetDate. Use when the user asks to create or set up an Incident SLA policy (predefined or custom, with or without specific business hours), configure SLA milestones on Incidents, set up entitlement processes for ITSM, or enable SLA tracking for incident management. For Incidents, use this instead of the single-step SLA policy, milestone, or activation skills. DO NOT TRIGGER when: the user asks about Case entitlements or Case SLA (not Incident), querying existing SLA policies without setup intent, general Entitlement sObject CRUD unrelated to Incident, or Milestone queries for reporting purposes only.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.2 KB |
| assets/attach-milestone-action.json | config | 3.9 KB |
| assets/attach-milestone.json | config | 553 B |
| examples/milestone-patterns.md | markdown | 14.9 KB |
| examples/output-templates.md | markdown | 4.3 KB |
| references/mcp-invocation.md | markdown | 49.3 KB |
| references/workflow.md | markdown | 32.5 KB |
assets/attach-milestone-action.json
View on GitHub{
"_notes": "Phase 5 request-body templates for POST /connect/sla-management/sla-policies/<slaId>/milestones/<milestoneId>/actions. Send EXACTLY ONE action sub-object per call. timeLength/timeUnit live INSIDE checkpoint. timeUnit is Minutes|Hours|Days only. Never send isInitiationCheckpoint. Confirm success from body.success + non-empty body.actionMappings (+ triggerId for timed checkpoints), not the 201. UNIQUENESS: the actionFieldUpdate name/developerName must be unique per milestone (a WorkflowFieldUpdate DeveloperName is unique on the Incident object) — attaching the same-named action to a second milestone fails with DUPLICATE_DEVELOPER_NAME. Suffix both with the milestone (e.g. _FR for First Response, _RES for Resolution). These mirror the example bodies in references/mcp-invocation.md (Milestone Actions — see 'Milestone-action bodies') — keep the two in sync.",
"warningAction": {
"_notes": "Warn BEFORE target. timeLength = round(targetMinutes * (1 - X/100)). 2-hr (120-min) milestone, warn at 75% -> 30 min before. Default action = Field Update raising Urgency = High. NOTE: Incident.Priority is DERIVED from Impact x Urgency and is NOT directly updateable (createable:false/updateable:false) — a Field Update targeting Priority fails INVALID_FIELD_FOR_INSERT_UPDATE, so escalate by driving its updateable inputs (Urgency here, Impact on breach). Replace <MS> in name/developerName with a per-milestone suffix. For a custom-field target, put its 00N... CustomField id in columnEnumOrId (not the __c API name).",
"isSuccessCheckpoint": false,
"checkpoint": { "isWarning": true, "timeLength": 30, "timeUnit": "Minutes" },
"entityName": "Incident",
"actionFieldUpdate": {
"name": "SLA Warn 75pct <MS>",
"sourceTable": "Incident",
"targetTable": "Incident",
"columnEnumOrId": "Urgency",
"developerName": "SLA_Warn_75_<MS>",
"operationString": "LITERAL",
"literal": "High"
}
},
"violationAction": {
"_notes": "Escalate ON breach = Violation with timeLength 0 (fires at target). Default: raise Impact = High. If the paired warning action also fired (Urgency already = High), both axes are then High — on a DEFAULT matrix that derives the top Priority tier, but the matrix is org-configurable so the resulting Priority depends on the org's mapping; read the derived Priority back after the action fires to confirm the tier (Priority itself is not directly updateable — see warningAction _notes). Replace <MS> in name/developerName with the same per-milestone suffix used for the warning.",
"isSuccessCheckpoint": false,
"checkpoint": { "isWarning": false, "timeLength": 0, "timeUnit": "Minutes" },
"entityName": "Incident",
"actionFieldUpdate": {
"name": "SLA Escalate on Breach <MS>",
"sourceTable": "Incident",
"targetTable": "Incident",
"columnEnumOrId": "Impact",
"developerName": "SLA_Escalate_Breach_<MS>",
"operationString": "LITERAL",
"literal": "High"
}
},
"istBusinessHours": {
"_notes": "'IST business hours' is a POLICY-level BusinessHours, not a milestone-action field. Resolve-then-create: reuse an existing BusinessHours with TimeZoneSidKey='Asia/Kolkata' if present, else POST /sobjects/BusinessHours with this body (confirm first; BusinessHours is NOT API-deletable). Attach via the policy/Entitlement BusinessHoursId. ignoreMilestoneBusinessHours only changes how time remaining is displayed; target dates still follow these Business Hours.",
"Name": "IST Business Hours",
"TimeZoneSidKey": "Asia/Kolkata",
"MondayStartTime": "09:00:00.000Z",
"MondayEndTime": "18:00:00.000Z",
"TuesdayStartTime": "09:00:00.000Z",
"TuesdayEndTime": "18:00:00.000Z",
"WednesdayStartTime": "09:00:00.000Z",
"WednesdayEndTime": "18:00:00.000Z",
"ThursdayStartTime": "09:00:00.000Z",
"ThursdayEndTime": "18:00:00.000Z",
"FridayStartTime": "09:00:00.000Z",
"FridayEndTime": "18:00:00.000Z"
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |