Analytics Performance

Version: Tokyo
SERVICENOW ADMINISTRATOR
Performance Analytics
ARTICLE (1 OF 57)
Performance Analytics Objectives

In this module, you will learn to:
Activate the Performance Analytics - Premium plugin

Describe the Performance Analytics data and visualization layers
Design Performance Analytics into your applications
Create indicator sources to filter data
Create indicators to refine data into scores
Create breakdown sources to specify which unique elements a breakdown contains
Filter data into scores using breakdowns
Create data collectors
Historical: collects past data
Data collector: collects current data
Use Analytics Hub to analyze Performance Analytics data, trends, targets, thresholds, and forecasts
Create dashboards using Performance Analytics widgets
Use bucket groups to visualize data and draw conclusions that are not obvious when looking at raw
data
PREREQUISITES: Familiarity with Scheduled Script Executions and Events

(https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_automatingapps_tokyo_automatin
(scheduled jobs) and Dashboards
(https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_reportanalytics_tokyo_reporting_a
ARTICLE (2 OF 57)
About This Learning Module
IMPORTANT: The content in this learning module was last updated for the San Diego ServiceNow release and was not
updated for the Tokyo release. You may see differences between the Tokyo release and the content in this learning
module.
The Earthquakes application is used throughout this learning module to introduce and demonstrate the
concepts and processes behind creating an application. You do not build the Earthquakes application.
You will develop the NeedIt application in the hands-on exercises.
Exercises are indicated in three ways:
Exercise icon in the Navigation pane.

Exercise icon and the word Exercise at the top of the page.
The word Exercise or the word Challenge in the page title.
The NeedIt application allows users to request services from multiple departments. You will use source
control to begin with all NeedIt application files needed for this learning module.
EXERCISE (3 OF 57)
Exercise: Fork Repository and Import

Application for the Performance Analytics
Module
ServiceNow uses GitHub to provide application repositories to copy and use with the Developer Site
learning content. The repositories contain tags, which are fixed sets of application files, to start you with a
partially built application. By copying and importing a ServiceNow-provided repository into your Personal
Developer Instance (PDI), you get all the files needed for the hands-on exercises in the modules.
NOTE: See the GitHub Guide (/dev.do#!/guide/tokyo/now-platform/github-guide/github-and-the-developer-site-training-guide-
introduction) for more information on how ServiceNow uses GitHub with the Developer Program learning content and to see
a video on how to fork a repository and import an application.
In this exercise, you will:
1. Fork the ServiceNow repository to your GitHub account.

2. Import the application into your PDI from your fork of the repository.
IMPORTANT: If you have already forked and imported the repository, you can proceed to the next exercise, where you will
create a branch from a tag to load the application files to your PDI. The NeedIt application files are needed to complete the
module.
Fork the Repository

In this section of the exercise, you will create a personal fork of the application repository to use with
Developer Site learning content.
1. In a web browser, open github.com (https://github.com/).

2. If you have a GitHub account, sign in. If not, sign up for a new account.
3. Once signed in, open the NeedIt repository (https://github.com/ServiceNow/devtraining-needit-tokyo).
4. Click the Fork button ( ) to create a copy of the repository in your GitHub account.
5. On the Create a new fork page, deselect the Copy the main branch only option.
6. Select your personal GitHub account as the fork Owner, then click the Create fork button.
7. Verify the URL for your fork of the repository is similar to: <YourGitHubUsername>/devtraining-
application-release.
8. Copy the forked repository's URL.
1. Click the Code button.
2. Make sure the URL contains your GitHub username, not ServiceNow.
3. Make sure HTTPS is selected. If not, select the HTTPS tab in the Clone flyout.
4. Click the Copy to clipboard button ( ).

NOTE: You will use the copied URL to configure the connection to your forked repository in the next section.
Import the Application from the Forked Repository

In this section of the exercise, you will import the application repository into ServiceNow. As part of the
process, you will first create a Credential record for your GitHub account, then you will use Studio to
import the application repository into your PDI.
1. Log in to your PDI as the admin user. If you do not have a PDI, open the ServiceNow Developer Site
(https://developer.servicenow.com) to obtain a Tokyo PDI.
NOTE: See the Personal Developer Instance (PDI) Guide (/dev.do#!/guide/tokyo/now-platform/pdi-guide/personal-
developer-instance-guide-introduction) for instructions on how to obtain a PDI.
2. Create a Credential record for the GitHub connection.
IMPORTANT: Credential records only need to be created once. If you have already created a credential record in
another exercise, please skip this step.
1. Use the All menu to open Connections & Credentials > Credential.
2. Click the New button.
3. In the What type of Credentials would you like to create? list, click the Basic Auth Credentials
link.
4. Configure the Credential record.
Name: GitHub Credentials - <Your github.com Username>

User name: <Your github.com Username>
Password: <Your github.com personal access token>
IMPORTANT: GitHub requires personal access tokens to access repositories from other platforms, like
ServiceNow. A personal access token is used in place of a password when authenticating. See the
Authenticating to GitHub (/dev.do#!/guides/tokyo/developer-program/github-guide/using-servicenow-provided-
application-repositories#authenticating-to-github) section of the GitHub Guide for instructions on creating a GitHub
personal access token.
5. Click the Submit button.
3. Use the All menu to open System Applications > Studio.
4. Studio opens in a new browser tab.
5. In the Select Application dialog, click the Import From Source Control button.
6. In the Import Application dialog, configure the connection to the forked repository.
URL: <URL you copied for your forked version of the repository>
Credential: GitHub Credentials - <Your github.com Username>
Branch: main
NOTE: When you change the Branch value to main, an information message informs you that Use of the default
naming convention is strongly encouraged. The value in the Branch field must exist in the repository. The Developer
Site training repositories all have a main branch, which should be used in place of the default value.
7. Click the Import button.
8. When the application import is complete, click the Select Application button.
NOTE: If the connection fails, you may have entered the ServiceNow repository URL in the URL field instead of the
forked repository URL, or you may have enabled two-factor authentication on your GitHub account. See
Troubleshooting GitHub Issues (/dev.do#!/guide/tokyo/now-platform/github-guide/troubleshooting-github-issues) for
instructions on how to troubleshoot the connection.
9. In the Select Application dialog, click the application to open it for editing in Studio.
IMPORTANT: You will not see any application files in Studio until you successfully create a branch from a tag in the
next exercise.
EXERCISE (4 OF 57)
Exercise: Create a Branch for the Performance

Analytics Module
In this exercise, you will create a branch of the NeedIt application for the Performance Analytics module
that includes the application files used in the module.
NOTE: Before you begin this exercise, you need to have forked and imported the NeedIt repository as described in
Exercise: Fork Repository and Import Application for the Performance Analytics Module.
1. If the NeedIt application is not open in Studio from the previous exercise, open it now.
1. In the main ServiceNow browser window, use the All menu to open System Applications >
Studio.
2. In the Select Application dialog, click the NeedIt application.
2. In Studio, open the Source Control menu and select the Create Branch menu item.
3. Configure the branch.
Branch Name: PerformanceAnalytics

Create from Tag: LoadForPAModule
4. Click the Create Branch button.
5. Click the Close button.

6. To load the application files included in the tag, return to the main ServiceNow browser tab (not
Studio) and click the browser's reload button to refresh the page.
NOTE: If branch creation fails, you may have entered the ServiceNow repository URL in the URL field instead of the
forked repository URL or enabled two-factor authentication on your GitHub account. See the Troubleshooting GitHub
Issues (/dev.do#!/guide/tokyo/now-platform/github-guide/troubleshooting-github-issues) section of the GitHub Guide for
instructions on how to troubleshoot GitHub connection issues.
ARTICLE (5 OF 57)
What is Performance Analytics?

Performance Analytics is a single system of record for collecting and analyzing data. Use Performance
Analytics to track, aggregate, and visualize key performance indicators over time, instead of reporting on
a point in time.
With Performance Analytics, applications can:
Drive performance
Provide actionable insight
Share clear, up-to-date visualizations
ARTICLE (6 OF 57)
Reporting vs. Analytics

The line between reporting and analytics is not always clear. Generally speaking, reporting shows current
state and analytics shows trends. Reports are more suitable for managing records and analytics focuses
on managing processes. You need both.
Reporting
Reporting presents data as discrete facts. Reporting typically focuses on a single set of records to
indicate what has happened to date. Reporting does not predict future results and is not subjective. For
example, reports might answer questions such as:
How many earthquakes have occurred in the month of March?

How many people were injured in earthquakes last year?
When was the most recent earthquake?
Analytics
Analytics explores and uncovers relationships between data sets to answer questions about the data,
processes, or objectives. Analytics are often used to predict future outcomes or to improve processes.
Analytics can be subjective. For example, analytics might answer questions such as:
At what earthquake level does it become unsafe to live in a wooden house?

Does fracking affect earthquake frequency?
Are earthquakes more likely to occur randomly or during certain months, days, or hours?
ARTICLE (7 OF 57)
The Performance Analytics - Premium Plugin

All ServiceNow instances are provisioned with an unlicensed version of Performance Analytics that has
configuration limitations. A license is required to enable the complete set of Performance Analytics
features. Custom applications require activation of the Performance Analytics - Premium
(com.snc.pa.premium) plugin.
The Performance Analytics - Premium plugin's features include:
Create indicators, breakdowns, widgets, and other records

Create interactive filters and use interactive analysis
Create text analytics widgets
Use Performance Analytics with external data
Preserve scores longer than 180 days
Create in-form analytics
Use a Microsoft Excel data source as part of the Report Designer report creation workflow
Schedule Scorecard export to PDF
IMPORTANT: Performance Analytics licenses are required to activate licensed Performance Analytics plugins on
production instances. Licenses are not required to activate Performance Analytics plugins on a development or test
instance.
EXERCISE (8 OF 57)
Exercise: Activate the Performance Analytics -

Premium Plugin
In this exercise, you will activate the Performance Analytics - Premium plugin.
Activate the Performance Analytics - Premium Plugin
1. In the main ServiceNow browser window (not Studio), use the All menu to open System Definition >
Plugins.
2. Use the Search field to find the Performance Analytics - Premium plugin.
3. Click the Install button for the Performance Analytics - Premium plugin.
4. In the Activate Plugin dialog, click the Activate button.
5. When the plugin activation is complete, click the Close & Reload Form button in the Plugin
Activation dialog.
ARTICLE (9 OF 57)
Performance Analytics Data Architecture

The Performance Analytics data layer includes collecting and refining data into key performance
indicators (KPIs). KPIs are also known as indicators or metrics. The data layer is made up of:
Data Collectors: collect data from indicator sources

Indicator Sources: collect filtered data from ServiceNow tables
Indicators: refine data into performance measurements
Breakdown Sources: collect unique values from a filtered set of records
Breakdowns: filter or group indicator scores for detailed analysis
In the visualization layer, dashboards organize Performance Analytics widgets into logical groupings to
provide real-time insight into application data and performance.
When implementing Performance Analytics, define indicators (what to measure) and breakdowns (more in
depth analysis), then collect scores, then visualize the scores and trends.
ARTICLE (10 OF 57)
Data Field Types Drive Analytics

Performance Analytics should be built into an application starting from the data model design. Not all data
types work well with analytics. For example, strings are not a good fit with analytics because users can
enter any value into a string field. Data types typically used in analytics include:
Date/time: Date and Date/time fields are a good fit, because most analytics are time-based. Include
at least one Date/time field in the application data model.
Choice and Reference: Field types with a limited set of values that resolve to sys_ids are a good fit,
because the values can be used to group data.
Integer and Decimal: Numeric values are a good fit, because numeric visualizations convey values
and identify trends.
Boolean: Boolean fields have only two possible values. Data types with a limited set of values are a
good fit, because the values can be used to group data.
When designing the data model, make sure that:
All data required for analytics is collected

Data types are carefully chosen
Fields needed for analytics are mandatory
ARTICLE (11 OF 57)
Indicator Sources
Indicator sources define sets of records from a ServiceNow table that have a common characteristic, such
as the Priority is critical. Indicator sources are used by indicators to calculate scores. Indicator scores are
KPI values. Indicator sources specify a table and the frequency for collecting data.
Indicator sources include filter conditions to limit the record set. Typically, an indicator tracks the data on a
certain date. The indicator source conditions include a date-related filter, such as [Opened] [on] [Today].
Indicators collected less frequently might specify a larger date range, such as [Closed] [on] [This month].
Create indicator sources carefully. Since an indicator source may be used by multiple indicators, indicator
sources are not easily changed.
ARTICLE (12 OF 57)
Creating Indicator Sources

Users with the admin, pa_admin, or pa_data_collector roles can create indicator sources.
To create an indicator source, use the All menu to open Performance Analytics > Sources > Indicator
Sources. Click the New button.
Configure the Indicator Source.
Name: Descriptive name for the indicator source. By convention, but not required, names have the
syntax TableName.DataDescription.
Description: Details about the indicator source such as frequency, where it is used, and the purpose
of the indicator source.
Configure the Validity for Indicator frequency.
Calendars: Select either Standard Calendar or a custom business or fiscal calendar.

Valid for frequency: Choose how often the indicator source collects data. This setting is governed
by the date condition.
Configure the Source of record data.
Report source: Specify an existing data source

(https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_reportanalytics_tokyo_reporti
for data collection. A data source specifies a facts table and filtering conditions.
Facts table: Specify a table or a database view and any conditions for filtering the records for
collection.
Conditions: Conditions for filtering records from the Facts table field. The Conditions field is not used
with Report sources.
Configure the Records view.
List View: Choose a View to use when viewing records in Analytics Hub.
EXERCISE (13 OF 57)

Exercise: Indicator Sources
In this exercise, you will create two indicator sources for the NeedIt application. One indicator source will
use a facts table and the other indicator source will use a report source.
Create an Indicator Source - Facts Table
1. In the main ServiceNow browser window (not Studio), use the All menu to open Performance
Analytics > Sources > Indicator Sources.
3. Configure the indicator source:
Name: NeedIt.ThisMonth
Description: NeedIt requests due this month
Valid for frequency: Monthly
Facts table: NeedIt [x_58872_needit_needit]
Conditions: [When needed] [on] [This month]
Explore the Active NeedIt Requests Report Source

Report sources are filtered sets of table data. If a data set changes, developers only need to modify the
report source and not all indicator sources using the report source. In this part of the exercise, you will
explore the Active NeedIt Requests report source which is already part of the NeedIt application.
1. In the main ServiceNow browser window (not Studio), use the All menu to open Reports >
Administration > Report Sources.
2. Open the Active NeedIt Requests record for viewing.
3. Examine the Active NeedIt Requests report source configuration.
QUESTION: Does the Active NeedIt Requests report source include all records from the NeedIt table or a
subset of records from the NeedIt table?
ANSWER: The Active NeedIt Requests report source is a subset of records from the NeedIt table. Only
active NeedIt requests records are included in the report source.
Create an Indicator Source - Report Source
Analytics > Sources > Indicator Sources.
3. Configure the indicator source:
Name: NeedIt.ActiveWeekly
Description: Active NeedIt requests this week
Valid for frequency: Weekly
Report source: Active NeedIt Requests (NeedIt)
Facts table: This value is automatically populated. Use the default value.
Conditions: This value is automatically populated. Use the default value.
ARTICLE (14 OF 57)
Indicators
Indicators, also known as Key Performance Indicators (KPI), measurements, or metrics, define
performance metrics taken at regular intervals. There are three types of indicators:
Automated: Scores are automatically collected using scheduled data collection jobs
Manual: Scores are entered manually or imported from a third-party source
Formula: Scores are calculated using scores of other indicators
View indicators in dashboard widgets or in Analytics Hub.

ARTICLE (15 OF 57)
Automated Indicators
Automated indicators save scores from an indicator source at a regular frequency such as daily, weekly,
or monthly.
Creating Automated Indicators

Users with the pa_admin, pa_power_user, pa_data_collector, or admin roles can create indicators.
To create an Automated Indicator, use the All menu to open Performance Analytics > Indicators >
Automated Indicators. Click the New button.
Not all fields are visible at all times. Some fields are shown or hidden based on values in other fields.
Some commonly configured fields include:
Name: Give the indicator a descriptive name.

Description: Document the purpose of the Indicator.
Indicator Properties
Calendars: Select either Standard Calendar or a custom business or fiscal calendar. This field is
hidden after the Indicator source is selected.
Frequency: Select a frequency to filter the Indicator source choice list. Only Indicator sources with a
matching frequency are added to the Indicator source choice list. This field is hidden after the
Indicator source is selected.
Direction: Set the preferred behavior of the indicator source scores over time: Maximize (increase),
Minimize (decrease), or None (does not matter).
Unit: Select a unit of measurement.
Key: Set the indicator as a key indicator to use when filtering indicator lists.
Precision: Set the number of decimal places in the indicator score.
DEVELOPER TIP: Indicators round results using banker's rounding or mathematical rounding
(https://docs.servicenow.com/bundle/tokyo-performance-analytics-and-reporting/page/use/performance-
analytics/concept/r_FormulaRounding.html) depending on the value in the Precision field.

Source
Indicator source: Select an indicator source.

Collect records: Select to store sys_ids for individual records when the indictor is collected.
Selecting this check box enables you to drill down to those details in Analytics Hub and widgets by
querying for the attributes when the record is viewed. When available, collected records appear on
the Records tab.
Aggregate: Apply a function when calculating the indicator: Count, Sum, Average, Minimum,
Maximum, Count Distinct.
Value when nil: Set a value to use as the score when no value is collected.
When the Aggregate field value is not set to Count, additional Source fields are available.
Scripted: Select to write a server-side script to perform the aggregation.

Field: Select a field for the aggregation if a script is not used.
Script: Select a script to perform the aggregation. Scripts are defined in Performance Analytics >
Automation > Scripts.
See the ServiceNow docs site for information about configuring the Additional conditions, Access control,
Other, Collect breakdown matrix, Collection periods, and Forecasting
analytics/task/t_CreateAnAutomatedIndicator.html) sections.
EXERCISE (16 OF 57)
Exercise: Create Automated Indicators

In this exercise, you will create automated indicators that use the indicator sources created in an earlier
exercise.
NeedIt: Due Monthly: the count of NeedIt requests with When needed field values aggregated
monthly
NeedIt: Active Weekly: the count of active NeedIt requests by week
Create the NeedIt: Due This Month Automated Indicator

Analytics > Indicators > Automated Indicators.
3. Configure the new indicator source:
Name: NeedIt: Due Monthly
Description: NeedIt: NeedIt requests due monthly measured as a count (#). It is the sum of
the indicator source: NeedIt.ThisMonth.
Frequency: Monthly
Direction: None
Unit: #
Precision: 0
4. Configure the Source section (tab).
Indicator source: NeedIt.ThisMonth
Aggregate: Count
Value when nil: 0
Challenge: Create the NeedIt: Active Weekly Automated Indicator
Create an automated indicator that counts active NeedIt requests by week. The automated indicator
requirements are:
The name must be NeedIt: Active Weekly.

The Description field must contain a meaningful explanation of the the automated indicator.
The automated indicator must count the number of weekly active NeedIt requests using the
appropriate indicator source (Hint: You do not need to create an indicator source.).
The count must be a whole number: 1 and not 1.0.
If there are no active NeedIt requests for a week, the count should be 0.
CHALLENGE SOLUTION:
ARTICLE (17 OF 57)
Breakdowns
Breakdowns filter or group indicator scores for more detailed analysis and groups the scores by the
breakdown elements. For example a country breakdown breaks down the indicator source into individual
country records (breakdown elements). A breakdown source defines the list of breakdown elements.
A breakdown can be used for multiple indicators based on different facts tables. For example a country
breakdown could be used for indicators from the incident, change, and earthquakes fact tables.
Breakdowns are visualized in Analytics Hub and dashboards.
The three breakdown types are:
Automated: A breakdown source determines selectable elements

Manual: Developers define the breakdown elements and the indicator scores for each element
manually instead of using records from a breakdown source
External: A JDBC data source and SQL statement retrieve breakdown elements
ARTICLE (18 OF 57)
Creating Breakdowns
Users with the admin, pa_data_collector, or pa_power roles can create breakdowns.
To create a breakdown, use the All menu to open Performance Analytics > Breakdowns > Create New.
Use the Create a new breakdown wizard to configure the breakdown.
Select the breakdown source panel: Select an indicator and field for the breakdown.
Define the breakdown panel: Select an existing breakdown or create a new breakdown.
Link to indicators panel: Make the breakdown available to one or more selected indicators from the
same table.
Data Collection panel: Collect broken-down scores and snapshots based on the new breakdown for
all of the linked indicators.
Summary panel: Review the breakdown.
When configuration is complete, click the Apply button on the Summary wizard panel to create the
breakdown record.
ARTICLE (19 OF 57)
Breakdown Sources
Breakdown sources specify which unique elements a breakdown contains. A breakdown source is a set of
records from a table or database view. Multiple breakdowns can use the same breakdown source. For
example, instead of seeing all assignment groups for Number of Open Changes, breakdown sources can
limit the element list to just those groups that are part of the change process.
The example shows creating a breakdown using the Country field for the Earthquakes: Monthly New
indicator.
The Define the breakdown wizard panel indicates that a breakdown source is already defined for the
selected indicator and field. This happens when a source table extends another source table or when
breakdown sources are defined for reference fields pointing to the same table. A join is created between
the breakdown source and a facts table on which indicators are defined to do a group by of indicator
scores to breakdown elements.
Recall that a breakdown source can be used by multiple breakdowns. If a breakdown source is already
defined for the same set of records the new breakdown uses, the Breakdown wizard indicates the
overlap.
Use existing: If a mapping exists between a breakdown with the selected breakdown source and a
field on a parent of the indicator table, add the mapping to an existing breakdown.
Create new: If no mapping exists for a parent table, select an existing breakdown or create a
breakdown.
EXERCISE (20 OF 57)
Exercise: Breakdowns
In this exercise, you will create breakdowns for the automated indicators created in a previous exercise.
Request Type
Requested for
Priority
Create a Breakdown by Request type

Analytics > Breakdowns > Create New.
2. Configure the new indicator source.
1. Configure the Select the breakdown source panel to break data down by Request type.
Indicator: NeedIt: Due Monthly
Field: Request type
2. Click the Next button.
3. Configure the Define the breakdown panel to name the breakdown.
Breakdown: NeedIt Request type
5. Configure the Link to indicators panel to link the breakdown to both NeedIt table indicators.
NeedIt: Due Monthly: Selected (checked)
NeedIt: Active Weekly: Selected (checked)
7. Configure the Data Collection panel to collect data from the past 90 days.
Collect data from the past: Selected (checked)
Period: 90 days ago
9. Review the Summary panel containing the breakdown configuration.
3. Click the Apply button.
Create a Breakdown by Requested for

1. In the Create a new breakdown wizard, click the Create another breakdown button.
2. Configure the new indicator source.
1. Configure the Select the breakdown source panel to break data down by Requested for.

Field: Requested for
3. Configure the Define the breakdown panel to name the breakdown.
1. Click the Create new button.

2. Name the breakdown NeedIt Requested for.
3. Make a note of the value in the Breakdown source field.
5. Configure the Link to indicators panel to link the breakdown to both NeedIt table indicators.
NeedIt: Due Monthly: Selected (checked)

NeedIt: Active Weekly: Selected (checked)
7. Configure the Data Collection panel to collect data from the past 90 days.
Collect data from the past: Selected (checked)

Period: 90 days ago
9. Review the Summary panel containing the breakdown configuration.
Challenge: Create a Breakdown by Priority

Create a breakdown by NeedIt request priority. The breakdown requirements are:
Works for the NeedIt: Active Weekly indicator only.

Uses the NeedIt table Priority field.
Collects data from the past 90 days.
QUESTION: On the Define the breakdown wizard panel, why is there no Create new button?
ANSWER: The NeedIt table extends the Task table. The Priority field on the NeedIt table is inherited from
the Task table. A breakdown source already exists for the Priority field from another table, Incident, which
also extends Task and inherits the Priority field. There is no need to create another breakdown source for
the Priority breakdown.
CHALLENGE SOLUTION:
ARTICLE (21 OF 57)
Data Collectors
Data collectors are scheduled jobs that collect data from indicator sources. Create data collectors after
defining indicator sources, breakdown sources, and indicators or data collectors will not return any
results.
Creating Data Collectors

Users with the pa_admin, pa_data_collector, or admin roles can create data collectors.
To create a Data Collector, use the All menu to open Performance Analytics > Data Collector > Jobs.
Click the New button.
Collection parameters
Name: Give the data collector a descriptive name.

Description: Document the purpose of the data collector.
Operator: Select Fixed start to collect data for an absolute time period. Select Relative to collect a
dynamic range of data.
Fixed start: Enter a date to start collecting data. Only available when the Operator field value is
Fixed.
Fixed end: Enter a date to stop collecting data. Only available when the Operator field value is Fixed.
Relative start: Enter the number of days, weeks, or months (set in the Relative start interval) for the
relative start. This determines how far back scores are retrieved. Available only when the Operator
field value is Relative.
Relative start interval: Select days ago, weeks ago, or months ago to set the frequency for the
interval. Only available when the Operator field value is Relative.
Relative end: Enter the number of days, weeks, or months (set in the Relative start interval) for the
relative end. This determines when to stop collecting scores. Available only when the Operator field
value is Relative.
Relative end interval: Select days ago, weeks ago, or months ago to set the frequency for the
interval. Only available when the Operator field value is Relative.
Job parameters
Run as: Select the user that runs the scheduled job. The data collection job does not check Access
Controls for the user unless there is a scripted indicator or scripted breakdown.
Run as tz: Select the time zone that queries use when they are executed from the job. By default the
System time zone is used.
Active: When selected, the data collection occurs at the scheduled date and time.
Run: Choose the frequency to execute the data collector.
Time/Day/Repeat Interval/Starting: These fields depend on the value in the Run field. All time fields
use a 24-hour clock (HH:mm:ss): 23:00:00 = 11:00:00 PM.
Collect: Select Scores only, Text analytics only, or Both scores and text analytics. Data collection
jobs have separate steps for collecting scores and collecting text analytics.
Conditional: When selected, write a server-side script to specify a condition for running the data
collector.
DEVELOPER TIP: To run a data collector on the last day of the month, configure a monthly data collector set to run on
day 31. The data collector will run on the last day of the month, even for months with fewer than 31 days.
DEVELOPER TIP: Create an admin user to Run the data collector which has the Web service access only setting
selected. The Web service access only configuration does not allow the user to log in to the ServiceNow user interface.
Adding Indicators to Data Collectors

After a data collector is saved, the related lists are added to the form. On the data collector record, scroll
to the Indicators related list (tab). Click the Edit... button. Select indicators in the Collection slushbucket
and add them to the Indicators List slushbucket.
Click the Save button.

Indicators can be added to a data collector at any time. The data collector collects new indicators
beginning with the next collection period. For historical data collectors, execute the data collector to
collect data for new indicators.
ARTICLE (22 OF 57)
Historical Data Collectors

Performance Analytics collects scores from indicator sources on an ongoing basis. To analyze data that
existed prior to setting up Performance Analytics, use a historical data collector to collect scores and
snapshots for existing records. Historical data collectors are data collectors with a special configuration.
Run historical data collection when:
Performance Analytics is first set up for an application

Indicator sources are created
Indicators are created
Configuring Historical Data Collectors

Historical data collectors require specific values in the Run fields. The example shows the required fields
for a historical data collector.
Collection parameters
Operator: Relative or Fixed.

Relative start: Enter the number of days, weeks, or months (set in the Relative start interval) for the
relative start. This determines how far back, scores are retrieved.
Relative start interval: Select days ago, weeks ago, or months ago to set the frequency for the
interval.
Relative end: Enter the number of days, weeks, or months (set in the Relative start interval) for the
relative end. This determines when to stop collecting scores.
Relative end interval: Select days ago, weeks ago, or months ago to set the frequency for the
interval.
Job parameters
Run: On Demand.
The Run as, Run as tz, Collect, and Conditional fields can also be configured for historical data collectors.
Data collectors collect data daily even if there are indicators in the job that are based on indicator sources
with a Valid for frequency value that is not daily, such as monthly or weekly.
NOTE: The Active field does not have to be selected for historical data collectors. Clicking the Execute Now button for an
On demand scheduled job executes the schedule job even if the Active field is not selected.
Running a Historical Data Collector

To collect historical data, click the Execute Now button in the Data Collector record. The Execute Now
button is only available after the record has been saved. The data collector executes a scheduled job that
retrieves records and calculates scores.
EXERCISE (23 OF 57)
Exercise: Create NeedIt Records

Performance Analytics needs data in order to calculate scores and visualize data. In this exercise, you will
use a script to create random records for the NeedIt table.
Make the NeedIt When needed field date Business Rule Inactive
The NeedIt When needed field date Business Rule prevents creating NeedIt records with When needed
field values in the past. In this part of the Exercise, you will make the NeedIt When needed field date
Business Rule inactive so you can create NeedIt records with When needed field values in the past.
1. If the NeedIt application is not still open in Studio from a previous exercise, open it now.
Studio.
2. In the Select Application dialog, click the NeedIt link to open the NeedIt application for editing.
2. Deactivate the NeedIt When needed field date Business Rule.
1. In Studio, use the Application Explorer to open Server Development > Business Rules >
NeedIt When needed field date.
2. Deselect (uncheck) the Active configuration field.
3. Click the Update button.
Use a Scheduled Script Execution to Generate NeedIt Records
1. In Studio, use the Application Explorer to open Server Development > Scheduled Script
Executions > Generate Random NeedIt Records.
2. Examine the value in the Run field to see when the Scheduled Script Execution runs.
3. Read through the script and the script comments to determine what the script does.
QUESTION: How many NeedIt records does the script create?

ANSWER: The recordsToMake variable in line 2 of the script sets the number of NeedIt records to
create when the script executes. The sample script is set to generate zero records by default in case
the script is accidentally executed.
4. Modify the value of the recordsToMake variable to generate 1200 NeedIt records.
var recordsToMake = 1200;
Create NeedIt Records

1. In the main ServiceNow browser window (not Studio), use the All menu to open NeedIt > All.
2. Make a note of the number of existing NeedIt records. There may be no NeedIt records on your
instance.
3. Generate NeedIt records.
1. Return to Studio.
2. In the Scheduled Script Execution tab, click the Execute Now button.
4. Verify the records were created.
1. Return to the main ServiceNow browser window and refresh the list of NeedIt records. It may
take a few seconds for all of the NeedIt records to be created.
2. When all 1200 NeedIt records have been created, browse through the records to make sure the
field values were set by the script as expected.
Make the NeedIt When needed field date Business Rule Active
1. Return to the NeedIt When needed field date Business Rule tab in Studio.
2. Select (check) the Active configuration field.
EXERCISE (24 OF 57)
Exercise: Historical Data Collector

In this exercise, you will create and run a historical data collector for NeedIt records from the past six
months plus the current month.
Create and Run a Historical Data Collector for the NeedIt Indicators
Analytics > Data Collector > Jobs.
3. Configure the historical data collector:
Name: NeedIt Historical Data

Description: Data Collector for NeedIt Historical data. Collects 6 months of data including
the current month.
Operator: Relative
Relative start: 6
Relative start interval: months ago
Relative end: 1
Relative end interval: days ago
Run: On Demand
Collect: Scores only
4. Click the Additional actions menu ( ) and select the Save menu item.
5. Add indicators to the historical data collector.

1. Scroll to the Indicators related list (tab) and click the Edit... button.
2. In the Collection slushbucket, select NeedIt: Active Weekly and NeedIt: Due Monthly.
3. Click the Add button ( ) to move the indicators to the Indicators List slushbucket.
4. Click the Save button.
6. Click the Execute Now button to collect data for the NeedIt indicators.
View the Job Logs

1. In the NeedIt Historical Data data collector record, switch to the Job Logs related list (tab).
2. You may need to refresh the list. Right-click the Job logs header and select the Refresh List menu
item.
3. Examine the record for the data collection. The state should be Collected or Collected with
warnings. The warnings are caused when the data collector tries to collect data farther back than the
data in the indicator.
EXERCISE (25 OF 57)
Exercise: Daily Data Collector

In this exercise, you will create a daily data collector for NeedIt records.
Create a Data Collector for the NeedIt Indicators
3. Configure the data collector:
Name: NeedIt Daily

Description: Daily data collector for NeedIt data.
Operator: Relative
Relative start: 1
Relative start interval: days ago
Relative end: 1
Relative end interval: days ago
Run: Daily
Collect: Scores only
Time: 01:00:00
5. Add indicators to the data collector.
1. Scroll to the Indicators related list (tab) and click the Edit... button.
2. In the Collection slushbucket, select NeedIt: Active Weekly and NeedIt: Due Monthly.
3. Click the Add button ( ) to move the indicators to the Indicators List slushbucket.
ARTICLE (26 OF 57)
Analytics Hub
Analytics Hub is the user interface for assessing, comparing, and predicting the performance of indicators
over time. Analytics Hub displays data for a single indicator.
Visualizing Data in Analytics Hub

After collecting data with a historical data collector, view an indicator in Analytics Hub to visualize the
collected data. Use the All menu to open Performance Analytics > Analytics Hub. Open an indicator.
To view aggregate data such as the monthly sum of scores, apply a time series such as By week
SUM. The menu shows only the timeframes that are meaningful for the indicator frequency.
To view the score at a certain date, click that date. After selecting a date, add a comment, target, or
threshold at that date.
To change the period for which the chart is drawn, select one of the fixed time frames, specify
specific from and to dates, or drag the date selector in the time series.
To see the records used by the chart, click the Show Records button.
To change the chart type, or to hide or display targets, thresholds, or comments, use the chart
options tools.
To temporarily filter data out of the chart, drag a handle to highlight the data to filter out. In the
example, the highlighted data from 2009 to half of 2013 is filtered out of the chart.
Publishing on Analytics Hub

To see indicators in the Performance Analytics > Analytics Hub module, the indicator must be
published on Analytics Hub.
Use the All menu to open Performance Analytics > Indicators > Automated Indicators. Set the
Publish on Analytics Hub value to true.
Indicators with a Publish on Analytics Hub value of true are accessible in the Analytics Hub module.
NOTE: If an indicator is published to Analytics Hub and users cannot see it in the Analytics Hub module, check the roles
assigned to the indicator. Access controls might be denying access to the users.
ARTICLE (27 OF 57)
Analytics Hub - Breakdowns
Open the Breakdowns menu ( ) or use the Search for breakdowns and elements field to select a
breakdown to visualize for the indicator. If no breakdowns are configured for an indicator, the Breakdowns
panel indicates that no breakdowns are available.
The Breakdown pane lists the breakdown elements and their scores. The chart shows the breakdown
element data.
ARTICLE (28 OF 57)
Analytics Hub - Compare

Use the Compare tab to compare the scores of an indicator on two measurement periods.
Click the Selected period date and the Comparison period date to select a period.
If the scores refer to a count, information about the comparison is available as scores and Venn diagrams:
The number of records that have moved out or left the indicator since the selected period.
The number of records that are shared by the indicator in both periods. The records are in the
indicator in both the selected period and the comparison period.
The number of records that moved in or that were added to the indicator in the comparison period.
The number of records in the comparison period.
ARTICLE (29 OF 57)
Analytics Hub - Comments

Use comments to add annotations to a chart. Comments are useful for calling out important, critical, or
anomalous data.
To add a comment to a chart, click in the chart to select a date.

Click the Comments icon in the Analytics Hub header (not in the chart toolbar), then click the New
Comment link.
Enter a comment, then click the Save button.
To view comments on a chart, hover over the comment indicator.

Click the Comments icon in the chart toolbar to toggle the visibility of comments on the chart.
EXERCISE (30 OF 57)
Exercise: Analytics Hub

In this exercise, you will explore Analytics Hub using the NeedIt application indicators.
Examine the NeedIt: Due Monthly Indicator in Analytics Hub
1. Open the NeedIt: Due Monthly indicator.
2. Open the NeedIt: Due Monthly automated indicator.
3. Click the Show Analytics Hub related link.
2. Examine the Chart section.
1. Use the time series selector to display six months of data on the chart.
3. Hover over the chart line to get the exact count of NeedIt records due each month.
4. Add a comment to the chart.
1. Click anywhere on the chart line to select a data point.
2. Click the Comments icon in the Analytics Hub header (not in the chart toolbar).
3. In the Comments panel, click the New Comment link.
4. Enter the comment of your choice, then click the Save button.
5. Close the Comments panel.
5. View the comment on the chart.
1. Hover over the comment indicator in the chart to see the comment.
2. Close the Comments panel.
3. Disable the comment indicators in the chart by clicking the Comment icon in the chart
toolbar.
3. Examine the indicator breakdowns.
1. Click the Breakdowns menu ( ) to open the Breakdown panel.
2. Click the NeedIt Request type breakdown to view the breakdown elements and scores.
3. Examine the breakdown elements and scores.
4. View the breakdown data on the chart.
5. Switch to the NeedIt Requested for breakdown. View the breakdown elements and scores.
6. Click the Close button to close the Breakdowns panel.

4. Examine the NeedIt Records for the selected period.
1. Click the Show Records button.
2. Examine the bottom of the Records list to see how many NeedIt records are due in the selected
time period.
3. Use the Previous Period or Next Period icons to pick a different month.
4. Examine the bottom of the Records list again to see if the number of records in the list changed.
5. Click the currently selected month in the score pane to open the calendar picker. Use the
calendar picker to select a different month.
QUESTION: Why are some months in black text in the calendar picker and other months are in gray
text?
ANSWER: The historical data collector collected data for the past six months plus the current month.
The months in black text are the months for which Performance Analytics has data.
6. Click the Hide Records button to close the list of records.
5. Compare data from two different months.
1. Switch to the Compare tab.

2. Use the calendar picker or the Preview period/Next Period buttons to select the two periods of
your choice to compare.
3. Examine the scores for the selected period and the comparison period. Are there more NeedIt
requests due in the comparison period than the selected period?
4. Examine the Venn diagrams. Did more records move out or move in for your data?
5. Click a section in one of the Venn diagrams to update the records list.
6. Switch to the Overview tab.
1. If the chart is not displaying six months of data, use the time series selector to select 6
MONTHS.
2. Use the chart toolbar to enable/disable Labels, Year over year, Score, Change, Change %,
and Visualization. For each setting, examine the chart to see the impact of the option.
NOTE: For lower screen resolutions, some of the chart tools might be collapsed into a More icon. Click the More
icon ( )to see the complete set of tools.
Challenge - NeedIt: Active Weekly Score

View the NeedIt: Active Weekly automated indicator in Analytics Hub. Notice that the line showing the
number of weekly active NeedIt requests is flat.
Modify the NeedIt: Active Weekly automated indicator to add the Additional condition:
[When needed] [before] [This week]
Execute the NeedIt Historical Data data collector again.
View the updated NeedIt: Active Weekly indicator in Analytics Hub. Examine all of the sections.
CHALLENGE SOLUTION:
Publishing on Analytics Hub

To see indicators in Analytics Hub, the indicators must be published to Analytics Hub.
1. Use the All menu to open Performance Analytics > Indicators > Automated Indicators.
2. Use the Search field to search for the two NeedIt indicators.
1. Set the Search field choice list to Name.

2. In the Search field, type *needit.
3. Press the <return> or <enter> key on the keyboard.
3. If the Publish on Analytics value is false for the two NeedIt indicators, change it to true.
1. Double-click in the Publish on Analytics Hub field.

2. Use the choice list to set the value to true.
3. Click the Save button ( ).
4. Verify the NeedIt indicators are accessible in Analytics Hub.
1. Use the All menu to open Performance Analytics > Analytics Hub.
2. Use the Search field to find the two NeedIt indicators.
3. Open one of the NeedIt indicators in Analytics Hub.
ARTICLE (31 OF 57)

Targets
Targets are goals an organization wants to achieve using an application. Use targets to visualize the
difference between the desired score and indicator score.
A target can be personal or global. A personal target is visible only to the user who created it and appears
as a light line on a chart. A global target is visible to all users and appears as a dark line on a chart or a
time series widget.
Enable targets on Analytics Hub charts by clicking the Target icon in the chart toolbar. To see target
values, hover over the chart data.
ARTICLE (32 OF 57)
Creating, Editing, and Deleting Targets

Users with the pa_viewer role can create personal targets. Users with the pa_target_admin or admin roles
can create global targets.
Creating Targets in Analytics Hub

Targets are applied beginning from the measurement period selected until the next target. Select a
measurement period with the calendar picker then click the Targets icon in the Analytics Hub header (not
the chart toolbar).
Click the New Target link in the Targets pane. Select either Global or Personal. Configure the target.
Set target as an improvement of the baseline: Select to configure a target value that is relative to
a baseline value
Target Calculation: Select how to calculate the Target value from the baseline
Direction: Select if the target value should be an increase or decrease from the baseline value
Percentage (%) / Units of the KPI: Select the value to increase or decrease from the baseline
Baseline: Select the source for the baseline value
Target: Set a value to reach
Start date: Set a date to start applying the target
Review date: Set date to review the applied target for adjustment
Editing and Deleting Targets

To edit or delete a target, open the Targets pane in Analytics Hub.
Click the target in the Targets list to edit a target. Click the Delete target icon to delete a target.
ARTICLE (33 OF 57)
Target Notifications
When a target is reached, Performance Analytics generates a notification. For personal targets, the target
owner automatically receives the notification. Developers must configure recipients for global targets.
Configure Target Notification Recipients

To configure who receives global target notification, open Performance Analytics > Indicators >
Targets. Open a target for editing by clicking the Preview record icon ( ) for the target, then click the
Open Record button.
In the Users related list, click the Edit... button.
NOTE: Personal target records do not have a Users related list.
Move the users to notify from the Collection slushbucket to the Users List slushbucket.
EXERCISE (3 4 OF 57)
Exercise: Targets
In this exercise, you will set personal and global targets for the NeedIt indicators.
Set Targets for the NeedIt: Due Monthly Indicator
1. Open the NeedIt: Due Monthly indicator in Analytics Hub.
OR
2. Use the calendar picker to set the time period to six months ago. The date you select will be
different than the date shown in the example.
3. Use the time series selector to set the chart to show All data.
5. Add a global target.
1. Click the Target icon in the Analytics Hub header to add a target.
2. Click the New Target link.
3. Configure the target.
Global: Selected
Target: 150
6. Add a personal target.
Personal: Selected
Target: 200
7. If the targets are not visible, click the Target button on the chart toolbar to see the targets on the
chart.
QUESTION: How can you tell the global target from the personal target when looking at the Analytics Hub
chart?
ANSWER: The personal target is a thin, light gray line on the chart. The global target is a thick, dark gray
line on the chart.
Challenge
Set a personal and a global target for the NeedIt: Active Weekly indicator using the values and time series
of your choice.
ARTICLE (35 OF 57)
Thresholds
Thresholds define a normal range of scores for an indicator. Thresholds send a notification when certain
events occurs, such as when a score reaches an all-time high or low.
A threshold can be personal or global. A personal threshold is visible only to the user who created it and
appears as a light grey dotted line on a chart. A global threshold is visible to all users and appears as a
dark grey dotted line on a chart or a time series widget.
ARTICLE (36 OF 57)
Creating, Editing, and Deleting Thresholds

Users with the pa_viewer role can create personal Thresholds. Users with the pa_threshold_admin or
admin roles can create global thresholds.
Creating Thresholds
Thresholds are applied to all data unless a time series is selected. After selecting a measurement period,
click the Thresholds icon in the Analytics Hub header (not the chart toolbar).
Click the New threshold link. Select either Global or Personal. Use the Threshold choice list to choose:
All time high

All time low
Less than
More than
For Less than and More than, enter a Threshold value.
Enable targets on Analytics Hub charts by clicking the Thresholds icon in the chart toolbar.
Editing and Deleting Thresholds
To edit or delete a threshold, open the Thresholds panel in Analytics Hub.
To edit a threshold, click the threshold in the threshold list. To delete a threshold, click the Delete
threshold icon.
ARTICLE (37 OF 57)
Threshold Notifications
When a notification threshold is reached, Performance Analytics generates notifications:
PA Threshold Reached: Sends a notification for a specific indicator threshold to a set of users
PA Thresholds Notification: Sends a notification with an overview of all indicators for which a
threshold is reached
Configure PA Threshold Reached Recipients

To configure who receives the PA Threshold Reached notification, open Performance Analytics >
Indicators > Thresholds. Open a threshold for editing. Scroll to the Users related list and click the Edit...
button. Move the users to notify from the Collection slushbucket to the Users List slushbucket.

Configure PA Thresholds Notification Recipients
To configure who receives the Configure PA Thresholds Notification, open System Notification > Email >
Notifications. Open the PA Thresholds Notification record. The PA Thresholds Notification record must
be edited in the Global scope. Click the link in the information message to switch to the Global scope.
Configure the recipients in the Who will receive section.
Learn more about the Who will receive

section in the Notifications
module.
EXERCISE (38 OF 57)
Exercise: Thresholds
In this exercise, you will set a personal and global threshold for the NeedIt indicators.
Set Thresholds for the NeedIt: Due Monthly Indicator
1. Open the NeedIt: Due Monthly indicator in Analytics Hub.
OR
2. Open the NeedIt: Due Monthly scorecard.
2. Use the calendar picker to set the time period to six months ago. The date you select may be
different than the date shown in the example.
3. Use the time series selector to set the chart to show All data.
5. Click the Thresholds icon to add a threshold.
6. Click the New Threshold link.
7. Configure the threshold.
Global: Selected
Threshold: All time low
9. Add another threshold.
Personal: Selected
Threshold: More than
More than value: 225
11. Close the Thresholds pane.
12. If you do not see the thresholds on the chart, click the Thresholds icon in the charts toolbar.
Examine the thresholds on the chart.
QUESTION: How can you tell the global threshold from the personal threshold when looking at the chart?
ANSWER: The personal threshold is a dotted, light gray line on the chart. The global threshold is a
dotted, dark gray line on the chart.
Challenge
Set a personal and a global threshold for the NeedIt: Active Weekly indicator using the values and time
series of your choice.
ARTICLE (39 OF 57)
Scores Forecasts
Using existing trends, Performance Analytics can forecast future data in time series widgets and detailed
scorecards. Forecast data appears as a dotted line on charts.
Creating Forecasts
Configure the forecast in the Forecasting section of an indicator record. The number of data points
included in the forecast depends on the indicator frequency, and the number of Periods to forecast
configured on the indicator.
Forecast method used: Select None, Auto, Linear, Drift, Naive Seasonal, Naive Seasonal Drift, STL
(Seasonal Trend Loess), or Random Forest (https://docs.servicenow.com/bundle/tokyo-performance-
analytics-and-reporting/page/use/performance-analytics/concept/c_ForecastingData.html#forecast-methods).
Periods to forecast: Number of future periods to forecast. Period length depends on the indicator
frequency. For daily indicators, a period is defined as 7 days, for weekly as 13 weeks, for monthly as
12 months, and for yearly as 4 years. See the Forecast periods table
analytics/concept/c_ForecastingData.html).
Forecast lower limit: The lowest possible value for the forecast data. Scores lower than the
forecasted lower limit are displayed at this value.
Forecast upper limit: The highest possible value for the forecast data. Scores higher than the upper
limit are displayed at this value.
Forecast based on: Select All Scores, Previous Periods, or Fixed Start.
Periods: Select the number of periods for the Forecast based on field. Only available for Previous
Periods forecasts.
Start date: Use the calendar to select a start date for the forecast. Only available for Fixed Start
forecasts.
DEVELOPER TIP: Auto is the recommended setting for the Forecast method used field. The auto setting forecasts using
all six forecast methods then selects the method with the best fit.
Viewing Forecasts
To view a forecast on a chart in Analytics Hub, click the Forecast button on the charts toolbar. If no
forecast is defined in the indicator record, Analytics Hub does an Auto forecast for the indicator when a
user enables forecasts in the chart.
EXERCISE (40 OF 57)
Exercise: Forecasting
In this exercise, you will configure and enable forecasting for the NeedIt indicators.
Configure the Forecast for the NeedIt: Due Monthly Indicator

2. Switch to the Forecasting section (tab).
3. Configure the forecast.
Forecast method used: Auto
Periods to forecast: 3
Forecast based on: Previous Periods
Periods: 1
Enable and View the Forecast
2. If not enabled, enable the forecast on the chart by clicking the Forecast icon in the chart toolbar.
3. Examine the forecast on the chart. What trend does the forecast predict? Is the number of NeedIt
requests due monthly expected to increase, decrease, or stay the same?
Challenge
Configure forecasting for the NeedIt: Active Weekly indicator. The requirements are:
Automatically determined forecast

Forecast for two periods
Lower forecast limit of 100
Upper forecast limit of 500
Forecast based on all scores
View the forecast on the NeedIt: Active Weekly indicator chart in Analytics Hub.
CHALLENGE SOLUTION:
The NeedIt records were randomly generated. Your NeedIt: Active Weekly scores and forecast line may
have different values than the example. Your Forecast configuration should match the configuration in the
example.
NeedIt: Active Weekly Forecast Configuration

NeedIt: Active Weekly Forecast in Analytics Hub
ARTICLE (41 OF 57)
Performance Analytics Dashboards

Dashboards are a drag and drop canvas for gathering visualizations used regularly into a single location
organized by tabs and widgets. Design application dashboards with multiple visualizations that together
convey meaningful information to application users.
This section of the module explains how to add Performance Analytics widgets to dashboards. A more
comprehensive discussion of dashboards
is available in the Data Visualization module
DEVELOPER TIP: Create dashboards for each of the application personas, such as service worker/fulfiller,
service/process/app owner, executive, and customer/end user.
ARTICLE (4 2 OF 57)
Creating Performance Analytics Dashboards

To create a Performance Analytics dashboard, open Performance Analytics > Dashboards. Click the
Create a dashboard button. Configure the dashboard.
Name: Name of the dashboard that appears in the dashboard selector.
Group: Where to place the dashboard in the dashboard selection list. The baseline groups are Agent
Intelligence, CMDB Dashboard, Flow Designer, Incident, Platform, Problem, SLA, and Other. If a
group is not selected for a dashboard, then it will be automatically placed in the Other group.
Order: Order in which the dashboard appears on the dashboard landing page and pick lists. Order is
ascending from low numbers to high. The Admin Console, Flow Designer Operations, and Analytics
Usage Overview dashboards always take precedence over user-created dashboards.
Restrict to roles: Role required to access the dashboard.
Disable multiple element selection: Restrict users to selecting only one element of a breakdown
when filtering.
Active: Select to make the dashboard usable in runtime.
Owner: ServiceNow user who owns the dashboard record.
Save (not Submit) the dashboard record, then click the View Dashboard Related Link to add widgets and
tabs to the dashboard.
DEVELOPER TIP: Create a group for applications so application dashboards appear together on the dashboards list.
ARTICLE (43 OF 57)
Adding Performance Analytics Dashboard

Widgets
To add a Performance Analytics widget to a Performance Analytics dashboard, click the Add Widgets
icon ( ).
In the Add Widgets choice list, select the Performance Analytics item.
Select the Performance Analytics data type for the widget, such as Breakdown or Score.
Choose from the existing list or create a #New <PA element>, for example, #New Score or #New
Breakdown.
In the widget preview, click the Add button. The Click here link is not clickable in the preview.
ARTICLE (4 4 OF 57)
Configuring Performance Analytics Dashboard

Widgets
Configure a new Performance Analytics widget by clicking the Click here link.
Configure the widget. The configuration field values depend on the widget type and visualization.
Click the Submit button.
Click anywhere in the widget to open the indicator in Analytics Hub.
Add additional widgets to organize, summarize, and present data to convey information in a meaningful
way. Dashboards help application developers and users:
Identify trends
Monitor field values
Look for outlying data
Track work
View progress
EXERCISE (45 OF 57)
Exercise: Performance Analytics Dashboard

In this Exercise, you will create a dashboard for the NeedIt: Due Monthly indicator.
Create a Dashboard
Analytics > Dashboards.
2. Click the Create a dashboard button.
3. Configure the dashboard.
Name: NeedIt Application
Order: 10
4. Create a group for the dashboard.
1. In the Group field, click the Lookup using list icon ( ).

2. In the Dashboard Groups dialog, click the New button.
3. Configure the group.
Name: NeedIt
Order: 1
4. Click the Submit button in the Dashboard Group window.
5. In the Dashboard New record form, click the Additional actions menu ( ) and select the Save
menu item.
Add a Performance Analytics Score Widget to the Dashboard

1. In the dashboard form, click the View Dashboard related link.
2. Add a Score widget to the dashboard.
1. Click the Add Widgets icon ( ).
2. In the Widget Category choice list, select Performance Analytics.
3. In the list of Performance Analytics widget types, select the Score widget type.
4. On the list of scores, click #New Score.
5. Click the Add button.
3. Click the Click here link in the widget to configure the #New Score widget.
Name: NeedIt Requests Due this Month
Description: Score for NeedIt requests due this month.
Type: Score
Visualization: Dial
QUESTION: Using the NeedIt Requests Due this Month score widget, how can you open the NeedIt: Due
Monthly indicator in Analytics Hub?
ANSWER: Click in the NeedIt Requests Due this Month score widget to open the NeedIt: Due Monthly
indicator in Analytics Hub.
Add a Performance Analytics Time Series Widget to the Dashboard
1. Add a Time Series widget to the dashboard.
2. In the list of Performance Analytics widget types, select the Time Series widget.
3. On the list of time series, select #New Time Series.
2. Click the Click here link to configure the #New Time Series widget.
Name: NeedIt Requests this Year by Month
Description: Line chart of NeedIt requests this Year by Month
Type: Time Series
Visualization: Line Chart
3. Configure the Date Settings section (tab).
Period: 1y
Show date range selector: Selected (checked)
4. Configure the Display Settings section (tab).
Show target: Selected (checked)
Show thresholds: Selected (checked)
QUESTION: Although the NeedIt Requests this Year by Month time series widget is configured to display
one year#singleQuotes worth of data, you may see less than twelve months of data in the widget. Why
would you see less than twelve months of data?
ANSWER: The script used to generate random data generated only six months of data. Performance
Analytics does not display scores for months with no data.
Add a Performance Analytics Breakdown Widget to the Dashboard

1. Add a Breakdown widget to the dashboard.
2. In the list of Performance Analytics widget types, select the Breakdown widget.
3. On the list of breakdowns, select #New Breakdown.
2. Click the Click here link to configure the #New Breakdown widget.
Name: NeedIt Requests Due this Month by Request Type
Description: Donut chart showing NeedIt requests due this month by Request type
Breakdown: NeedIt Request type
Type: Breakdown
Visualization: Donut
Sort on: Value
Show visualization selector: Selected (checked)
Show breakdown selector: Selected (checked)
5. Examine the NeedIt Requests Due this Month by Request Type widget.
1. Use the Visualization choice list to change the visualization from Donut to the visualization of
your choice.
2. Use the Breakdown selector to change the Breakdown to NeedIt Requested for.
Change the NeedIt Dashboard Layout
1. On the dashboard, click the Configuration icon ( ).
2. In the Apply Quick Layout section, click the two column layout with a 1/3-width column on the left and
2/3-width column on the right.
3. Drag the widgets to rearrange the dashboard.
1. The first row, first column contains the NeedIt Requests Due this Month widget. The first row,
second column contains the NeedIt Requests this Year by Month widget.
2. The second row, first column contains the NeedIt Requests Due this Month by Request Type
widget.
EXERCISE (4 6 OF 57)
Challenge: Add a Dashboard Tab

In this challenge, you will add a tab to the NeedIt Application dashboard for the NeedIt: Active Weekly
indicator.
Your Mission
Add a tab to the NeedIt Application Dashboard to contain widgets for the NeedIt: Active Weekly
indicator.
The tab title for the new tab should be Active Weekly.
The tab title for the original tab should be Due Monthly.
The tab should contain at least four Performance Analytics widgets.
Use the widgets of your choice but all must be configured to use the NeedIt: Active Weekly
indicator.
Use at least two different Performance Analytics widget types.
The tab layout can be anything except the default layout. Choose a layout that displays the widgets
you created so they are easy to read. For example, do not make time series widgets too narrow in
the layout.
There is no right or wrong answer to this challenge. Use your creativity and skills with Performance
Analytics to create a meaningful dashboard tab for the indicator.
HINT: Use the Configuration icon ( ) to add a tab
(https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_reportanalytics_tokyo_reporting_and_analytics/app_store_
to a dashboard.
ARTICLE (47 OF 57)
Performance Analytics Bucket Groups (Optional)

Typical traffic pattern charts for a store are available on the Internet:
In a traffic pattern chart, the number of visits to a store is counted and sorted into hourly buckets. Using
the traffic pattern chart, shoppers can decide the best time to visit the store.
In Performance Analytics, a bucket group is a special type of breakdown source that divides values
returned by a script or field into discrete buckets. Bucket groups are useful for drawing conclusions that
may not be obvious when looking at the raw data. The Earthquakes by Day of Month - 12 Month Sum
widget shows that the majority of earthquakes in the last year occurred on the 5th or 6th of the month.
The widget also shows that there are no days of the month, in the last 12 months, without earthquakes.
There is no "safest day".
Use bucket groups when the breakdown elements for grouping scores are not available in a table in the
application. Developers can create the breakdown elements and use the breakdown elements in
breakdown sources.
The steps for working with bucket groups are:
1. Create a bucket group or choose an existing bucket group.

2. Create a breakdown source that uses the bucket group.
3. If no field is available to group scores, write a breakdown mapping script to sort the breakdown
source data into the buckets.
4. Create a breakdown from the breakdown source and map to the script.
5. Add the breakdown to an indicator.
6. Run the historical data collector job for the indicator to calculate scores for the new breakdown.
7. Create a widget to visualize the data or examine the data on a scorecard.
ARTICLE (4 8 OF 57)
Creating Bucket Groups (Optional)

Bucket groups define ranges of values to use when grouping scores. Bucket groups are reusable. Before
creating a bucket group, check for an existing bucket group to use.
To create a bucket group, open Performance Analytics > Breakdowns > Bucket Groups. Click the
New button.
Configure the bucket group.
Name: Descriptive name of the bucket group.

Description: Explanation of the purpose of the bucket group.
Buckets: Define the buckets.
Name: Name of the bucket. The name appears on scorecards and widgets.
Start: Starting value for the bucket.
End: Ending value for the bucket.
NOTE: Bucket groups are inclusive of the Start value and exclusive of the End value.
ARTICLE (49 OF 57)
Bucket Group Breakdown Source (Optional)

To create a breakdown source, use the All menu to open Performance Analytics > Sources >
Breakdown Sources. Click the New button.
Bucket group breakdown sources have a required configuration.
Facts table: Buckets [pa_buckets]

Field: Sys ID
Condition: [Bucket group] [is] [<Name of bucket group>]
ARTICLE (50 OF 57)
Creating Breakdown Scripts (Optional)

A breakdown script is a server-side script that returns the data to sort into the breakdown group buckets.
Breakdowns use breakdown scripts when there is no direct mapping of an existing Facts table field to the
buckets.
To create a breakdown script, open Performance Analytics > Automation > Scripts. Click the New
button.
Configure the script.
Name: Descriptive name of the script

Description: Describe what the script does
Facts table: Indicator source for the script
Fields: List of fields from the Facts table to use in the script
Script: Server-side script to return a field from the Facts table
In the script, current is a record from the Facts table. The last line of the script must return a number to
use when grouping scores into buckets.
ARTICLE (51 OF 57)

Breakdown and Mapping (Optional)
Bucket group breakdowns map to the bucket group's breakdown source. The mapping script sorts
breakdown data into buckets.
Creating a Bucket Group Breakdown

Create an automated breakdown for the bucket group. Set the Breakdown source field value to the bucket
group breakdown source.
Save the Breakdown record.
Creating a Breakdown Mapping

In the breakdown record, switch to the Breakdown Mappings related list and click the New button.
Configure the breakdown mapping.
Facts table: Facts table for the script or field.

Field: Field to map to the buckets. Only available when Scripted is not selected.
Script: Script to return the data to map to the buckets. Only available when Scripted is selected.
Scripted: Select to apply a script to the mapping. If not selected, specify a field to map.
ARTICLE (52 OF 57)

Adding the Breakdown to an Indicator (Optional)
To add a breakdown to an indicator, open Performance Analytics > Indicators > Automated
Indicators. Open an indicator for editing or create an indicator. Click the Edit... button in the Breakdowns
related list. Use the Add button to move the bucket group breakdown from the Collection slushbucket to
the Breakdowns List slushbucket.
NOTE: To calculate values for the new breakdown, run the historical data collector job for the indicator.
EXERCISE (53 OF 57)
Exercise: Bucket Group (Optional)

In this optional exercise, you will create a bucket group to determine whether more NeedIt requests are
due in the first half of the month or the second half of the month.
Create a Bucket Group - Month Halves

In this section of the exercise, you will create a bucket group with two buckets.
Analytics > Breakdowns > Bucket Groups.
3. Configure the bucket group.
Name: Month Halves

Description: Bucket group to divide the month into two parts: Days 1 - 15 and days 16 - 31.
4. Add buckets to the bucket group.
1. In the Buckets list, double-click Insert a new row....

2. Configure the bucket.
Name: 1 - 15
Start: 1
End: 16
3. Add and configure a second bucket.
Name: 16 - 31
Start: 16
End: 32
QUESTION: Why is the value 16 the End field value for the 1 - 15 bucket and the Start field value for
the 16 - 31 bucket? Will NeedIt requests with When needed field values on the 16th of the month be
counted twice?
ANSWER: Bucket groups are inclusive of the Start field value and exclusive of the End field value.
When needed date field values for the 15th of the month will only be included in the 16 - 31 bucket.
For the same reason, the 16 - 31 bucket ends with the value 32.
Create a Breakdown Source

In this section of the exercise, you will create a breakdown source for the bucket group.
Analytics > Sources > Breakdown Sources.
3. Configure the breakdown source.
Name: NeedIt Requests by Month Half
Description: Break NeedIt request data into requests due in the first half of the month and
in the second half of the month.
4. Configure the Source section (tab).
Facts table: Bucket [pa_buckets]
Field: Sys ID
Conditions: [Bucket group] [is] [Month Halves]
Create a Breakdown Mapping Script

The When needed field on the NeedIt table is of type GlideDateTime. To group the When needed values
into the 1 - 15 bucket or the 16 - 31 bucket, you need to extract the day of the month from the
GlideDateTime object. In this section of the exercise, you will write a script to extract the day of the month.
Analytics > Automation > Scripts.
3. Configure the script.
Name: NeedIt.day
Description: Extract the day of the month from the When needed date.
4. Pass the When needed field to the script.
1. Click the Unlock Fields button ( ).

2. In the Available slushbucket, select When needed.
3. Click the Add button ( ) to move the When needed field to the Selected slushbucket.
5. Copy this script and paste it into the Script field.
whichDay = function(){
//Create a whenNeeded object from the GlideDateTime class. The value

//of whenNeeded is the When needed date from the NeedIt record.
var whenNeeded = new GlideDateTime(current.u_when_needed);
//Return the day of the month part of the whenNeeded object

return whenNeeded.getDayOfMonthLocalTime();
};
whichDay();
6. Read the script and the script comments to make sure you understand what the script does.
Create a Breakdown and Mapping

In this section of the exercise, you will create a bucket group breakdown and map the script to the
breakdown.
Analytics > Breakdowns > Automated Breakdowns.
3. Configure the breakdown.
Name: NeedIt Requests by Month Halves
Description: Breakdown for NeedIt requests to divide requests into the first and second
halves of the month by When needed field value.
4. Configure the Automated section (tab).
Breakdown source: NeedIt Requests by Month Half
6. Scroll to the Breakdown Mappings related list and add the script to the breakdown mapping.
2. Configure the Breakdown Mapping.
Scripted: Selected (checked)
Script: NeedIt.day
7. Click the Submit button on the Breakdown Mapping form.
Add the Bucket Group Breakdown to the NeedIt Indicator

In this section of the exercise, you will add the NeedIt requests by Month Half breakdown to the NeedIt:
Due Monthly indicator.
2. Open the NeedIt: Due Monthly indicator for editing.
3. Scroll to the Breakdowns section (tab) and add the breakdown to the indicator.
1. Click the Edit... button.
2. In the Collection slushbucket, click the NeedIt Requests by Month Halves breakdown.
3. Click the Add button to move the breakdown to the Breakdowns List slushbucket.
Run the Data Collector - NeedIt Historical Data

2. Open the NeedIt Historical Data data collector.
3. Click the Execute Now button.
4. To verify the bucket group breakdown calculation worked, open the NeedIt: Due Monthly indicator
record and click the Scores for this indicator related link. The example has been edited to show
only the NeedIt Requests by Month Halves scores. Your scoresheet will also include scores for the
other breakdowns for the indicator. Your scores may be different than the scores shown because the
NeedIt record data was randomly generated.
Create a Dashboard Widget for the Bucket Group Breakdown
Analytics > Dashboards.
2. Open the NeedIt Application dashboard.
3. Add a Breakdown widget to the dashboard.
1. Click the Add Widgets icon.
3. In the list of Performance Analytics widget types, select the Breakdown widget.
4. On the list of Breakdown widgets, select #New Breakdown.
4. Click the Click here link to configure the #New Breakdown widget.
Name: NeedIt Requests by Which Half of Month - 6 Month Sum
Description: Display NeedIt requests by month half using the day of month from the When
needed field.
Breakdown: NeedIt Requests by Month Halves
Time Series: 6m running SUM
Type: Breakdown
Visualization: Column
Sort on: Value
Sort direction: Ascending
Show visualization selector: Selected (checked)
Show breakdown selector: Not selected (unchecked)
7. Examine the NeedIt Request by Which Half of Month - 6 Month Sum widget.
QUESTION: Based on your data, is the first half of the month busier for the NeedIt fulfillment team than
the second half of the month?
ANSWER: Recall that the NeedIt records were randomly generated so your data may be different than
the example. To see the exact number of requests, hover your mouse over the widget columns. In the
example, the second half of the month is busier on average, than the first half of the month.
EXERCISE (54 OF 57)
Exercise: Save Your Performance Analytics Work

(Optional)
Source control applications, like GitHub, allow developers to commit changes (save completed work)
outside of the Personal Developer Instance (PDI). Commit changes made to the application to save your
work in source control.
In this exercise, you will save the work completed in this module to your GitHub repository.
NOTE: See the GitHub Guide (/dev.do#!/guide/tokyo/now-platform/github-guide/github-and-the-developer-site-training-guide-
introduction) for more information on how ServiceNow uses GitHub with the Developer Program learning content and to see
a video on how to save your work.
Commit Changes
1. If the NeedIt application is not open in Studio, open it now.
Studio.
2. In the Select Application dialog, click the application.
2. Open the Source Control menu and select the Commit Changes menu item.
3. Select the updates to commit.
1. In the Select files to commit to source control for <Application> dialog, select All Update Sets.
2. Review the application files to be committed.
3. Click the Continue button.
4. In the Confirm files to commit to source control for NeedIt dialog, enter a Commit comment, such as
Performance Analytics Module Completed.
5. Click the Commit Files button.
6. When the Commit Changes dialog reports success, click the Close button.
NOTE: If the commit change fails, you may have entered the ServiceNow repository URL instead of the forked
repository URL in the URL field. See the Troubleshooting GitHub Issues (/dev.do#!/guide/tokyo/now-platform/github-
guide/troubleshooting-github-issues) section in the GitHub Guide for instructions on how to troubleshoot GitHub
connection issues.
ARTICLE (55 OF 57)

Test Your Performance Analytics Knowledge
Want to verify your understanding of Performance Analytics? These questions will help you assess your
progress. For each question, determine your response then click anywhere in the question to see the
answer.
QUESTION: Which of the following are true statements about Performance Analytics? More than one
response may be correct.
1. Collects and analyzes data

2. Aggregates data over time
3. Provides actionable insight
4. Forecasts future performance
5. Shares clear, up-to-date visualizations
ANSWER: All of the responses are correct.
QUESTION: True or False? Performance Analytics can be run on any ServiceNow instance.
ANSWER: The correct response is False. This is a bit of a trick question. Although basic Performance
Analytics can be run on any ServiceNow instance, Performance Analytics Premium requires a license to
run on production instances.
QUESTION: Which of the following data types are a good fit with Performance Analytics? More than one
response may be correct.
1. String
2. Date/time
3. Boolean
4. Journal
5. Choice
ANSWER: The correct responses are 2, 3, and 5. The String and Journal data types allow entry of
freeform text. Freeform text is difficult to report on.
QUESTION: Which Performance Analytics component is described by the following?
A set of records from a ServiceNow table that have a common characteristic such as the Priority is critical.
1. Field type
2. Breakdown
3. Data Collector
4. Indicator Source
5. Bucket Group
ANSWER: The correct response is 4.
Performance metrics taken at regular intervals.
1. Indicator
2. Indicator Source
3. Breakdown Source
4. Breakdown
5. Data Collector
Filters or groups indicator scores for more detailed analysis.
1. Indicator
2. Indicator Source
3. Breakdown Source
4. Breakdown
5. Data Collector
QUESTION: Which of the following are true statements for Data Collectors? More than one response may
be correct.
1. Fixed Data Collectors collect data for an absolute time period

2. Relative Data Collectors collect data for an absolute time period
3. Can be configured to use a server-side script to determine when to run
4. Always runs automatically based on a schedule
5. Uses the System time for queries
ANSWER: The correct responses are 1 and 3. Data Collectors do not need to be configured to always
run based on a schedule. It is optional. For example, Historical Data Collectors are configured to run on
demand. In the baseline case, Data Collectors use System time for queries but can be configured to
execute queries in another time zone using the Run as tz configuration field.
QUESTION: Which of the following are features of Analytics Hub? More than one response may be
correct.
1. Comments
2. Thresholds
3. Scorecards
4. Forecasts
5. Targets
ANSWER: The correct responses are 1, 2, 4, and 5. Analytics Hub replaced Scorecards starting with
the Madrid release of ServiceNow.
QUESTION: Which features of Analytics Hub send notifications? More than one response may be correct.
1. Comments
2. Thresholds
3. Forecasts
4. Targets
5. Comparisons
ANSWER: The correct responses are 2 and 4.
QUESTION: Which of the following are true statements about Dashboards? More than one response may
be correct.
1. Applications are allowed to have only one Dashboard

2. Dashboards can have a maximum of four widgets
3. All users can view all dashboards
4. Dashboards are configured using a drag and drop canvas
5. Dashboards can contain widgets and tabs
ANSWER: The correct responses are 4 and 5. Applications typically have a Dashboard for each of an
application#singleQuotes personas, because different user types are interested in different information.
Dashboards can have as many widgets as needed to convey the required information from an application
or process. Access to Dashboards is restricted by role. All users can see Dashboards that do not have a
role assigned.
QUESTION: Which of the following are true statements about Bucket Groups? More than one response
may be correct.
1. A special type of Breakdown Source

2. Must be viewed in Analytics Hub
3. Can be created by Dashboard users
4. Divides values returned by a script or field into discrete groupings
5. Can provide insights that are not obvious by looking at raw data
ANSWER: The correct responses are 1, 4 and 5. Indicators that use Bucket Groups can be viewed in
Analytics Hub or on a Dashboard. Developers can create Bucket Groups but users cannot.
ARTICLE (56 OF 57)
Performance Analytics Module Recap

Core concepts:
The Performance Analytics - Premium plugin can be activated and used on dev and test instances
without a license
The Performance Analytics architecture includes a data layer and a visualization layer
Application developers should design Performance Analytics into their data models
Avoid freeform or string fields
Use reference, boolean, date/time, integer, decimal, and choice list data types
Indicator sources define filtered sets of records that are collected at a regular frequency
Indicators define performance metrics for a regular interval
Breakdowns filter or group indicator scores for more detailed analysis
Breakdown sources are a set of records from a table or database view used to calculate breakdown
scores.
Multiple breakdowns can use the same breakdown source
Breakdowns are visualized on scorecards and dashboards
Data collectors are scheduled jobs that collect data from indicator sources
Historical: collect past data
Current: collect current data
Analytics Hub visualizes data for a single indicator
Analyze indicator data
Aggregate data
Compare breakdown scores
View changes over time
Targets visualize the difference between the desired score and indicator scores
Thresholds define a normal range of scores for an indicator
Forecasts predict future data based on past performance
Dashboards are a drag and drop canvas for gathering visualizations used regularly, into a single
location organized by tabs and widgets
Bucket groups are a special type of breakdown source that divide values returned by a script into
discrete buckets
Bucket groups are useful for drawing conclusions that may not be obvious in the raw data
Buckets sort data into reusable logical groupings
Bucket group breakdowns must be mapped to an indicator
Visualize bucket group breakdowns on dashboard widgets, Analytics Hub, or scorecards
ARTICLE (57 OF 57)
After Completing Performance Analytics, You

Might Also Be Interested In...
Congratulations on completing the Performance Analytics module. Based on your interest in performance
analytics, you might also enjoy:
ServiceNow Developer Glossary (http://developer.servicenow.com/to.do?u=PAN-T-GUI-SNGlossary): In

this Developer Site glossary, terms are defined that apply to the Now Platform.
Performance Analytics (http://developer.servicenow.com/to.do?u=PAN-T-DOC-PALandingPage): On the
ServiceNow docs site, you will find a complete set of reference materials for Performance Analytics.
Performance Analytics REST API (http://developer.servicenow.com/to.do?u=PAN-T-API-PAAPI): On the
ServiceNow Developer Site, you will find the reference documentation for the Performance Analytics
REST API.
Performance Analytics: Getting Started (http://developer.servicenow.com/to.do?u=PAN-T-COM-
PAGetStarted): In this community site article, you will find links to articles about activating, configuring,
and analyzing with Performance Analytics.

Analytics Performance

Uploaded by

Copyright:

Available Formats

Analytics Performance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Analytics Performance

Uploaded by

Copyright:

Available Formats

Version: Tokyo

Performance Analytics Objectives

Activate the Performance Analytics - Premium plugin

PREREQUISITES: Familiarity with Scheduled Script Executions and Events

About This Learning Module

You will develop the NeedIt application in the hands-on exercises.

Exercises are indicated in three ways:

Exercise icon in the Navigation pane.

Exercise: Fork Repository and Import

NOTE: See the GitHub Guide (/dev.do#!/guide/tokyo/now-platform/github-guide/github-and-the-developer-site-training-guide-

a video on how to fork a repository and import an application.

In this exercise, you will:

1. Fork the ServiceNow repository to your GitHub account.

Fork the Repository

1. In a web browser, open github.com (https://github.com/).

8. Copy the forked repository's URL.

1. Click the Code button.

4. Click the Copy to clipboard button ( ).

Import the Application from the Forked Repository

NOTE: See the Personal Developer Instance (PDI) Guide (/dev.do#!/guide/tokyo/now-platform/pdi-guide/personal-

developer-instance-guide-introduction) for instructions on how to obtain a PDI.

2. Create a Credential record for the GitHub connection.

another exercise, please skip this step.

2. Click the New button.

4. Configure the Credential record.

Name: GitHub Credentials - <Your github.com Username>

Authenticating to GitHub (/dev.do#!/guides/tokyo/developer-program/github-guide/using-servicenow-provided-

application-repositories#authenticating-to-github) section of the GitHub Guide for instructions on creating a GitHub

personal access token.

5. Click the Submit button.

3. Use the All menu to open System Applications > Studio.

4. Studio opens in a new browser tab.

7. Click the Import button.

Troubleshooting GitHub Issues (/dev.do#!/guide/tokyo/now-platform/github-guide/troubleshooting-github-issues) for

instructions on how to troubleshoot the connection.

Exercise: Create a Branch for the Performance

3. Configure the branch.

Branch Name: PerformanceAnalytics

4. Click the Create Branch button.

5. Click the Close button.

Issues (/dev.do#!/guide/tokyo/now-platform/github-guide/troubleshooting-github-issues) section of the GitHub Guide for

instructions on how to troubleshoot GitHub connection issues.

What is Performance Analytics?

With Performance Analytics, applications can:

Reporting vs. Analytics

How many earthquakes have occurred in the month of March?

At what earthquake level does it become unsafe to live in a wooden house?

The Performance Analytics - Premium Plugin

The Performance Analytics - Premium plugin's features include:

Create indicators, breakdowns, widgets, and other records

Exercise: Activate the Performance Analytics -

Activate the Performance Analytics - Premium Plugin

4. In the Activate Plugin dialog, click the Activate button.

Performance Analytics Data Architecture

Data Collectors: collect data from indicator sources

ARTICLE (10 OF 57)

Data Field Types Drive Analytics

When designing the data model, make sure that:

All data required for analytics is collected

ARTICLE (11 OF 57)