ServiceNow Incident Management SpotApp

SpotApps are ThoughtSpot’s out-of-the-box solution templates built for specific use cases and data sources. They are built on ThoughtSpot Modeling Language (TML) Blocks, which are pre-built pieces of code that are easy to download and implement directly from the product.

The ServiceNow Incident Management SpotApp mimics the ServiceNow data model. When you deploy it, ThoughtSpot creates several worksheets, answers, and Liveboards, based on your ServiceNow data in your cloud data warehouse.

This is a sample Liveboard, created after you deploy the ServiceNow Incident Management SpotApp:

ServiceNow SpotApp Liveboard

Use the ServiceNow Incident Management SpotApp for incident management. You can track the number of tickets submitted, and understand the efficiency of how those tickets are resolved.

Prerequisites

Before you can deploy the ServiceNow Incident Management SpotApp, you must complete the following prerequisites:

Deploy the ServiceNow Incident Management SpotApp

After you complete the prerequisites, you are ready to deploy the ServiceNow Incident Management SpotApp and begin leveraging its pre-built content.

To deploy the ServiceNow Incident Management SpotApp, refer to Deploying SpotApps.

ServiceNow Incident Management SpotApp schema

The following table describes the schema for the ServiceNow Incident Management SpotApp.

Table Column Column type Required column

cmn_location

country

VARCHAR

N

cmn_location

name

VARCHAR

N

cmn_location

state

VARCHAR

N

cmn_location

sys_id

VARCHAR

N

config_item

name

VARCHAR

N

config_item

sys_id

VARCHAR

N

contract_sla

duration

DATE_TIME

N

contract_sla

sys_id

VARCHAR

N

contract_sla

sys_name

VARCHAR

N

contract_sla

target

VARCHAR

N

contract_sla

type

VARCHAR

N

core_company

name

VARCHAR

N

incident

active

VARCHAR

Y

incident

assigned_to

VARCHAR

Y

incident

assignment_group

VARCHAR

Y

incident

business_service

VARCHAR

Y

incident

category

VARCHAR

Y

incident

close_code

VARCHAR

Y

incident

closed_at

DATE_TIME

Y

incident

closed_by

VARCHAR

Y

incident

close_Ntes

VARCHAR

Y

incident

cmdb_ci

VARCHAR

Y

incident

company

VARCHAR

Y

incident

escalation

VARCHAR

Y

incident

location

VARCHAR

Y

incident

major_incident_state

VARCHAR

Y

incident

number

VARCHAR

Y

incident

opened_at

DATE_TIME

Y

incident

opened_by

VARCHAR

Y

incident

priority

VARCHAR

Y

incident

reassignment_count

VARCHAR

Y

incident

reopen_count

VARCHAR

Y

incident

reopened_time

VARCHAR

Y

incident

resolved_at

DATE_TIME

Y

incident

resolved_by

VARCHAR

Y

incident

route_reason

VARCHAR

Y

incident

service_offering

VARCHAR

Y

incident

severity

VARCHAR

Y

incident

state

VARCHAR

Y

incident

subcategory

VARCHAR

Y

incident

sys_created_on

DATE_TIME

Y

incident

sys_id

VARCHAR

Y

incident

sys_updated_by

VARCHAR

Y

incident

sys_updated_on

DATE_TIME

Y

incident

task_effective_number

VARCHAR

Y

incident

urgency

VARCHAR

Y

service_offering

name

VARCHAR

N

service_offering

sys_id

VARCHAR

N

services

name

VARCHAR

N

services

sys_id

VARCHAR

N

sys_user

name

VARCHAR

N

sys_user

sys_id

VARCHAR

N

sys_user

title

VARCHAR

N

sys_user_group

name

VARCHAR

N

sys_user_group

sys_id

VARCHAR

N

task_sla

active

VARCHAR

N

task_sla

end_time

DATE_TIME

N

task_sla

has_breached

VARCHAR

N

task_sla

planned_end_time

DATE_TIME

N

task_sla

sla

VARCHAR

N

task_sla

stage

VARCHAR

N

task_sla

start_time

DATE_TIME

N

task_sla

__status

VARCHAR

N

task_sla

sys_created_on

DATE_TIME

N

task_sla

task

VARCHAR

N