|
|
|
**Pulse** version 5.8.3 is now available for [download](https://forum.cubewise.com/c/pulse/pulse-clients).
|
|
|
|
|
|
|
|
This release is an update to v5.8.2. it includes a lot of fixes.
|
|
|
|
|
|
|
|
## Important information
|
|
|
|
|
|
|
|
**Pulse v5 end of support date: June, 30th 2022**
|
|
|
|
Pulse v5 is still supported and we will provide support and updates until the 30th of June 2022. We hope by this date, all our customers will have upgraded to Pulse v6.
|
|
|
|
|
|
|
|
If your IBM Planning Analytics version is v2.0.8 or later, we recommend you to skip v5.8.3 and upgrade to the latest Pulse v6.
|
|
|
|
|
|
|
|
The latest Pulse v6 release is v6.0.1 and it is available to download:
|
|
|
|
* https://forum.cubewise.com/t/pulse-release-v6-0-1/4287
|
|
|
|
|
|
|
|
Everything that you should know before upgrading to Pulse v6 is available in the following help article:
|
|
|
|
* https://code.cubewise.com/docs/things-to-consider-when-upgrading-from-pulse-5-to-pulse-6
|
|
|
|
|
|
|
|
## Recommendations
|
|
|
|
|
|
|
|
* **Pulse data will be migrated if upgrading from Pulse 5.5.1 or earlier**: If you are upgrading from Pulse 5.5.1 or earlier, Pulse will migrate the Pulse data from the old monitor and docs databases to the new h2 database. It is important to remark that, If you are upgrading from Pulse v5.6.x or v5.7.x, data migration will not be performed, as Pulse v5.6.x is already using the new database.
|
|
|
|
* **Restart TM1 instances**: The Pulse TM1 processes (starting with **}src**) have been updated, Pulse will copy the new **}src** TM1 processes to the TM1 data folder, therefore, it is required to restart the TM1 instances, to register these new processes within the TM1 instances.
|
|
|
|
|
|
|
|
|
|
|
|
## Enhancements
|
|
|
|
* [#2245](https://support.cubewise.com/code/pulse/issues/2245): Added support for TM1 instances with a remote TM1 Admin Hosts
|
|
|
|
* [#2247](https://support.cubewise.com/code/pulse/issues/2247): Added scaling into the Pulse Summary Report charts.
|
|
|
|
* [#2362](https://support.cubewise.com/code/pulse/issues/2362): The way Pulse handles long running WMI queries has been enhanced by adding a 750 milliseconds timeout.
|
|
|
|
|
|
|
|
## Fixes
|
|
|
|
* [#1764](https://support.cubewise.com/code/pulse/issues/1764): The Pulse Validation Report will work when Validate Rules is set to true and Include Cubes to false.
|
|
|
|
* [#1982](https://support.cubewise.com/code/pulse/issues/1982): Improved the way Pulse handles multiple reports in the Pulse Thick Client.
|
|
|
|
* [#2040](https://support.cubewise.com/code/pulse/issues/2040): Improved the Pulse database update scripts when downgrading Pulse.
|
|
|
|
* [#2160](https://support.cubewise.com/code/pulse/issues/2160): Improved support for hierarchies in the change tracking features (closed in #2242)
|
|
|
|
* [#2173](https://support.cubewise.com/code/pulse/issues/2173): Fixed the export as csv button of the list of processes using a text file in the process list
|
|
|
|
* [#2189](https://support.cubewise.com/code/pulse/issues/2189): Removed links in the Model Spotlight if the cube does not exist.
|
|
|
|
* [#2234](https://support.cubewise.com/code/pulse/issues/2234): Improved the support for control objects in the technical documentation when Include Control Dimensions is set to true.
|
|
|
|
* [#2242](https://support.cubewise.com/code/pulse/issues/2242): Improved support for hierarchies in the change tracking features
|
|
|
|
* [#2272](https://support.cubewise.com/code/pulse/issues/2272): Added support for an update in the TM1 loggers introduced with PA 2.0.9.1.
|
|
|
|
* [#2295](https://support.cubewise.com/code/pulse/issues/2295): Improvements to avoid errors when migrating Pulse data from H2 to SQL Server.
|
|
|
|
"* [#2344](https://support.cubewise.com/code/pulse/issues/2344): For the Message in log alert to fire, the filter field must contain a value."
|
|
|
|
* [#2365](https://support.cubewise.com/code/pulse/issues/2365): Added support for null values in the License Optimization report when comparing against the Last Login Date.
|
|
|
|
* [#2369](https://support.cubewise.com/code/pulse/issues/2369): Fixed the Alert email severity setting not used.
|
|
|
|
* [#2373](https://support.cubewise.com/code/pulse/issues/2373): Pulse 5 will skip minor errors and proceed to finalise the documentation.
|
|
|
|
* [#2404](https://support.cubewise.com/code/pulse/issues/2404): Added support for multi-lines feeders in the relationship diagram
|
|
|
|
* [#2433](https://support.cubewise.com/code/pulse/issues/2433): Improved the way Pulse populates the Sessions table.
|
|
|
|
* [#2470](https://support.cubewise.com/code/pulse/issues/2470): Improved the way Pulse calculates the chore/process execution time.
|
|
|
|
* [#2475](https://support.cubewise.com/code/pulse/issues/2475): Pulse 5 documentation will skip hierarchies.
|
|
|
|
* [#2544](https://support.cubewise.com/code/pulse/issues/2544): Improved the way Pulse determines if a TM1 user is admin or not.
|
|
|
|
* [#2546](https://support.cubewise.com/code/pulse/issues/2546): Added support for custom SSL certificates.
|
|
|
|
* [#2583](https://support.cubewise.com/code/pulse/issues/2583): Added support for the following scenario: a dimension is updated by a TM1 process executed by Pulse during a migration.
|
|
|
|
* [#2629](https://support.cubewise.com/code/pulse/issues/2629): The ServerNameOverride parameter is now case insensitive.
|
|
|
|
* [#2658](https://support.cubewise.com/code/pulse/issues/2658): Improved the way Pulse generates alert emails information for CPU across all TM1 instances.
|
|
|
|
* [#2671](https://support.cubewise.com/code/pulse/issues/2671): Added support for case insensitivity in blob references.
|
|
|
|
* [#2693](https://support.cubewise.com/code/pulse/issues/2693): Added support for different time zones date formats in the chore/process history gantt chart
|
|
|
|
* [#2710](https://support.cubewise.com/code/pulse/issues/2710): Improved the way Pulse reads the process error log time.
|
|
|
|
* [#2727](https://support.cubewise.com/code/pulse/issues/2727): Added support for localised weights in the Migration feature.
|
|
|
|
* [#2799](https://support.cubewise.com/code/pulse/issues/2799): The migration feature has been improved to support when a leaf element becomes a consolidation.
|
|
|
|
* [#2827](https://support.cubewise.com/code/pulse/issues/2827): Pulse will always include .dimd file during Migration.
|
|
|
|
|
|
|
|
## Download
|
|
|
|
https://forum.cubewise.com/c/pulse/pulse-clients |
|
|
|
\ No newline at end of file |