Reports &Update Sets

• What are ServiceNow reports?

L A
• Reports are visualizations of your data that you can share with users on dashboards and service
portals, export to PDFs, and send via email. Reports are created within the Report Builder,
Performance Analytics, or custom.

V U
• ServiceNow provides a built-in reporting engine that allows users to create reports using pre-defined

A R
templates, or to create their own custom reports using a drag-and-drop interface.
• Show Bar Report That Contains Priority Based Incidents?

U M
K
E M
P R
• ServiceNow Reporting are enable to you to create and distribute reports that show the current state
of instance data ,such as how many open incidents of each priority there are reporting functionality

• Reports> View/run> Create new (or) L A

is available by default for all tables, except for system tables.

Reports > Create new

V U
Dashboards:

A R
In ServiceNow, dashboards are interactive and customizable displays of key performance indicators

U M
(KPIs) and other relevant data. Dashboards provide a visual representation of data that can help
organizations to quickly understand the status of their IT systems, services, and processes.

K
Overall, dashboards in ServiceNow provide organizations with a powerful tool for managing and

E M
monitoring their IT systems, services, and processes. They allow organizations to make informed
decisions based on real-time data and to respond quickly to changing conditions.

P R
Dashboards> self-service> Dashboards>createNew (or)
Pa_dashboards.LIST
Updates sets:
• Update sets in ServiceNow are a way to capture and move changes between instances of ServiceNow, such as
from a development instance to a production instance.

L A
U
• In ServiceNow, updates sets are used to track and manage customizations made to the platform.

V
• Update set is nothing but the group of customization move them between one instance to another instance

• Captures:
A R
• Note: only customization are moved And not record’s
Not Captures:

M
• Tables • Incidents

U
• problem
• fields
K
• change etc...
• form layout • Users
• list layout
E M • Groups
• Email

R
• workflows

• UI pages
P
• business rules,clientscripts,script include

• System Properties
• update sets are created and managed using the Update Set module in the ServiceNow platform. When a developer
makes a change to a configuration item in ServiceNow, such as modifying a field or creating a new business rule,

L A
the platform automatically detects the change and prompts the developer to add the change to an update set.
The developer can then add the change to an existing update set or create a new update set.

V U
• Once an update set has been created, it can be moved to another instance of ServiceNow using the Update Set
Migration module. The developer can export the update set as an XML file, which can then be imported into

R
another instance of ServiceNow. The import process will create or update the configuration items in the target
instance, based on the changes captured in the update set.

A
• Some of the key benefits of using update sets in ServiceNow include:

U M
1. Change management: Update sets provide a structured and controlled way to manage changes in ServiceNow,
making it easier to track and manage changes over time.

K
2. Collaboration: Update sets can be shared among multiple developers or teams, allowing them to work together on

E M
a set of changes and reduce conflicts and duplication of effort.
3. Reusability: Update sets can be saved and reused, making it easier to move changes between instances of

P R
ServiceNow and reduce the time and effort required to make the same changes in multiple instances.
4. Control: Update sets provide a way to control the movement of changes between instances of ServiceNow,
reducing the risk of errors or unintended consequences when making changes to a production instance.
• Overall, update sets are a powerful tool for managing changes in ServiceNow, and are an essential part of the
development process for ServiceNow applications and configurations.
• Use Case 1:

A
• Create Client Script and Business rule in one of service-now instance and then move that client script
functionality to another ServiceNow instance?

U L
• You have to create 2 instances one is dev instance another one is test
instance. V
A R
U M
K
E M
P R
 L A
V U
A R
U M
K
E M
P R
"Visual Task Boards" (VTBs)::In ServiceNow, which provides a visual interface for managing tasks and workflows.
• VTBs in ServiceNow are based on the Kanban methodology, where tasks are represented as cards that move across

change management, or project management.

L A
columns on a board. VTBs can be used to manage workflows for various types of tasks, such as incident management,

V U
• VTBs in ServiceNow can be accessed from the Visual Task Board module, where users can create new boards, customize
columns and cards, and configure the behavior of the board. VTBs can also be integrated with other ServiceNow modules

R
and features, such as the Task table, allowing users to manage tasks and workflows directly from the VTB.

A
• Some of the key benefits of using VTBs in ServiceNow include:

M
• Visual workflow management: VTBs provide a visual interface for managing tasks and workflows, making it easier to

U
understand and track the progress of tasks and identify any issues or bottlenecks in the workflow.

K
• Customization: VTBs can be customized to meet the specific needs of different teams or workflows, with the ability to
create new boards, customize columns and cards, and configure the behavior of the board.

E M
• Integration: VTBs are integrated with other ServiceNow modules and features, such as the Task table, allowing users to
manage tasks and workflows directly from the VTB.

P R
• Collaboration: VTBs support collaboration and communication among team members, with the ability to add comments,
attachments, and other information to cards on the board.
Overall, VTBs are a powerful tool for managing tasks and workflows in ServiceNow, providing a visual and customizable
interface that can help teams improve their efficiency and productivity.In
Visual Task Board use:
• User can create, view, and edit freeform, flexible, and guided visual task boards, and add users to these boards
as members.

L A
U
• With Visual Task Boards you can:Create a freefrom board
• Create a data driven board
V
• Delete a task board
• Add or modify task board lanes
A R
• Add users to boards
• Add cards
U M
K
E M
P R
Access Control List (ACL): s a feature in ServiceNow that allows administrators to define rules for controlling access
to data and functionality within the platform. ACLs are used to enforce security policies by controlling which users or

platform.
L A
groups can access, read, write, or delete data in tables, fields, UI actions, and other elements of the ServiceNow

V U
• ACLs consist of a set of conditions and permissions that are applied to a specific table, field, or UI action. The
conditions specify the criteria for the access, such as the user's role or group, the state of the record, or the type

R
of operation being performed. The permissions determine the level of access that is granted or denied based on
the conditions, such as read, write, create, or delete.

A
• ACLs in ServiceNow are defined using the ACL editor, which provides a graphical interface for creating and

U M
managing ACLs. ACLs can be assigned to individual tables, fields, or UI actions, or they can be inherited from
parent tables or other elements in the platform.

K
• Some of the key benefits of using ACLs in ServiceNow include:

E M
1. Improved security: ACLs provide a powerful mechanism for enforcing security policies and controlling access to
data and functionality within the platform.

P R
2. Customization: ACLs can be customized to meet the specific needs of different applications or workflows, with
the ability to create rules that are tailored to specific tables, fields, or UI actions.
3. Simplified administration: ACLs can simplify administration by allowing administrators to define and manage
access controls in a centralized location, rather than having to manage access controls on a per-application or
per-workflow basis.
4.Granular control: ACLs provide granular control over access to data and functionality, with the ability to define
rules that restrict access based on a wide range of criteria, such as the user's role, group, or location.

L A
Overall, ACLs are an essential tool for enforcing security policies and controlling access to data and functionality
within the ServiceNow platform. By using ACLs effectively, administrators can ensure that users have the appropriate

breaches.
V U
level of access to the data and functionality they need, while minimizing the risk of unauthorized access or data

• ACL evaluation process

A R
• An ACL rule only grants a user access to an object if the user meets all of the permissions required by the

M
matching ACL rule.
• The condition must evaluate to true.

K U
• The script must evaluate to true or return an answer variable with the value of true.

E M
• The user must have one of the roles in the required roles list. If the list is empty, this condition evaluates to true.
• [Record ACL rules only] The matching table-level and field-level ACL rules must both evaluate to true.

P R
Pre and post query ACL checks:
Your instance checks ACL rules both before and after a user makes a query. Because different information is available before

A
and after a query, results can be different.

L
Pre-query ACL check

U
Before your instance runs a database query, it checks ACL rules for each field in the queried table to determine which fields a

V
user may access. This check only looks at the
user's roles, and checks to see if these roles allow access to fields. Because this check runs before the query, the ACL doesn't

A R
have access to the records on the table, so it
cannot take that data into account. Scripts and conditions that rely on knowing contents of a record are not evaluated.
If the user doesn't have read access at this point, the value for the field is not shown to the user.
Post-query ACL check

U M
After the query, your instance checks each record returned by the query. During this check, there is context for the ACL, so the

K
role, condition, and script portions of the ACL
are evaluated. If the user doesn't have read access at this point, the value for the field is not shown to the user, however the

M
user will see the field label if their roles allow access to the field.

E
P R
• ACL rules in scoped applications:
• You can create ACL rules for objects in the same scope as the ACL rule and for tables with at least one field that
is in the same scope as the ACL rule.

L A
U
• For tables that are in a different scope than the ACL rule record, the types of rules are limited.You can create an
ACL rule for any table, UI page, or other object that is in the same scope as the ACL rule.

V
• You can create an ACL for a field that is in the same scope as the ACL rule.

A R
• If the table is in the same scope, you can use a script to evaluate permissions.

M
• If the table is in a different scope, you cannot use a script to evaluate permissions.

K U
• You cannot create or modify ACL rules for objects that are in a different scope than the application you have
selected in the application picker, including adding a role to an ACL in a different scope.
• You can create wildcard table rules (*) only in the global scope.

E M
• You can create wildcard field rules (*) only for tables in the same scope as the ACL rule.

P R
ACL rule types
• In ServiceNow, there are several types of ACL rules that can be used to control access to data and functionality within the
platform. Some of the most common ACL rule types are:

L A
1. Table ACLs: Table ACLs control access to tables and their associated records. They can be used to restrict access to certain

or the type of operation being performed.

V U
tables or to specific types of records within a table, based on conditions such as the user's role or group, the state of the record,

R
2. Field ACLs: Field ACLs control access to individual fields within a table. They can be used to restrict access to sensitive data,
such as social security numbers or credit card information, or to prevent users from modifying certain fields that should be read-
only.
A
U M
3. UI Action ACLs: UI Action ACLs control access to UI actions, which are buttons or links that perform actions within the platform,
such as creating a new record or updating an existing one. They can be used to restrict access to certain UI actions or to specific

K
types of records or fields, based on conditions such as the user's role or group.
4. Catalog Item ACLs: Catalog Item ACLs control access to catalog items, which are items in the Service Catalog that users can

M
request, such as software installations or equipment requests. They can be used to restrict access to certain catalog items or to

E
specific groups of users who are authorized to request certain items.

P R
5. Business Rule ACLs: Business Rule ACLs control access to business rules, which are scripts that run on the server when certain
events occur, such as when a record is created or updated. They can be used to restrict access to certain business rules or to
specific types of records or fields.
• Overall, ACLs provide a powerful mechanism for controlling access to data and functionality within the ServiceNow platform, and
by using the appropriate types of ACL rules, administrators can ensure that users have the appropriate level of access to the
data and functionality they need.
 L A
V U
A R
U M
K
E M
P R
 L A
V U
A R
U M
K
E M
P R