Pulse version 5.8.1 is now available for download.
This release is an update to v5.8.0. it includes a lot of fixes.
Most of the issues below are set to confidential, only the person who created the ticket will be able to see it.
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 if upgrading from Pulse v5.7.4 or earlier: The Pulse TM1 processes (starting with }src) have been updated in Pulse v5.7.5. If you are upgrading from a Pulse version which is prior to Pulse v5.7.5, Pulse will copy the new }src TM1 processes to the TM1 data folder, therefore, it is required to restart the TM1 instances, in order to register these new processes within the TM1 instances.
1900: After recreating a package, Pulse will redirect you to the new package.
2004: A new parameter SessionTimeout has been added to the Pulse.cfg file. This new parameter can be used to manage the Pulse session timeout. The default value is set to 20 min.
1737: The way Pulse manages the memory has been improved.
1771: The label include/exclude instances was not consistent in the user settings.
1803: Increase the size of the connection pool to allow more connections between the Pulse services.
1819: Migration was not working when overwriting an existing cube with a new dimension structure.
1821: In the system summary report, refreshing the report was always reverting back to the summary tab.
1835: The footer and header of the technical and validation report slows down the creation of the PDF, these options are now deactivated by default.
1850: The REST API of the temporary Pulse instance used during migration has been deactivated to avoid port conflicts.
1856: Pulse was caching 15 min of history in the browser, this was causing some browser issues when more than 1000 sessions across TM1 instances. The default value is now 5 min (300 seconds). A new parameter LogClientMax in the Pulse.cfg has been added to manage how much time of history you want to keep in your browser.
1858: Pulse was losing connection to TM1 instances.
1883: The sort functionality in the memory analysis report was not working.
1920: Pulse was not able to connect to a TM1 instance with CAM Passport due to the TM1 password already being saved in the Pulse instance settings.
1921: Pulse was not displaying TM1 server message log.
1931: The Date range behavior was not consistent between the Migration and the change history features.
1942: The setting "Process To Keep Alive CAM Passport" was not working correctly.
1951: In the technical documentation, the dynamic flag was set to false incorrectly for a dynamic subset containing.
1958: TM1 message logs were not showing in Pulse Live Monitor due to a low value in Connection Pool, the default value for new Pulse installation is now 10.
1993: Migration was not working for TM1 instances containing a "." in the name.
1995: Pulse returns an error when executing a package with a very long description.
2006: The previous email to create a ticket was replaced with a link to support.cubewise.com/code/pulse.
2008: Pulse will now ignore Cubes set as load on demand when executing the documentation.
2017: With PAL 2.0.5 or later, the Pulse process }src_export was generating an info message when the }CubeSecurity and }DimensionSecurity do not exist. Once Pulse upgraded, you will need to restart your TM1 instances to get the latest version of the Pulse processes.