March 2026 - Dashboard Release Notes

Some performance optimisations were made around the users/sync post API endpoint and the users/syncPayload get API endpoint.

• Reduced the number of SQL queries being generated during the phase related to fetching permissions for the authenticated user. This is particularly noticeable in cases where the authenticated user is subscribed to a large number of organisations.

• Improved accuracy of performance logs within the JSON returned upon a successful (200) response. Added an ‘Initialising time tracking’ entry, allowing the content between this entry and the entry related to fetching user permissions to be time tracked accurately.

• Made several code performance optimisations related to converting Groovy code to Java code where possible.

A recent security fix resulted in users being unable to directly paste some types of content into card charts and reports. This has now been resolved.

We have added the ability to use object values for comparison when setting table colours. When editing a table, within the colours tab, you will find a measure and dimension icon pair within the value input.

Open

Selecting this will bring up a dropdown, which will allow you to select an object within the table for comparison. This includes objects used within additional data.

Open

Upon selecting this object, its corresponding value will be used for comparison to colour the cell. A pill will appear within the input, displaying the selected object name. This can be removed with the X button on the pill.

Open

As well as regular tables, this works with cross tabs, editable tables and rotated tables. Merged tables currently do not support this. Here is an example with a cross tab.

Open

All of the appropriate colours will be applied upon exporting.

Object values can be used for a single (i.e. equals) and double (i.e. between) value operators - additionally, for double value operators you can use plain text for one value and an object for the other.

We have added the ability to change the line style in some charts.

Supported Charts

The line style is set by changing the Line Style attribute of any supported chart.

Open

Available Line Styles

Dash	Dash Dot	Dot	Long Dash
Open	Open	Open	Open
Long Dash Dot	Long Dash Dot Dot	Short Dash	Short Dash Dot
Open	Open	Open	Open
Short Dash Dot Dot	Short Dot	Solid
Open	Open	Open

Previously, once a Date Range Category Object had values defined - either via a configured default or due to a selection - you would be unable to easily clear those values from the input fields or apply those cleared values in order to remove the Filter entirely. This has been resolved with the addition of a ‘Clear’ button in the Date Range Picker popup and the ability to ‘Apply’ this cleared selection.

A new timeout setting has been added that allows you to define a maximum time that a Schedule will be allowed to run before being considered ‘Failed’ and therefore being cancelled. This will ensure that if a scheduled job stalls for some reason, it won’t indefinitely block other jobs from starting. Previously, you would have to notice that a job seemed to be failing to complete and then manually suspend it. This new setting is available as timeoutInMinutes under the Scheduler section of dashboard.json and can either be configured there, via the Configuration-Tool, or via the SCHEDULER_TIMEOUT_IN_MINUTES environment variable. By default, this option is set to 120 minutes. If you wish to disable this functionality entirely, you can set it to 0.

As well as the main timeout functionality that attempts to not only fail the job to unblock the Scheduler queue but close down any open connections or requests a backup is in place that will simply fail the job. This runs as part of the normal checking for available Scheduler jobs and is offset from your defined timeout by 5 minutes to prioritise the preferred, full close-down method.

All Windows executables are now signed with a digital signature, increasing the trust assigned to those on Windows. In some cases, that will be the original signature from source, for example in Java. Any executables without signatures are now signed with our own signature.

Particularly after the addition of the ability to configure the ‘Inner Size’ for a Doughnut chart, but even prior to this, the logic related to placing the labels on Pie/Doughnut charts often failed to place them properly. It would be overly aggressive in terms of hiding labels and would quite often place labels fully/partially outside the bounds of their slices, even though there was more than enough room within them. These issues were even more prevalent on Variable Radius Charts. Below you can see a comparison of the same charts using the old logic (top) compared to the new (bottom):

Old Logic

Open

New Logic

Open

As you can see, far more labels are shown within their slices than before. If labels overlap with one another, the label for the smaller segment is hidden. For doughnut charts with an ‘Inner Size’ set above 40%, the aim is to position the label in the centre of the slice. Below this, and this includes Pie Charts, the label is shifted slightly closer to the edge - closer to 2/3rds of the distance from the centre. This should match the position prior to these changes fairly closely and looks better on large slices than a central label.

In terms of styling, the labels now have a contrasting ‘stroke’ applied in order to not only help them standout more against the slice background colour but to ensure any that do partially bleed over into the background remain legible. You can remove this behaviour either at a Theme or Chart level by adding stroke: none; to the .pi-style__chart__pie-and-donut__data-value CSS section under the ‘Charts’ tab. This stroke does not currently appear on any web-based exports, which is a pre-existing limitation due to it not having the required fidelity in that context to look good.

Note: As part of this work, the labels had to be changed from HTML elements to SVG elements. This means that you will have to update any styling you have defined on the .pi-style__chart__pie-and-donut__data-value to be compatible with SVGs e.g. in order to set the text colour you would use fill instead of color.

The temporary filters were not being passed to the export request object in the temporary filters screen. It has now been added to the export request object as temporary criteria. This applies to both temporary filters using the UI and the URL.

Added enhanced error handling to catch a wider range of potential errors when connecting to a data connection via SSH. Where previously certain connection interruptions and failures would display errors, now they instead trigger reconnection attempts first.

Fixed an issue where the incorrect tooltip labels appear on combined charts where Y Axis and Y2 Axis labels are defined in attributes tab.

Previously, small values in Bar Range Charts could appear as semi-circles rather than a bar with rounded corners, this is now resolved.

Open

Previously, even with the ‘Enable y-axis Zooming’ attribute setting checked, Bar and Column Range Charts would begin any selected zoom region from the start of the y-axis. This has now been resolved.

• Enhanced the codes that determines if a user set interval would still be visible on the y-axis

• Modified codes that allows the displaying and hiding of the warning about not using the user interval due to too many ticks. Previously once an interval is set we do not change the y-axis values anyore, this change determines the y-axis values dynamically hence the need to dynamically display/hide the warning as well.

• Updated the displaying of the title and value labels of the speedometer and power ring charts, they should now display, scale and export properly.

• The export to word has also been updated so that the image would no longer stretch incorrectly.

After upgrading the Dashboard, it is possible for some previously working targets to suddenly appear broken in the UI: their fields will all be blank, they cannot be deleted, and attempting to change any values will result in a new Target being created instead. This has now been resolved.

Upgraded logback to version 1.5.26 to resolve CVE-2025-11226 and CVE-2026-1225 (pi#3471)

Go has been updated across multiple projects to 1.25.7 (excel-reader#64, scheduler#133)

A stored XSS vulnerability has been identified and resolved (41548)

Add line_style to mis_hierarchy_columns

pi#3468

29229

mis_hierarchy_columns.line_style

Added operand_one_compares_to_object to mis_chart_colors

pi#3434

29050

mis_chart_colors.operand_one_compares_to_object

Remove passwords from password-protected charts

3549

n/a

There is a known issue whereby if a user has a password-protected chart and the password is removed within the chart editor, when saved the chart should open without requiring a password. It is currently not doing this. A password is still being requested. We are aiming to resolve this issue in the April 26 release