SLA Percentage Timer action
Summarize
Summary of SLA Percentage Timer Action
The SLA Percentage Timer action in ServiceNow allows users to monitor when a task's SLA record reaches a specific percentage and triggers various actions based on this percentage. This feature is crucial for managing SLAs efficiently by enabling notifications and other flow logic when specific SLA milestones are reached.
Show less
Key Features
- Percentage Configuration: Users can define a positive integer percentage to calculate the scheduled end time of the SLA, allowing for tailored SLA management.
- Status Tracking: The action provides various status indicators such as Completed, Paused, Repair, Skipped, and Waiting, each enabling different flow logic based on the SLA's progress.
- Total Duration Monitoring: The action tracks how long it ran, which helps in assessing SLA adherence over time.
- General Guidelines: Users must add SLA Percentage Timer actions only to flows initiated by an SLA Task trigger and ensure unique cumulative wait percentages for each timer action to avoid simultaneous completions.
Key Outcomes
By implementing the SLA Percentage Timer action, ServiceNow customers can enhance their ability to manage SLAs proactively. It ensures timely notifications and actions are taken based on SLA progress, thereby improving overall compliance and operational efficiency. Additionally, customers can customize flows based on specific status values, streamlining their workflows to better meet service delivery objectives.
Identify when a task SLA record reaches a specific percentage value and perform other actions or flow logic that is based on the SLA percentage. For example, send a notification when an SLA percentage timer completes.
Roles and availability
Available as a Workflow Studio ServiceNow core action. Users with the flow_designer or admin role can add an action to a flow and define configuration details.
Fields
| Field | Description |
|---|---|
| Percentage | The positive integer percentage of the total SLA duration used to compute an end time. For example, a 50% percentage results in the system computing an end date-time value that is 50% of the total SLA duration. If an SLA requires tasks to be completed within 24-hours, then 50% of that SLA would be 12 hours. |
Scheduled End Date/Time
- If the end date is in the future, the system creates a system event to continue running the action at that future date. While the system waits for the scheduled end date, it pauses the flow and action.
- If the end date is in the past, the system immediately sets the Status of the SLA Percentage Timer action.
Status
The Status data pill contains the result of the SLA percentage timer.
| Status | Description |
|---|---|
| Completed | The timer action reached its scheduled end date/time. Flow designers can build specific flow logic for this action status. |
| Paused | The timer was paused before its scheduled end date/time. If the timer resumes running, Workflow Studio generates a new scheduled end date/time value. Flow designers can build specific flow logic for this action status. |
| Repair | The flow is running in repair mode, and the scheduled end date/time is in the past. Flow designers can build specific flow logic for this action status. |
| Skipped | The timer did not run because the scheduled end date/time is in the past. Flow designers can build specific flow logic for this action status. |
| Waiting | The timer is running and has yet to reach the scheduled end date/time. |
Workflow Studio sets the action status when the SLA state matches an SLA condition or when certain UI actions are selected.
| SLA state | Action status set | Flow run state |
|---|---|---|
| SLA attaches and the scheduled end date/time is in the future. | Set action status to Waiting. | The flow waits until the SLA timer completes, is cancelled, or is paused. |
| SLA attaches and the scheduled end date/time is in the past. |
|
The flow runs the next action or flow logic in the flow sequence. |
| SLA Cancels. | Set action status to a null value. | The flow stops with a state of Cancelled. |
| SLA Pauses. | Set action status to Paused. | The flow waits until the SLA Task flow is cancelled or is resumed. |
| SLA reaches Scheduled End Date/Time. | Set action status to Completed. | The flow runs the next action or flow logic in the flow sequence. |
| SLA Resumes. | Set action status to Waiting. | The flow waits until the SLA timer completes, is cancelled, or is paused. |
| SLA Stops. | Set action status to a null value. | The flow stops with a state of Cancelled. |
Total Duration
The Total Duration data pill lists the total number of seconds that the action ran. The total duration is computed from the action start time and the time when the action reached the Completed status. Status values other than Completed produce a null value Total Duration.
General guidelines
Follow these general guidelines when creating flows that contain Service Level Agreement (SLA) Percentage Timer actions.
- Add SLA Percentage Timer actions only to flows with an SLA Task trigger
- An SLA Percentage Timer action can only run when the flow starts from an SLA Task trigger. You cannot activate a subflow containing an SLA Percentage Timer action.
- Create conditional flow logic for expected Status values
- Use the value of the Status field as a condition for flow logic. Build flow logic for expected Status values such as Completed, Repair, and Skipped. For example, add an If flow logic block to send a notification when the SLA Percentage Timer has a status of Completed.
- Assign each SLA Percentage Timer action a unique cumulative Wait for percentage value
- Each SLA Percentage Timer action computes its own Scheduled End Date/Time using its Wait for percentage value. If you create multiple SLA Percentage Timer actions, give each action its own unique cumulative Wait for percentage value. For example, create three separate actions with different percentage complete values such as 25%, 50%, and 75% complete. Setting all three actions to the same percentage complete value such as 25% causes the timers to complete at the same time.
- Copy existing flows to make customizations
- Reduce development time by copying the default SLA flows and customizing the copies with your own logic. Select a customized flow to run from the SLA definition. See Create an SLA definition .