Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Interactive Analysis

Interactive Analysis

Interactive Analysis enables you to quickly explore data using visualizations.

Note: This functionality requires Performance Analytics Premium.

From any list of records you can access an interactive set of reports on the list data, as well as manipulate the data by grouping, stacking, and applying interactive filters. You can click a visualization to drill down into the data.

Figure 1. Interactive Analysis on Incident data
Interactive analysis on incident data

Launch Interactive Analysis

Launch Interactive Analysis from a list.

Before you begin

Role required: none

You must have access to the list of records that you want to analyze.


  1. Navigate to any list.
  2. (Optional) Configure the columns that are displayed on the list.
    The columns that appear on the list when you launch Interactive Analysis determine which fields are included in the analysis. The included fields determine which Group by and Stack by options are available, and which interactive filters appear by default.
  3. Right-click the column header for a reference, choice, date/time, or boolean field and select Launch Interactive Analysis.
    The column that you launch Interactive Analysis from is used as the default Group by value.
  4. (Optional) Change how data is aggregated by selecting different values in the Group by and Stack by choice lists, or filter the data by applying one or more interactive filters.
  5. (Optional) Drill down into a subset of the data by clicking a visualization, such as a bar in the bar chart or a cell in the heatmap.

Cascading filters

Cascading filters allow you to filter based on multiple values in a hierarchy, such as by region, country, and city.

Lower level choices are filtered by the values selected at higher levels. For example, you can create a cascading filter that allows users to select from a list of managers, then select from user groups that are managed by the selected manager. Report data is then filtered to show only records assigned to that group.

Alternatively, you can leave lower levels of the filter unselected, such as by selecting only a manager but no user group. Report data is then filtered to show records assigned to any group managed by that manager.

Create a cascading filter

To create a cascading filter, define each level of the filter, the relationship between levels, and how a selection at each level filters the report data.

Before you begin

Role required: hp_publisher_admin and report_admin. The hp_publisher_admin role exists only for managing interactive filters. By default, it contains no other roles and is not contained in any other roles.

You must have Performance Analytics Premium to create new interactive filters.

Ensure that the structure of the data that you use to create the filter is consistent. For example, in a cascading filter based on location, ensure that the top level choices are all regions, and the second-level choices are all countries. You can define filter conditions to ensure that only appropriate choices for each level are available.

About this task

This procedure includes examples based on a cascading interactive filter using managers and groups. In this example, the top-level choice allows users to select a manager and the second-level choice allows users to select a user group managed by that manager.
Figure 2. Example cascading filter
Example of a cascading filter
Note: You can filter reports based on the values in reference fields only. Cascading filters support only the Single Select UI control type.


  1. Homepage Admin > Interactive filters.
  2. Click New.
  3. In the Filter based on choice list, select Cascading Filters.
  4. Right-click the form header and select Save.
  5. Define the first level of the cascading filter.
    1. In the Cascading Filter related list, click New.
    2. Select the Table and the Display field from the table that contains the values you want to use as the top-level filter choices. The Display Field is limited to the types boolean, choice, reference, and string.
      For example, to define the top level of a hierarchy based on managers and the groups they manage, select Group [sys_user_group] as the Table and Manager as the Display field.
    3. (Optional) Use the Filters field to limit which choices are available to users.
      Filter conditions are especially useful when you create a cascading filter based on a self-referencing table, such as Location [cmn_location]. Filter the data to ensure each level of the cascading filter has only options appropriate for that level.
    4. Right-click the form header and select Save.
  6. Define the next level of the hierarchy.
    Cascading filters use a one-to-many relationship between higher-level filters and lower-level filters. One higher-level filter can affect the choices available in any number of lower-level filters.
    1. From the manager filter, in the Cascading Filter related list, click New.
    2. Select the Table and the Display field from the table that contains the values you want to use as the second-level filter choices. The Display Field is limited to the types boolean, choice, reference, and string.
      In the managers and groups example, select Group [sys_user_group] as the Table and Name as the Display field.
    3. In the Parent Reference Field field, select the field that contains the value selected from the higher-level filter.
      For example, when you create the Group filter, the Parent Reference Field value is Manager. In this example, the manager selected in the first filter is used to filter the list of available groups based on the Manager field value of each group.
    4. Right-click the form header and select Save.
    5. Repeat these substeps for each additional filter you want to add. To add another level to the filter hierarchy, add a new record in the Cascading Filter related list of the lowest-level filter such as the Group filter, instead of the top-level filter such as the Manager filter.
  7. Define how each filter level applies the filter to reports on a dashboard.
    1. In the Target Tables related list, click New.
    2. Select the Target table that contains the data you want to filter, such as Incident.
    3. Select the Field to filter on.
      The field must reference the table specified in the filter. For example when filtering incident data, the Field for the top-level manager filter is Assignment group.Manager. In this example, the Field for the second-level group filter is Assignment group.
    4. Click Submit.
    5. Repeat these substeps to add targets for each level of the filter.
      You can define multiple targets for each filter level, such as to filter incident data by assignment group or to filter CMDB CIs by support group using the same Groups [sys_user_group] filter.
      Note: A cascading filter hierarchy must specify at least one target. You can define a cascading filter that skips levels in a hierarchy, or a cascading filter that only specifies targets for certain levels in a hierarchy. For example you can define a target only for the Group-level filter and not the Manager-level filter. In this example, reports are filtered only when a user selects a specific group and not just a manager.
    The following images demonstrate the completed configuration for the example cascading filter. The Cascading Filter related list (not shown) in the top-level filter contains the second-level filter.
    Figure 3. Top-level filter
    Cascading filter — top-level filter form
    Figure 4. Second-level filter
    Cascading filter — second-level filter form

What to do next

After you create all levels of the filter, add it to a homepage or dashboard.

Request Interactive Analysis

The Interactive Analysis plugin (com.glideapp.interactive_analysis) requires Performance Analytics Premium.

Before you begin

Role required: none


  1. In the HI Service Portal, click Service Requests > Activate Plugin.
  2. Fill out the form.
    Target Instance Instance on which to activate the plugin.
    Plugin Name Name of the plugin to activate.
    Specify the date and time you would like this plugin to be enabled

    Date and time must be at least 2 business days from the current time.

    Note: Plugins are activated in two batches each business day in the Pacific timezone, once in the morning and once in the evening. If the plugin must be activated at a specific time, enter the request in the Reason/Comments.
    Reason/Comments Any information that would be helpful for the ServiceNow personnel activating the plugin such as if you need the plugin activated at a specific time instead of during one of the default activation windows.
  3. Click Submit.