|
|
**Pulse** version 5.8.1 is now available for [download](https://forum.cubewise.com/c/pulse/pulse-clients).
|
|
|
|
|
|
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.
|
|
|
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**.
|
|
|
|
|
|
## 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 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.
|
|
|
* **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.
|
|
|
|
|
|
|
|
|
## Enhancements
|
... | ... | @@ -15,7 +15,7 @@ This release is an update to v5.8.0. it includes a lot of fixes. Most of the iss |
|
|
## Fixes
|
|
|
* [1737](https://support.cubewise.com/code/pulse/issues/1737): The way Pulse manages the memory has been improved.
|
|
|
* [1771](https://support.cubewise.com/code/pulse/issues/1771): The label include/exclude instances was not consistent in the user settings.
|
|
|
* [1803](https://support.cubewise.com/code/pulse/issues/1803): Increae the size of the connection pool to allow more connections between the Pulse services.
|
|
|
* [1803](https://support.cubewise.com/code/pulse/issues/1803): Increase the size of the connection pool to allow more connections between the Pulse services.
|
|
|
* [1819](https://support.cubewise.com/code/pulse/issues/1819): Migration was not working when overwriting an existing cube with a new dimension structure.
|
|
|
* [1821](https://support.cubewise.com/code/pulse/issues/1821): In the system summary report, refreshing the report was always reverting back to the summary tab.
|
|
|
* [1835](https://support.cubewise.com/code/pulse/issues/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.
|
... | ... | @@ -25,7 +25,7 @@ This release is an update to v5.8.0. it includes a lot of fixes. Most of the iss |
|
|
* [1883](https://support.cubewise.com/code/pulse/issues/1883): The sort functionality in the memory analysis report was not working.
|
|
|
* [1920](https://support.cubewise.com/code/pulse/issues/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](https://support.cubewise.com/code/pulse/issues/1921): Pulse was not displaying TM1 server message log.
|
|
|
* [1931](https://support.cubewise.com/code/pulse/issues/1931): The Date range behaviour was not consistent between the Migration and the change history features.
|
|
|
* [1931](https://support.cubewise.com/code/pulse/issues/1931): The Date range behavior was not consistent between the Migration and the change history features.
|
|
|
* [1942](https://support.cubewise.com/code/pulse/issues/1942): The setting "Process To Keep Alive CAM Passport" was not working correctly.
|
|
|
* [1951](https://support.cubewise.com/code/pulse/issues/1951): In the technical documentation, the dynamic flag was set to false incorrectly for a dynamic subset containing.
|
|
|
* [1958](https://support.cubewise.com/code/pulse/issues/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.
|
... | ... | |