Building an Interactive Incident Management Dashboard Using ServiceNow UI Builder

Introduction

ServiceNow UI Builder provides a visual development environment that allows developers to create customized and interactive user experiences using reusable components, data resources, and event handlers.

In this practical guide, we will build an Incident Management Dashboard using ServiceNow UI Builder.

The dashboard will retrieve incident records from the Incident table and display them in individual cards. Each card will show the incident number, caller, short description, and priority.

We will also implement navigation functionality so that when a user clicks an incident card, the corresponding incident record opens on a separate page within the same experience.

By the end of this guide, you will learn how to:

  • Create an Incident Management Dashboard.
  • Configure an Incident Lookup data resource.
  • Use a Repeater component to display multiple incident records.
  • Bind incident fields to UI Builder components.
  • Design reusable incident cards.
  • Create a separate Incident Record page.
  • Configure the Card Clicked event.
  • Map the event to the newly created page.
  • Pass the selected incident’s sys_id dynamically.
  • Preview and test the completed dashboard.

1. Prerequisites

Before starting, ensure that you have:

  1. Access to a ServiceNow instance.
  2. Access to UI Builder.
  3. An existing experience or permission to create one.
  4. Access to the Incident table.
  5. Appropriate permissions to configure pages and event mappings.

2. Understanding the Dashboard Architecture

The dashboard will consist of the following components:

ComponentPurpose
ExperienceProvides the application environment
Incident DashboardMain dashboard page
Incident LookupRetrieves incident records
RepeaterDynamically generates incident cards
Card Base ContainerProvides the card structure
HeadingDisplays incident number
Label ValueDisplays caller
Stylized TextDisplays short description
Highlighted ValueDisplays priority
Incident Record PageDisplays the selected incident
Event MappingHandles card click navigation

The implementation follows this structure:

Experience → Incident Dashboard → Incident Lookup → Repeater → Card Base Container → Incident Information.

When a card is clicked, the event mapping navigates the user to the Incident Record Page and passes the selected record’s identifier.

3. Creating the Incident Management Dashboard

Step 1: Open UI Builder

  1. Log in to your ServiceNow instance.
  2. Navigate to UI Builder.
  3. Open your Incident Management Experience.
  4. Navigate to the Pages section.

Step 2: Create the dashboard page

  1. Click the option to create a new page.
  2. Select an appropriate page template.
  3. Enter the page name as Incident Dashboard.
  4. Complete the page creation process.

You should now have a blank dashboard page where you can add components.

4. Configuring the Incident Lookup Data Resource

A data resource retrieves records from a ServiceNow table and makes the returned data available to components.

For this implementation, we will use Incident Lookup.

Step 1: Add the data resource

  1. Open the Incident Dashboard.
  2. Locate the Data and scripts section on the left.
  3. Expand Data resources.
  4. Add the Incident Lookup data resource.
  5. Configure it to retrieve records from the Incident table.

Step 2: Configure the data source

Configure the required table and query conditions.

PropertyConfiguration
Data resourceIncident Lookup
TableIncident
Table nameincident
OutputIncident records

You can optionally add conditions to retrieve only active incidents.

Step 3: Verify the returned data

Execute or preview the data resource and verify that incident records are returned.

Check for fields such as:

  • Number
  • Caller
  • Short description
  • Priority
  • Sys ID

5. Adding and Configuring the Repeater

The Repeater component allows us to display multiple records using a single reusable component structure.

Instead of manually creating individual incident cards, the Repeater generates them based on the returned data array.

Step 1: Add a column layout

  1. Select Body in the Content panel.
  2. Click Add content.
  3. Search for Column layout.
  4. Add the required column layout.
  5. Add a column inside the layout.

Step 2: Add the Repeater

  1. Select the column.
  2. Click Add content.
  3. Search for Repeater.
  4. Add Repeater 1.

Step 3: Configure Repeater data

  1. Select Repeater 1.
  2. Open the Configure tab.
  3. Locate the Repeater data section.
  4. Find the Data array property.
  5. Click the Bind data icon.
  6. Select Data resource.
  7. Expand Incident Lookup.
  8. Select the results array.
  9. Click Apply.

The Repeater is now connected to the incident records.

For example, if the data resource returns 10 records, the Repeater can generate 10 corresponding cards.

6. Creating and Designing Incident Cards

Step 1: Add Card Base Container

  1. Select Repeater 1.
  2. Click Add content.
  3. Search for Card Base Container.
  4. Add Card Base Container 1.

Step 2: Configure card interaction

  1. Select Card Base Container 1.
  2. Open the Configure tab.
  3. Locate the Interaction property.
  4. Select Click.

This enables click interaction on the card.

Step 3: Configure card dimensions

Open the Styles tab and configure:

PropertyValue
Width300 px
Height200 px
PaddingAs required

Adjust the dimensions according to your dashboard layout.

7. Binding Incident Information to Card Components

We will add four components inside the Card Base Container.

7.1 Heading – Incident Number

  1. Select Card Base Container 1.
  2. Click Add content.
  3. Search for Heading.
  4. Add Heading 1.
  5. Select the Heading component.
  6. Open Configure.
  7. Locate the Label property.
  8. Click Bind data.
  9. Select Repeater under Data types.
  10. Select value.
  11. Expand the incident number field.
  12. Select displayValue.
  13. Click Apply.

The card will display the incident number dynamically.

Example: INC0000002.

7.2 Label Value – Caller

  1. Select Card Base Container 1.
  2. Add a Label Value component.
  3. Select the component.
  4. Open Configure.
  5. Locate its value property.
  6. Click Bind data.
  7. Navigate to Repeater → value.
  8. Expand the caller_id field.
  9. Select displayValue.
  10. Click Apply.

The caller’s name will now appear on the card.

7.3 Stylized Text – Short Description

  1. Select Card Base Container 1.
  2. Add a Stylized Text component.
  3. Select the component.
  4. Open Configure.
  5. Locate the Text property.
  6. Click Bind data.
  7. Select Repeater.
  8. Select value.
  9. Expand short_description.
  10. Select displayValue.
  11. Click Apply.

This displays the incident short description dynamically.

7.4 Highlighted Value – Priority

  1. Select Card Base Container 1.
  2. Add a Highlighted Value component.
  3. Select the component.
  4. Open Configure.
  5. Locate the value property.
  6. Click Bind data.
  7. Navigate to Repeater → value.
  8. Expand priority.
  9. Select the appropriate display value.
  10. Click Apply.

The incident priority will now appear on the card.

Example: 1 – Critical.

Note: The exact field paths depend on the data resource response. Verify the available fields in the data picker before applying the bindings.

8. Creating a Separate Incident Record Page

Now that the dashboard displays incident records, we need another page to display the complete details of an individual incident.

Instead of navigating to an unrelated page, we will create a separate record page within the same experience.

Step 1: Return to the Experience overview

  1. In UI Builder, locate your experience name in the upper-left corner.
  2. Click the experience name.
  3. Navigate back to the Experience overview.
  4. Locate the Pages section.

Step 2: Create a new page

  1. Click the plus (+) icon in the Pages section.
  2. You will see the available page creation options.
  3. Select Create a new page.

Important: Select Create a new page instead of Add a variant to page.

A page variant creates an alternative version of an existing page, whereas we need a separate destination page for displaying individual incident records.

Step 3: Select the page template

  1. Browse the available page templates.
  2. Locate the Standard Record template.
  3. Select Use template.

The Standard Record template provides a starting point for creating a page that displays record information.

Step 4: Configure page details

Enter the following information:

PropertyValue
Page nameIncident Record Page
PurposeDisplay individual incident details
TemplateStandard Record
  1. Click Continue.
  2. Review the page configuration.
  3. Select Looks Good.
  4. Click Create.

The Incident Record Page is now created within your experience.

Step 5: Verify page creation

  1. Return to the Experience overview.
  2. Open the Pages section.
  3. Verify that Incident Record Page appears in the list.
  4. Open the page and review its configuration.

At this point, we have two pages:

  • Incident Dashboard – Displays multiple incident cards.
  • Incident Record Page – Serves as the destination for the selected incident.

9. Configuring Card Click Event Mapping

This is the most important part of the implementation.

We want the application to identify which incident card was clicked and navigate to the Incident Record Page with the correct record identifier.

For this, we will configure an event mapping on the Card Base Container.

Step 1: Return to Incident Dashboard

  1. Navigate back to the Experience overview.
  2. Open Incident Dashboard.
  3. In the Content panel, expand the component hierarchy.

Navigate to:

Body → Column Layout 2 → Column 1 → Repeater 1 → Card Base Container 1.

  1. Select Card Base Container 1.

Step 2: Open the Events tab

  1. Locate the right-side configuration panel.
  2. Select the Events tab.
  3. Click Add event mapping.

Step 3: Select the component event

  1. Browse the available component events.
  2. Select Card clicked.
  3. Click Continue.

This event will be triggered when the user clicks an incident card.

Step 4: Select the event handler

  1. Select Open page or URL as the event handler.
  2. Click Continue.
  3. Select Pages in current experience.
  4. Choose Incident Record Page.

This connects the card click event to the separate page we created earlier.

Step 5: Configure destination parameters

The destination page needs to know which incident record should be displayed.

Configure the following parameters:

ParameterValue
Tableincident
sysIdDynamically bound incident identifier

Table configuration:

Enter:

incident

sysId configuration:

The sysId must be dynamically populated based on the incident card clicked by the user.

Step 6: Bind the sysId dynamically

Follow these steps:

  1. Locate the sysId field in the destination configuration.
  2. Hover over the field.
  3. Click the Bind data icon.
  4. In the data picker, select Repeater under Data types.
  5. Open Pill view.
  6. Select value.
  7. Expand _row_data.
  8. Locate uniqueValue.
  9. Double-click uniqueValue.
  10. Click Apply.

The expected binding path is:

Repeater → value → _row_data → uniqueValue

Why is this binding important?

Each incident card represents a different incident record.

The uniqueValue identifies the individual record represented by the current Repeater item.

For example:

  • Clicking INC0000002 passes the identifier of INC0000002.
  • Clicking INC0000003 passes the identifier of INC0000003.
  • Clicking INC0000007 passes the identifier of INC0000007.

Without dynamic binding, the application might navigate using a static or incorrect record identifier.

Step 7: Complete the event mapping

  1. Review the selected destination page.
  2. Verify that the table is set to incident.
  3. Verify that sysId uses the Repeater’s dynamic uniqueValue binding.
  4. Configure the Open in new tab option according to your requirement.
  5. Click Add to complete the event mapping.

The Card Base Container is now configured to navigate to the Incident Record Page when clicked.

10. Saving and Testing the Dashboard

After completing the configuration, save the changes and test the implementation.

Step 1: Save the configuration

  1. Click Save in UI Builder.
  2. Wait for the changes to be saved.
  3. Click Preview.

Step 2: Verify incident cards

Check that each card displays:

  • Incident number
  • Caller name
  • Short description
  • Priority

Verify that the information is displayed correctly for different records.

Step 3: Test card navigation

  1. Click the first incident card.
  2. Verify that Incident Record Page opens.
  3. Check whether the correct incident details are displayed.
  4. Return to Incident Dashboard.
  5. Click another incident card.
  6. Verify that the corresponding incident record opens.

Expected result

Selected CardExpected Destination
INC0000002Record for INC0000002
INC0000003Record for INC0000003
INC0000007Record for INC0000007
INC0000015Record for INC0000015

Every card should navigate to its own incident record.

11. Best Practices

1. Use Repeater for dynamic records

Avoid manually creating individual cards for every incident. A Repeater makes the dashboard easier to maintain.

2. Use dynamic data binding

Bind the component properties to the Repeater data instead of entering static values.

3. Maintain consistent card dimensions

Use consistent width, height, and spacing to create a clean dashboard.

4. Pass the correct record identifier

Always verify that the selected card passes its own sys_id to the destination page.

5. Test multiple records

Test different incident cards to ensure that navigation works correctly.

6. Consider responsive layouts

Test your dashboard at different viewport widths to ensure that cards remain readable.

12. Conclusion

In this practical implementation, we created an interactive Incident Management Dashboard using ServiceNow UI Builder.

We configured an Incident Lookup data resource to retrieve incident records and used a Repeater to display them dynamically in reusable cards.

We added components to display incident numbers, caller names, short descriptions, and priorities using data binding.

We then created a separate Incident Record Page using the Standard Record template and configured the Card Clicked event on the Card Base Container.

Finally, we mapped the event to the newly created page and passed the selected incident’s unique identifier dynamically using the Repeater’s uniqueValue.

This implementation demonstrates how UI Builder components, data resources, Repeaters, and event mappings can work together to create an interactive, data-driven ServiceNow experience with minimal scripting.

Happy Learning and Happy Building!

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top