🚀 Pulse v7.1 Release Notes

We’re excited to introduce Pulse v7.1, bringing smarter monitoring, improved session control, and enhanced security features to your TM1 environment.

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

🔒 Cancel All Sessions by Session ID

Managing parallel processes just got easier. A new button in Pulse Live Monitoring lets you instantly cancel all sessions sharing the same session ID—perfect for terminating multiple processes launched by the same user in one click.

Open

📊 Enhanced Excel Workbook Monitoring

Pulse Explorer now includes new fields in the pulse-server-state index, allowing you to search by:

• Workbook name

• Worksheet name

• PAfE or Slice version

This makes it easier to pinpoint Excel workbooks that may be impacting performance for other users. A new dashboard is available in the Pulse Explorer > Dashboards > Pulse - Excel Monitoring:

Open

🚨 Alert for Invalid TM1 Credentials

Pulse now monitors the TM1 credentials configured in Administration > Instance Settings. If the credentials become invalid, you’ll receive an immediate alert—so you can take action before it affects session tracking: https://cubewisecare.atlassian.net/wiki/spaces/CS/pages/527499267/Invalid+Credential?atlOrigin=eyJpIjoiYzhhMjIxMzczZGFmNDlhM2JjYzU1Njg1OWE0MTE2MTIiLCJwIjoiYyJ9

📧 OAuth Support for SMTP Emails

With Microsoft phasing out native authentication for SMTP, Pulse now supports OAuth tokens for secure email setup. For configuration details, refer to the linked article in the documentation: https://cubewisecare.atlassian.net/wiki/spaces/CS/pages/535658497/Email?atlOrigin=eyJpIjoiMDcxM2QwMTViYmQyNDI2NjgzOTllMjkwZTkwNGMyZTAiLCJwIjoiYyJ9