Installed with push notifications
- UpdatedJul 31, 2025
- 3 minutes to read
- Zurich
- Notifications
Several types of components are installed with the push notifications plugins.
Tables installed with push notifications
These tables are installed with push notifications.
| Table name | Description |
|---|---|
| Push Applications [sys_push_application] | Push applications registered to the instance to receive push messages. |
| Push Default Registrations [sys_push_notif_default_reg] | Contains all the notifications users are automatically subscribed to for a given push application. You can add notifications to this table on the Push Default Registrations related list on the Push Application form. |
| Push Feedbacks [sys_push_feedback] | Feedback from the APNs that tells the instance which push devices can no longer receive push messages. The feedback is handled either on the same instance where your notifications are triggered, or on a central instance that uses a REST call to tell your instance which push applications to deactivate. |
| Push Message Attribute Definitions [sys_push_notif_msg_attr_def] | The attribute definitions used for push message content specification. |
| Push Message Attribute Values [sys_push_notif_msg_attr_val] | The values associated with push messages. |
| Push Notifications [sys_push_notification] | The push notifications that the instance attempted to send to users. |
| Push Notification Actions [sys_push_notif_act_script] | The action scripts that the instance uses in response to an actionable push message. |
| Push Notification Installations [sys_push_notif_app_install] | The devices with push apps where users agreed to receive push notifications. This
table lists the records by the token for the push app. The instance uses this
information to know which push device and app to send notifications to. Records are
created in this table when a user logs on an instance with the push app. The Mobile Devices [sys_mobile_devices] table, which is installed with the Mobile UI plugin, contains all the user devices that logged in to the instance with the ServiceNow mobile application. |
| Push Notification Messages [sys_push_notif_msg] | Messages customized for push notifications. These messages can be associated with a notification. |
| Push Notification Message Contents [sys_push_notif_msg_content] | The entire content, including JSON, for push messages. |
| Push Platforms [sys_push_platform] | The platforms that are supported for push notifications, and the maximum payload size. |
Business rules installed with push notifications
These business rules are installed with push notifications.
| Business rule | Table | Description |
|---|---|---|
| Build Device and Subscriptions | Push Installation [sys_push_notification_installation] | Automatically creates a notification device on a user's notification preferences when the user registers a mobile application with the instance. |
Outbound REST messages installed with push notifications
These outbound REST messages are installed with push notifications.
| REST message | Description |
|---|---|
| ServiceNowMobileApp Push | The REST message that you can use with your custom iOS mobile app. |
Roles installed with push notifications
These roles are installed with push notifications.
| Role | Description |
|---|---|
| push_admin | Can create and modify push notifications. |
Push components installed with push notifications
These components are installed with push notifications.
| Push application | Description |
|---|---|
| ServiceNowPushApp | The push application record for the ServiceNow
ServiceNow
mobile application. Note: The ServiceNow mobile app automatically subscribes users
to several push notifications. You can see the list of these notifications in the
Push Default Registrations related list on the ServiceNowPushApp application
record. |
| Message content | Description |
|---|---|
| ConnectMessageContent | The payload for ServiceNow connect messages. |
| Generic Approval (Background) | The payload that provides an approval and rejection option to the user receiving the push message. |
| Generic Approval (Foreground) | The payload that provides an approval and rejection option to the user receiving the push message. |
| Generic Record Payload | A generic payload that you can use to send push messages to users. |
| Push notification action | Description |
|---|---|
| Approval - Approve | Allows an administrator to approve a request. |
| Approval - Reject | Allows an administrator to reject a request. |
| Push notifications | Table | Description |
|---|---|---|
| ConnectMessagePushNotification | Live Feed Message [live_message] | Sends a push notification when a new live feed message |
Related Content
- Push notification system
The push notification system involves several key elements that manage the delivery of push messages and push notification responses.
- Activate push notifications
Several plugins must be activated to use push notifications. If you have the Mobile UI (com.glide.ui.m) plugin active, push notification plugins are automatically activated.
- Push notification properties
Push notifications provides several properties to customize the setup.
- Push notification setup with the ServiceNow mobile app
The ServiceNow mobile application automatically enables push notifications and configures mobile devices for push notifications when users initially log in to the instance.
- Push notification setup with a custom push application for ServiceNow mobile apps
If you are using your own custom mobile or push application, you must configure your app for use and set up the push contents.
- Requeue failed push notification messages
Push notification delivery might fail for various reasons. You can view which messages failed and requeue them to be sent out if necessary.
- Push notification retention
You can archive and eventually destroy push notifications that you no longer need or if your Push Notification table is excessively large.