We are pleased to present our latest offering of pi - our November release! This page helps summarise and familiarise you with the changes we have made and is supported (where applicable) with useful videos to help explain the changes we have delivered.
| Info |
|---|
Before upgrading, we recommend taking a backup. You can find more information here. |
Here’s what we’ll cover
| Table of Contents |
|---|
Added
Description
Screenshots/Videos
Warnings/Alerts
Description
Screenshots/Videos
Warnings/Alerts
Description
Screenshots/Videos
Warnings/Alerts
Description
Screenshots/Videos
Warnings/Alerts
Description
Screenshots/Videos
Warnings/Alerts
Description
Screenshots/Videos
Warnings/Alerts
Changed
Alpha tag for import/export for data connections, schedules and reports has now been removed and replaced with a help icon and some help text, providing information on how to import/export between different dashboard versions.
When creating/ editing Category Filters, for certain Category Filter types, the system offers a pop up for selecting the default value(s). The pop-up panel now has pagination, which improves performance when there are lots of values to be displayed.
The same implementation is done for selecting Report Filter Default Values.
Fixed
Previously, when changing from a chart with Sorts and/or Targets to a chart type that doesn’t support them, errors may have been displayed due to the Sorts and Targets not being immediately removed. This has been resolved in this release of the Dashboard.
Previously, the renderer was adding extra blank pages when a report with a table was exported in PDF. This issue only used to happen in certain scenarios usually where the table content was higher than the size of the page. An extra space of 40px has now been reserved in the report page to make sure no blank pages are created.
The details of an XML licence that are displayed in the ‘Licence’ tab of the configuration-tool would disappear if they had not yet been applied via the ‘Apply and Run’ option and you navigated to a different tab. These details now persist between tab changes.
If configured (via ‘Dashboard URL’) to access the Dashboard via HTTPS whilst using Self-Signed or Invalid certificates the Renderer would reject the request due to a certificate-related error being raised. A new setting has been added to the Renderer to ignore these errors allowing the request to complete successfully. This new setting can be found under the Renderer tab of the Configuration-Tool or within your dashboard.json configuration file as ‘ignoreHttpsErrors’. Its use is generally not recommended as it does have a negative impact on the security of your configuration.
Need screenshot
Previously, Light Bulb charts would hide their data value when this was smaller than a certain size even if it would have been perfectly legible.
Now, both Light Bulb and Traffic Light charts will display this value, on both the dashboard and in reports containing them, no matter how small they become.
Previously, if you changed your UUID license to an invalid one the encrypted licence stored in the database would be used. This hid the fact that the new licence was invalid until the encrypted one expired.
Now, if the UUID licence is invalid you won’t be able to log in and the encrypted licence will be removed from the database.
Regardless of the type of database being run, the audit data sent to the ALM when using a UUID licence would state that it was a ‘HyperSQL’ database. Now, the database type is identified and reported correctly.
Fixed an issue with the renderer throwing an error and breaking when an empty table is scheduled to export or is exported in a single chart mode or as a part of a report.
Previously, the table width ratio was not being respected when exporting tables as Word on Windows. Now, if you create a table with varied column width/ratios, the set column widths will be adhered to when exporting tables in both single chart mode and reports.
Repository backups created through the ‘Create Backup’ button under the ‘Repository’ tab of the configuration-tool mistakenly had two adjacent dots as part of their filename. They now have a single dot as intended.
If an output message was wider than the ‘messages’ screen of the Configuration Tool, the overflowing contents would be hidden. This would happen relatively frequently as messages were rendered on a single line regardless of their length. Now, word-wrapping is applied to each message allowing them to be broken up into multiple lines as long as logical splitting points are present.
Known Issues
Description
Screenshots/Videos
Workarounds
Warnings/Alerts
Description
Screenshots/Videos
Workarounds
Warnings/Alerts
| Info |
|---|
|
