3.2 Notifications & Collaboration Tools
Key Takeaways
- Email Notification records define who is notified (When to send, Who will receive, What it will contain) and are triggered by an event, record insert/update, or condition.
- Inbound Email Actions parse incoming email and act on records by type: New creates a record, Forward, and Reply (which updates the matching record by Watermark or number).
- Knowledge Management organizes articles into Knowledge Bases with workflows for Draft, Review, Published, and Retired states, and supports user feedback.
- The Service Catalog presents requestable items as Catalog Items, Order Guides, and Record Producers, generating Request, Requested Item (RITM), and Catalog Task records.
- Modern ServiceNow collaboration uses the Connect/Conversation sidebar and the activity stream rather than the legacy Live Feed application.
Why Notifications and Collaboration Matter
Configuring applications for collaboration is not only about data structure — it is about keeping the right people informed at the right time. The CSA exam tests how an administrator sets up email notifications, processes inbound email, and uses Knowledge and the Service Catalog to scale self-service and communication.
Email Notifications
An Email Notification record (table sysevent_email_action) answers three questions, which map to the three tabs on the notification form:
| Tab | Question | Key Settings |
|---|---|---|
| When to send | What triggers it? | Send when: Record inserted/updated, Event is fired, or via Conditions and a filter |
| Who will receive | Who gets the email? | Users/Groups, fields like Assigned to, Watch list, Caller |
| What it will contain | What does it say? | Subject, message, Email Templates, and dynamic fields like ${number} |
Notifications can be triggered directly by a record change or indirectly by an Event registered in the Event Registry and fired by a business rule. Users control their own delivery through Notification Preferences, and a system property / Email diagnostics page lets admins confirm whether email sending is enabled (instances are often in a restricted state where email is logged but not actually sent).
Inbound Email Actions
An Inbound Email Action tells ServiceNow what to do when email arrives at the instance mailbox. Each action has a Type:
| Type | Trigger | Typical Behavior |
|---|---|---|
| New | Email does not match an existing record | Create a new record (for example, a new Incident) |
| Reply | Email is a reply to a record (matched by Watermark or record number in the subject) | Update the matching record, often adding to comments |
| Forward | Email is forwarded | Configurable handling, often create or relate a record |
A Watermark is a unique code ServiceNow injects into outbound email so a later reply can be matched back to the exact record. Inbound actions run in priority order, and only the first matching action of the applicable type executes.
Knowledge Management
Knowledge Management stores reusable answers as Knowledge Articles grouped into Knowledge Bases. Each base can use a publishing workflow so articles move through states such as Draft → Review → Published → Retired. Key administrator concepts:
- User Criteria controls who can read or contribute to a knowledge base — this is the access mechanism the exam expects, not ACLs alone.
- Articles support versioning, feedback/ratings, and flagging.
- Knowledge can be surfaced contextually on Incident and from the Service Portal search.
Service Catalog Basics
The Service Catalog is the storefront for requestable services. Three building blocks:
| Object | Purpose |
|---|---|
| Catalog Item | A single requestable thing (laptop, access request) with variables |
| Order Guide | Bundles multiple items into a guided multi-step request (for example, onboarding) |
| Record Producer | A catalog-style form that creates a record on any table (such as creating an Incident from a friendly form) |
Submitting a catalog request generates a Request [sc_request], one or more Requested Items [sc_req_item] (commonly called RITMs), and Catalog Tasks [sc_task] that fulfillers complete. Variables capture user input and can be reused in workflow and fulfillment.
Connect, Conversations, and Live Feed
Modern ServiceNow uses Connect (a real-time conversation sidebar) and the Activity stream on records for collaboration. Connect supports direct messages, group conversations, and conversations tied to a specific record. The older Live Feed social application is legacy and largely replaced; the exam favors the Connect/Conversations model and the record activity stream as the supported way teams collaborate inside the platform.
An administrator needs an email sent to the assignment group every time an Incident's priority changes to 1 - Critical. Which configuration object is primarily used?
How does ServiceNow match an inbound email reply to the correct existing record?
Which catalog object should an administrator use to let users create an Incident through a simple, guided form instead of the native Incident form?
Which records are typically generated when a user submits a Service Catalog request? Select all that apply.
Select all that apply