Skip to content

Notification Updates Guide

April, 2025 - Recent Notification updates in ExoSense.

Overview

To expand features, functionality, and usability of ExoSense Notifications, a number of improvements have been made and are planned for how users manage their notifications within the application.

  • Some changes and updates will apply to all ExoSense users, instances, and tiers.
  • Some functionality and features will be available at higher tiers or as add-ons.

New Concepts

To provide greater flexibility, notifications are now supported with a feature called Notification Lists within ExoSense. Notification lists provide users the ability to not only specify what assets (or groups of assets), but also a filter of what they want to be notified for. Unlike before, users are now able to create multiple lists which provides the flexibility to create filters for different groups of assets.

Long term, Notification Lists will also have support for managed lists involving many users. Team leaders, managers, administrators may manage lists on behalf of customers and teams.

Rollout Plan

The initial rollout of Notification Lists was released in v2.47.0, replacing the legacy notification interface, while user's subscriptions were migrated to the new interface.

Additional features will be added in the future.

Changes

Layout

Notification Lists will be managed in a dedicated section of the ExoSense application, found in the side navigation. Here, users will find notification lists they own (private) or are a part of (future "managed" functionality).

New Notification Management Page
New Notification Management Page

Each list provides the ability to choose specific assets or entire groups. When a group is selected, all assets in the group (and child sub-groups) are considered a part of the list. This allows dynamic updates as assets are created or removed from the group.

The Filters on the list allows users to choose to which status rule event types, condition lifecycle, and condition policies to receive notifications for on the specific list. This enables different lists to serve different purposes.

Example Supported Use Cases

Different Lists for Different Assets

An example may be a list for only critical runtime parts of a machine leveraging subsystems and/or condition policies to filter these for delivery of critical notifications. Another list can be set up for the other parts of those machines (assets) that may not be as highly prioritized for receiving notifications for.

-> status warning or status critical ->

-> status critical ->

Different Lists for SMS and Email Severity Levels

Two (or more) lists may also be used to separate the types of notifications to receive via Email (all) and via SMS (only critical). This would allow only the most important severity messages for a set of assets to be sent via SMS, while another list includes all severity levels via email.

-> status warning ->

-> status critical ->

User Profiles

User's will continue to manage their contact information and notification rules (time of day) in their user account profile, with some slight changes to the UI.

Changes to User Profile

Changes to User Profile
Changes to User Profile

Future

Exosite has collected user feedback and continues to look at ways to add and improve functionality that benefits users and to improve workflows and processes. Additional updates will be incorporated to improve the experience and options for notifications over time that may not be outlined here. Exosite will be planning out additional features that include concepts for:

Managed Lists

Users with the permission in their role will be able to create Notification Lists that include many users. This ensures a team is getting the right notifications and not requiring each user to manage themselves.

User Teams

This is a collection of users to simplify managed lists.

Escalations

This will provide the ability to create lists that will notify sets of users at a later time period and to continue to send notifications until the condition no longer exists. This description is using the term 'condition' loosely, as this functionality will apply to other scenarios outside of just conditions.

Here is a summary of the functionality proposed for Notification Lists vs the legacy notification functionality in ExoSense.

Functionality Notification Lists Legacy Notifications
Per User (Private) Notification Lists (Subscriptions)
Filtering on Rule Event States
Filtering on Condition Events
Subscriptions for entire groups
Filtering on Condition Policies
Multiple Lists (Different sets of Subscriptions / Filters )
Filtering on Subsystems
Managed (Multi-User) Notification Lists
User Teams
Escalations
More Controls of User Notification Profile Rules