×
![]()
Notifications App Release Notes
The initial installation of ITRS Analytics includes all required app, such as the Web Console, bundled by default. No separate installation steps are required for individual apps. For installation guidance, refer to the Install ITRS Analytics apps documentation.
To stay informed about the most recent updates and packaging versions, you can refer to the ITRS Analytics Packaging Changelog. This resource provides direct links to release notes for each bundled version of the ITRS Analytics Platform and its apps, bill of materials listing all included components, and references to the published Docker images.
Notifications 3.9.0 Copied
Released: 30 October 2025
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-404 | Added a new placeholder notification.name that displays the name of the triggered notification. This allows you to reference the specific notification name in your messages, making notifications clearer and easier to identify. |
| OBAN-441 | Moved incident table field override settings from Target to Notification configuration, allowing dynamic placeholders in custom field values and making ServiceNow integrations more flexible and easier to configure. |
| OBAN-445 | Updated the placeholders dialog to let users copy templates directly to the clipboard by clicking on them, streamlining the setup of notifications. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| OBAN-449 | Updated Spring Framework to version 3.5.6 to address a high-severity security vulnerability CVE-2025-41249. |
Notifications 3.7.0 Copied
Released: 25 July 2025
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-293 | The Notifications REST APIs are now available and support creating, retrieving, updating, and deleting notifications, as well as notification targets. |
| OBAN-407 | Updated the Notification app to align with the latest UI framework. |
Notifications 3.6.0 Copied
Released: 10 June 2025
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-324 | Email is now available as a notification target. Notifications can be sent to an email address or distribution list using the settings of an SMTP server. TLS is supported as well as custom server certificates for private SMTP servers. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| OBAN-329 | Fixed an issue with the notifications count not updating properly when changing time presets. |
| OBAN-380 | Resolved the following CVEs related to libxml2 and spring-security-crypto:
|
Known issues Copied
These are the known issues affecting this release:
| Security advisory ID | Known issue description |
|---|---|
| CVE-2025-22868 | In SQLite versions 3.44.0 to 3.49.0, the concat_ws() SQL function contains an integer overflow vulnerability. An attacker can exploit this by providing a large, attacker-controlled separator argument, leading to insufficient memory allocation and a heap-based buffer overflow. |
| CVE-2025-29087 | A reported security vulnerability allows an attacker to cause excessive memory consumption by providing a malformed token during parsing. |
| CVE-2025-4638 | A vulnerability in the inftrees.c component of the zlib library, bundled with PointCloudLibrary (PCL), can lead to undefined behavior due to improper pointer arithmetic. This issue primarily affects PCL versions older than 1.14.0, or installations where WITH_SYSTEM_ZLIB is explicitly set to FALSE. |
Notifications 3.5.0 Copied
Released: 25 March 2025
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-325 | Microsoft Teams is now available as a notification target. Notifications can be sent to an MS Teams channel using a Workflow URL, which can be generated through the channel’s Workflows option. |
| OBAN-326 | The entity Notification URL now takes users to the Activity tab of the entity details panel. |
| OBAN-328 | When navigating to an entity from a Notification URL, the page now displays the entity’s ancestors and descendants. |
| OBAN-352 | The group Notification URL now navigates to a drill-down view of the triggered group. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| OBAN-363 | Resolved the following high-severity security vulnerabilities:
|
Notifications 3.4.0 Copied
Released: 23 January 2025
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-308 | The ${url} placeholder now redirects the user to the Entity Viewer app.
|
Legacy releases Copied
Notifications 3.3.0 Copied
Released: 4 October 2024
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-305 | Upgraded the base image to resolve CVEs. |
| OBAN-306 | App workloads now restart if any of their configuration options change via a helm upgrade. |
Notifications 3.2.1 Copied
Released: 16 August 2024
Minimum required ITRS Analytics Platform version: 2.5.0
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-307 | Upgraded iam-tools to version 2.6.0 to resolve critical CVEs. |
Notifications 3.2.0 Copied
Released: 10 April 2024
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-259 | Implemented GetBulkMetrics to fetch notification statistics. |
| OBAN-282 | Updated Kubernetes containment rules in line with Platform 2.2.0 changes. |
Notifications 3.1.0 Copied
Released: 23 January 2024
Caution
Before upgrading, you must first uninstall all ITRS Analytics apps. Due to a breaking change in a core library (Spring Boot), you need to upgrade all ITRS Analytics apps at the same time. Make sure that you reinstall the latest mutually compatible versions of ITRS Analytics apps. See the ITRS Analytics Compatibility Matrix.
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-260 | Upgraded Spring Boot to version 3.2.1, which resolves the following reported security vulnerability: BDSA-2023-3298 or CVE-2023-46589. |
Notifications 3.0.0 Copied
Released: 8 December 2023
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-247 | Upgraded app for compatibility with ITRS Analytics Platform 2.0. |
Notifications 2.1.0 Copied
Released: 31 July 2023
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-210 | The Slack test connection now checks whether the channel’s name is configured instead of its ID. This prevents an error previously encountered when only the channel name was supplied and it did not match the channel ID. |
| OBAN-216 | ServiceNow is now available as a notification target.
|
| OBAN-221 | Placeholders are now supported in ServiceNow incident table field values. |
| OBAN-222 | The following placeholders are now supported:
|
| OBAN-235 | The following self-monitoring data are now available:
|
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| OBAN-206 | Renamed targets are now correctly reflected in the value of the notification-url attribute for Slack and ServiceNow. |
| OBAN-209 | The Snackbar error is not displayed when the error is handled from the UI with a dialog, such as when a target or notification is out-of-sync or not found. |
| OBAN-211 | When a notification is updated with one or more targets that have been deleted, a new dialog is displayed, indicating that the targets (which are not found) will be removed from the selection. |
| OBAN-212 | Updating the target’s channel ID now correctly updates the notification-url attribute value to point to the new channel. |
| OBAN-213 | Previously, it was possible to save an out-of-date notification when you double-click the Save button. A dialog is now displayed indicating that the notification will be updated. |
| OBAN-224 | Entities with their notification-url attribute removed due to a notification or target being disabled are now correctly re-tagged when the notification or target is re-enabled. |
Notifications 2.0.0 Copied
Released: 28 June 2023
Caution
Upgrading to the Notifications app version 2.0.0 will not be compatible with previous versions of the app. Any existing notification configurations and internal states on notifications by a previous version of the app will be permanently and irreversibly deleted when you upgrade.
Caution
Before upgrading, you must first uninstall all ITRS Analytics apps. Due to Web Platform security changes, you need to upgrade all ITRS Analytics apps at the same time. Make sure that you reinstall the latest mutually compatible versions of ITRS Analytics apps. See the ITRS Analytics Compatibility Matrix.
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| OBAN-125 | Inactive entities are now detected through the inactive-since attribute instead of last-observed. |
| OBAN-149 | Renamed Conditions field to Filter in the main configuration screen. |
| OBAN-150 | Improved error handling when configuring the notification trigger timings. |
| OBAN-151 | Decoupled integration-specific target configurations from the main configuration screen and moved them to a new screen. You can now manage targets independently of notifications, while multiple notifications can now use the same target. Notifications may only use targets of the same type, such as Slack. The Notification app has also been moved out of Alerting and into its own top-level item on the sidebar. |
| OBAN-183 | Restricted notification and target names to a maximum of 50 characters, and notification and target descriptions to a maximum of 150 characters. |
| OBAN-188 | Cloned notification configurations are now disabled. |
| OBAN-191 | User actions related to CRUD operations on target and notification configurations are now logged in a parsable and searchable format. |
| OBAN-194 | A placeholder message is now shown when no targets have been configured for an integration. |
| OBAN-195 | Improved error messages when saving a notification or target configuration. |
| OBAN-196 | Notification configurations prior to version 2.0.0 of the app are removed during the upgrade. |
| OBAN-201 | The notification entity filter and groupings cannot be modified after being set. To change the filter or grouping, the notification configuration needs to be cloned. |
| OBAN-204 | Notification and target names are now limited to 50 characters, while notification and target descriptions are limited to 150 characters. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| OBAN-134 | Attempting to enable a draft notification prior to setting the mandatory notification target fields no longer results in an error. |
| OBAN-137 | The notifications table has been made adaptive to the screen size. |
| OBAN-138 | Entities are now correctly tagged with a Slack permalink when a Slack channel name is used in the configuration instead of an ID. |
| OBAN-148 | The ${url} placeholder now points to the correct ITRS Analytics URL. |
| OBAN-175 | Notifications are no longer triggered on inactive entities. |
| OBAN-176 | A more meaningful error message is shown when trying to save a grouped notification using a placeholder that is only available for non-grouped notifications. |
Disclaimer
The information contained in this document is for general information and guidance on our products, services, and other matters. It is only for information purposes and is not intended as advice which should be relied upon. We try to ensure that the content of this document is accurate and up-to-date, but this cannot be guaranteed. Changes may be made to our products, services, and other matters which are not noted or recorded herein. All liability for loss and damage arising from reliance on this document is excluded (except where death or personal injury arises from our negligence or loss or damage arises from any fraud on our part).
["ITRS Analytics"]
["Release Notes"]