Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 39 ยท Workflows and Flow Designer

Approvals, Notifications and SLAs in ServiceNow

Learn how ServiceNow handles approvals with the Ask For Approval action, email notifications with triggers and templates, and SLA definitions with start, pause and stop conditions.

Three features turn raw records into a managed process: approvals (someone must say yes), notifications (people hear about it) and SLAs (the clock matters). They are used constantly in IT service management, and they all can be built without code.

Approvals

When a request needs sign-off, a flow uses the Ask For Approval action. You choose:

  • Record: the record being approved (usually the triggering record).
  • Table: the table of that record.
  • Approval Field: the field that stores the result, for example Approval on a request.
  • Approval Conditions: who must approve and how many are needed.
  • Rules: written like "Approve when Manager approves" or "Approve when anyone approves; Reject when anyone rejects".

The action creates one approval record (table sysapproval_approver) per approver, in state Requested. Approvers answer from the email link, the Self Service My Approvals page or the record. The action then sets your approval field to Approved or Rejected, and the flow continues with an If on that result.

Important rules to remember:

  1. An approval needs people or groups. You can name users, a group, or a pill such as Caller > Manager.
  2. Group approvals can require anyone, all or a count of members.
  3. Include a Due date or a reminder strategy. An approval waiting forever is a stuck process.
  4. Decide what happens on Rejected. Close the request? Notify the requester? Always handle this branch.
flowchart TD
    R["Request submitted"] --> A["Ask For Approval: Manager"]
    A --> D{"Result"}
    D -->|Approved| F["Create fulfillment task"]
    D -->|Rejected| X["Close request, notify requester"]
    D -->|No answer in 3 days| W["Remind approver, then escalate"]

An approval needs a plan for all three outcomes, not just approval.

Notifications

A notification is an email (or SMS, or push) the platform sends when a rule is met. Two ways to send them:

  • Send Email action in a flow: precise control, direct from a step.
  • Notification record (System Notification > Email > Notifications): fires from events or record changes, independent of any flow.

A notification record has three tabs worth knowing:

Tab What you set
When to send Table, whether it triggers on insert, update or an event, and a condition
Who will receive Specific users, groups, or users from fields (for example the caller) and event parameters
What it will contain Subject, message body (HTML or text), and a template

Message bodies can include variables like ${number} and ${short_description}, and a link to the record. The platform lets you preview an email for a chosen record before saving.

Good practices:

  • Send to people who must act. Notification overload makes people ignore everything.
  • Use events when several notifications react to one thing. The event is the single trigger, and each notification subscribes to it.
  • Test in a development instance. Most instances have outbound email disabled or set to a test inbox, so check Email Logs (System Logs > Emails) to see what was generated and why.
  • Respect each user's notification preferences.

SLAs

A service level agreement is a promise about time, for example "resolve priority 1 incidents within 4 hours". ServiceNow models it with an SLA definition (table contract_sla) that attaches to a task table. When the start condition is true, the platform creates a task SLA record that tracks the clock.

An SLA definition includes:

  • Type: SLA, OLA (operational level agreement, between internal teams) or Underpinning Contract.
  • Table: the task table, for example Incident.
  • Duration: a fixed time, such as 4 hours, or a relative duration from a field.
  • Schedule: when time counts, such as 8-5 weekdays (business hours) or 24x7.
  • Start condition: when the clock begins, for example Priority is 1.
  • Pause condition: when the clock stops temporarily, for example State is On Hold.
  • Stop condition: when the SLA is satisfied, for example State is Resolved.
  • Reset condition: when the clock restarts from zero.
  • Retroactive start: whether the clock counts from the record's creation time even if the condition became true later.

The task SLA moves through stages: In Progress, Paused, Achieved, Breached. Percentage fields (50%, 75%, 100%) feed escalations: at a threshold the platform can send an email or run a flow.

How the business clock works

An SLA of 4 hours on a 8-5 weekday schedule that starts at 16:00 on Friday does not breach on Friday night. Only business hours count, so 1 hour passes on Friday and the remaining 3 hours run on Monday from 08:00, breaching at 11:00. The stand-in below models this calculation.

JS Stand-in: SLA breach time with business hours

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The results are the Friday start breaching Monday morning, a same-day start breaching at 13:00, and a pause pushing the breach out by the paused time. A real SLA also supports holidays and several time zones through its schedule.

A stand-in for approval rules

Approval rules look at several decisions. This JavaScript model shows how "approve when all approve", "when any approves" and "count of 2" differ. It is not the platform code.

JS Stand-in: approval rules for a group

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the Ask For Approval action create?

    Each approver gets an approval record, and the action sets the result field when the rule is satisfied.
  2. 2. Which SLA condition stops the clock only temporarily?

    Pause suspends the timer, for example while a ticket waits for the customer.
  3. 3. Where can you check why an email was or was not sent?

    System Logs > Emails shows generated emails and their details.
  4. 4. An SLA with a business-hours schedule starts late Friday. When does time mostly count?

    The schedule decides which hours count toward the duration.

Summary

  • Ask For Approval creates approval records and writes Approved or Rejected; always handle rejection and delay.
  • Notifications come from flows (Send Email) or notification records triggered by events and conditions.
  • SLA definitions use start, pause, stop and reset conditions with a schedule; task SLAs track achieved or breached.
  • Test emails and SLAs in a non-production instance using the logs.

Next: Server-Side Scripting and GlideRecord