Pulse 7.2.1 delivers important performance improvements, enhanced control over Chore/Process logging, and a more streamlined installation experience. This release removes the Thick Client, adds new filtering options for session‑based alerts, and resolves multiple issues across dashboards, documentation updates, pagination, and history views. Overall, the update focuses on stability, performance, and simplifying the user workflow.

Downloads:

• https://forum.cubewise.com/t/pulse-release-v7-2-1/7534

Important considerations when upgrading

1. Before executing the Pulse installer, it is recommended to stop the Pulse services manually.

2. If your Pulse server is v6.6.0 on Windows (Pulse Monitor should be v2.2.0), then you don't need to upgrade the Pulse Monitor. It is recommended to upgrade to the latest Pulse Monitor (now at v2.2.1) for Linux. Significant optimizations have been added to the Pulse Monitor in v6.6.0. If your Pulse version is lower than v6.6.0 then after upgrading the Pulse Application Server, you should upgrade the Pulse Monitor on each TM1 server (Customers on IBM Cloud are not impacted).

3. It is recommended to Back-up Pulse.

4. The conf\server.xml file is overwritten by the Pulse installer by default. You can now untick the option to overwritte this file. If you do not untick this option, you will be able to find your changes in the conf\server.xml.backup file.

5. After upgrading Pulse to v7.0.0 from v6.4.0 or earlier version, a restart of Pulse will be required to include the new dashboards and features of Opensearch. After installing Pulse and Pulse is running, you will need to restart Pulse again to allow Pulse Opensearch to be fully operational.

PgStart Setting Issue in Versions 7.2.0 and 7.2.1

What's New

server.xml preservation option

During installation, you can now choose not to overwrite the server.xml file. Untick this option if you have manually updated the file, unless the release notes explicitly require it.

Open

Session filtering for alerts

Runtime, Waittime, and Waiting Time alerts now include a new option to filter or exclude sessions based on matching text.

Open

Improved Chore/Process History

Performance has been significantly enhanced, and a new configuration setting allows you to exclude selected processes or chores from logging. This helps reduce noise from high‑frequency tasks. Use the ExclusionPatterns setting in Pulse.cfg to define a comma‑separated list of patterns (e.g., Daily*).

Enhancements (2)

• The Pulse Thick Client is no longer included in the installer. All capabilities have been migrated to the Pulse Web Client.

• Added Display Package Name to the Migration Approval Page.

Fixes (10+)

• Login status incorrectly shows IBMID for OpenID logins.

• Pulse dashboard unable to display other environments with no TM1 instances.

• User Session Report: Refresh button intermittently unresponsive.

• Typo in templates/conf/Pulse.template.env (Linux installer).

• Pagination issues in ngtable on several Pulse pages.

• PAaaS (v12): Documentation update fails when high availability is enabled.

• PAaaS (v12): Documentation update errors when processing some TM1 Applications.

• Alert Template Wizard now displays only active TM1 instances.

• Pagination on the Instances table does not update when filters are applied.

• Process History Page timeout on large OpenSearch queries.

• Chore/Process History Page continuously sends requests when queries take too long to compute.

• Report/Change History view fails for objects with names starting with #.

• Freemarker exception when generating cube reports.

• Actual users not displayed in Change History due to session‑ID mismatch when TM1 runs on Linux.

• Wizard Next button disabled after selecting Server and Service.

• Support added for Cube Data in Live Packages when Pulse runs on Linux.