We’re excited to announce the latest Pulse release, packed with new features, security improvements, and critical fixes to enhance performance and usability.

Downloads:

• https://forum.cubewise.com/t/pulse-release-v7-2-0/7474

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. If you updated this file manually, 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.

✅ New Features

Support for Postgres Database (Beta)

Pulse now supports Postgres in addition to MS SQL Server. Moving from the default H2 database to Postgres improves performance in large environments with many users.

Object Locking in Arc+

Starting with Arc v5.2.0 and Pulse v7.2.0, developers can lock objects (processes or rules) to prevent changes. Only the locker or a Pulse admin can unlock them. A new page Called Object Locking has been added to Pulse to help unlocking multiple objects at the same time.

Open

Enhanced Security for Opensearch Connectivity

Improved security measures for communication between Pulse and the Pulse Opensearch Cluster.

Instance Settings: Reuse Credentials

TM1 credentials can now be entered at the Environment level, allowing all TM1 instances in that environment to share the same login information. This simplifies credential management significantly. Select an Environment, tick the option Use Root Credential and then enter the TM1 credentials:

Open

Pulse System Alerts Activated by Default

Pulse System Alerts notify admins when a component is not functioning correctly. These alerts are now enabled by default for new installations. For existing setups, see the activation guide in our documentation: https://cubewisecare.atlassian.net/wiki/spaces/PUM/pages/584548356/Configuration#System-Alerts

🔍 Enhancements

• Pulse Server now runs on Tomcat v9.0.112.0 and uses JVM v1.8.0_472 for improved stability and performance.

• Added a warning message in the Pulse User Sessions page indicating that only the top 200 users are displayed in the table.

• Enhanced handling to prevent unexpected termination of Pulse application services.

• The option to clean TM1 server logs is now hidden when the TM1 instance runs on Planning Analytics Cloud.

• Improved error handling and messages when connecting to IBM Cloud.

🛠 Bug Fixes

• Fixed issue where Pulse failed to create migration packages.

• Resolved migration rule errors after upgrading to Pulse 7.1.

• Corrected change tracking issues in Arc+.

• Fixed Pulse OAuth email error.

• Addressed migration package changes incorrectly marked as SYSTEM instead of MIGRATION.

• Parameters column now correctly displays process parameters.

• Fixed exception in License Optimization Report when summarizing sessions by user.