Open

July 23

*non public patch release, and therefore not made available to all customers

Always use the latest point release (if available) for any major version at it will contain important fixes.

We are pleased to present our latest offering of pi - our July 2023 product release! This page helps summarise the areas of the dashboard we have Added, Changed, or Fixed meaning you can make a quick and informed decision on when to upgrade to the latest release.

Here is what is included in the release.

Product Release

Added

Auditing has been added for a number of administrator activities across the dashboard. When performing any of the below actions, a record will now be added to the dashboard table MIS_AUDITS with relevant information for the activity. This auditing will occur when performing the action through the UI or the API unless otherwise stated.

The newly added auditing covers:

For a comprehensive list of all audited activities please see our Auditing page.

It is now possible to use Object References in Chart Filters, by supplying the name of the object in question flanked by #~ ~#.

The table below details which operators can and cannot be used when using Object Referencing in Chart Filters;

Open

When using an object reference the object will be resolved in the SQL, allowing you to filter on the associated values. Where the referenced object is from a table that is not used in the creation of the chart (but the tables have a join), adding the filter will force the join of the tables to allow the filter to be applied.

To learn more about this topics, please refer to our Object Referencing page.

Three new magic variables have been added:

For more information on magic variable, please take a look at our Magic Variables page.

Previously icons in the top left of a chart panel header could be styled via editing the Theme’s ‘.pi-style__chart-panel__header .panel .paper-button' block (under the “Chart Panel” tab). This styling would only apply to these icons for users that had the ‘Display Chart Info’ permission enabled.

Now, a separate class has been added '.pi-style__chart-panel__header .chart-multi-icons-non-clickable-button’ (next to the previously mentioned one) to style these elements for those users that have the permission disabled.

Changed

Tomcat has been upgraded to the latest bugfix release 8.5.90

Java for Windows installations has been migrated to Eclipse Temurin build 8.0.372

7-Zip has been updated to version 23.01

Code changes made to facilitate a future Angular upgrade.

Code changes made to facilitate a future Grails upgrade.

Fixed

If the post-logout page threw an exception it was manually refreshed. This has now been resolved.

Resolved an issue with the objects containing special characters, including "&" symbol, not being highlighted when clicked as part of a parent chart. Any value selected in the parent chart will now be highlighted.

Fixed a couple of issues with how zero values were being rendered on charts.

Firstly, data value labels were not being applied to zero values when “Show Data Values” was selected in the chart’s Attributes tab.

Secondly, a chart that had all of its values as zero would fail to render the y-axis and the line representing those zero-value points.

Now, in situations were all of the values are zero, the y-axis will render as if the max was set to 1 - as shown by chart on the left-hand side of the image below. An alternative, centralised way to display this data can be achieved by setting the ‘Interval’ for this axis in the chart’s Attributes tab to any value - as shown by the chart on the right-hand side of the image below:

Previously, when you had ‘show row numbers’ toggled on for a merged table, you would be unable to drill down if one of the tables being merged had a drill down level beneath it. Now, you can drill down successfully with this option toggled on.

The message above would frequently appear in logs and the source of the '}' was unknown and would consistently reappear. Now, the cause has been identified and fixed.

Previously, custom theme styling related to the ‘Mobile’ theming would not always been retained when restarting the Dashboard due to being removed from the CSS file associated with that theme. Now the styling is correctly retained.

In the previous release a standard administrator user could not save themes, unless they were the super administrator. This has been resolved.

Previously, a date selected in a Date Picker category object (for example) could have its ‘Display Date’ representation be a day behind the entered value for users located in time zones behind UTC. Now, the date(s) selected in a Date Picker should display the expected date whilst retaining their locale-based formatting.

Previously you would be unable to save the user access screen in certain scenarios. This has now been resolved.

In the initial July 23 release, Tomcat took longer than usual to startup because of some incorrect configuration applied. This has been resolved in 2023_07.1.

Fixed an issue where user and role variable replacement was not working in the reports and, if available, was defaulting to the variables set at the global level. This has been resolved in 2023_07.4.

Schema Changes