Admin Doc (1)
Admin Doc (1)
ServiceNow
Fundamentals
participant guide
© COPYRIGHT 2019 SERVICENOW, INC. ALL RIGHTS RESERVED.
ServiceNow provides this document and the information therein “as is” and ServiceNow
assumes no responsibility for any inaccuracies. ServiceNow hereby disclaims all
warranties, whether written or oral, express or implied by law or otherwise, including
without limitation, any warranties of merchantability, accuracy, title, non-infringement
or fitness for any particular purpose.
In no event will ServiceNow be liable for lost profits (whether direct or indirect), for
incidental, consequential, punitive, special or exemplary damages (including damage to
business, reputation or goodwill), or indirect damages of any type however caused even
if ServiceNow has been advised of such damages in advance or if such damages were
foreseeable.
TRADEMARKS
ServiceNow and the ServiceNow logo are registered trademarks of ServiceNow, Inc. in
the United States and certain other jurisdictions. ServiceNow also uses numerous other
trademarks to identify its goods and services worldwide. All other marks used herein
are the trademarks of their respective owners and no ownership in such marks is
claimed by ServiceNow.
ServiceNow Fundamentals
© 2019 ServiceNow, Inc. All Rights Reserved
ServiceNow Fundamentals
The ServiceNow Story
ServiceNow Fundamentals 5
© 2019 ServiceNow, Inc. All Rights Reserved.
The ServiceNow Story
Who better to explain what ServiceNow is than its founder, Fred Luddy.
“What is ServiceNow? It’s a platform; a piece of technology that lets people automate
workflow in a business. It was infuriating to me that IT people could make regular business
people feel so silly or ignorant. So for the first 9 months, we built a platform, showed it to a
number of people and it was received with a resounding, yawn. Now, it’s almost 15 years on,
and they’re using the platform exactly as we had envisioned.
“An entrepreneur is somebody who cares so deeply about solving a problem. I will guarantee
you that pretty much everybody that has been one of the tech-types over the past decade and
a half was more interested in solving the problem than they were in making money. That’s
entrepreneurial; doing something which is disruptive and is going to surprise the world in a
very wonderful way.
“Everything I’ve ever done in technology has been inspired by something I’ve seen somebody
doing, struggling to do, wishing they could do differently.”
“Today, ServiceNow’s customers include 850 of the Global 2000 biggest companies.” - Forbes
Magazine, May 29, 2018
ServiceNow Fundamentals 6
© 2019 ServiceNow, Inc. All Rights Reserved.
Module 1: User Interface & Navigation
User Interface and Navigation Module Objectives
• Explain how users can access ServiceNow
Collaboration
• Name the tables where Users and Groups are stored
Database Administration
• Identify the three components of the Now Platform® User Interface
Self-Service and Automation • Demonstrate how to navigate to applications and modules in
ServiceNow using the Application Navigator
Introduction to Development
Capstone Project
ServiceNow Fundamentals 7
© 2019 ServiceNow, Inc. All Rights Reserved.
Section 1.1:
ServiceNow Overview
User Story
As users of ServiceNow,
ServiceNow Fundamentals 8
© 2019 ServiceNow, Inc. All Rights Reserved.
Now Platform®
Security Human Resources
A leader in Enterprise Service Management (ESM), the ServiceNow Service Automation Platform
provides a modern, easy-to-use, service management solution in the cloud allowing your
organization to automate manual repetitive setup tasks, manage your core IT processes, standardize
service delivery, and focus on your core business, not just ITSM infrastructure.
ServiceNow provides all of this to users from a configurable web-based user interface, built on top
of a flexible table schema.
The ServiceNow platform and the applications that run on it use a single system of record and a
common data model to consolidate your organization’s business processes.
Another advantage to this single system is that it can be leveraged to build custom applications.
It is not limited to a specific department or function but encompasses the entire enterprise.
ServiceNow Fundamentals 9
© 2019 ServiceNow, Inc. All Rights Reserved.
Now Platform® Interfaces
Platform®
The Now Platform® User Interface is the primary way to interact with the applications and
information in a ServiceNow instance. To access the platform interface, a user navigates to a secure,
unique URL: https://<instance_name>.service-now.com The ability to use a custom URL is also
supported. To learn more about custom URLs, consult the ServiceNow product documentation.
The ServiceNow Classic Mobile App (currently available in the Google Play Store and iTunes)
provides the user with the ability to:
• Respond quickly to requests, no matter where they are
• Stay informed with real-time updates and information
• Save favorite lists and records to the app home screen
• Access the Service Catalog
• Use Connect Chat to collaborate with others
The Service Portal provides a user-friendly self-service experience by providing access to specific
features using widgets. When accessing the portal via web browser,
https://<instancename>.service-now.com/sp> users can:
• Search for articles, catalog items, records
• Submit requests
• Browse the corporate news feed, and more!
ServiceNow Agent introduces a true native mobile experience for IT Service Management (ITSM)
and Field Service Management (FSM) users on Android and iOS. Utilizing native phone applications
(location, camera, etc.), users can manage tasks, collaborate with team members, respond to
requests, access the knowledge base, and much more!
ServiceNow Fundamentals 10
© 2019 ServiceNow, Inc. All Rights Reserved.
What is the ServiceNow Instance?
When you are accessing ServiceNow, you are accessing an instance of the platform. An
organization can have several instances (e.g. Dev, QA, Test, Prod) and each instance is a
single implementation of the ServiceNow platform.
A load-balanced instance is located (hosted) in one of the ServiceNow Data Centers around the
world, or for a very, very small percentage of our customers, an instance can be implemented onsite
at the customer’s location. Each ServiceNow instance has a unique URL that uses a format similar to
https://<instance name>.service-now.com
The ServiceNow multi-instance architecture, organized in an instance stack, provides these distinct
advantages:
• The multi-instance architecture allows ServiceNow to perform actions on individual
customer instances such as performing an upgrade, on a schedule that fits the compliance
requirements and needs of your enterprise.
• Data is truly isolated in their own databases, making hardware and software maintenance on
these unique customer instances far easier to perform and issues can be resolved on a
customer-by-customer basis.
Each customer organization receives two instances of ServiceNow: production and sub-production.
They have the ability to obtain additional sub-production instances to be used for User Acceptance
Testing (UAT), Review, Development, or Quality Assurance (QA).
ServiceNow Fundamentals 11
© 2019 ServiceNow, Inc. All Rights Reserved.
Users and Groups
Users Groups
Within a ServiceNow instance, users are: A collection of users is a group
• Updating records Groups share a common purpose such as
• Importing data users approving change requests or users
• Requesting items receiving e-mail notifications
• Implementing flows Examples of Groups include:
• Approving knowledge content • Service Desk
• Running reports • Knowledge Base Authors
• Developing applications • HR Administrators
Manage the individuals who can access ServiceNow by defining them as users in the platform. User
names (represented by user IDs) are unique in ServiceNow.
User credentials are matched to different saved credentials for each method. Multiple Provider SSO
allows the selection/use of several identity providers (IdPs) to manage authentication as well as
retain local database authentication.
A group is part of the user hierarchy, and a user is part of a group. Groups may be imported from a
corporate directory (LDAP) or created manually in ServiceNow.
ServiceNow Fundamentals 12
© 2019 ServiceNow, Inc. All Rights Reserved.
Now Platform® User Interface
Banner Frame
Content Frame
Application
Navigator
The User Interface (UI) is the main way for users to interact with the applications and information in
a ServiceNow instance. Notable ServiceNow features include real-time form updates, user presence,
an application navigator designed with tabs for favorites and history, and enhanced activity streams
all of which you will explore in this training. This is an example of the System Administration
homepage.
NOTE: The position of these components on your screen may vary depending on your region.
ServiceNow Fundamentals 13
© 2019 ServiceNow, Inc. All Rights Reserved.
Banner Frame
1 2 3 4 5 6
Across the top of the platform interface, the banner frame is displayed. The banner frame contains
the following components:
1. Logo image (can be modified for the instance) returns the user to the homepage when
clicked.
2. User menu provides options to access your profile and preferences. Administrators can
impersonate users and elevate their security role.
3. Global text search icon: Finds records from multiple tables (quickest way to locate an
individual record)
4. Connect sidebar icon: Lets you begin or continue conversations. This icon is visible if
Connect is enabled.
5. Help icon: Opens the help panel with embedded help, where available. If there is no
embedded help, it offers help search options.
6. Gear icon: Opens the system settings for the user interface (UI). For more information on
system settings, search ServiceNow’s Product documentation (docs.servicenow.com) for the
article titled System settings for the user interface (UI).
ServiceNow Fundamentals 14
© 2019 ServiceNow, Inc. All Rights Reserved.
Application Navigator
The application navigator, or left navigation bar, provides access to all applications and the modules
they contain. An application is a group of modules, or pages, that provide related information and
functionality in an instance. For example, the Incident application contains modules for creating and
viewing incidents. The Configuration Management application contains modules for configuring
servers, databases, and networks.
There are four components in the application navigator which help a user quickly find information
and services:
• Filter navigator
• All applications
• Favorites
• Your history
Tip: Double-click the All applications icon to expand or collapse all applications in the navigator
ServiceNow Fundamentals 15
© 2019 ServiceNow, Inc. All Rights Reserved.
Application Navigator: Filter Navigator
Above the application list, use the Filter navigator to
quickly navigate to applications and modules
Just for fun! Try kb_knowledge.CONFIG in the filter navigator. Notice a separate tab opens in your
browser window. What kind of information is shown for the table?
ServiceNow Fundamentals 16
© 2019 ServiceNow, Inc. All Rights Reserved.
Application Navigator: Favorites tab
Every user can collapse and expand the application navigator by clicking on the arrow icon at the
bottom left of the application navigator. When the application navigator is collapsed, the filter
(funnel) icon and the favorites icons are displayed at the left of the user interface. To expand the
application navigator, click the filter icon or the arrow icon.
More information for adding/editing favorites can be found by searching ServiceNow’s product
documentation (docs.servicenow.com) for the article titled Use the UI16 navigator.
Tip: Admins can view favorites set by any user by navigating to System Definition > Bookmarks.
ServiceNow Fundamentals 17
© 2019 ServiceNow, Inc. All Rights Reserved.
Application Navigator: Your History
By default, the maximum number of activities displayed in the history tab of the application
navigator is 30. Administrators can configure this setting in the system properties table
(sys_properties.list) by modifying the value in the glide.ui.nav.history_length property.
The system creates history entries for many types of content, including lists, records, and
homepages. Some content types are not tracked in the history, such as UI pages and other non-
standard interfaces.
ServiceNow Fundamentals 18
© 2019 ServiceNow, Inc. All Rights Reserved.
Content Frame: Common Types of Interfaces
ServiceNow Fundamentals 19
© 2019 ServiceNow, Inc. All Rights Reserved.
ServiceNow Classic Mobile App
Mobile Favorites – Favorites display as icons on the homepage and provide links to records in the
system. Favorites automatically synchronize between the mobile UI and the desktop UI. Long press a
favorite to edit the following properties:
• Label
• Text and icon color
• Icon image
Mobile Lists – Lists appear as a single column of records on the mobile app UI display. Each row
represents a separate record. Live list updates are not available on mobile devices when other users
make changes. Mobile lists automatically reload when a record change is made by the currently
logged in user.
Mobile Service Catalog – Browse the service catalog using a browser on your mobile device or with
the ServiceNow Classic mobile app. The mobile UI for Service Catalog contains the following
elements:
• Current catalog
• Back button
• Search
• Application navigator button
• Shopping cart
Mobile Connect Chat – Communicate with coworkers using the ServiceNow Classic mobile app.
Many features supported in the desktop interface are available in the mobile app.
ServiceNow Fundamentals 20
© 2019 ServiceNow, Inc. All Rights Reserved.
ServiceNow® Agent
• Update records
• Coordinate with co-workers
• Receive push notifications
• Track their location
• Work offline
With the Madrid release, ServiceNow introduces a true native mobile experience for IT Service
Management and Field Service Management users on Android and iOS. Utilizing native phone
applications (location, camera, etc.), users can manage tasks, collaborate with team members,
respond to requests, access the knowledge base, and much more!
ServiceNow Fundamentals 21
© 2019 ServiceNow, Inc. All Rights Reserved.
Product Documentation: Docs and Community
https://docs.servicenow.com
https://community.servicenow.com
If anything in this class seems interesting, we highly encourage you to explore the topic in more
detail through either of the following websites:
docs.servicenow.com is the official documentation resource for ServiceNow, with content produced
by ServiceNow. From features to functionality, and even release notes, this resource should have all
of the information needed to get the most out of the platform.
This is a great resource to learn from users with real-life experience on the platform!
ServiceNow Fundamentals 22
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab 1.1:
Applications and
Modules
As users of ServiceNow,
ServiceNow Fundamentals 23
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab
Applications and Modules 1.1
610-15m
Lab Objectives
You will achieve the following objectives:
• Log on to your training instance
• Use the Application Navigator and its filter to access different areas of ServiceNow
• Add Knowledge and Service Catalog modules to Favorites
Scenario
This course builds on a scenario where you work for a division of a fictitious electronics
company called Cloud Dimensions.
Upon the reveal of their Infinity product, a portable holographic projector, you support a team
of department Subject Matter Experts (SMEs) with the implementation of ServiceNow.
ServiceNow will initially be used by Cloud Dimensions for tracking Infinity inventory, order
fulfillment, and customer support.
You will be required to impersonate various user personas – representing Cloud Dimensions
employees – throughout this course’s labs.
To start, you will assume the system administrator identity to accomplish a series of tasks.
Note: Your instructor will provide you with a registration URL for requesting a student instance
2. Log on using the System Administrator (admin) credentials provided when you
requested your student instance using the registration URL.
ServiceNow Fundamentals 24
© 2019 ServiceNow, Inc. All Rights Reserved.
B. Use the Filter Navigator
1. Take some time to scroll through the Application Navigator and notice the available
application menus and modules.
2. Set the Application Navigator view to display all applications in an expanded view
(double-click the All applications navigator icon to expand/collapse all), then locate
the Incident application to view the 9 incident modules.
Note: Notice how the user interface has changed in the Content Frame from a list of incident
records to an individual incident record/form.
5. From the Application Navigator, use the Filter navigator to filter the list of
application menus and modules by typing self-service into the Filter navigator.
Note: A single application menu, Self-Service, appears with many modules. Scroll down to see
all of the modules under the Self-Service application.
Note: Notice yet another user interface type displayed in the Content Frame.
ServiceNow Fundamentals 25
© 2019 ServiceNow, Inc. All Rights Reserved.
7. From the Application Navigator, type the keyword service into the Filter navigator.
Note: Scroll to see all of the applications and modules that contain the text “service” display.
2. Impersonate the Cloud Dimensions employee Joe Employee by typing their name
into the Search for user field.
Note: After selecting their name from the drop-down list, ServiceNow should reload and you
are now impersonating Joe Employee:
3. Take some time to scroll through the Application navigator and notice the available
application menus and modules compared to those seen by the system
administrator.
7. Download the necessary lab files for class by selecting the Class Lab Files article.
Note: Selecting the Class Lab Files article will download a zip file to your local machine titled
ServiceNow Fundamentals Class Lab Files. At your convenience, unzip the file.
ServiceNow Fundamentals 26
© 2019 ServiceNow, Inc. All Rights Reserved.
8. Hover over the Knowledge module, then add the Knowledge module as a favorite
by selecting the Add to Favorites icon (star) to the right of Knowledge.
Note: Upon selection, the Add To Favorites star will appear filled in.
Note: In addition to application menus and modules, the Filter navigator will display favorites
based on keywords:
10. Clear the Filter navigator keyword by selecting the X to the right of the Filter
navigator.
ServiceNow Fundamentals 27
© 2019 ServiceNow, Inc. All Rights Reserved.
11. Next, navigate to the Favorites tab of the Application Navigator to see the module
favorites you have created:
12. On the bottom-right of the Application Navigator, select the Edit Favorites (pencil)
icon.
Note: The Set up your favorites screen displays in the Content Frame. A favorite can be
customized to have any name, color, and icon.
14. Select any color and icon for the Self-Service > Knowledge favorite.
15. Repeat steps 12 and 13 to add Self-Service > Service Catalog as a favorite.
17. Minimize (collapse) the Application Navigator by selecting the Minimize Navigator
icon (circled arrow) at the bottom of the Navigator:
ServiceNow Fundamentals 28
© 2019 ServiceNow, Inc. All Rights Reserved.
18. From the minimized Application Navigator, notice that
the two favorites appear in the color and icon you have
selected:
Note: Your color and icon choices may vary from what is
shown here for demonstration purposes.
19. Navigate to the homepage by selecting the Home favorite displayed on the
minimized Navigator:
Lab Verification
Note: The Lab Verification section displays one, or more, screenshots of what you should have
created during this lab. Sometimes the lab verifications have been shown in earlier steps – as is
the case below.
Self-Service Favorites
Now you know how to create and maintain application and module favorites!
ServiceNow Fundamentals 29
© 2019 ServiceNow, Inc. All Rights Reserved.
Knowledge Check
What are the different interfaces for What are the components of the
accessing a ServiceNow instance? Application Navigator?
- Now Platform® User Interface - All applications
- Service Portal - Favorites
- ServiceNow Mobile Classic - Your history
- ServiceNow Agent - Filter navigator
ServiceNow Fundamentals 30
© 2019 ServiceNow, Inc. All Rights Reserved.
Section 1.2:
Lists and Filters
User Story
ServiceNow Fundamentals 31
© 2019 ServiceNow, Inc. All Rights Reserved.
Roles
Once access has been granted to a role, all of the groups or users assigned to that role are granted
the same access.
Additionally, a role may contain other roles and any access that is granted to one role is
automatically granted to any role that contains it. By assigning a role to a group, all the users in the
group inherit all of the roles within that role.
*TIP: Rather than adding roles to individual users, add the user to a group and assign the role to the
group. This method of role assignment makes maintenance easier when people transfer to different
roles in the organization. A user can be removed from one group and added to a new group;
inheriting all the permissions needed to perform their duties.
NOTE: You cannot delete roles that are assigned to the group from a user record. You must remove
the user from the group record.
ServiceNow Fundamentals 32
© 2019 ServiceNow, Inc. All Rights Reserved.
Roles
ServiceNow Fundamentals 33
© 2019 ServiceNow, Inc. All Rights Reserved.
Base System Roles
ServiceNow baseline includes many base system roles; some of which are shown here. To get more
information on base system roles, please search ServiceNow product documentation and search for
the title, Base system roles.
The System Administrator (admin) role has almost all roles and access to all platform features,
functions, and data, with some exceptions such as HR and Security Operations constraints. Grant
this privilege carefully.
Users holding the admin role can create and modify user roles, as well as impersonate other users.
However, not even users with the admin role can impersonate a security_admin role user and
elevate privileges while impersonating to access higher security functionality.
• Specialized Administrator roles have broad access but generally manage specific functions
or applications.
• Fulfiller/Process users have clearly defined paths and workflows in the platform and have
one or more roles, including the itil and approver_user roles. They can access all
functionality based on assigned roles.
• Approvers have the approver_user role, but no other roles.
• Requesters use the Service Catalog and Self Service applications. They can make requests
only on their own behalf, and are not assigned roles.
NOTE: The impersonator role can be assigned to a user to allow impersonation of other users,
excluding admins, for testing and visibility purposes.
ServiceNow Fundamentals 34
© 2019 ServiceNow, Inc. All Rights Reserved.
Impersonate a User
Users with the admin or impersonator
1
role can impersonate other users for
testing purposes.
2
To impersonate a user:
1. Open the user menu by clicking your
user name
2. Select Impersonate User
3. Select a user from the recent
impersonations list or enter the user’s 3
name to search for the user
*Not all users can be impersonated. If an admin attempts to impersonate a user with an specialized
administrator role for Human Resources or Security Incident Response, they will not be able to
access features granted by that role.
TIP: It is recommended to create logins for the following roles to effectively test the system:
• admin – to do work
• itil – to test as a fulfiller
• ess – to test as an end user
ServiceNow Fundamentals 35
© 2019 ServiceNow, Inc. All Rights Reserved.
Viewing Table Data: Lists
A list displays a set of records from a table within the content frame of ServiceNow
Each column
represents one field
Lists and forms are the most common ways to interact with data. A list displays a set of records from
a table. Lists can be filtered and customized to display the information you need.
In this example, the system administrator is accessing the User Administration application and a list
of users through the Users module. Other roles, such as user_admin, grant users the permissions to
manage users, groups, and roles.
ServiceNow Fundamentals 36
© 2019 ServiceNow, Inc. All Rights Reserved.
List Anatomy
1
1. Title Bar:
Displays the list title and, in 2
some cases, the view name as 3
well as search list values and a 4
record count
2. List Filters/Breadcrumbs:
Offers a quick form of filter 5
navigation
3. Column Headings:
Displays column (table field)
names and provides some list
controls
4. Column Header Search:
Provides a search within a
specific column
5. Field Values:
Right-click on a field value to
access additional actions
Although lists display data captured in different tables, their interface remains consistent with
common features.
ServiceNow Fundamentals 37
© 2019 ServiceNow, Inc. All Rights Reserved.
Context Menus
Context menus provide
1
different levels of controls
for a given list view 2
List Context (or control) menus, also sometimes called Additional Actions, can be accessed from
lists, columns, or on records by using right-click menus which provide different levels of controls:
• List Context Menu: Click the list context menu icon next to the title of the list (Incidents in
this example) to access options related to viewing and filtering the entire incidents list.
• Column Context Menu: Click the column context menu icon in the desired column header to
display actions related to that column, such as creating quick reports, configuring the list,
and exporting data.
• Record Context Menu: Right-click in a row’s cell to see a menu with actions related to the
values in that cell, such as filtering options, assigning tags, and more.
ServiceNow Fundamentals 38
© 2019 ServiceNow, Inc. All Rights Reserved.
List Filters
A filter is a set of conditions applied to a table list to isolate a subset of the data
1. Field
2. Operator
1 2 3
3. Value
Click the show / hide filter icon ( ) to add, remove, or edit filter conditions and apply
All users can apply, create, modify, and save filters. You may start with a list of all incidents but filter
those records to view only active incidents assigned to you.
Select Run to see the results of your filter, displayed in the list. To save a filter, click Save. A new field
will appear where you can name your filter. After naming the filter, click the Save button to the right
of the name field. The new filter will be available by selecting Filters from the list context menu.
Filter conditions applied to the list are summarized in the breadcrumbs, shown in blue letters across
the top of the list. Not only do the breadcrumbs provide an “at-a-glance” view of the filter’s
conditions, but you can modify conditions and add to your favorites directly from the breadcrumbs .
Filter operators will change depending on field data type. Example field operators include:
• Text value: is, is not, contains, is one of, starts with, ends with
• Numeric: is, is not, greater than, less than, greater than or is, less than or is
• Date: on, before, after, between, is more than, is less than
ServiceNow Fundamentals 39
© 2019 ServiceNow, Inc. All Rights Reserved.
List Editing
The List Editor allows a field value to
be edited in a list without opening the
record
1
Locate a record with the field value to
change:
1. Double-click in an empty area of
the field
3
2. Enter the appropriate value(s)
3. Save the record by clicking the 2
save icon
– Clicking the cancel icon or pressing the
Escape key retains the original value
Users can edit data in lists using various methods but certain field types cannot be edited.
Additionally, list editing is disabled for some tables.
The list editor is the quickest method to update a field on multiple records.
Procedure
1. Select the records to be edited.
2. Open the list editor by double-clicking (or clicking, depending on setup) in an empty area of
the field. The number of selected rows that will be edited is indicated. If any rows cannot be
edited due to security constraints, that is indicated. Administrators can configure the list
editor and by default, list editing is disabled for some tables.
3. Enter the appropriate values and click the save icon.
Quick edit functions may also be used to edit records. Right-click a field and select the appropriate
function:
• Assign to me: For records that use assignments, places the logged-in user's name into the
Assigned to field
• Approve: For records that use approvals, changes the approval state of the record
to Approved
• Reject: For records that use approvals, changes the approval state of the record to Rejected
• Assign tag: For records that are to be tracked based on a user-defined label
ServiceNow Fundamentals 40
© 2019 ServiceNow, Inc. All Rights Reserved.
Tags
Use tags to categorize, flag, and locate records
Use the Viewable by field when editing a tag to control how it is shared: visible only to the owner
(Me), visible to the owner and specific groups or users (Groups and Users), or visible to everyone
(Everyone).
To use the Everyone option under Viewable by, a user must have the admin or tags_admin role.
ServiceNow Fundamentals 41
© 2019 ServiceNow, Inc. All Rights Reserved.
Views
A view is a version of a customized list or form which defines which fields appear
and in what order. Different views can be created and used for different roles.
For list views, the same number of records for that particular table display, but
different fields may be visible and display in a different order.
Views: Views enable users to quickly display the same list or form in multiple ways. System
administrators can create views for lists or forms. For example, different views can be created and
used on Incident for an ESS user, an ITIL user, and a mobile user.
To switch between the different views of columns on a list (as shown here), open the List Context
Menu then select View. Then, select the name of the desired view.
The view name appears in brackets beside the table list title and form record type when a view
other than the Default view is selected.
NOTE: Switching views on a form will attempt to save all changes made to the record. A message
displays asking to save or discard all changes made to the record, before the form reloads and
displays the selected view.
Sort Controls: A list that is displayed to a user for the first time will be sorted by one of the
following:
• The order field, if one is present in the table
• The number field, if one is present in the table
• The name field, if one is present in the table
• The field specified as the display field for the table
ServiceNow Fundamentals 42
© 2019 ServiceNow, Inc. All Rights Reserved.
Views: Layout Configuration (all users)
Configure the List Layout to show or
hide fields from a view and change
the list column order
Slushbucket
Users with the admin or personalize_list role can add or remove columns (fields) from a list or
change the order in which the columns appear in the list for all users.
The slushbucket opens and has two sections: the available items on the left, and the selected items
on the right. Items from the available section can be added to the list and items from the selected
section can be removed from the list.
Once items are in the selected box, you can adjust their order (up or down) on the list.
NOTE: To create a new list view, select New… from the View name choice list on the list
configuration page. Ensure the List view shows the list to be modified.
ServiceNow Fundamentals 43
© 2019 ServiceNow, Inc. All Rights Reserved.
Views: Personalization (logged-in user)
Where the List Layout configuration affects everyone*, the Personalize List modifies the layout of a
list for an individual user. It does not affect the platform default.
*except individuals using personalized layouts for the view created using Personalize list
ServiceNow Fundamentals 44
© 2019 ServiceNow, Inc. All Rights Reserved.
Finding Information
Find information quickly in ServiceNow with Wildcard Syntax Search Type
any of the available search functions:
• Wildcards *searchTerm contains
Wildcards use a symbol to represent zero or more characters and are available for searches. Various
wildcards can be used to refine the search in lists (text searches of all fields), the global text search,
and the Knowledge Base. Results with using wildcards may vary depending on the search method
used.
Searches are not case sensitive. Use advanced options for more specific queries.
ServiceNow Fundamentals 45
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab 1.2:
Lists and Filters
ServiceNow Fundamentals 46
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab
Lists and Filters 1.2
15-20m
Lab Objectives
You will achieve the following objectives:
• Create a new Infinity list view on the Incident table
• Apply and save a filter on a list of records
• Locate and update incident records using inline editing
Scenario
One goal of Cloud Dimensions with using ServiceNow is handling Infinity support.
Before the product is launched, however, Cloud Dimensions employees are actively testing
Infinity devices.
Winnie Reich – manager of the Service Desk – has requested help from the Cloud Dimensions
system administrator in creating a new Infinity view on the incident table.
This view will be configured to include the necessary fields for supporting Infinity, for both
internal and external users alike.
Winnie has also asked her direct report, Kevin Edd, to create and share a list filter that will
filter active incidents and display only those submitted by Infinity employee testers.
ServiceNow Fundamentals 47
© 2019 ServiceNow, Inc. All Rights Reserved.
3. From the list column header, open the “slushbucket” to create a new list view:
b) Select Configure
Note: Selecting any field will work, but Number was used in this example.
4. Beneath the Available and Selected buckets, open the View name drop-down menu
from the List view section.
Note: Choosing an existing view from this list will allow you to modify it.
ServiceNow Fundamentals 48
© 2019 ServiceNow, Inc. All Rights Reserved.
7. Click OK.
Nothing appears to have happened to the page, but you should now notice Infinity
as the selected List view:
8. Working with the Available and Selected buckets, use the Add and Remove buttons
(“>” and “<” icons, respectively) to create the Infinity list view with the following
fields:
Number
Priority
State
Caller
Category
Subcategory
Short description
Assignment group
Assigned to
Tags
Updated
Note: Ensure the fields are listed in this same order under Selected, as seen above. Use the
Move up and Move down arrows, on the right of Selected, to set the correct order.
TIP: You may select multiple fields under Available or Selected, then add or remove them with
one click.
9. Once the fields have been added to the Selected bucket, click the Save button.
10. Impersonate Kevin Edd to confirm the view is available for the Service Desk group.
ServiceNow Fundamentals 49
© 2019 ServiceNow, Inc. All Rights Reserved.
12. Open the List Context Menu and select View, then finally select Infinity:
Note: The list view name now appears at the top of the list in square brackets:
13. Confirm the fields appear in order, from left to right, as listed in step 8 above.
1. Open the filter condition builder by selecting the Show / hide filter icon (funnel):
Tags | EIT
Note: This will search for all active incident records with EIT as one of its tags. The EIT tag is
something Cloud Dimensions employees have created to help distinguish internal testing
incidents from customer incidents – it stands for Employee Infinity Testing.
ServiceNow Fundamentals 50
© 2019 ServiceNow, Inc. All Rights Reserved.
The filter should look like this:
4. Open the filter condition builder again to save the filter for later use.
5. Click Save…
Note: The ability to select a group to share with others is provided by additional user
permissions. For this exercise, the Service Desk group was granted the filter_group role.
8. Input Service Desk into the group reference field to share this filter with its
members.
9. Click Save:
10. Impersonate Megan Burke, another member of the Service Desk group, to confirm
the filter is now available for the Service Desk group.
ServiceNow Fundamentals 51
© 2019 ServiceNow, Inc. All Rights Reserved.
12. Open the List Context Menu and select Filters, then finally select Infinity Testing:
INC0000061 was submitted by Alissa Mountjoy and will need to be updated to include the EIT
tag as the incident reports an error found with the Infinity holographic settings page.
1. As Megan Burke, using methods of your choice, locate and open Alissa’s incident
record: INC0000061.
2. With the INC0000061 record displayed, open More options from the form header:
ServiceNow Fundamentals 52
© 2019 ServiceNow, Inc. All Rights Reserved.
3. Click Add Tag.
5. Press Enter on your keyboard to add the tag to the incident record:
Note: By updating the record, you should return to the filtered incident list. If not, navigate to
Incident > Open and then apply the Infinity Testing filter.
Use the inline editor to update a record’s category value right from the list.
ServiceNow Fundamentals 53
© 2019 ServiceNow, Inc. All Rights Reserved.
3. Click the Save icon (green checkmark) to update the record:
4. Select multiple records to update field values with one set of steps:
b) Hold Shift + Ctrl (Shift + Command on Mac) and click the Inquiry / Help category
for INC0000023
5. Double-click on the Inquiry / Help category value for INC0000023 to open the
Category drop-down.
ServiceNow Fundamentals 54
© 2019 ServiceNow, Inc. All Rights Reserved.
8. Save to update both records.
ServiceNow Fundamentals 55
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab Verification
Infinity Incident List View
Now you can create list views to provide the information you need
in an order that makes it easiest to use!
ServiceNow Fundamentals 56
© 2019 ServiceNow, Inc. All Rights Reserved.
Knowledge Check
ServiceNow Fundamentals 57
© 2019 ServiceNow, Inc. All Rights Reserved.
Section 1.3:
Form Configuration
User Story
ServiceNow Fundamentals 58
© 2019 ServiceNow, Inc. All Rights Reserved.
Viewing Single Records: Forms
A form displays fields from one record – users can view and edit the record data
A form displays information from one record in a table. The specific information depends on the
type of record displayed. Users can view and edit records in forms. Administrators can configure
what appears on forms.
In addition to fields, the form can also contain sections and Related Lists. Related Lists show records
in tables that have a relationship to the current record. For example, the User form features Roles
and Groups Related Lists. Related Lists do not appear on a form until a record has been saved to the
database.
A form can load directly by searching on a record number in the Global Text Search or by clicking a
record in a list.
ServiceNow Fundamentals 59
© 2019 ServiceNow, Inc. All Rights Reserved.
Header Icons
1 2 3 4 5 7
6
1. Form Context Menu: Options related to viewing and filtering form data
2. Add or remove files with Manage Attachments
3. Show the Activity Stream for a real time, sequential display of record activities
4. Personalize form: show/hide fields on the form for the selected view
5. Open the More Options menu for additional form tools like templates and tags
6. Form UI actions (e.g. Retire, Update, Delete, Save, etc.)
7. Cycle through records by using Next record and Previous record
Each form has different fields, UI actions, and options specific to the application within which it was
created.
ServiceNow Fundamentals 60
© 2019 ServiceNow, Inc. All Rights Reserved.
Field Types
1. String - Freely populated 4
using letters, numbers,
and special characters 2
2. Reference - Query that 5
displays records from 3
another table
3. Date/Time - Populated 1
with the day and time of
day
4. Choice - Drop-down menu
with multiple values
5. True/False - Boolean field
that appears as a
checkbox
ServiceNow Fundamentals 61
© 2019 ServiceNow, Inc. All Rights Reserved.
Formatters
Formatter Formatter Examples
A formatter is an element used to display Some Formatters included in the base
information that is not a field in the record platform are:
• Activity
• Process
• Parent breadcrumbs
• Approval summarizer
• CI relations
The activity formatter provides an easy way to track items not saved with a field in the record, for
example, journal fields like comments and work notes
ServiceNow Fundamentals 62
© 2019 ServiceNow, Inc. All Rights Reserved.
Form Designer
Quickly create new or change existing form layouts
• Change the order/location of fields on a form for
different form views
• Add fields to appear on the form
• Configure field properties
Warning: It is not recommended to add the same field to more than one section of a form unless
the field displays read-only data. Having two or more instances of an editable field can cause data
loss and prevent the proper functioning of UI and data policies.
ServiceNow Fundamentals 63
© 2019 ServiceNow, Inc. All Rights Reserved.
Form Design Interface
Page Header
Field Navigator
Form Layout
Fields can be dragged and dropped to different locations on the form and new fields can be added
to the form by dragging and dropping from the Fields tab or the Field Types tab.
Documentation regarding the form designer can be found by searching ServiceNow’s product
documentation (docs.servicenow.com) for the article titled Using the form designer.
ServiceNow Fundamentals 64
© 2019 ServiceNow, Inc. All Rights Reserved.
Form Designer: Sections
*By default, the first section on the form is read-only. That is, the label cannot be changed (contains
the name of the table) and the section cannot be removed.
ServiceNow Fundamentals 65
© 2019 ServiceNow, Inc. All Rights Reserved.
Form Designer: Fields
Cell components:
• Handle icon: use for moving the field to a different location on the form
• Field label: read-only to identify the field
• Settings icon: use to modify the field settings (label, mandatory, read only, reference,
choices, etc.)
• Remove icon: use to remove the field from the form (not from the table)
ServiceNow Fundamentals 66
© 2019 ServiceNow, Inc. All Rights Reserved.
Related Lists
Related lists show records in tables that have a relationship to the current
record. Related lists are presented as tabs at the bottom of the form view.
ServiceNow Fundamentals 67
© 2019 ServiceNow, Inc. All Rights Reserved.
Form Configuration: Related Lists
Using the slushbucket, related lists can be added, removed, or moved on the form view.
• To add a related list to the form, locate the list item in the Available column and double-click
the list item to move it to the Selected column.
• To remove a related list from the form, locate the list item in the Selected column, then
double-click the list item to move it to the Available column.
• To change the display order for the related lists, click on the list item in the Selected field,
then use the arrows at the right to move the item up or down in the list. Top to bottom in
the Selected column corresponds to tabs being shown left to right in the related lists section
of the form.
NOTE: Ensure the View name is correct for the form you are modifying.
ServiceNow Fundamentals 68
© 2019 ServiceNow, Inc. All Rights Reserved.
Templates
Templates allow fields to be populated
automatically, simplifying the process of
submitting new records
To use a template, populate the most-used fields for a specific table, save it as a template, and then
make the template accessible to users. Users can manually apply a template when creating records,
or an administrator can define scripts to apply templates automatically. Fields updated by the
application of a template will have a checkmark icon next to the field label.
Create templates for the forms that are used frequently, such as incident, problem, and change.
There is no limit to the number of templates that a user can create or access, but having many
templates for each form makes the templates more complex to manage.
NOTE: Template creation should be restricted to select groups as it can be used to by-pass process,
like mandatory fields, UI policies, etc. This is especially important for any record using condition
based workflows.
ServiceNow Fundamentals 69
© 2019 ServiceNow, Inc. All Rights Reserved.
Saving Forms
Save records by using one of the following methods:
Changes
Click Update to save changes on
Made
an existing record and return to
the previously viewed page
When a form is saved, all the text in the Work Notes field is recorded to the Activity Log field. Work
Notes and Additional Comments are fields that share information with various users associated
with certain record types.
Additional Comments are visible to all users accessing the record, whereas Work Notes are visible
to only users with the itil role.
NOTE: If you make changes to an existing record and then attempt to leave the form (whether using
web browser controls such as the ‘Back’ button, or through the ServiceNow user interface), you will
be prompted with a message asking if you are sure you want to leave the record without saving.
Once enabled, select the Form Context menu icon in the header bar then select Insert or Insert and
Stay to save a new record to the database instead of updating the current item. Insert will exit the
form returning to the previously viewed page, but Insert and Stay will remain on the form.
There is no ”Save As” in ServiceNow but Insert closely emulates this functionality.
ServiceNow Fundamentals 70
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab 1.3:
Form Configuration
ServiceNow Fundamentals 71
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab
Form Configuration 1.3
615-20m
Lab Objectives
You will achieve the following objectives:
• Create and configure a new form view using the Form Designer
• Create and update Infinity incident records
Scenario
Internal employee testing of Infinity has proven worthwhile for a number of reasons.
Winnie Reich will lead an initiative to further improve and organize Infinity testing support by
creating a form view on the incident table that contains the appropriate fields for accurately
identifying reported issues.
2. NOTE: Winnie is inheriting the personalize role from a group that she belongs to,
which allows her to configure forms and create new views.
ServiceNow Fundamentals 72
© 2019 ServiceNow, Inc. All Rights Reserved.
5. Open the Form Context Menu and select Configure, then finally select Form Layout:
6. Find and highlight the Location field under the Available list:
ServiceNow Fundamentals 73
© 2019 ServiceNow, Inc. All Rights Reserved.
7. Click the Add button (>) between the Available and Selected list:
Note: Doing this adds the Location field to the bottom of the Selected list.
8. Use the Move up button (^) to move the Location field under Configuration item.
9. From the Configuring incident form page, click Save to return to the incident form.
1. Open the Form Context Menu and select Configure, and then Form Design.
The Form Designer will open in a new tab or window. Go to the page that looks like
this:
At the top left of the page are two drop-down menus in the header; the menu on
the left indicates the table the form view is associated with, and the menu on the
right includes the various views defined for the selected table.
ServiceNow Fundamentals 74
© 2019 ServiceNow, Inc. All Rights Reserved.
2. Open the view (right) menu and select New… at the bottom of the list.
4. Click OK.
Notice the new view is automatically selected in the view menu on the page’s
header:
5. On the Fields tab of the Field Navigator on the left, scroll down to locate the Created
by field.
ServiceNow Fundamentals 75
© 2019 ServiceNow, Inc. All Rights Reserved.
7. Repeat these steps to add the Updated and Updated by fields to the form layout,
within the Incident section.
8. Find the Business service field on the form layout, then click the Remove field
Business service icon to remove it from the view:
Note: The gear icon name changes based on the field. In this example, the tooltip text
shows Remove field Business Service when hovering over the gear icon. For the caller
field, the tooltip text shows Remove field Caller.
Removing a field returns it to the Fields tab of the Field Navigator, so it may be re-
added to the form if desired.
9. Click and drag the Contact type field to be displayed beneath the Number field:
10. Repeat this step to reorganize the fields in the Incident section to match this layout:
ServiceNow Fundamentals 76
© 2019 ServiceNow, Inc. All Rights Reserved.
C. Define a New Field
1. From the Field Navigator, click the Field Types tab to add a new field to the form
layout:
3. Add the field to the form layout under the Caller field:
4. Click the Edit field New True/False icon to configure the field’s properties.
Label: Employee
Name: u_employee
Note: The name features the prefix u_ to indicate it is a user-created item. This is a common
naming convention used throughout ServiceNow.
7. Click the Save action from the page header to save the form view:
8. Close the Form Design tab/window and return to the ServiceNow lab instance.
ServiceNow Fundamentals 77
© 2019 ServiceNow, Inc. All Rights Reserved.
9. Use the Form Context Menu to reload the form (Reload form).
10. Now open the Form Context Menu and select View, then finally select Infinity to
display the form as designed!
Additionally, Kevin Edd has received a new incident from Buster Wubbel in person. Submit a
new incident to capture the details provided by Buster Wubbel.
3. Apply the Infinity form view and fill in the fields as follows:
Note: The Location field should have populated automatically because of the Caller value
inputted.
8. Update.
9. If the active incidents list does not display, navigate to Incident > Open.
ServiceNow Fundamentals 78
© 2019 ServiceNow, Inc. All Rights Reserved.
10. Apply the Infinity Testing filter.
There are now four total open Infinity employee testing incident records:
Challenge: Update records to change the state, assignment group, and “Employee”
checkbox values.
As Kevin Edd, use the strategies of your choice to update the following records:
NOTE: If required, set the value for the On hold reason and Additional Comments (Customer
visible) fields to Awaiting Caller.
ServiceNow Fundamentals 79
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab Verification
Infinity Incident Form View
Well done! You have created a new form view which can be used
by the members of the Service Desk group!
ServiceNow Fundamentals 80
© 2019 ServiceNow, Inc. All Rights Reserved.
Knowledge Check
Which field type displays as a What are the three main components
check box on the form? of the Form Designer?
- True/False - Page Header
- Field Navigator
Which field type displays - Form Layout
information from another table?
- Reference What allows fields to be populated
automatically when applied?
Which tool can be used to change - Template
the layout of the form view for all
users? Which UI action saves information for
- Form Designer a new record and leaves the form?
- Submit
ServiceNow Fundamentals 81
© 2019 ServiceNow, Inc. All Rights Reserved.
Section 1.4: Branding
User Story
ServiceNow Fundamentals 82
© 2019 ServiceNow, Inc. All Rights Reserved.
Instance Personalization
Click the Settings icon from the
banner frame to customize your
instance.
The Settings icon (gear) in the upper-right side of the Banner Frame contains additional settings and
options for personalizing your view of the platform.
NOTE: Users may be limited to what settings they have access to based on their role.
After selecting the Settings icon, the categories on the left (General, Theme, Lists, Forms,
Notifications, and Developer) provide different settings, including:
• General Tab: Compact the user interface optimizes the UI to display more information in the
browser window when this setting is enabled.
• Theme Tab: Select a theme for the user interface. Select the System theme to return to the
default theme.
• Lists Tab: Wrap longer text in list columns allows for long strings to wrap in list columns
instead of appearing as one long line.
• Forms Tab: Form sections and related lists appear in tabs when the Tabbed forms setting is
enabled. Also Related list loading is used to determine when Related Lists load on forms.
• Notifications Tab: Allows you to enable various notification channels, as well as manage
your notification subscriptions.
• Developer Tab: Settings for ServiceNow application developers.
ServiceNow Fundamentals 83
© 2019 ServiceNow, Inc. All Rights Reserved.
Instance Branding
Many branding options are accessible from System Properties > Basic Configuration UI16
ServiceNow Fundamentals 84
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab 1.4: Branding
As a change enablement
specialist,
I want the branding of our
ServiceNow instance to align
with the rest of the
organization
So users see ServiceNow as a
trusted platform and will
more readily adopt the
Time Pages
solution.
5-10m 86-88
ServiceNow Fundamentals 85
© 2019 ServiceNow, Inc. All Rights Reserved.
Lab
Branding the Instance 1.4
65-10m
Lab Objectives
You will achieve the following objectives:
• Use the UI16 module to brand the ServiceNow instance for all users
User Story
As a change enablement specialist, I want the branding of our ServiceNow instance to align
with the rest of the organization so users see ServiceNow as a trusted platform and will more
readily adopt the solution.
ServiceNow Fundamentals 86
© 2019 ServiceNow, Inc. All Rights Reserved.
2. Select the Basic Configuration UI16 module. (System Properties > Basic
Configuration UI16)
Note: Replace <YourFirstName YourLastName> with your own first and last name
Color Applies to
#1d3341 - Header background color
- Navigation header/footer
- Navigation background expanded items
- Navigation selected tab background color
- Navigation unselected tab divider bar color
- Navigation separator color
#f8f6ef - Banner text color
- Module text color for UI16
- Border color for UI16
#388ac7 - Header divider stripe color
- Unselected navigation tab icon and favorite icons color
#2de8e4 - Navigation selected tab divider bar color
- Currently selected Navigation tab icon color for UI16
#293e40 - Background for navigator and sidebars
Note: As you enter values, especially for color fields, changes may or may not display in real-
time. Some changes may not be visible until the form is saved, and the page refreshed.
ServiceNow Fundamentals 87
© 2019 ServiceNow, Inc. All Rights Reserved.
4. When finished, click the Save button.
Lab Verification
Cloud Dimensions System Theme
Note: For demonstration purposes, as well as clarity of these training materials, screen shots in
future labs will use the “Cloud Dimensions” system theme as defined in this lab.
Congratulations!
You have branded the instance to align with the rest of Cloud Dimensions!
ServiceNow Fundamentals 88
© 2019 ServiceNow, Inc. All Rights Reserved.
Knowledge Check
Which icon on the banner frame is What are some reasons for changing
selected to customize an the look and feel of a ServiceNow
individual’s instance? instance?
- System settings (gear icon)
ServiceNow Fundamentals 89
© 2019 ServiceNow, Inc. All Rights Reserved.
ServiceNow Fundamentals 90
© 2019 ServiceNow, Inc. All Rights Reserved.
Module 2: Collaboration
User Interface and Navigation Module Objectives
• Identify common tables that extend the task table
Collaboration
• Name two methods of automatically assigning tasks to users
Database Administration • Discuss the differences between the My Work and the My Groups
Work modules
Self-Service and Automation
• Explain what information is stored in the Activity Stream for a task
Introduction to Development • Understand the difference between events and notifications
• Define how dot-walking is used in notification configuration
Capstone Project
• Demonstrate how to use Connect Chat to collaborate on a task
ServiceNow Fundamentals 91
© 2019 ServiceNow, Inc. All Rights Reserved.
Section 2.1:
Task Management
User Story
ServiceNow Fundamentals 92
© 2019 ServiceNow, Inc. All Rights Reserved.
What is a ServiceNow Task?
Within ServiceNow, all work to be
Tasks done is handled through tasks
ServiceNow
Incident
[incident]
A task record is created from a table
that extends the Task [task] table Problem
[problem]
Work is performed upon a task and it
…
is eventually moved to a closed state Change Request
[change_request]
Tasks are created by users who are requesting the task to be performed, and are then updated as
the task moves along a workflow. Tasks can be assigned to specific users or user groups.
The Task [task] table is one of ServiceNow’s core tables and provides a series of standard fields used
on each of the tables that extend it, such as the Incident [incident] and Problem [problem] tables. In
addition, any table which extends Task can take advantage of task-specific functionality for driving
tasks, including:
• Approvals: Approvals can be generated to a list of Approvers, either manually or
automatically, according to Approval Rules. Approvals can be incorporated into workflows or
can stand alone.
• Assignments: Assignment rules can automatically assign tasks to users or groups, ensuring
that tasks are handled by the most appropriate team members.
• Service Levels: Service level agreements can track the amount of time that a task has been
open, to ensure that tasks are completed within an allotted time.
• Inactivity Monitors: Inactivity monitors ensure that tasks do not fall by the wayside by
notifying users when tasks have been untouched for a predefined period of time.
• Workflow: An administrator can specify a specific workflow process to apply to tasks that
meet certain conditions. After a task is created that meets the conditions, the workflow
applies an automated process to the task. The process is defined in the graphical workflow
editor.
ServiceNow Fundamentals 93
© 2019 ServiceNow, Inc. All Rights Reserved.
Task Assignment
1 2 3
Add Users to Groups Apply Roles to Groups Assign Tasks to Groups
1
Service Desk Service Desk
2
3
4
Service Desk schedule_admin Assign Tasks to Users
itil 1 2
catalog
Users can belong to more than one group, and groups identify a subset of users based on roles.
Every user belonging to a group inherits that group's roles, so the preferred method of role
management is:
• add users to group
• apply roles onto groups
When removing a user from a group, roles inherited by that group are revoked for that user.
Similarly, a group may contain other groups, where a child group inherits all roles owned by its
parent. Users added to child groups gain roles of that child group plus any parent groups.
With groups defined, tasks can be assigned to them and then to single users belonging to that
group. In other words, a task record can be assigned to an assignment group and an assigned user.
ServiceNow Fundamentals 94
© 2019 ServiceNow, Inc. All Rights Reserved.
Task Assignment: Assignment Rules
Assignment rules can automatically set a value in the assigned_to and assignment_group fields of a task record
Conditions defined in the assignment rule determine when the rule will trigger and what values it will set
Create an assignment rule by navigating to the System Policy > Rules > Assignment module.
Additionally, assignment rules can be scripted, giving even more flexibility on the trigger and
outcome.
Assignment lookup rules is another type that can be created by navigating to the System Policy >
Rules > Assignment Lookup Rules module. These rules only apply to incident records and have less
options, compared to the other assignment rules.
ServiceNow Fundamentals 95
© 2019 ServiceNow, Inc. All Rights Reserved.
Task Assignment: Agent Intelligence
Users with the admin or ml_admin role will be able to initiate the setup of Agent Intelligence.
Once activated and defined, Agent Intelligence is truly personalized machine learning tailored to
your data.
For example, when an incident is created, ServiceNow will automatically assign the correct category,
priority and assignment group based on the record’s short description. A requester no longer has to
scroll down multiple lists to choose the most appropriate category. Additionally, the incident created
gets the right attention and SLA it deserves, thus increasing the overall service level satisfaction.
This functionality does require multiple plugins – more information about setup and initial
configuration can be found by searching docs.servicenow.com.
ServiceNow Fundamentals 96
© 2019 ServiceNow, Inc. All Rights Reserved.
Accessing Tasks: My Work / My Groups Work
My Work
The Service Desk application menu
allows you to locate all work assigned List of all active tasks assigned to you,
including:
to your group(s) or to you
• Change Request
• Group Approval
• Incident
• Knowledge Base Submission
• Request
• Security Case
• Visual Task Board Task
There are various features for managing and closing task records.
You can quickly locate all work assigned to your group or to you specifically in ServiceNow, using the
Service Desk application.
When an active task (which might include work such as incidents, problems, changes, and more) is
routed to your group, it can be located under the Service Desk > My Groups Work module. From
there, a group member or manager may assign the task to an individual within the group.
At that point, locate any active task specifically assigned to you under the Service Desk > My Work
module.
ServiceNow Fundamentals 97
© 2019 ServiceNow, Inc. All Rights Reserved.
User Presence
The User Presence feature facilitates synchronous collaboration within one record
See who is online, view their current status, and what they are viewing or editing, all in real -time
Imagine a scenario in which you have a critical issue documented in a Priority 1 record. Multiple
stakeholders may need to view and update the record simultaneously. The User Presence feature
facilities that collaboration, showing you who is viewing the record, displaying the record activity
stream, and even allowing you to customize notifications alerting you to record updates.
The number of active viewers is listed in the form title bar. Click for a list of viewers.
NOTE: If you do not see this icon, you are the only viewer on this record.
Click the Show Activity Stream icon to jump to the record Activity section, which includes the
record history and updates by you and other viewers.
Follow the record to receive notifications when the record is updated. Open Connect to customize
these notification or start a real-time conversation with record viewers and other stakeholders.
ServiceNow Fundamentals 98
© 2019 ServiceNow, Inc. All Rights Reserved.
User Presence: Real-Time Editing
Edit records in real-time and see edits saved by other users, improving collaborative efforts
Real-time editing is an extension of User Presence. It allows you to work with others on the same
record, indicating their state (editing or viewing) as well as what their edits are (shown through the
blue "pulse" icons in this screen capture).
User Presence enables you to work on task records seamlessly with others using entirely different
interfaces or devices to perform tasks. This is achieved when using Visual Task Boards (VTBs),
Connect Chat, Apple Watch, and more.
User Presence is about working with others in real-time - reducing record resolution from days to
mere minutes.
ServiceNow Fundamentals 99
© 2019 ServiceNow, Inc. All Rights Reserved.
Notes Tab: Work Notes and Additional Comments
The Notes tab allows you to document task activities throughout its lifecycle for both an external
and internal audience. Depending on the task record type, additional fields may be available to
accomplish similar outcomes including, but not limited to, the Additional comments field. In the
example seen here, an incident record’s Notes tab is displayed.
1. The Work notes field provides a log to document all the technical and behind-the-scenes
work on a task. Upon saving, Work notes are stored in the record Activity section, where
they can be viewed and added upon by users with permissions to view the record. Fully
documenting work notes is beneficial for Knowledge Management and critical for continuity
in the task management process. Work notes are only visible to fulfillers and are not
available to external users or customers.
2. Use the Additional comments (Customer visible) field to communicate back and forth with
the requester and other stakeholders directly in ServiceNow. For example, you may want to
keep the customer apprised of progress on their record or request additional information.
Upon saving, the additional comments (including the updated information and comments
history) are emailed directly to the requester. When the requester receives an email
notification containing additional comments, they can respond directly to the email and
their feedback will be documented in the Activity log of the record, along with your
additional comments.
NOTE: When responding to an email from ServiceNow, do not change the Subject as it may not
be saved to the correct record.
Who?
The Activity section
located under the Notes
tab provides a complete
history of a record What?
It details:
• Who made an update?
• What was the update?
• When was the update
made?
Selecting the filter (funnel) When?
icon allows activity
information to be filtered
From creation through to closure, the entire history of an incident record is automatically tracked
and recorded in the incident Activity section, located within the Notes tab.
The Activity section, which is read-only, documents when a change was made and by whom. These
changes include assignment and reassignment, additional comments and work notes, updated field
values, state changes, and more.
The funnel icon in the top-right of the Activity section allows you to filter your view to see only your
desired categories of information.
3
2
Just like real-time editing on a form, inline commenting on the activity stream means you can
annotate active records as updates are made, allowing multiplied efforts across several pieces of
work simultaneously.
A benefit of activity stream inline editing is that you are able to update multiple active records
without having to open a single record.
Quick Panel
Transform your lists and forms
into an interactive graphical Lanes
experience using Visual Task
Boards (VTBs)
Cards
Visual Task Boards allow you to:
• Manage your tasks through a
visual, drag-and-drop interface
• Identify process bottlenecks at
a glance, in real-time
• Track embedded activity screens
to view updates all in one place
Use Visual Task Boards (VTBs) to create a personal to-do list, collaborate in real-time with group
members on assignments, and more. Displayed graphically as lanes and cards, VTBs provide a
landing page to view and organize work in ServiceNow.
To get started with a Visual Task Board, navigate to Self-Service > Visual Task Boards and follow the
displayed instructions for creating a board.
Lab Objectives
You will achieve the following objectives:
• Browse the Service Portal
• Submit an incident from the Service Portal
• Use work notes, comments, and chat to cooperatively manage an incident
User Story
In addition to internal testing, Cloud Dimensions has begun allowing major partners to test
Infinity devices.
Before submitting an incident to report a problem, these partner users have been instructed
to first browse the Knowledge Base in the Cloud Dimensions Service Portal.
If the user is unable to find a solution to their problem, they are instructed to submit an
incident so they can receive support by an agent in the Infinity Customer Support group.
The Infinity Customer Support group has defined processes for incident assignment and
resolution, which uses assignment rules and connect chat to ensure the best help is offered to
an end-user.
1. If you are not using a different browser, log out of your instance.
https://instance-###.lab.service-now.com/sp
5. Type infinity holograph broken into the How can we help? search bar on the home
page; then press enter on your keyboard.
6. Click the ServiceNow logo in the top-left corner to return to the homepage.
Urgency: 3 – Low
Please describe your issue below: The Infinity is having trouble displaying clearly.
4. Click Submit.
You may briefly see a message on the top of the screen indicating your incident was
created and your profile badge should show one Request.
Note: If you opted to use another browser for these steps, return to the original session and
move to step 1 of the Update the Incident section below. Otherwise, continue on to the next
step.
6. From your instance URL, remove the /sp suffix (including everything that follows).
Note: If you experience issues with the interface caching, refresh the browser and click on the
ServiceNow logo.
Note: Rita is a Customer Support Agent on the Infinity Customer Support group specializing in
software-related issues.
Note: The incident was automatically assigned to Rita’s group (Infinity Customer Support)
by an existing assignment rule created for the purpose of this exercise.
4. Locate and open the most recently created incident record and update the following:
State: In Progress
Assigned to: Rita Center
Note: Assume Rita has remotely accessed Jon’s device and found no apparent issues.
6. Update the incident record to inform Jon that it must be escalated to another team:
a) From the Notes tab, type into the Work notes field: Hello Jon, I was not able to
find anything on my end, but this incident will be escalated appropriately.
Note: Confirm the Work notes field label changed to Additional comments (Customer
visible before posting.
Category: Hardware
Assigned to: Trey Tout
Note: Rita will now receive notices when any new comments or work notes are added.
Additionally, Rita can now use chat to facilitate the resolution of this incident with peers.
11. Open the Connect Sidebar to locate the conversation around the incident:
12. Select the “Infinity is having trouble” conversation from the Connect Sidebar to
open a chat window.
14. With Trey added to the conversation, type the following message into the Worknote
text field at the bottom of the chat window:
Hello Trey, I thought you could help with this as there are no software issues
detected. Thanks!
Note: Trey is an Engineer on the Infinity Customer Support group. If you are unable to find his
name while impersonating Rita, switch back to System Administrator before impersonating
again.
4. Open the incident by clicking on the View Document icon on the chat window
header.
5. If open, close the chat window and collapse the Connect Sidebar.
6. With the record open, under the Notes tab, click the Show all journal fields icon to
the right of Work notes:
Note: The Show all journal fields displays both Work notes and Additional comments, making it
easy to add both internal and external comments to the record.
7. Update the Work notes with the following: Not enough information provided,
contacting the customer to request more.
8. Update the Additional comments (Customer visible) field to say the following:
Hello Jon, I have been added to help resolve your issue. Could you please provide
additional information about what you are experiencing? Thank you.
9. Click the Post button to add the Work notes and Additional comments to the
incident activity stream.
12. Notice the Connect Sidebar icon has changed, indicating two new messages have
been received:
Note: Although the incident was not resolved at this time, Jon will be able to respond to Trey’s
inquiry and provide more information to identify a solution.
Review the updates made to the Activity section, recognizing internal (work notes) and
external (additional comments) communication:
You’ve learned how easy it is to submit an incident from the Service Portal, locate the
incident in ServiceNow, and collaborate using Connect Chat to resolve the incident!
Which module displays a list of tasks Which tab contains the activity
assigned to a user’s group, but not stream for a task?
yet assigned to an individual? – Notes
– My Groups Work
User Story
Events Notifications
An event is an indication that certain conditions Email notifications can be triggered by events and
have occurred in the system, which are then require no scripting knowledge
responded to with pre-defined actions
All baseline events have built-in logic to respond when an event occurs. Possible responses include
making a change to a record in the database, creating a new record, sending a notification, or
logging a message.
The event definitions are in the Event Registration [sysevent_register] table. The Event Log displays
records from the Event [sysevent] table. To see a log of every generated event navigate to System
Policy > Events > Event Log.
By convention, events are named using the syntax <table name>.<unique event name>. For
example, incident.updated, or problem.closed.
A notification is a tool for alerting users when events that concern them have occurred through the
following methods:
• Email
• SMS
• Meeting Invitation
Notifications are received by configured users and voluntary recipients and can notify of specific
activities in the platform, such as updates to incidents or change requests.
1 2 3
Choose When to Send Choose Who will Receive Choose What it Says
Notifications can be sent when a record is Inserted or Updated (or both) into a table, only if the
specified conditions are met.
Send notifications to specific users and/or groups. If you address the Notification to a user with an
inactive record in the User [sys_user] table, the system does not send the notification to that user.
TIP: Consider limiting the recipient list of any notification to 1000 users. By default, if a notification
has more than 100 intended recipients, the system creates multiple notification messages with up
to 100 recipients each. If you want to change the recipient limit, set the system
property glide.email.smtp.max_recipients.
If using an Email Template then Subject and Message will be used from the template unless
overridden with a different (new) subject and/or message.
The recipients of this notification include the user who is experiencing an issue and the user that is
assigned to resolve the incident. In the base system, this is easily achievable because the fields
representing these users are a part of the incident record by default (Caller and Assigned to,
respectivey).
A variation of this could include sending the notification to the caller’s manager as well, but this
would require dot-walking because the Manager field (and value) is not found on the incident table.
To achieve this while defining a notification, dot-walk through the Caller field to the User table. This
is possible because the value stored in the Caller field is simply a user record, referencing data
stored on the User table. After dot-walking to the User table, all of this table’s fields (and their
stored data) is accessible, including the Manager field.
In the example illustrated above, the caller of an incident is David Loo. David’s manager, Bud
Richman, is also able to receive the notification because of dot-walking.
Another benefit to using dot-walking is that notifications do not rely on hardcoded data – instead,
the values are automatically populated based on the fields selected. In other words, this notification
will automatically identify the caller and the caller’s manager (if applicable) based on the
information provided within the incident.
Subscriptions
Subscriptions allow users to be informed of
various activity occurring in the platform,
whether it directly relates to them or not
The Notifications page of Settings is where users can define notification channels (methods of
receiving notifications), as well as manage their subscriptions to system notifications.
SMS (Short Messaging Service) is the standard protocol used to deliver short text messages to
mobile devices. Most mobile phones support SMS, even if they do not support more sophisticated
messaging, like email notifications.
Notifications to SMS devices are particularly useful when critical events require immediate
attention, and waiting for an email notification to be accessed and viewed is too slow.
Chat
Connect Chat is a messaging
tool that lets you work with
others in real-time
Workspace
The Connect Workspace
provides a full-screen view
of all your Connect Chat
conversations in one place
ServiceNow provides several tools to help you communicate with your team in real-time, based on
information within the platform. Connect Chat is accessible from the Connect icon in the Banner
Frame (opens a sidebar within the Content Frame). You can create new conversations with
individual ServiceNow users or create custom chat groups. A green dot indicates participants who
are currently online. Additional options allow you to add attachments to the chat, customize your
notifications to stay in the loop on the conversation, and easily view and update related records.
The Connect Workspace provides a full-screen view of all your Connect Chat and Connect Support
conversations in one place, plus additional tools to help keep track of important information in
conversations. To open the Connect Workspace, navigate to Connect > Connect Chat or click the
Open Connect standalone interface icon from the Connect Sidebar. If you do not have any recent
conversations, a screen appears with helpful information about Connect.
Lab Objectives
You will achieve the following objectives:
• Develop a new email notification
• Test the notification
Scenario
Buster Wubbel – manager of Infinity Security – has requested that a notification be created to
alert him and his team whenever a critical employee Infinity incident is active and categorized
with Security. Additionally, the notification should alert any manager of the assigned group,
seeing as the incident as urgent.
A. Develop a Notification
We will assume Buster Wubbel has shared the notification requirements with the system
administrator – whom which you will impersonate to create the new notification.
3. New.
4. After the new notification record loads, open the More options menu from the form
header, then select Toggle annotations on / off.
Note: This notification will be defined to inform the Infinity Security group and the assignment
group’s manager whenever a critical (Priority 1) employee Infinity security incident is active as a
result of being created or updated.
Inserted: [checked]
Updated: [checked]
Conditions:
Active | is | true AND
Priority | is | 1 – Critical AND
Category | is | Security AND
Short description | contains | infinity
OR Short description | contains | Infinity
Note: The Security category choice was previously defined for this exercise.
Note: Instead of selecting a user by name, thus hardcoding that particular user to the
notification, select a field that contains the data of a user account. Doing so will require dot-
walking tables.
10. Select Assignment group (+) under the Available bucket and click the (+) to expand.
Note: The (+) icon indicates a field is a reference field, which can then be used to dot-walk from
one table to another.
Note: This adds Assignment group.Manager to the Selected bucket or, in other words, the
notification will be sent to the manager of the incident’s assignment group.
13. Click the Edit Groups icon (closed lock) on the Groups field:
a) From Select variables, expand the Fields list by clicking the + icon
c) Highlight ${number} from the Message HTML field, then copy the text to your
clipboard
d) Click your cursor into the Subject field at the end of the text
Note: The ${number} placeholder is added to the end of the subject text and is dynamic,
meaning it will automatically populate with the incident number value of the record that
18. Update the Message HTML field to include the following text, replacing any existing
text:
Critical Incident ${URI_REF} has been created with an Infinity Security category.
Note: The ${URI_REF} placeholder includes an upper-case “i” after the “UR” text. Check to see
how this placeholder behaves after the notification is generated.
Note: Because email is disabled on the instance, impersonate System Administrator to check
the instance’s email logs.
7. Locate the record with the Subject IMPORTANT! P1 Infinity Security Incident
Created INC#######, then click on the Created timestamp to open the record.
Note: The ${URI_REF} placeholder renders as a direct link to the incident record.
LAB VERIFICATION
Outbox: Infinity Security P1 Notification
Recipient List
Great work! You have successfully created and tested a new email notification.
User Story
Reports can be visually represented in many different ways, including bar charts, pie charts, dials,
lists, pivot tables, donuts, and more. Reports can be run manually or scheduled to be run
automatically. There are a range of predefined reports that pertain to applications and features like
Incident Management and Service Catalog requests, including Key Performance Indicator (KPI)
reports.
ServiceNow reports are interactive. Users with access can drill down into the report gauges to view
and manipulate the underlying data.
If none of the predefined reports meet your needs, you can create your own reports by navigating to
the Reports > View / Run module. Alternatively, you can simply click most column context menus in
any list to generate a report directly from the data in that list.
The ServiceNow base instance comes with over 25 standard report types,
including:
Other report types include: Speedometer, Dial, Single Score, Pie, Semi Donut, Bubble, Multi-Level
Pivot Table, Line, Column, Area, Spline, Bar, Histogram, Horizontal Bar, List, Funnel, Calendar,
Pyramid, Box, Trend, Control, Trendbox, Map, Pivot Table, and Text Analytics.
One report variation, a Pareto chart, named after Vilfredo Pareto, is a type of chart that contains
both bars and a line graph, where individual values are represented in descending order by bars, and
the cumulative total is represented by the line. Pareto Charts are useful to show the significance of
factors for a given question/process. Pareto Charts use the rule that about 20% of input produces
almost 80% of the outputs.
You can build reports from scratch, but it is often easier to start with a filtered list or an existing
report. When you start with an existing report, reporting configuration choices will be provided for
you. By modifying the provided options, you can configure the report to meet your needs. It is a
best practice to copy a base report then edit your copy.
The Reports > View / Run module contains a library of reports which you can run and use to create
your own custom reports. Many of these reports came with the platform and others were created
by your reporting administrators specifically for your company.
The Reports page contains different sections for reports which are visible to different audiences.
NOTE: Every time you make an adjustment through these controls, remember to click the Run
button in the top-right to redraw the report with your changes.
Report actions become available once the report has been saved and they depend on your role.
Many of the actions are easily understood; therefore only some of them are detailed here:
• Update: Overwrite report, return to the report list
• Insert: Save a duplicate copy of the report, return to the report list
• Insert and Stay: Save a duplicate copy of the report, remaining on the report
• Save as report source: Allows you to create a pre-defined data set that can be used for
creating reports
Share Publish
To make a report visible to a Steps to publish and view a report:
particular group or user, use
the Share option to select 1. With desired report displayed click the
Groups and/or Users Sharing menu icon, then click Publish
2. Click the Copy report link icon from the
report header to copy the URL to your
clipboard
3. Open URL in browser
When distributing a report, sharing has the ability to make the report visible to authenticated users
within ServiceNow.
For more information on options available under the sharing menu in Report Designer, please refer
to the ServiceNow product documentation by searching for the article titled: Share a report -
Report Designer.
System tables are, by default, restricted from the reporting module. These tables include, but are
not limited to the following: syslog, syslog_transaction, sys_attachment, and sys_email.
Compared to reports, metrics are used to measure and evaluate the effectiveness of IT service
management processes. A metric could measure the effectiveness of the incident resolution process
by calculating how long it takes to resolve an incident.
Sometimes a metric can be easily obtained from the data. For example, to find the number of
incidents that were created today, a report will count the number of incident records in the Incident
table with a created date of today. Other times, metrics need to be gathered as data is updated. For
example, determining how long an incident was assigned to a certain group requires collecting
information about assignment changes and calculating the duration of each assignment.
The Metric Definition plugin provides a declarative way of defining metrics, and, once defined, the
data for the metric is gathered, and occurrences of the metric are calculated and stored.
Dashboards enable
you to display multiple
Performance Analytics,
reporting, and other
widgets on a single screen.
NOTE: There is a lot you can do with dashboards so it is encouraged that you to find more
information at the ServiceNow product documentation site.
Lab Objectives
You will achieve the following objectives:
• Create a report for a group
• Share the report to a group
Scenario
Members of the Service Desk would like a report built which provides a high-level summary of
all incidents assigned to their group, organized by incident category and priority.
Winnie Reich will create a report and then have the system administrator share it to her team.
A. Create a Report
1. Impersonate Winnie Reich.
Note: Although the first part of the lab is completed as Winne Reich, any user with the correct
role can access the Reports application menu and modules to create and share reports.
4. Use the search bar at the top-right to search for reports containing incidents by
priority in their title.
Note: Your report may look different than the screenshot provided.
7. Select the Data breadcrumb title from the panel on the left, then update the name
of the report to Incidents by Priority and State (Service Desk):
10. From the Report Designer header, click the Run button:
3. Locate and open the record for the Incidents by Priority and State (Service Desk)
report.
6. Select Share.
7. Choose Groups and Users, then add the Service Desk to the Groups list:
Lab Verification
Access Report from Group Category
Note: The Infinity report is now available to all users in the Service Desk group.
Wonderful! In this lab you have learned how to modify an existing report and share it.
Which module opens the Report What are the four tabs used to guide
Designer interface? the user through creating a new
– Reports > View / Run report in the report designer?
– Data, Type, Configure, and Style
User Story
Data in ServiceNow is stored and managed according to a database structure that administrators
can view and configure:
• Tables are a data structure or database component, which contain records
• Records are the data stored on tables, which contain fields
• Fields are individual pieces of data within a record
The System Dictionary contains the definition for each and every table and field in the database.
Navigate to System Definition > Dictionary to access the system dictionary to modify table and field
attributes.
Tables can be accessed using the following modules within the System Definition application:
• Dictionary - defines every table and field in the system. Table records are identified as a
Collection type.
• Tables & Columns - lists existing tables in the database. Selecting a table name will display its
contents.
• Tables - contains a record for each table in the database. Custom tables can be created when
the New button is selected.
Lists and forms provide a friendly user interface (UI) for managing tables, records, and fields.
Fields
Each field corresponds to a column In this case, one element such as
in a table and represents individual the user ’s name or email address
pieces of data in a record
Record numbers are automatically incremented, and the number format per table in the system can
be changed by visiting the System Definition > Number Maintenance application.
For example, the default problem record number prefix is “PRB” but can be redefined as “PRBLM.”
Fields are available in a variety of different types, including: Choice, Date/Time, Journal, Reference,
and more. Field types define how a field is interacted with through the interface, as well as the type
and format of data it can store.
In addition to the System Dictionary, use the System Definition > Tables & Columns module to view
the field settings and attributes for a table.
Examples of a field label seen above includes User ID, Full Name, and Location
The name is a unique term that does not always match a field’s label.
For example, the name attribute of the Location field on the User table is sys_user.location. Do not
confuse the name attribute with the Name field on the user table, which is a label. The name
attribute of the Name field on the User table is sys_user.name.
NOTE: The Name field is a combination of the First name and Last name fields of the user record.
Values are the actual data, such as this user’s name, Aileen Mottern, or her location, Rome. In some
cases, the value may be empty, or null.
A reference field stores a unique system identifier (known as the sys_id) of a record on another
table which is what establishes the reference relationship. For example, the Caller field on the
Incident table is a reference to a record on the User table.
When you define a reference field, the platform creates a relationship between the two tables.
Adding a reference field to a form makes the other fields in the referenced table available to the
form.
Administrators can create new reference fields and configure several options for reference fields.
NOTE: A reference field can refer only to records from one other table. To add a field that can refer
to records on any table in the platform, regardless of a shared reference, use the Document ID
element type.
One-to-Many: Within a table, a field can hold a reference to a record on another table. There are
three one-to-many relationship fields:
1. Reference Fields - Allows a user to select a record on a table defined by the reference field.
Example: Caller field on the Incident table allows a user to select any record on User table.
2. Glide List - Allows a user to select multiple records on a table defined by the glide list.
Example: The Watchlist field on the Incident table allows the user to select any record or
records on the User table.
3. Document ID Fields - Allows a user to select a record on any table in the instance. Example:
Document field on the Translated Text table.
Many-to-Many: Two or more tables can be related in a bi-directional relationship, so that the
related records are visible from both tables in a related list. Example: software vendors can sell
multiple products and products can be sold by multiple vendors.
Database Views: Two tables can be joined virtually using the Database Views Plugin to allow for
reporting on data that might be stored in more than one table. Database Views are read-only. Create
Database Views by navigating to System Definition > Database Views.
Extensions: A table can extend another table. The extended table includes unique fields plus all of
the fields and their properties from the parent table.
In ServiceNow, you can create a new table that stands alone or that extends another table.
The Task table and Configuration table are examples of parent classes that are extended to child
classes.
For example, child tables extended from the Task table include Change Request, Incident, and
Problem. Child tables extended from the Configuration table include Database, Hardware, and
Software.
Extending a table incorporates all of the fields of the original table and allows for unique fields to be
created on the new table. The inheritance of the fields of the original table is used to create
subcategories of data. Examples include the Incident, Problem, and Change Request tables, which
are all subcategories of the Task [task] table.
Using the Dictionary overrides feature provides the ability to define a field on an extended table
differently from the field on the parent table. Examples include overriding the default values, field
dependencies, or read-only status of a field.
Task
The task table is such a table, making
it both a parent and a base class
If a field is on a base parent table such as the Task [task] table, for example, a different label can be
defined for each extended table, such as Incident or Problem. To add a different label for an
extended table, navigate to System Definition > Language File, then create a new entry for the
extended table.
Every child table is a specialization of the previous base table or previous child table. The Task [task]
table provides a series of standard fields used on every table that extends it.
To extend a table, select the table to extend in the Extends Table field on the table record.
NOTE: This option is available only when you are creating a table but not all tables are extensible.
Although custom tables are not in the base system, they can still interact with existing core tables.
For example, a reference field on a custom table can access data stored on a core table. By doing so,
a relationship between the tables is created which makes them related tables. This relationship is
not exclusive between just a custom table and a core table. Related tables can be a combination of
multiple core tables and/or multiple custom tables.
NOTE: When creating a new custom table, the table name is automatically populated based on the
table label and a prefix. If the table is being created in a scoped application, the name is prefixed
with a namespace identifier, indicating that it is a part of an application. Otherwise, custom tables in
the global application feature ”u_” as their prefix, and then the table label.
Relationships can be
filtered by extension or
reference classes by
checking the appropriate
boxes at the top of the
map.
In this example map, you will see the Task table as the focus of the map (highlighted in yellow).
NOTE: The schema map is available to those users with the personalize_dictionary role as well as
those with the admin role.
Tables with blue bars, including Problem and Change Phase, are tables that extend the Task table.
Demonstrated with the Problem table, you can use the Schema Map to identify which columns
(fields) originate on Problem, and which columns are inherited from the Task table. Additionally, you
can see what field type they are.
Tables with red bars, including Location and User, are tables that are referenced by the Task table.
A series of filters at the top of the Schema Map allow you to show/hide tables based on criteria such
as whether they are referenced by the Task table, reference the Task table, are extended by the Task
table, or extend the Task table.
The Tables window on the far right of the screen provides a summary of all the tables presented and
their relationships.
Lab Objectives
You will achieve the following objectives:
• Create a new table
• Configure the table form view
• Update the application menu and create new modules
Scenario
With an active procedure of testing Infinity devices, Cloud Dimensions needs a method for
managing inventory and tracking how many devices have been issued and to whom.
The various teams involved with Infinity testing have come up with a solution but will need the
help of the system administrator to implement it.
Their plan is to have this information accessed through an application menu with a series of
modules.
The primary data point being tracked will be the Infinity devices but information about the
users, such as name and email, will also be available.
Label: Infinity
Name: u_cmdb_ci_hardware_infinity (auto fills with u_infinity)
Extends table: Hardware [cmdb_ci_hardware]
New menu name: Infinity (auto fills)
Note: The Name field automatically populates with u_infinity. The table name can be changed,
as long as it starts with the u_ prefix indicating it is a custom table. It is best practice to rename
the table to indicate it is a custom CMDB CI table.
4. Submit.
Note: During the creation of the Infinity table, the Create module checkbox was selected. As a
result, this automatically created the new module Infinities which is a pluralized form of the
table name, Infinity.
Note: In a future lab, you modify the Infinities list layout before importing device records from
spreadsheets.
4. Open the Form Context Menu, select Configure > Form Layout.
5. Remove the Assigned to, Category and Fault count fields, keeping Name, Asset tag,
Installed, and Status in the Selected list.
6. Add the Owned by and Support group fields to the Selected list from the Available
list.
d) Select Add
You should now see Owned by.Email under the Selected list:
Note: The Owned by.Email field’s value represents the email of the device’s owner, and will
automatically populate when a value is entered into the Owned by field, as long as the user
record includes an email address..
11. After adding the new fields, rearrange the fields under the Selected list to look like
this:
2. Hover your curser over Infinity and click the Edit Application icon (pencil):
Note: You could alternately access this record by navigating to System Definition > Application
Menus and searching for Infinity in the list.
8. Click Update.
11. Click the Link Type* tab and fill out the fields as shown:
Note: The Table field appears to be read-only (indicated by gray) but clicking on the table name
will open the drop-down menu.
13. Submit.
Note: Before creating any table in ServiceNow, the question to always start with is: should the
table be created from scratch or by extending an existing table?
Confirm the Add Inventory form has the correct fields in the correct order.
Which modules can you use to How can you edit the title of an
create a new table? application menu?
– Tables – Click the Edit Application
– Tables & Columns (pencil) icon
– Update the Title field on the
form
What is created by default when you Which tools can be used to create or
create a new table? modify a form layout?
– Application Menu with the same – Configure > Form Layout or
name as the table Label (e.g. – Configure > Form Design
Infinity)
– Module with the plural of the
table Label (e.g. Infinities)
User Story
User
Authentication/ User Interface Database
Login
Groups
Governed by Roles Governed by
Global System
Roles Properties
Governed by
Access Control Rules
ServiceNow provides several levels of security before an end user has the capability to perform
CRUD (Create, Read, Update, Delete) operations on a table:
• User Authentication/Login: Users, Groups, and Roles
• Application and Modules Access: Controlled by roles configured at the Application and
Module level
• Database Access: Access to tables and their records and fields are controlled via globally
defined system properties (deny access is the default behavior) as well as table and field
level access controls
There are three security modules typically used by the System Administrator:
• System Properties > Security
• System Security > Access Control (ACL)
• System Security > High Security Settings
In addition to restricting CRUD operations, Access Control rules can restrict ServiceNow-specific
operations on tables and fields.
Users with the appropriate permissions can modify rules and their definitions
Users with the admin role have special access to all platform features , functions, and data because
admins can override Access Controls and pass all role checks so grant the admin privilege carefully!
With this said, in order for a user to create or update Access Control roles, they must have the
security_admin role.
In this example, a user with the itil role is granted permission to write (update) records in the
change_request table.
No specific field selected - this This rule applies to only one field Wildcard – this rule applies to
rule applies to the whole table on a record and in this case, the every field on a record without a
including all of its records Caller field on an incident record table.field rule
Each Access Control specifies the table or type of record (including fields), operation being secured,
and unique object identifier.
Access Control rules are defined for and applied to a specific table so that the rule is within the
context of the table and the type of data stored.
This processing order ensures that users gain access to more general objects before gaining access
to more specific objects.
• If a user fails a table ACL rule, the user is denied access to all fields in the table, even if the
user passes a field ACL rule.
• If a user passes a table ACL rule, but fails a field ACL rule, the user cannot access the field
described by the field ACL rule.
If there is a matching access control rule, then the system evaluates if the user has the permissions
required to access the object and operation (role, conditions, script). If an access control rule
specifies more than one permission, then the user must meet all permissions to gain access to the
object and operation. Failing any one permission check prevents the user from accessing the
matching object and operation.
If a user does not meet the permissions of the first matching rule, the system evaluates the
permissions of the next matching access control rule as specified by the access control processing
order. If the user fails to meet the permissions of any matching access control rule, the system
denies access to the requested object and operation.
2
To view the Access Controls
associated with a table:
1. Type <table name>.CONFIG
2. Select the Access Controls
tab
Access Controls are automatically created. It is very rare to have a table created with no Access
Controls. In lab 3.1, the table, u_cmdb_ui_hardware_infinity, was created. In addition to the table,
the following were created:
• u_infinity_user role
• Table Access Control Rules
• create
• delete
• read
• write
This image shows the “Default access control on u_cmdb_ci_hardware_infinity” granting create
access to users with the u_infinity_user role.
One of the real benefits of using the wildcard type of rule is to reduce the amount of rules required
to control access, which also results in less required maintenance.
For example, taking the same series of rules above – it could accomplish the same end results
without a wildcard rule. The role definition for the change_request.* rule grants access to all fields
except those with a specific rule (change_request.type in this example)
Without a wildcard rule, six separate rules would be required to control access. That is a significant
more amount of rules to manage, should changes be needed in the future.
Time Pages
So I can ensure the integrity of
15-20m 175-181 the inventory data.
Lab Objectives
You will achieve the following objectives:
• Update a role
• Provide application menu and module access for a specified role
• Create an Access Control rule to grant data permissions
Scenario
After much deliberation, Cloud Dimensions management have decided to limit access to
Infinity device data to only those teams actively supporting the product.
The result is a requirement to restrict access to the Infinity Inventory application menu and
modules, as well as controlling which fields the users can update.
As the system administrator, you will act upon the requirements provided by Cloud
Dimensions management to successfully secure Infinity device data.
Note: This role was automatically created when the Infinity table was added to the database,
along with the creation of four table Access Control rules. All of these are optional during the
table creation process and can be avoided through settings.
4. Type into the Description field: Support role for the Infinity
Note: Two infinity roles now exist which will allow for access provisioning in the future:
2. Use any method to find and open the Infinity Inventory application menu.
4. Click the Edit User Roles icon (pencil) next to the Roles field:
5. Save.
3. Confirm Rita Center cannot access the Infinity Inventory application and its
modules.
Discussion: A module is missing from the application menu. Which one? Why?
Note: Although Kevin Edd has inherited the u_infinity_support role because he is a member of
the Service Desk group, which has access to the Infinity Inventory Application, the role does not
currently have the rights for creating new data.
As a result, the Infinity New record page is blank when Kevin attempts to access it.
Access Control rules can be created to allow users with a certain role access to work with a
table’s data, but first let us update Rita and Kevin’s group permissions so Service Desk and
Infinity Customer Support group members are granted access to the application and all of its
modules.
5. Click Save.
Note: You have added the u_infinity_user role and its permissions under the u_infinity_support
role. This means all users with the u_infinity_support role now automatically inherits the
permissions found with u_infinity_user.
12. Confirm the Infinity Inventory application menu is accessible and its two modules
display.
Note: Both Rita Center and Kevin Edd can now access both of the Infinity Inventory modules.
Additionally, they can now create new records and update existing ones.
5. Click OK.
6. Notice the page refreshes and there is now an unlocked pad icon next to your name
on the User menu:
10. From the Name field, select the drop-down to the right of the selected value,
Infinity [u_cmdb_ci_hardware_infinity].
12. Open the Form Context Menu and select Insert and Stay.
16. Type admin and click the save icon to add the role.
17. Update.
Note: The u_cmdb_ci_hardware_infinity.asset_tag rule was created and added to the Access
Control List.
Note: All fields but Asset tag and Email should be editable. These same fields would also not be
editable for existing records, for all users in Service Desk or Infinity Customer Support groups. As
system administrator, all fields on the form are editable.
With this lab, application and module access was adjusted, and an Access Control rule was
created to limit permissions to table data.
User Story
Import Sets Data Sources Import Set Table Transform Target Table
HTTP /
FTP User
TRANSFORM
- HR Implementers may use Import Sets to EXCEL IM PORT SET Incident
copy a large number of HR Stories into the TABLE
Development instance during CSV
implementation Groups
Import Sets provide a mechanism to pull data into ServiceNow. Import Sets store data in Import Set
tables. Any user logged in with the admin or import_admin role can manage all aspects of Import
Sets.
Data Sources are records in ServiceNow that contain information regarding an Import Set data
source. You can import a file from a local source (i.e. XML, CSV, Excel) or from a network server by
providing a path and authentication information. A data source can come from a file, an LDAP
connection, or a JDBC connection.
The Import Set Table acts as a staging area for records imported from a data source.
Transform Maps provide a guide for moving data from Import Set tables to “Target” tables; field
mapping provides direct field-to-field data moves.
A Transform Map is a set of field maps that determine the relationships between fields in an Import
Set and fields in an existing ServiceNow table (such as Incidents or Users). Once defined, existing
Transform Maps can be reused for mapping data from an Import Set to a ServiceNow table. The
Transform Map Module enables an administrator to define destinations for imported data on any
ServiceNow tables. Transform mapping can be as simple as dragging and dropping to specify linking
between source fields on an Import Set table and destination fields on any ServiceNow table.
The Target Table is an existing table in where the data will be placed, post-transformation.
Before importing any data, it is important to understand what data you are bringing in and where
that data should go.
You should verify the data before you import it since bad data will complicate things later in the
import and transform processes. Extra time spent planning and examining data before import will
save time and potential problems later.
Data should not be imported in extremely large chunks. Creating an extremely large Import Set can
cause extensive delays. The imported file label is used to determine the name for the Import Set
table that data will be loaded into.
NOTE: It is also possible to choose an existing Import Set table to use for loading data from the
same source, or data that has the same field/column designations. When an existing Import Set
table is chosen, the table fields are added when the incoming source of data contains
fields/columns that do not exist.
Transform Map
Transform mapping is flexible; the specification can be as simple as having the application auto-
match field names from source and destination, or mapping can use advanced logic and leverage
the full power of the ServiceNow scripting environment. A single Import Set field can also be
mapped to multiple fields on a target table. Any table is a potential destination for transformation of
an Import Set, and any field within a table can serve as a potential destination for transformation
from a field within an Import Set.
Select the ServiceNow table where you want transformed data to be placed. You can select only
tables within the currently selected application scope, the global scope, or tables that grant write
access to other applications. Name and Source table are set based on the label which was assigned
to the Import Set. It is necessary to assign a target table into which the data can be transferred.
Automatic Mapping Utility: The simplest mapping method is where all of the field names of the
Import Set match the name of the fields on the Target table where the data will be transformed. In
this case, simply click Auto Map Matching Fields in the related list in the Table Transform Maps form
and confirm proper matching. If there are any discrepancies in terms of how fields were
automatically matched, these can easily be corrected using the Mapping Assist utility. When all
fields are matched properly, click Transform in the related links to begin transforming data onto the
destination table.
Mapping Assist Utility : The Mapping Assist utility provides a visually intuitive environment for
specifying mapping between Import Set fields and Target table fields. With the Mapping Assist utility
it is possible to map a single source field (field on an Import Set table) to multiple destination fields
(fields on a Target table).
Coalescing a field (or multiple fields) means the field will be used as a unique
key during imports
There are several possible configurations you can use to coalesce data in Import Sets:
• No coalesce: If no coalesce is defined, all imported rows are treated as new records. No
existing records are updated. If the import is executed again, duplicate records will be
created.
• Single-field coalesce: You can coalesce on a single field to update an existing record. If a
target table record exists with the same value in the coalesce field as the staging table record,
the target table record is updated using the Import Set record values.
• Multiple-field coalesce: You can coalesce on multiple fields to update an existing record. If a
target table record exists with the same values in all coalesce fields as the staging table
record, the target table record is updated using the staging table record values. All coalesce
field values between the target and staging tables must match to coalesce with multiple
fields.
• Conditional coalesce: You can use a script to determine if a staging table row should coalesce
to a target record. Most conditional coalesce scripts are defined in the source script field of a
field map for the sys_id field. To update a target record using the staging table record values,
the script must return the sys_id of the target table record.
A Data Policy enforces requirements on field and record data when the data is imported into
ServiceNow or when the data in an Import Set is submitted through an external system. Data
Policies can be opted out for Web Services and Import Sets. A Data Policy is used to set mandatory
and read-only states on form fields. Data Policies can be used on lists to make a field read-only; the
field will appear to be editable, but the update will fail.
The purpose of a Data Policy is to standardize the same data across ServiceNow applications.
NOTE: Data Policies are not about security, they are about managing the integrity of the information
stored in the database.
Lab Objectives
You will achieve the following objectives:
• Modify a list layout as preparation
• Create an Import Set Table and Transform Map
• Transform multiple imports
• Clean up import data
Scenario
In this lab, you will use Import Sets to load data that has been collected outside of ServiceNow
into the Infinity table.
The data will represent asset registration by Cloud Dimensions employees and partners, and
include information about the user and their registered Infinity device.
In the data cleanup, you will clean up the Import Set Table’s data.
2. Open the Column Context Menu from any field, then select Configure > List Layout:
4. Click Save.
Note: The following steps (process) can be completed by any user with the role import_admin
or import_set_loader and import_transformer.
3. Click Submit.
Note: You may notice the records in a different order than above.
3. Save.
5. Verify that four fields auto mapped: Name, Device Number, Device Version, and
Support Group:
7. From the Source: Infinity Imports staging table, move Device Owner and Owner
Location into the Field Map.
8. From the Target: Infinity table, move the Owned by, and Location into the Field
Map:
2. For Import set table, select the Existing table radio button.
Note: The import of the Infinity data to the staging table is complete, but you are not ready to
run the transform yet because you need to add a coalesce. Rather, you should tell the system
what the key field is to ensure that existing records are updated rather than adding duplicate
records by the imported data.
The device number (u_device_number) field seems to be the best candidate as the
coalesce because it will contain a unique value. If a match is found for the value of
this field, then the record will be updated instead of creating a new record.
4. From the u_device_number row, in the Coalesce column, double-click the word
false, then select true from the list:
2. In the Selected maps box, verify you are using the correct Transform Map: Infinity
Assets – u_cmdb_ci_hardware_infinity
Note: Notice that some of the records have an updated time from the initial upload (infinity-
data.xlsx) and some have an updated time from the incremental upload (infinity-updates.xlsx).
Also notice that in the infinity-updates.xlsx spreadsheet, in record CDE0100102, there was no
Owner Location information. Compare this to the same record in the infinity-data.xlsx
spreadsheet, which had Owner Location information.
If you had Copy empty fields checked and active in the Transform Map, it would have removed
the location data for this record. Since Copy empty fields was not active, the data from the
original import still remains in the table.
2. Add the Infinity Imports [u_infinity_imports] table to the Delete these tables box.
4. The checkbox for Delete data only (preserve table structure) should be selected.
Note: This will remove the data collected in the Infinity Imports staging table.
5. Click the Cleanup button – you should see a Cleanup completed verification message
and actions taken displayed in an Import Log.
Note: If you wanted to delete the Import Set table and any reference to it, including the Infinity
Assets Transform Map, you would have checked the Delete related transform maps checkbox
Which module is used as the first Which option allows you to update
step for importing data? existing target table records when
– Load Data importing data from an import set?
– Coalesce
What are the steps for importing Which tool is used to determine
data using an import set? relationships between fields in an
– Load the data import set and an existing table?
– Create a transform map – Transform Map
– Transform the data
– Clean up the import table
User Story
The Configuration Application provides core functionality for the Configuration Management
Database (CMDB), including modules for hardware and other configuration items. This functionality
is part of the CMDB plugin, which is activated in a base install.
A configuration item is any component that needs to be managed in order to deliver services. CIs
typically include business services and their underlying components, such as business applications
and hardware.
ServiceNow's CMDB, in contrast to a static list, not only tracks the CIs within your platform, but also
the relationships between those items.
Two key CMDB tables are Configuration Item [cmdb_ci] which contains CI data, and CI Relationship
[cmdb_rel_ci] which contains CI relationship data.
Toggle between CI
Health Dashboard view
and Form view
CI Attributes
Relationships
to other CIs
Click the reference icon (i) to the right of the Configuration item field to be redirected to the
selected configuration item record in ServiceNow.
A CI record contains all of the relevant attribute data about an item such as name, version,
descriptions, ownership, etc., which are documented in fields on the form.
Toggle between the CI Health Dashboard view and the form view using the options in the form title
bar.
The form also contains information about the relationships between items. Search for configuration
items, add new relationships, view the CI Map, or adjust the relationship view settings using the
options in the Related Items toolbar.
ServiceNow relationship rules use separate tables to define the relationships between specific CI
base classes and dependent classes. When you extend a table in the CMDB, you must create a new
relationship rule in Configuration > Relationships > Suggested Relationships.
You can view relationships between the current item and other items. An advanced feature is the
Related List in configuration item records which displays additional components.
All service management processes relate to and involve the CMDB. For example: someone calls with
an issue, and you want to do a root cause analysis, the CMDB gives you insights to effectively
troubleshoot.
Examples:
• A database runs on a server
• A rack provides power for a
server
Use the CI relationship editor to create configuration item relationships. It is accessed from the
Related Items toolbar on a configuration item form.
When you use the relationship editor, the CI record which the editor was launched is designated as
the base configuration item. You can then select one or more items to include in the relationship.
Depending on the selected relationship type, the base CI can become the parent CI or the child CI in
a new relationship.
Dependency Views indicate the status of configuration items, and allow access to the CI's
related alerts, incidents, problems, changes, and business services
The Dependency View mapping interface is powered by D3 and Angular technology, providing a
modern interactive graphical interface to visualize configuration items and their relationships.
Use the Dependency View to view other configuration items “upstream” that feed data into an
email service, for example, and then “downstream,” where you can view all of the other items that
the email service is dependent on.
Hover over
connection line Icons: View lists of active
to view the problem, incident, or
current change records for this CI
relationship
Right-click on
CI icon to
view menu
options
In a Dependency View, icons and glyphs indicate whether a CI has an active, pending issue. You can
investigate the tasks that are connected to a configuration item to get more details. The map
collapses and expands clusters to make them easier to view.
Understanding the dependencies and other relationships among configuration items will enhance
the operational delivery of incident, change, and problem management processes.
Lab Objectives
You will achieve the following objectives:
• Create a new CI class in the CMDB
• Define CI relationships
Scenario
All Infinity devices rely upon a media server, to process and stream data, which will require
tracking in the CMDB.
The media server can be categorized under the existing CI Server Class.
With both the Infinity and media server being tracked in the CMDB, a relationship between the
two CI Classes will be established – this relationship could be used by Cloud Dimensions to
potentially identify an impact of a change mangement request or outage.
A CI Class represents a type of Configuration Item or essentially a table collecting certain data,
such as Applications, Computers, Printers, Servers, etc.
In the last lab, a new CI Class was defined for the Infinity – categorizing it as a Hardware CI
because of the cmdb_ci_hardware table extension.
Note: This user is the Configuration Manager of Cloud Dimensions. They were provided the itil
role, in order to access the CI Class Manager. If your company does not have a Configuration
Manager, this responsibility could fall onto the system administrator.
4. From the CI Classes menu, scroll down to locate and expand the Hardware section,
to find the Infinity class:
Note: This confirms that the Infinity table and its consequential data records are tracked in the
CMDB, even though they are accessed from their own application menu and respective
modules.
2. From the Form Context Menu select Configure > Form Layout.
Note: This field displays after the alphabetically sorted list of available fields, as it is a formatter
rather than a standard field. It will not display on the form layout until the record has been
saved.
7. Submit.
The Infinity Media Server is responsible for sending content to Infinity devices.
With a CI relationship defined, tools like the CI dependency view can be used by Infinity
Support agents to identify the level of impact when issues occur.
5. Submit.
7. New.
9. Save.
10. Scroll down to the Related Items section, and select the Add CI relationship icon:
11. In the Suggested relationship types field, select * Sends data to (Child)...
12. From the Configuration Items section, use the Updated field to sort the records by
last updated.
Note: While only the Sends data to (Child) relationship was created, suggested relationships
also accounts for the converse relationship: Receives data from (Parent).
14. Scroll down to the Relationships section and add Infinity Media Server by selecting
the Create new relationships icon (+).
4. Open the Dependency View by Selecting the Show dependency views icon from
the Related Items toolbar:
Note: This displays an example relationship between the Infinity device and Infinity Media
Server CI Classes.
Excellent work! You have learned how to create a new CI class, add a CI to the CMDB, and use
Suggested Relationships to create relationships between configuration items!
Introduction to Development
Capstone Project
User Story
With Knowledge Management, each organization can have their own Knowledge Base (KB) with
flexible controls over who can see the information and who can help develop its content.
To view knowledge content, navigate to Self-Service > Knowledge to displays knowledge articles
organized by Knowledge Base and Category, as well as Featured Content, and popular articles (Most
Useful and Most Viewed).
From the Knowledge homepage you can browse or search for articles, sorting by relevancy, most
recently updated, and the number of views.
Once an article has a category and is accessible in the knowledge base, there are a number of
features that allow the organization’s users to provide their feedback whether adding comments
to the article or flagging it, which will bring the article to the attention of the KB contributors.
Some ServiceNow applications, such as Incident, allow contextual searching of Knowledge Base
content. This gives users the ability to troubleshoot their issue before submitting an incident by
displaying potential relevant articles.
IT Knowledge Base
From the homepage, users with the correct permissions can import a Word document to a
Knowledge Base using the Import Articles button, create a new article using the Create an Article
button, or ask a question using the Post a Question button.
Administrators can create multiple Knowledge Bases and assign them to individual managers
responsible for controlling the behavior and organizational scheme of each Knowledge Base. Every
Knowledge Base can have unique lifecycle workflows, user criteria, category structures, and
management assignments.
Category Hierarchy:
• Knowledge articles within a Knowledge Base can be grouped by category
• Category groups can help you define the Knowledge Base taxonomy, and can help users find
articles within a Knowledge Base
• Knowledge Managers can define knowledge categories to pre-populate the list of available
categories, and knowledge contributors can select categories, and add or edit categories, if
enabled, for a Knowledge Base
When importing a Word document, the following styles and elements are preserved:
• Titles
• Headings
• Images (Images may not be aligned exactly as in the Word document you import)
• Links
• Bold text
• Italic text
• Underlined text
• Ordered and unordered lists
• Tables
*Optional steps. Check the Publish check box to initiate the publishing workflow after the import
completes.
NOTE: If the publish checkbox is not visible, the system administrator will need to modify a system
property. To show the Publish check box, navigate to Knowledge > Administration > Properties and
activate the Show publish checkbox on the knowledge import pop-up property.
The publishing and retirement processes for a knowledge article are controlled by workflows
defined for the Knowledge Base that the article belongs to.
The Knowledge Base workflows available in the ServiceNow baseline instance include:
• Knowledge – Approval Publish: Requests approval from a manager of the Knowledge Base
before moving the article to the published state. The workflow is canceled and the article
remains in the draft state if any manager rejects the request.
• Knowledge – Approval Retire: Requests approval from a manager of the Knowledge Base
before moving the article to the retired state. The workflow is canceled and the article
remains in the published state if any manager rejects the request.
• Knowledge – Instant Publish: Immediately publishes a draft article without requiring an
approval.
• Knowledge – Instant Retire: Immediately retires a published article without requiring an
approval.
• Knowledge – Publish Knowledge: A subflow that moves the knowledge article to the
published state. You can use this subflow when defining your own workflow.
• Knowledge – Retire Knowledge: Moves a knowledge article to the retired state.
NOTE: This is only a selection of the base instance workflows to choose from, as designed for
Knowledge Base management.
User Criteria defines conditions that are evaluated against users to determine
which users can create, read, write, and retire knowledge articles
Knowledge bases use user criteria records to determine which sets of users can read or contribute
knowledge within that Knowledge Base. If a Knowledge Base has no user criteria selected, articles
within that Knowledge Base are available to all users.
To implement user criteria, navigate to Knowledge > Knowledge Bases and select a knowledge
base. User Criteria records are accessed from the Can read or Can contribute related lists.
When creating user criteria, the Match All check box to determine whether all elements from each
populated criteria field must match. If selected, only users who match all criteria are given access. If
cleared, the user must meet one or more of the set criteria to be given access. By default, this check
box is cleared so that any condition met provides a match.
The biggest benefit to implementing a virtual agent is so your users can get immediate help, day or
night.
Offer a personalized customer experience with a virtual agent by automating typical Tier 1 support
tasks to be accomplished, including:
• Answering FAQs
• Providing tutorial (“how to”) information
• Querying or updating records – for example: get the status on cases or incidents
• Gathering data, such as attachments, for the agent
• Performing diagnostics
• Resolving multi-step problems
Virtual Agent offers a web-based interface available for Service Portal, iOS and Android mobile
environments, and also supports third-party messaging applications through ServiceNow adapters
for Slack and Microsoft Teams.
Lab Objectives
You will achieve the following objectives:
• Create a knowledge base article by importing a Word document
• Approve the article for publishing
• Define, apply, and test user criteria on the knowledge base
Scenario
After a few positive rounds of Infinity testing, the product has been greatly improved and the
testing audience is ready to be expanded to include interested Cloud Dimensions employees.
Working with members of the Human Resources group, the Infinity testing coordinator will
provide guidelines for enrolling in Infinity testing to be published in the HR knowledge base.
Appropriate members of the HR group will be granted the appropriate authoring permissions
by the system administrator so that they may create, review, and publish articles.
The system administrator will assist with ensuring the article remains secure and accessible
only by Cloud Dimensions employees.
2. Locate Jasmin Gum, a member of the Human Resources group, and open the user
record.
4. Using the slushbucket, move the knowledge manager role to the Roles List by
double-clicking on the role.
5. Click Save.
3) Click the Browse Files button and browse your computer for the
Infinity_Open_Enrollment.docx file
4) Double-click the file name or highlight the file name and select Open.
1 2
Note: Multiple files can be imported when you drag and drop multiple files into the Import a
Word File box.
The Short Description is the same as the file name of the imported Word document.
5. Click on the knowledge article link in the Import Completed dialog box.
Note: The default publish workflow for the Human Resources Knowledge Base is Knowledge –
Approval Publish. This means after an author clicks the Publish button on their article, it goes
into a Review state. Other users with the correct permissions can view the article and determine
if any changes are needed before approving and publishing the article.
Note: Gracie Ehn is also a member of Human Resources and acts as the review board for new
content submitted to be published.
5. Assume the content looks good, then click Approve from the form header:
7. Open the Human Resources Knowledge Base to confirm the article appears:
The system administrator will create user criteria and apply it to the Knowledge Base to
appropriately control who can view the content.
Note: To select Cloud Dimensions, click on the Unlock Companies (padlock) icon, type cloud,
select Cloud Dimensions, and click on the Lock Companies (open padlock) icon.
5. Submit.
9. Click Edit…
11. Save.
Note: Remember, Jon Floyd works for a partner company of Cloud Dimensions. We will use his
user account to verify the Human Resources Knowledge Base is unavailable to access because
of the user criteria applied to it.
Add another feather to your cap – you have learned how easy it is to import Word articles
into a ServiceNow database!
What is the module used to import Word What tool controls the publishing
documents as articles? and retiring process for knowledge
– Knowledge > Articles > Import Articles articles?
What access does a user need to be able – Workflows
to import articles to a knowledge base?
– Can contribute
User Story
Service Catalog
The Service Catalog is a robust ordering
system for services and products offered
by various departments for users:
The Service Catalog lets users see a list of things they may need (to create a request for) or would
like to have – usually, but not limited to: IT products and services. Administrators and users with one
of the various catalog roles can define catalog items, including formatted descriptions, photos, and
prices.
Categories define the organization for Service Catalog items. Categories organize service catalog
items into logical groups. Categories can have a parent-child relationship, such as IT and Laptops. A
child category is a subcategory of its parent category. Each Catalog Item, Order Guide, Record
Producer, Content Item, and subcategory appears as a single item within the category.
The ServiceNow platform supports multiple Service Catalogs. Users with the admin or
catalog_admin role can manage multiple Service Catalogs and provide services to different teams
within the organization. Examples include: IT Services, Human Resources, and Facilities
Management. Views can be defined for groups that view a Catalog, and Catalog Items can be shared
by multiple catalogs. This results in the ability to dynamically control the ordering options from user
to user.
Items: In the Service Catalog, users locate a category for an item or service they want to order, and
then click the subcategory link.
Variables: Provide options gather specific information related to the customer's needs. Questions
that define item options can be added to ask the end user ordering the catalog item. Variables can
affect the order price. Service Catalog variables are flagged as "Global" by default and will display in
all the execution tasks of a requested item. A variable is defined once and can be used in multiple
places. The Service Catalog allows you to attach individual variables to a catalog item, or multiple
variables collected in a Variable Set.
Record Producer: An interface used as an alternative to lists and forms. Each Record Producer
focuses on a specific process or task and can be used anywhere in the ServiceNow platform. In the
Service Catalog, Record Producers are presented in categories along with catalog items. Users can
use Record Producers to create an incident, request an emergency change, and more. This enables
the Service Catalog to be used as a complete front-end UI.
Order Guides: Order Guides provide the ability to order multiple, related items as one request.
Questions can be used to present item options, and present users with only relevant questions and
choices at the appropriate time in the ordering process.
Flows: When you create a new service catalog item, you can create a new corresponding flow at the
same time. This flow is used to drive complex fulfillment processes and can send notifications to
defined users or groups.
Examples:
• Which monitor size?
• Who is the hiring manager?
Once an item is published to the Service Catalog, users • What is the budget code?
will be able to order it
Service Catalog variables are global by default and provide options to tailor a catalog item to the
customer's needs. For example, a computer may be available with different operating systems.
The Service Catalog lets you attach variables either to a catalog item or to an execution plan.
Functionally, a Variable Set is just a container, so it has only two fields: Name and Description. From
the Application Navigator, select Service Catalog > Catalog Variables > Variable Sets, and create a
new variable set. After you save the variable set, you will get a Related List at the bottom where you
can add as many variables as you want.
Used by items and variables, the Order field establishes the sequence for displaying information. For
example, an item with 100 in the Order field, displays first in the list. An item with 200 in the Order
field will display second.
A Record Producer focuses on a specific process or task and can be used anywhere in the
ServiceNow platform. In the Service Catalog, Record Producers are presented in categories along
with catalog items where each table has its own record-identifying designation.
RITM# RITM#
Request Item Request Item
SCTASK# SCTASK#
Catalog Task Catalog Task
SCTASK#
Catalog Task
Items are the building blocks of the Service Catalog. Once you have built a complete item with
variables and a delivery workflow, you can do a number of things with it, such as add it to an Order
Guide.
Order Guides provide the ability to order multiple, related items as one request. Remember that
variables are presented by the Order field number.
Use an Order Guide to assist users in determining what items they need.
Service Catalog
REQ#
Summary of order, Request State
Request
RITM# RITM#
Item Ordered, Quantity, Stage
Request Item Request Item
SCTASK# SCTASK#
Catalog Task Catalog Task
For Catalog Items, a request, an item, and a task are all created when an order is placed, each on a
corresponding table:
REQ# Request [sc_request] table: A request number generated to keep track of an order.
RITM# Requested Item [sc_req_item] table: Within a request generated from a catalog order, each
discrete item ordered is given a specific “Requested Item Number” known as an RITM (number).
SCTASK# Catalog Task [sc_task] table: In the Catalog Tasks section for an ordered item, the different
tasks display for what has to be done to get the item ready for delivery to the user, for example: the
Assignment group, the Due date, Work start, and Work end dates.
In this example, a manager orders two new computers for the team.
The first requested item is a desktop computer with two catalog tasks associated to it: order
equipment and configure equipment.
The second requested item is a laptop computer with two catalog tasks associated to it: order
equipment and configure equipment.
Although the requested items share similarly named catalog tasks, these tasks are tied directly to
their respective item because the required steps for completion may be different from item to item.
While viewing the requested item, you can expand the workflow stages which provide
summary-level feedback about the progress or state of an item in the delivery process
After an request has been submitted, users are able to easily track it by navigating to Self-Service >
My Requests and opening the record associated with the request.
Workflows attached to an item may indicate the progress or state of an item in the delivery process
with one of the following stages:
• Waiting for approval (In Progress)
• Approved
• Pending (has not started)
• Fulfillment (In Progress)
• Deployment/Delivery
• Completed
Additionally, workflows can have multiple rounds of approval actions as it relates to Service Catalog
requests. Each approval action can share the same stage value or their own separate stages.
Stages can be grouped into a Stage Set for convenience of applying related stage values from
workflow to workflow.
User Criteria defines conditions that are evaluated against users to determine
which users can access Service Catalog items.
To apply user criteria to an item or category, open the respective record and navigate to the
Available For or Not Available For related lists.
NOTE: These related lists are not on the form by default and must be added by configuring the form.
Next, click Edit to add an existing user criteria record, or click New to create a new one.
Save the record to associate the user criteria record with the item or category.
NOTE: The Not Available For settings override the Available For settings. A user on the Not
Available For list cannot access an item or category, even if that user is also on the Available For list.
Lab Objectives
You will achieve the following objectives:
• Create an Infinity service catalog item
• Add item variables
• Validate your work with “Try It”
Scenario
Up until now, the employee ordering and fulfillment process for an Infinity has been entirely
“off the books” – unofficial, to say the very least.
With the availability of the Service Catalog, Cloud Dimensions would like to improve the
process and ensure every employee has a chance to receive an Infinity device. Additionally,
tracking orders and inventory in one convenient location is appealing.
Note: This user account is provided the catalog_admin role, which grants them access to the
Maintain Items module in order to complete Service Catalog administration tasks.
3. Click New.
Name: Infinity
7. Click the lock icon (Lock Catalogs) to close the selection box.
Note: Category is used to determine where a catalog item appears within the Service Catalog.
From the left navigation pane, under Service Catalog > Maintain Categories, additional
categories can be created, and categories can be created hierarchically.
Description:
The Infinity is a portable holographic projector (PHP) that is capable of projecting
immersive environments around you. What are you waiting for? Get Infinity!
10. Select the Pricing tab and add in the Price field, enter 395.99
11. Select the Picture tab and in the Picture field, select Click to add…
3. Select the Infinity item from the list to open the order screen.
Note: This button deactivates the catalog item(s) selected on the list, making them inaccessible
to users in the Service Catalog. Until we finish defining our item, keep it deactivated.
The corporate-approved version of the Infinity is available in both 256GB and 512GB models.
11. Save the form, instead of Submit, to define the memory Question Choices.
12. Scroll to the Question Choices section then click the New button.
Text: 256GB
Value: 256
14. Submit.
16. Fill out the form for the second memory choice:
Price: $100.00
Text: 512GB
Value: 512
Note: The Price field is utilized by the 512GB choice, as it adds $100 to the overall price.
Additionally, the order value is set to 200 which will place the 512GB memory option second in
the choice list.
17. Submit.
3. Save.
4. Scroll to the Question Choices section then click the New button.
Text: Crimson
Value: crimson
6. Save.
7. Change the following field values for the second color choice:
Order: 200
Text: Silver
Value: silver
Note: You have just defined the values for the What color would you like? variable, using
question choices.
Another option for providing value choices is to use reference tables or fields from the
database. See the Choice table and Choice field options under the Type Specifications section on
the Variable form.
Visit docs.servicenow.com for the definitions of all the possible variable types.
Lab Verification
Test the Catalog Item
1. From the Infinity Catalog Item form, check the Active field to activate the item.
2. Save.
3. Next, click the Try It button from the form header to view the item order screen,
with the new variable options added.
4. Choose 512 GB and notice how the item Price changes from $395.99 to $495.99.
Congratulations! Now that you have created the Infinity in the Service Catalog, you’re ready
to create the flow to fulfill a new Infinity request!!
User Story
Launch the Flow Designer by navigating to Flow Designer > Designer in the Application Navigator.
The following roles may be required to work with the Flow Designer in one capacity or another:
flow_designer, flow_operator, and action_designer.
NOTE: You can expand the Flow Designer solution to integrate with external instances and third-
party applications with a separate subscription to IntegrationHub.
*A spoke contains Flow Designer triggers and actions dedicated to a particular application. For
example, the ITSM Spoke contains actions for managing Task records such as the Create Task action.
Spokes are activated when their parent application is activated.
In addition to these core actions, new application-specific core actions can be created by activating
the associated spoke.
Each time you add an action to a flow, Flow Designer adds a data pill to store its results.
The Data section of the Flow Designer contains data pills that can be used in subsequent
actions. To reference the data stored in the data pill, drag and drop the data pill from the
Data section to the appropriate field in the flow or click on the Data Pill Picker icon ( ).
When designing a flow, you can use the results of an action as inputs for other flows, actions, or
subflows. Using the sequence value (Trigger, 1, 2, 3, etc.), you can ensure you are using the correct
data pill as an input value.
When a flow runs an action, it generates the data pill runtime value, which remains the same for the
duration of the flow. For example, a data pill for [Trigger->Incident record] always contains the
incident record values from when the flow started.
NOTE: When using the Data Pill Picker icon, use the arrow keys to dot-walk to fields in other tables.
Lab Objectives
You will achieve the following objectives:
• Create a new flow from scratch
• Associate the flow to a Service Catalog item
• Test the flow
Lab Dependency: Requires the completion of Lab 4.2: Create a Catalog Item
Scenario
Now that Cloud Dimensions has opened enrollment for testing the Infinity across the entire
organization and the Infinity has been created in the Service Catalog, it is time to implement
procurement automation through a Flow.
Note: The Flow Designer Support for Service Catalog plugin has been activated in your student
instance. It is not installed by default but is necessary to create flows for service catalog.
Note: The Flow Designer opens and displays in a separate tab or browser window.
5. Click Submit.
B. Define a Trigger
1. Select Click to add a Trigger:
2. Select Action:
3. Select the Update Record default action type under ServiceNow Core.
Note: This will automatically populate the Table field with Requested Item [sc_req_item].
7. Select Done.
3. Drag and drop the Requested Item Record pill from section 1 - Update Record to
the Requested Item [Requested Item] field.
Note: Notice the Wait field is checked by default. This pauses the flow until the task completes
and is no longer active (e.g. when the task is marked Closed Complete)
6. Click Done.
Note: We will use dot-walking to locate the email address of the requester, so we can send
a confirmation when their order has been fulfilled.
3. Select the Data Pill Picker icon at the right of the To field.
Note: Selecting the Data Pill Picker icon will open a search box where you can dot-walk to
select the email address of the requester for the requested item.
4. With Trigger - Service Catalog highlighted, press the right arrow key on your keyboard
to highlight Requested Item…
5. Press the right arrow key again to dot-walk to the Requested Item table.
6. Arrow down to Request, then press the right arrow key to dot-walk to the
Request table.
Note: Rather than arrow down to a specific field, you can start typing the name of the field
and then press the right-arrow key to dot-walk to the next table.
8. Finally, arrow down to Email and press the Enter key on your keyboard.
Challenge: Use the Data Pill Picker icon to add fields to the email body!
2. Select Action:
Note: This will automatically populate the Table field with Requested Item [sc_req_item].
7. Select Done.
2. Select Action.
3. Select the Update Record default action type under ServiceNow Core.
Note: This will automatically populate the Table field with Request [sc_request].
7. Select Done.
Note: A message will appear confirming you would like to activate the flow – select OK.
2. Return to the main ServiceNow window and navigate to Service Catalog > Catalog
Definitions > Maintain Items.
4. On the Process Engine tab, clear the value in the Execution Plan.
Note: If the Execution Plan field has a value, the Flow and Workflow fields are (read-only).
5. Click the Order Now button to make the request and initiate the flow.
6. A verification the request was submitted is displayed at the top of the form.
3. Locate and open the Service Catalog Task associated with the Delivery workflow
activity. HINT: Search the Short description column for delivery.
4. Assume the item is in stock and can be delivered. Click the Close Task form button.
Note: This will mark the catalog task as Closed Complete for the Requested Item. It will also
trigger the email notification to Joe Employee.
LAB VERIFICATION
Since email is not enabled in your student instance, check the outbox to confirm an
email was created.
3. Confirm an email with subject “Your Infinity is on its way!” was created.
Impressive! You created your first Flow and associated it with Service Catalog item request!
What is the name of the interface for When attaching a flow to a service
building process automation capabilities? catalog item, which plugin needs to
– Flow Designer be activated?
– Flow Designer support for the
Which module is used to create or edit
Service Catalog
flow designer flows?
– Flow Designer > Designer
Where is the data from an action What are the components of a Flow
stored so it can be used in Designer flow?
subsequent actions in the flow? – Trigger
– Data Pill – One or more Actions
Capstone Project
User Story
JavaScript may execute on the client side (web browser) or the server side (ServiceNow
database) and can fundamentally alter the baseline instance and user experience.
Request
Internet
Response
Client refers to an application or system that accesses a remote service or another computer
system, known as a server. A server is the computer program running as a service; a physical
computer dedicated to running one or more services, or a system running a database.
ServiceNow uses an Application Platform as a Service (aPaaS) model; the web browser is the client.
The web browser is the only thing that is installed on the client. The application server and the
database live at the Data Center. Client scripts run on the client browser. Server scripts run on the
server (which includes the database).
Client to server round-trips take time and make the end-user wait for the round-trip to complete.
Request + Response = Round trip.
To immediately implement updates and changes to forms and lists, you can use UI Policies which
allow you to add sophisticated controls without having to write scripts and define custom process
flows for tasks.
NOTE: UI Policies are not about security, they are about managing the user experience.
A Data Policy enforces requirements on field and record data when the data is imported into
ServiceNow or when the data in an Import Set is submitted through an external system. Data
Policies can be opted out for Web Services and Import Sets. A Data Policy is used to set mandatory
and read-only states on form fields. Data Policies can be used on lists to make a field read-only; the
field will appear to be editable, but the update will fail.
The purpose of a Data Policy is to standardize the same data across ServiceNow applications.
NOTE: UI and Data Policies are not about security, they are about managing the user experience.
UI Actions can contain scripts that define custom functionality. UI Actions can be server or client
side depending on the 'client' check box selection. This setting determines when a UI Action can
appear.
UI Actions include:
• Form buttons
• Form context menu items (right-click the header)
• Form links (Related Links in a form)
• List buttons
• List context menu items (right-click a record)
• List choices (at the bottom of a list)
• List links (Related Links at the bottom of a list)
When Order 100 is specified, UI Actions with Order numbers greater than 100 will display after this
UI Action, while UI Actions with Order numbers less than 100 will display before this UI Action, in
the user interface.
NOTE: When the UI Actions Active box is checked, the UI Action is running and visible unless there is
a condition met that specifies otherwise.
Client Scripts allow for browser/form manipulation and verification such as making fields visible on a
condition. An example of this would be an alert appearing when a user changes the priority of an
incident. Client Scripts get executed on the browser, but you may also run a Client Script when a
database lookup is needed; if you think you need database info, and you need the info frequently
(such as every form load) then ask: Is it a field you can add to the form but hide? Is it something you
really, truly need?
Unlike onLoad() or onSubmit() scripts, onChange() scripts apply to a particular widget on a form,
rather than to the form itself. They are fired when a particular value on screen changes. An onLoad()
script runs when a form is first drawn and before control is given to the user to begin typing.
Typically you use an onLoad() script to perform some client side manipulation of the document on
screen. An onSubmit() script runs when a form is submitted. Typically you use an onSubmit() script
to validate things on the form to make sure the submission makes sense. As such, onSubmit() scripts
can potentially cancel a submission by returning false.
A Business Rule is configured to run when Business Rules can be set to run before or after
a record is displayed, inserted, updated, the database action has occurred
deleted, or when a table is queried
The When setting determines when the
Business Rule executes and has the following
choices:
• Before a record is saved to the database
• After a record is saved to the database
• Async (queued); client and server work
independently so the client is not waiting
for the server
• Display before the record is displayed
Although there are multiple ways to control behaviors in the ServiceNow application, most
customization of platform behavior is done using Business Rules. Business Rules are l oaded and
initialized at the beginning of each interaction between a user and the platform.
Every Business Rule includes what table to run against and timing (before or after insert and more),
what conditions to evaluate, what script to run based on the evaluation, and if it is client-callable.
Business Rules are consistently applied to records regardless of how they are accessed-through
forms, lists, or Web Services. This is one major difference between Business Rules and Client Scripts,
which only apply when editing through the form.
The primary objective of display Business Rules is to use a shared scratchpad object,
"g_scratchpad", which is also sent to the client as part of the form. This is useful when you need to
build client scripts that require server data that is not part of the record being displayed.
UI/Data Policies
Business Rules Client Scripts
UI Actions
UI Macros
UI Scripts
ACL Scripts SCRIPTING
UI Properties
UI Pages
ServiceNow has over 30 places where code can be inserted to change the behavior of the platform.
JavaScript is used almost everywhere and it is a very flexible and powerful language commonly
known for its inclusion in most modern web browsers. This has made it almost mandatory for web
development these days, with its simple syntax allowing many people to quickly add simple logic to
web pages with minimum effort. Taking advantage of this familiarity, ServiceNow uses JavaScript
both on the server and on the client.
Some plugins include demo data - sample records that are designed to illustrate plugin features for
common use cases. Loading demo data is a good policy when first installing the plugin on a
development or test instance. Demo data can loaded after the plugin is activated by repeating this
process and selecting the checkbox. If the plugin depends on other plugins, these plugins and their
activation status are listed.
Most plugins are published, and system administrators can activate any published plugin. But, some
plugins are available only by request due to operational considerations making the plugin only
appropriate for certain deployments. In these cases, to activate the plugin, make a Service Catalog
request to ServiceNow Technical Support using the Request Plugin Activation form at
https://hi.service-now.com.
Lab Objectives
You will achieve the following objectives:
• Create a UI Policy with a UI Policy Action
• Create a Business Rule
Scenario
Cloud Dimensions would like to continue configuring ServiceNow as much as possible by using
baseline functionality and available features.
One requirement for Cloud Dimensions’ process improvement is to require important Infinity
support data, with the goal to speed up resolution time by requiring the Assigned to field to be
populated for all employee incidents. A confirmation for each submitted incident has also
been requested.
A. Create a UI Policy
1. Ensure you are logged into the instance as System Administrator.
4. Click New.
You have just defined a UI Policy and set the conditions on which it will be enforced.
Next, indicate which field(s) to affect by the UI Policy.
Note: If you do not see the Employee field, use the context menu to switch to the Employee
Infinity Testing form view.
4. Uncheck the Employee field and notice that the Assigned to field is no longer
mandatory.
3. Click New.
5. Add a message:
6. Click Submit.
2. Fill out the incident form, including values for all mandatory fields.
3. Click Submit.
4. The new Business Rule displays your message in blue on top of the list:
Good job, you have learned how to create a UI Policy and Business Rule in this lab!
What is the language used for Does a business rule run on the
scripting in ServiceNow? client side or the server side?
- JavaScript - Server
User Story
As a System Administrator,
Basically an Update Set record is a “point in time” XML snapshot of process records. An Update Set
works by writing changes from tracked tables to the Customer Update [sys_update_xml] table.
An Update Set is used to apply changes that have been checked and verified in another instance.
When merging multiple Update Sets, if several Update Sets have modified the same object, (for
example: the Incident form), the most recent change will be the one moved to the new, merged
Update Set.
An Update Set is a container for configuration records. By navigating to System Update Sets > Local
Update Sets, you can create a new Update Set or set an existing one as your current Update Set.
Use an Update Set to migrate your code. When an Update Set is completed, you can transfer it to
another instance to move customizations from development, through testing, and into production.
It is recommended to avoid using the Default Update Set for moving customizations between
instances. Instead, use a named Update Set.
What is captured in an Update Set is typically a customization or a configuration change and does
not include changes to data records. For example, update sets track report definitions and related
data such as data source, report type, style, and sharing settings. However, the actual data and
report output are not tracked in an update set.
*Homepages are not captured in an Update Set but can be manually added by:
• Navigating to Homepage Admin > Pages,
• Right-clicking on a homepage record, then
• Selecting Unload Portal Page.
NOTE: Data is not captured in an Update Set. Examples: a new incident or new change record would
not be in an Update Set.
When completing work, you may want to move data records with your updates. These records can
be useful for testing or training. Data (such as user records, CIs, or locations) can be moved using the
Export XML function.
Other best practice recommendations include using the Preview to verify there are no conflicts with
committing the Update Set.
IMPORTANT: Both instances must be on the same version since customizations may not work if they
rely on code that has changed between versions.
Determine the changes to make in a single Update Set since ServiceNow recommends limiting
Update Sets to a maximum of 100 records to reduce the number of potential conflicts and make it
easier to identify and review changes.
Ensure that all platform records have matching sys_id fields since some platform records are created
on an instance after provisioning and do not match between different instances, leading to
problems with Update Sets. You can clone the production instance onto the sub-production
instance.
The most common processes required for integration are the CMDB, Incident Management,
Problem Management, Change Management, User Administration, and Single Sign-On.
A variety of techniques can be used, most notably Web Services, LDAP, Excel, CSV and email, as well
as any industry standard technologies that use SOAP or REST WSDLs.
Examples:
• Post a message and details in a Slack channel when P1 incident is created
• Create users and groups in Microsoft Active Directory
• Retrieve, create, update, or delete data on a server using REST
One major benefit of Integration Hub is that it reduces the need for code, while ensuring
discoverability and reuse.
It also features scale and control mechanisms that are designed to never fail, including an
extensibility framework which enables Applications to easily plug and play providers.
Use Integration Hub to extend the Flow Designer to call 3 rd party systems such as automating
Microsoft Services and infrastructure using PowerShell and REST.
As a System Administrator,
Lab Objectives
You will achieve the following objectives:
• Review an Update Set
• Create another Update Set
• Make platform changes and capture them in the new Update Set
Scenario
As Cloud Dimensions system administrator, review the Default Update Set to identify
configuration changes that have been captured throughout class.
Then create a new Update Set and capture additional changes that will be transferred to
another ServiceNow instance in the next lab.
1. Logged into the instance as System Administrator, open Settings from the banner
frame:
2. Select Developer.
3. Next, toggle on the switch for Show update set picker in header:
This is the Update Set Picker menu. It allows you to quickly select an Update Set to
capture platform configuration changes.
6. Locate and open the Default Update Set within the Global Application:
Note: Alternatively, you could click on the View current Update Set icon, located next to the
Update Set Picker to quickly open the current Update Set’s record:
What items are captured in the Update Set that were created in class?
What items are not captured in the update set but were created in class?
3. Enter the following name for the new Update Set: Catalog Item Form Changes.
4. In the Description field, enter the following description of this Update Set:
Added Updated and Updated by after Roles on Catalog Item form.
6. A brief confirmation message displays, and the current Update Set is shown:
7. The current Update Set is also represented in the Update Set picker:
3. From the Form Context Menu, select Configure > Form Layout.
5. Click Save.
4. Click Update.
5. With the status of Complete, this Update Set is now ready to be retrieved by
another ServiceNow instance.
Lab Verification
Verify you have one Form layout update on the Catalog Item table
What is used frequently to move What are the steps for applying an
customizations from on instance to update set to an instance?
another? - Retrieve
- Update Sets - Preview
- Commit
Which types of records are not
captured in an update set? Which ServiceNow product provides
- Data records the ability to quickly integrate with
3rd party applications without
Is a homepage captured in an scripting?
update set? - IntegrationHub
- Homepages are not automatically
included, but can be manually added
User Story
As an Application Developer,
I want to retrieve configuration
changes directly from an existing
instance of ServiceNow
So I can avoid downloading and
uploading update sets on my local
machine.
Delegated developers
are non-administrator
users and groups which
are assigned one or
more permissions to
develop applications
To manage delegated developers, navigate to System Applications > Applications, open the
application record, then click on Manage Developers.
Administrators can specify what parts of an application are accessible to other applications from the
custom application record and each application table record.
For example, suppose that you create a conference room booking application in its own application
scope. By default, the application can access and change its own tables and business logic but other
not applications unless you give them explicit permission.
By default, all custom applications have a private scope that uniquely identifies them and their
associated artifacts with a namespace identifier. The application scope prevents naming conflicts
and allows the contextual development environment to determine what changes, if any, are
permitted. Application developers specify an application scope when they create an application.
The global scope is a special application scope that identifies applications developed prior to
application scoping or applications intended to be accessible to all other global applications.
The system adds a namespace identifier to the front of application artifacts such as tables, scripts,
and configuration records.
These tests provide enough flexibility to help confirm the instance still
Tech Note
Tests include a series of steps that the test attempts to execute when ran. Once run, the Automated
Test Framework creates a Test Results record, which is available through a related list on the test
record.
Additionally, all test records are defined with test steps - the individual steps and the order in which
the test should execute them. A test step includes an action to take and the data needed to take
that action. ATF includes a number of a default set of step types (or step configs), but custom types
can also be defined.
If a test includes steps that involve a form or other user-interface element, it will run the steps in a
browser tab or window on-demand, or scheduled at a set time. Running tests in a browser is
especially useful to watch the test execute in real-time.
There are great resources here related to development, including: scripting API references, free
training and documentation, and access to a free, personal developer instance.
As an Application Developer,
I want to retrieve
configuration changes
directly from an existing
instance of ServiceNow
Lab Objectives
You will achieve the following objectives:
• Sign up for a developer instance
• Define an Update Source
• Retrieve an Update Set, committing platform changes to the developer instance
Scenario
To end class, you will be walked through the steps to sign up for a developer instance on the
ServiceNow Developer Portal.
You will also practice the procedure of retrieving completed update sets from one instance of
ServiceNow to another. This emulates the experience of taking configuration changes made to
the platform of one instance and pulling them into another – just like pulling work from a
development instance into production.
Lab Dependency: Requires the completion of Lab 5.2: System Update Sets
1. Go to https://developer.servicenow.com/
2. Select Register from the upper right-hand menu, then fill out the form, then finally
read and agree to terms of use before clicking Submit.
4. Select the link in the email message to validate and activate your account.
5. Sign in with your username and password created in step 2, then read and accept
the ServiceNow Developer Agreement.
Note: If this page does not display, you can click on the ServiceNow logo or, from the main
menu, select Manage > Instance.
8. Complete the form to tell ServiceNow how you will use the personal developer
instance, then click I understand.
9. You may choose any available version of ServiceNow you would like, but the most
recent version is recommended.
IMPORTANT:
Capture your username and password as it will not be available after the next step.
11. Under the instance log in credentials, click the link to log into the instance directly:
12. Use the credentials above on the login screen, then change the temporary password
to successfully sign into your instance as system administrator.
2. Select New
3. Observe the Updated and Updated by fields are not displayed on the form.
5. Click New.
Note: These are the system administrator credentials your instructor provided, and which you
have been using during class.
10. Type in a brief description of the Update Set into the Short Description field:
Modified Catalog Item form fields, adding Updated and Updated by.
Note: A brief Connection is OK message will display, which may also include language about
varying version snapshots.
13. Save.
15. Close the Retrieve Update Sets progress pop-up once it has reached 100%.
2. From the form header, click the Commit Update Set button.
Note: This update set has already been previewed – checked to make sure its contents do not
interfere with the target instance. If your developer instance is not running the same version of
ServiceNow as your student instance, you may need to click Preview and will get a collision
error. You may accept the remote update and Commit to continue with the lab.
5. You should see the new Update Set with a Committed state:
2. Select New.
3. You should now see the Updated and Updated by form fields:
Good job, you have learned how to bring over an update set from another instance without
having to export and import the update set!
1 2
Challenge Step-by-Step
• Included in your participant guide • Downloadable from your instance
• Provides minimum assistance to • Provides full assistance to achieve
achieve end results; objectives end results; detailed instructions
are given but how you get there is are given to walk you through the
mostly up to you completion of each task
The Capstone Project: Challenge Format is included in your participant guide. We strongly
recommend that you try to solve each Capstone Project task using just the Challenge format. If you
have difficulty completing a task, you can refer back to slides, notes, and labs.
If you find yourself still struggling, or prefer to complete the tasks “by the book” then no worries!
Step-by-Step task solution guides are available. Locate and download these solution guides from
your class lab instance. They are located under Capstone Project in the ServiceNow Fundamentals
Class Knowledge Base.
Cloud Dimensions needs a software solution to support new business processes, which are still
being developed, and requires that the solution be able to scale appropriately in order to support
ongoing, rapid growth.
ServiceNow has proven to be the best solution to meet Cloud Dimensions current requirements and
support plans for ongoing expansion. Therefore, Cloud Dimensions is ready to move forward with a
ServiceNow implementation for their latest product, the Infinity Handheld Holographic Display
(HHD).
A worldwide product launch date is aligned with the ServiceNow Go-Live date, so as a Cloud
Dimensions System Administrator, you have been tasked with the responsibility to customize the
Cloud Dimensions instance in support of technical needs for employees and customers alike!
Remember once you start the Capstone Project: this is suppose to be a fun exercise! It is meant to
test the knowledge you gained in class and, most importantly, give you a chance to look around in
the ServiceNow platform.
If you start with the Challenge format as suggested, remember to use all of the resources discussed
in class, including docs.servicenow.com.
Enjoy!
1. Instance Customization
3. User Administration
6. Mobile UI
8. Scheduled Reports
To successfully complete the Capstone Project, you must select the Capstone Project article in
the ServiceNow Fundamentals Class Knowledge Base of your lab instance.
This will download a zip file to your local machine titled Capstone Project which contains
relevant task files, as well as the Step-by-Step Solution guides for every task.
Additionally, you will create an organization company record to include contact information
and new welcome page content.
Create new Welcome Page Content text for all users on the login page to say:
• Short description: Welcome to Cloud Dimensions
• Text: Welcome to the home of Handheld Holographic Display! If you are an employee of
Cloud Dimensions, please use your company login credentials to enter.
2. Configure the Default View and place the HHD Model field beneath the Configuration item
field
3. Configure the Mobile View and place the HHD Model field beneath the Caller field
4. Modify the Category field on the Incident form to include a new HHD choice.
Additionally, set Fred Luddy as the Manager under Kara Prince’s user record.
Note: Test by submitting a request for the Service Catalog item by a user with a manager and
then impersonating every stakeholder involved, as determined by the activities created above,
to ensure it would work in a real-life situation.
TASK VERIFICATION
Note: By default, all Knowledge Base articles must go through a Review Process before they are
published. You will enable automatic publishing on the Knowledge Base level.
Click on the HHD item name to open the ordering screen where you can customize your
request. Once satisfied, click the Order Now button on the right-hand side.
• Short description:
Supporting HHD Service Catalog Requests
If the requester has placed an order and would like to know about their request, please
have them contact hhdorder@cloudd.com.
TASK VERIFICATION
Create a test incident by Kara Prince which has the HHD category and a short description My
HHD will not turn on.
Then, develop an email notification related to new critical HHD incidents assigned to the HHD
Support group. Afterwards, test to ensure the email sends correctly.
Verify the email is sending to the HHD Support Manager by creating a new Priority 1 HHD
incident assigned to the HHD Support group and checking the System Outbox.
TASK VERIFICATION
Schedule the report by sharing it with the HHD Support group every Monday to coincide with
their incident review meeting.
A. Create a Report
Set the following properties for the new report:
• Name: Active HHD Incidents by Priority
• Source type: Table
• Table: Incident [incident]
• Type: Pie
• Group by: Priority
Add the following schedule details which will appear within the email containing a copy of the
report:
• Subject:
Current HHD Active Incidents Count
• Introductory message:
Please find included the current count of all active HHD incidents grouped by
priority.
This information will be discussed during the team’s incident review meeting today
at 9:00am.
TASK VERIFICATION
2225 Lawson Ln, Santa Clara, CA 95054, USA • (858) 720-0477 • (858) 720-0479 • www.servicenow.com