Bolt Data Connect – ServiceNow

Docs: App Tour

Mon, 01 Jan 0001 00:00:00 +0000

Launching the App

Once you install the ServiceNow App, you"ll find the new Bolt Data Connect App Modules in the ServiceNow All Menu.

App Modules

Connected Assets Workspace

The Connected Assets Workspace is a ServiceNow Now Experience Workspace. The home page displays a Dashboard containing Visualizations which gives you a view of all of your “Things” connected to Bolt Data Connect and the Thing Types, Status, Alert History and Sensor Data available in Salesforce.

IoT Dashboard

IoT Console

The IoT Console is the centralized dashboard for viewing all Connected Assets within an Instance.

IoT Console Map

IoT Console Cards

IoT Setup

For your ServiceNow Instance Admins, the Bolt Data Connect App provides an IoT Setup Module to configure how the IoT Cloud integrates with your ServiceNow Instance. Here you can completely control the behavior of the Cloud and Edge Processing, as well as the ServiceNow automation and integrations.

IoT Setup Module

Docs: Gateways

Mon, 01 Jan 0001 00:00:00 +0000

Represents an IoT Gateway, the entry-point for IoT messages and a container for Connectors and Rules-Engine processing.

Sample Gateway

Gateway Registration

Gateways can be created in ServiceNow, and then registered with the IoT Cloud using either the Register UI Action or UX Action with the same name. The Gateway Id and Gateway Type will need to be specified.

Gateway Chart and Digital Twin

The IoT Gateway can also display the Thing Chart and Digital Twin components.

Like any other Thing, the IoT Gateway sends Telemetry (time-series) data at a regular interval and can be configured with Calculated Fields and Alert Conditions in it’s corresponding Thing Type. The Sensors are mostly focused on the performance of the device hosting the Gateway & Rules-Engine.

Alarms and Metrics

We’ve added more intelligent monitoring of our Gateways, including:

Gateway Alarms: Central monitoring of important runtime problems and warnings from Gateways and their connected Things.
Gateway Metrics: The Telemetry data sent by the Gateways now includes key metrics for each Thing Type being processed.

Gateway Metrics

Gateway Command Console

The Command Console tab on an IoT Gateway allows you to send/receive messages (IoT Commands) to the Gateway. The following catalog of out-of-the-box Command Templates is currently available:

Clear Registration Cache
Get Connector Status
Get Device Cache (Thing)
Get I/O Status
Get Registration Cache (All)
Get Registration Cache (Thing)
Get ThingType Cache
Restart Virtual Gateway
Test Thing Data
Reset ThingType Cache: Forces the Gateway Rules Engine to reload the ThingType
Reset Registration Cache: Forces the Gateway Rules Engine to reload the Gateway’s & Thing’s Registration and Integrations

Gateway Command Console

Custom Commands

Select the CUSTOM command to use a freeform editor to send any custom command message to the Gateway.

Restart Gateway

Description: It restarts a gateway. It does not apply to an asset.
Type: Request-Reply

Topic:

// topic pattern:
iot/gateway/+/command/+
iot/gateway/{gateway_id}/command/{command_name}

// example
iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/restart

Body

// example
{
  "request_id": "ppate1690571776080"
}

Get Registeration Cache (All)

Description: It retrieves registeration caches of all assets and gateways
Type: Request-Reply

Topic:

// topic pattern:
iot/gateway/+/command/+
iot/gateway/{gateway_id}/command/{command_name}


//  example
iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-thing-cache

Body

{
  "request_id": "ppate1690571863558"
}

Get Registeration Cache (Thing)

Description: It retrieves registeration cache of a specific thing. A thing could be gateway or asset.
Type: Request-Reply

Topic:

// topic pattern:
iot/gateway/+/command/+
iot/gateway/{gateway_id}/command/{command_name}


//  example
iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-cache-thingid

Body

{
  "thing_id": "{thing_id}", // e.g., 10P-KEG01, VirtualGateway-PLAATO-USEAST1-DEV-01
  "request_id": "ppate1690572125580"
}

Clear Registeration Cache

Description: It clears registeration cache of a thing. A thing could be gateway or asset.
Type: Request-Reply

Topic:

// topic pattern:
iot/gateway/+/command/+
iot/gateway/{gateway_id}/command/{command_name}


//  example
iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/clear-cache

Body

{
  "thing_id": "{thing_id}", //e.g., VirtualGateway-PLAATO-USEAST1-DEV-01, 10P-KEG01
  "request_id": "ppate1690572498198"
}

Get ThingType Cache

Description: It retrieves specification cache of a thing type.
Type: Request-Reply

Topic:

  // topic pattern:
  iot/gateway/+/command/+
  iot/gateway/{gateway_id}/command/{command_name}

  //  example
  iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-spec-cache

Body

{
  "thing_type": "{thing_type}", //e.g., Brewing_Keg, Virtual_Gateway_PLAATO
  "request_id": "ppate1690572761850"
}

Get IO Status

Description: It retrieves status of various IOs.
Type: Request-Reply

Topic:

  // topic pattern:
  iot/gateway/+/command/+
  iot/gateway/{gateway_id}/command/{command_name}


  //  example
  iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-io-status

Body

// example
{
  "request_id": "ppate1690573052355"
}

Get Connector Status

Description: It retrieves status of all connectors attached to a gateway.
Type: Request-Reply
Topic:

  // topic pattern:
  iot/gateway/+/command/+
  iot/gateway/{gateway_id}/command/{command_name}

  //  example
  iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-connector-status

Body

//example
{
  "request_id": "ppate1690573316704"
}

Get Device Cache

Description: It retrieves cache of a device data
Type : Request-Reply
Topic:

  // topic pattern:
  iot/gateway/+/command/+
  iot/gateway/{gateway_id}/command/{command_name}

  //  example
  iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/get-device-cache

Body

// example
  {
    "thing_id": {thing_id},
    "request_id": "ppate1690580697957"
  }

Test thing data

Description: It lets your test your data. It inputs sample data of an asset/gateway and outputs processed data from rules-engine.
Type: Request-Reply
Topic:

// topic pattern:
iot/gateway/+/status/+
iot/gateway/{asset_id}/status/{request_id}

//  example
iot/gateways/VirtualGateway-PLAATO-USEAST1-DEV-01/command/test-thing-data

Body

// example
{
  "externalKey": "{asset_id}", // e.g., 10P-KEG01
  "request_id": "ppate1690573756372",
  ... // add sensor data
}

Reset Registration Cache

Description: It resets cache of an asset or an gateway.
Type: Broadcast
Topic:

// topic pattern
iot/cache/registration/{asset_id}/invalidate


// example
iot/cache/registration/10P-KEG01/invalidate

Body

// example
{
  "externalKey": "{asset_id}", //e.g., 10P-KEG01
  "message": "Manual Registry cache reset."
}

Reset ThingType Cache

Description: It resets cache of thingtype. A thingType could be a gateway or thing
Type: Broadcast
Topic:

// topic pattern
iot/cache/specification/{thing_type}/invalidate


// example
iot/cache/specification/Brewing_Keg/invalidate

Body

// example
{
  "thingType": "{thing_type}", //e.g., Brewing_Keg
  "message": "Manual Registry cache reset."
}

MQTT Template

Type: The type of message (Broadcast, Request-Reply). NOTE: In the initial release only Broadcast is supported.
Topic: The MQTT Topic to publish the command to
Body: The JSON payload of the command

NOTE

This is especially useful if you are using a custom connector. This will allow you to publish a message to the Gateway, which will in-turn publish it to the connector itself. Use the following topic format for Connector commands: iot/gateways/{GATEWAY_ID}/connector/xxx

Docs: IoT Console

Mon, 01 Jan 0001 00:00:00 +0000

The IoT Console is the centralized dashboard for viewing all Connected Assets within an Instance. Connected Assets will be displayed on the Map for all Assets matching the current filter, if they have the Location fields filled in.

The IoT Console is available in the Connected Assets Workspace through the IoT Console button in the navigation bar.

Opening the IoT Console

The three tabs in the IoT Console are the Map, List View, and Card View. Filtering is shared between all three tabs.

Map

The Map displays every Connected Asset which matches the filters and whos Asset’s Location field is filled in. The Map groups assets by location dynamically. You can click into any of the regions, and if they have a subregion map that is suported within ServiceNow, it will filter by the region and group by the subregions. This filter and group by is shared by all three tabs within the IoT Console. Every filter change is shown in the breadcrumbs in the top left of the map. These breadcrumbs can be selected to revert the filter and map level back to what it was when the breadcumb was made.

World Region Map

USA Region Map

Filtered USA Region Map

List View

The List View displays the Connected Assets which match the filters and have an Asset with the Location field filled in. The Connected Assets are grouped by the current region level to match the Map tab.

List View

Card View

The Card View displays the Connected Assets which match the filters and have an Asset with the Location field filled in with clickable Cards. Each link on the Cards can be clicked to open the record within the workspace. The Connected Assets are grouped by the current region level to match the Map tab.

Card View

Classic Map View Module

The Connected Asset Map Module displays all of the Connected Assets in an Instance whose Asset’s Location Field is filled in. The map is set within the standard ServiceNow Google Maps system property. Each pin contains all of the Connected Assets in a given loction. When clicked, a list of these Connected Assets pops up. A Connected Asset within this list can be selected to navigate to the Classic Connected Asset record page to view the Connected Asset.

Connected Asset Map

Docs: Things

Mon, 01 Jan 0001 00:00:00 +0000

All of the below components are implemented as both ServiceNow UI Actions and ServiceNow UX Actions. The UI Actions are included in the Thing Type (x_bdngl_iot_thing_type) table, and can be shown / hidden from users using standard ServiceNow Roles, Views, UI Action Visibility Related List, and UI Policies. The UX Actions are included in the Connected Assets Workspace via the Thing Type Action Config record in the UX Form Actions Layout table, and can be shown / hidden from users using View Rules and the Thing Type Action Config record.

Thing Registration (Connected Asset Module)

The ‘Register’ UI Action allows you to Register a new Connected Asset using the fields visible in the form:

IoT Thing ID: The unique Id assigned to this thing / device.
IoT Gateway: The Gateway this Thing will be connected to.
IoT Thing Type: The ThingType (from the IoT Setup Module) that this thing will use.

Sync Context (Connected Asset Module UI Action)

The Connected Asset Module allows you to manually push the Context Data for this specific IoT Connected Asset to the IoT Cloud.

This could be useful if the Context Values have changed for this IoT Connected Asset, and you don’t want to wait for the next scheduled Context Sync job to run.

After clicking the button, wait up to 60 seconds or until you see a blue message at the top of your screen to verify the updated Context Sync status.

Sync Attributes (Connected Asset Module UI Action)

The Connected Asset Module allows you to manually pull the latest Sensor Data for this specific IoT Connected Asset from the IoT Cloud.

This could be useful if Sensor Data has changed for this IoT Connected Asset and you don’t want to wait for the next scheduled Sensor Sync job to run.

After clicking the button, wait about 30-60 seconds and refresh the page to verify the updated Asset Attribute records.

Thing Record Page

Manual Sensor Entry (Connected Asset Module UI Action)

The Connected Asset Page allows you to manually submit Sensor Values for this specific Thing to the IoT Cloud.

Manual Sensor Entry Button

This could be useful if this Connected Asset is not able to communicate due to security/firewalls or is temporarily disabled. The manually entered sensor values are uploaded and processed by the Rules Engine and stored in the IoT Cloud Data-Lake just like they would if they were received as a real IoT message.

Manual Sensor Entry

Note

It’s important to add to this Manual Sensor Entry form is dynamic, based on the Sensors defined in the Thing Type. The Data Type and Storage Data Type influence the type / validation of each field on the form.

Deregister (Connected Asset Module)

The Connected Asset Module allows you to De-Register a Connected Asset. This will remove the Connected Asset from the thing registry, stop the flow of data, and reduce device licensing.

Thing Chart & Data

By default, the 25 most recent messages will be displayed in the chart tab. This chart is fully interactive: zoom in/out, select/deselect sensors to hide/show them, scroll left/right, etc.

Thing Data Chart

The data tab allows you to see the same messages displayed in the chart tab, but in tabular/spreadsheet format, and download as a CSV file.

Thing Data Table

Stream

The Thing Chart now has the ability to Live Stream IoT data. After clicking on the “Play” Stream button, you’ll see the chart re-draw with each new message as it is received from the IoT Gateway.

Thing Chart Live Stream

Split Axes

The Thing Chart can now split the plotted values across 3 Axes by separating them by their maximum absolute values.

Thing Data Chart: Split

Thing Commands

This component allows the user to send a Command to a Connected Asset. Bolt Data Connect will route your command to the IoT Cloud, then the Edge Gateway, and ultimately to the device itself. Keep in mind that the device must know how to interpret this command for it to respond accordingly.

Thing Command

Thing Command on Thing Type Page

Thing Command in the Classic UI

Digital Twins

See the Digital Twin Diagram / Editor

On the IoT Connected Asset Record Page, add the IoT Digital Twin and easily view/edit the Digital Twin from any Thing in the configured Hierarchy.

The Diagram shows all of the most recent sensors and calculated fields from all Things in the same Digital Twin.

Digital Twin Viewer

The Legend shows the notation of the diagram including Sensors, Calculated Fields and Alert Conditions
Use the Digital Twin Toolbar to:
- Refresh the latest values
- Attach the data to the IoT Copilot Chat
  
  Attach Digital Twin Data to IoT Copilot

Unified Map

The Unified Map shows the same data that the Digital Twin Diagram shows, but it does so in an interactive environment. Each node in the Unified Map can be both moved and searched to help find specific fields. There are multiple layouts available in the Unified Map. The default layout is a horizontal heirarchy from left to right. If the ServiceNow version is Zurich or later, there will be additional buttons on the right side to switch the layout to a vertical heirarchy and a unified force view. In all views, assets and data can be dragged around and moved.

Unified Vertical Layout

Unified Force Layout

IoT Copilot

Use IoT Copilot to give users the ability to ask natural language questions in an IoT Copilot Chat. Users can ask questions about a connected asset’s performance based on IoT telemetry data and alert history, unlocking instant insights.

IoT Copilot Connected Asset Chat

The Global IoT Copilot found in the Connected Asset Workspace can be used to ask questions spanning all connected assets within the instance.

IoT Copilot Global Chat

Note

ServiceNow Now Assist licensing is not needed to take advantage of IoT Copilot. We are using Generative AI models behind our IoT Cloud API layer, utilizing a world-class Trust Layer to protect the data and privacy.

Configurable Options

Thing Type

Each Thing Type can be given unique instructions using the Copilot Instructions field. These instructions give IoT Copilot the context it needs to understand how to interpret each Thing Type to answer questions more accurately.

Thing Type instructions for IoT Copilot

Settings

You can configure the following options in IoT Setup -> Settings:

Introduction section of Connected Asset Agent Prompts
The Question section of Connected Asset Agent Prompts
The Answer section of Connected Asset Agent Prompts
Error response of Connected Asset Agent Prompts
Agent Model (LLM):

Connected Asset Agent Models

Sensor Gauges

The “Gauges” tab in the Connected Asset Record Page in the Connected Asset Workspace is used to render sensor values as a Single Score, a Progress Bar, or a Dial. There is a Gauge Configurator tab on the Thing Type Record page to set them up.

Open the desired Thing Type in the Connected Asset Workspace.

Gauge Configurator Location
Click the “Add Gauge” button to add Gauges to the thing type. You can set:
- Title
- Title is Sensor Name sets the title to the result of a sensor described by the Title field
- Sensor sets the sensor to display a Gauge for
- Gauge Type sets the Gauge to render as a Single Score, Progress Bar, or a Dial
- Row sets the vertical order that the Gauge will render on
- Column sets the horizontal order within a Row that the Gauge will render on
- Order sets the vertical order within a column that the Gauge will render on
- Min sets the minimum value for Progress Bars and Dials
- Max sets the maximum value for Progress Bars and Dials
- Precision controls how many decimal places to display on the gauge
Sensor Gauges Editor
Click Submit

Sensor Gauges Editor Submit Message
See the resulting Gauges in the Connected Asset Record Page in the Connected Asset Workspace

Sensor Gauges

Docs: Simulators

Mon, 01 Jan 0001 00:00:00 +0000

This section provides details on how to use and configure Connected Asset Simulators.

Simulators are runtime engines for testing IoT Gateways and Things. When you open the IoT Simulated Assets Module or the Simulated Assets table in the Connected Assets Workspace, it displays a list of all the Simulators within this ServiceNow org. These Simulators can “impersonate” devices by generating the messages typically sent from the actual devices.

Simulators

Simulators in the Workspace

Controlling Simulators

You can open a simulator by clicking on the name. With a simulator open, you can do the following:

Change the Status (#1)
Select the Connected Asset to simulate (#2)
Select the Mode (#3)

You can change the Connected Asset and Status from the list view. To remove a simulator, you can delete the record.

Modes (#3) are configured below, and define the different combinations of values being sent from the simulated devices. You can see which Mode every device is in, as well as change the mode by switching it in the Simulator Record. This will cause the device to send different values, possibly resulting in an Alert Condition, to aid in testing and validation of the configured automation.

Simulator Console Controls

Note

If your simulated Thing shows “running”, but is not connected or sending data, it is possible that:

There is a problem with the Simulator Config (next section). Double check all parameter values and types (Numbers, etc).
The Gateway might need to be re-registered.
The IoT Simulator Scheduled Job is not enabled.

Configuring Simulators

Simulator Builder

The Simulator Builder is a UI Page found on the right side of the Thing Type page in the Workspace. This can be used to configure Simulators which run within the ServiceNow Instance.

Instructions

Open the Thing Type in the Connected Asset Workspace.
Click the Simulator Builder Side Button to open the Simulator Builder.

Simulator Builder Button on a Thing Page

Add and fill out Parameters to Normal Mode.

See Schema and Sensor Parameters to see details for each paramter type and value

Add other Modes as needed.
Click “Submit” at the bottom of the Simulator Builder to save Simulator Configuration to the page.

Filling our a Constant Mode Constant Parameter

Filling our a Constant Mode Random Parameter

Modes

Each Thing Type can be setup with multiple “modes”. You should always start with the default “Normal” mode, then configure alternate modes.

BEST PRACTICE

It’s a best practice to configure a mode to correspond to each Alert Condition to enable easy testing.

Each mode can define what simulated value will be returned for each Sensor. Click the Add Parameter button to add a new sensor value simulation.

Sensor Parameters

The following types of Sensor Parameters are currently supported:

Constant Constants will send the same “Constant Value” consistently.

Simulator Parameter - Constant
Counter The Counter is a numeric value. It will default to the “Start” value, and will change by the “Step” amount at each “Interval”. When it reaches the “End”, it will start over again.

Simulator Parameter - Counter
Random-Uniform The Random / Uniform is a numeric value. It will be a random number between the “Lower” and “Upper” values, and will change at every “Interval”.

Simulator Parameter - Random
Random-Choice The Random / Choice can be numeric, boolean, text, etc. It will randomly choose between the provided “Choice Values”, and will change at every “Interval”.

Simulator Parameter - Choice
Datetime The Datetime can be numeric or text. It will be recalculated on every message, relative to the current date/time. The Offset can be either positive (future) or negative (past), or 0 for current date/time. The format can either be epoch (to return the epoch in milliseconds) or a valid Python datetime format (e.g. %Y-%m-%d_%H:%M:%S) to return any textual date or time format.

Simulator Parameter - Datetime

SAVE

After adding or editing the modes and parameters, don’t forget to Submit.

Direct JSON Configuration

Simulators can also be configured in the Simulator Config field in the Thing Type record using the following JSON format. It is recommended that Simulaters are configured within the Simulator Builder.

Simulator JSON Field

Schema

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "IoT Simulator Config",
  "description": "Schema for configuring IoT Simulated Asset data generation with various modes and parameter types.",
  "type": "object",
  "properties": {
    "interval": {
      "type": "number",
      "description": "The overall interval (in seconds) at which the device data should be generated.",
      "minimum": 0
    },
    "modes": {
      "type": "array",
      "description": "An array of different data generation modes, each with its own set of parameters.",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "The name of the data generation mode (e.g., Normal, Alert1)."
          },
          "parameters": {
            "type": "array",
            "description": "An array of specific parameters to be generated for the current mode.",
            "items": {
              "type": "object",
              "properties": {
                "paramType": {
                  "type": "string",
                  "description": "The type of parameter generation method.",
                  "enum": ["Random", "Constant", "RelativeDatetime", "Counter"]
                },
                "sensorName": {
                  "type": "string",
                  "description": "The name of the sensor or data point this parameter represents (e.g., ink_level, modelType)."
                },
                "interval": {
                  "type": "number",
                  "description": "The interval (in seconds) at which the counter should increment.",
                  "minimum": 0
                },
                "dataType": {
                  "type": "string",
                  "description": "The expected data type of the sensor value.",
                  "enum": ["Number", "Text"]
                }
              },
              "required": ["paramType", "sensorName", "interval", "dataType"],
              "oneOf": [
                {
                  "if": { "properties": { "paramType": { "const": "Random" } } },
                  "then": {
                    "properties": {
                      "randomDistribution": {
                        "type": "string",
                        "description": "The type of random distribution to use.",
                        "enum": ["uniform", "choice"]
                      },
                      "randomLower": {
                        "type": "number",
                        "description": "The lower bound for 'uniform' random distribution."
                      },
                      "randomUpper": {
                        "type": "number",
                        "description": "The upper bound for 'uniform' random distribution."
                      },
                      "randomChoiceValues": {
                        "type": "string",
                        "description": "A comma-separated string of possible values for 'choice' distribution."
                      }
                    },
                    "required": ["randomDistribution"],
                    "if": { "properties": { "randomDistribution": { "const": "uniform" } } },
                    "then": { "required": ["randomLower", "randomUpper"] },
                    "else": { "required": ["randomChoiceValues"] }
                  }
                },
                {
                  "if": { "properties": { "paramType": { "const": "Constant" } } },
                  "then": {
                    "properties": {
                      "constantValue": {
                        "type": ["string", "number"],
                        "description": "The fixed, unchanging value for this parameter."
                      }
                    },
                    "required": ["constantValue"]
                  }
                },
                {
                  "if": { "properties": { "paramType": { "const": "RelativeDatetime" } } },
                  "then": {
                    "properties": {
                      "offsetValue": {
                        "type": "number",
                        "description": "The value of the offset (e.g., -1 for 1 day ago)."
                      },
                      "offsetType": {
                        "type": "string",
                        "description": "The unit of the offset value (e.g., Days, Hours).",
                        "enum": ["Days", "Hours", "Minutes", "Seconds"]
                      },
                      "format": {
                        "type": "string",
                        "description": "The desired date/time format string (e.g., yyyy-MM-dd_HH:mm:ss, epoch)."
                      }
                    },
                    "required": ["offsetValue", "offsetType", "format"]
                  }
                },
                {
                  "if": { "properties": { "paramType": { "const": "Counter" } } },
                  "then": {
                    "properties": {
                      "counterStart": {
                        "type": "number",
                        "description": "The initial value of the counter."
                      },
                      "counterEnd": {
                        "type": "number",
                        "description": "The maximum value the counter will reach before resetting or stopping."
                      },
                      "counterStep": {
                        "type": "number",
                        "description": "The amount by which the counter increments each interval."
                      }
                    },
                    "required": ["counterStart", "counterEnd", "counterStep"]
                  }
                }
              ]
            },
            "minItems": 1
          }
        },
        "required": ["name", "parameters"]
      },
      "minItems": 1
    }
  },
  "required": ["interval", "modes"]
}

Docs: IoT Setup

Mon, 01 Jan 0001 00:00:00 +0000

Docs: User Setup

Mon, 01 Jan 0001 00:00:00 +0000

This section provides details on how to setup ServiceNow Users for Bolt Data Connect.

Roles

Included with the app are two Roles which can be used as-is:

IoT Admins x_bdngl_iot.admin: Full Admin access to all Bolt Data Connect features including the IoT Settings page.
IoT Users x_bdngl_iot.user: Access to Bolt Data Connect data, visualizations, and interactions.

Each Bolt Data Connect User should be assigned to one of the above Roles.

OAuth

For Users to setup the OAuth access, allowing the IoT Cloud to send alerts and other data into ServiceNow, you will need to access the following tables:

sys_alias
aws_credentials
auth_algorithm

For more details, see Authorize the ServiceNow Instance to access the IoT Cloud

Docs: Release Notes

Mon, 01 Jan 0001 00:00:00 +0000