May 2026 - Dashboard Release Notes
- 1 Patch Release
- 2 Added
- 2.1 X-axis items are converted from HTML to SVG by Highcharts
- 2.2 Theme classes which used to be SVG are now HTML, which is converted to SVG by Highcharts
- 2.3 Indicator added to theme classes to display that certain elements are converted from HTML to SVG by Highcharts
- 2.4 AI feature permission
- 2.5 Enhanced audit for AI actions
- 3 Changes
IMPORTANT NOTIFICATIONS
Schema Changes - the release contains 0 schema changes.
Upgrading - please read all release notes from the version you plan to upgrade from and to before you conduct an upgrade. Each release contains changes to functionality; therefore, it’s worth being aware of these before your customers raise queries with you.
Environment variable PI_LICENCE - In previous releases, using an incorrect casing for the environment variable
PI_LICENCEfor container deployments may not have caused an issue. This was purely by chance, as the issue was masked by various caching mechanisms. Config environment variables must be all uppercase. Anything other than this is not supported and should not be relied on.
Patch Release
2026_05.2 | pi#3756 |
| Dashboard, Data Connections |
|---|---|---|---|
Resolved a Null Pointer Exception with connected data connections entering the dashboard configuration screen after refreshing the dashboard. | |||
2026_05.1 | pi#3747 | 44654 | Dashboard, Data Connections |
|---|---|---|---|
Resolved a performance issue when using very large numbers of database columns which occurred as part of updates to the configuration of frameworks. | |||
Added
X-axis items are converted from HTML to SVG by Highcharts | pi#3539 |
| Charts, Themes, Exports | |||||
|---|---|---|---|---|---|---|---|---|
Currently, most of our inner-chart elements which are style-able by a class within the themes are straightforward HTML elements. Now, with x-axis related classes, we allow Highcharts to automatically convert these elements to SVG elements, and apply the styling as inline styling rather than via the class. The affected classes are:
The reason for this is that chart-related styles were being lost upon export. Now, exported charts containing styled x-axis items will retain their styling applied at both the theme and chart level. This is consistent across browser exports, scheduled exports, report exports and scheduled report exports. Style properties which have an SVG equivalent will be converted, e.g. ' The following style properties have no SVG equivalent and will therefore be lost:
We aim to gradually roll this change out across all chart-related style classes so that styles will no longer be lost upon export. | ||||||||
Theme classes which used to be SVG are now HTML, which is converted to SVG by Highcharts | pi#3542 |
| Charts, Themes, Exports |
|---|---|---|---|
Previously, the following style classes were applied to SVG elements rather than the standard HTML elements that most style classes are applied to:
Now, they follow the same functionality outlined in release item Previously, on these unique classes, you’d have to specify SVG-specific style properties such as All of the styles without an SVG equivalent mentioned in release item | |||
Indicator added to theme classes to display that certain elements are converted from HTML to SVG by Highcharts | pi#3541 |
| Charts, Themes, Exports | |
|---|---|---|---|---|
A new type of indicator has been added to theme classes to signify that certain classes are automatically converted from HTML to SVG by Highcharts. This is done to retain styling upon export. This indicator has been applied to the classes mentioned in release item
| ||||
AI feature permission | pi#3581 |
| AI, Permissions |
|---|---|---|---|
A feature permission has been added to enable the three currently supported AI features: Chart Finder, Chart Description & Report description tools. This is available to both users and roles. It is off by default due to cost and performance overheads, and includes a warning indicator to outline this. | |||
Enhanced audit for AI actions | pi#3585 | - | Audit |
|---|---|---|---|
To provide greater insight into the usage of AI features, which is especially important since they have direct performance and cost implications when used, we have added a comprehensive audit system in the repository database in line with the existing audit data that is already there. There is now a record created for each interaction, providing information on the user, the action invoked, an API key identifier (the last 6 characters of the API key) and token usage. You can use your repository data connection to build out charts, tables and reports around this data. | |||
Changes
Renderer reliability fix and improved logging | renderer#136 | 40874, 41030, 41032 | Renderer |
|---|---|---|---|
Improvements have been made to the Renderer in terms of:
| |||
Removal of database triggers | pi#3333 | - | Database |
|---|---|---|---|
Triggers that were set on the | |||
Fixed CSV export failing for some charts using custom SQL | pi#3594 | 41685 | CSV |
|---|---|---|---|
Despite rendering correctly on the Dashboard UI, charts using custom SQL that defined an alias, that did not match up to any data object defined on the chart would produce a corrupted CSV export. This has now been resolved. | |||
Upgrades |
|
| Upgrades |
|---|---|---|---|
| |||
Fixed Vulnerabilities | pi#3660 | 43387, 43805,43432,43417 | Dashboard |
|---|---|---|---|
Fixed multiple vulnerabilities in libraries used by pi Dashboard:
| |||
Upgrade LangChain4J | pi#3578 | n/a | Dashboard |
|---|---|---|---|
Upgraded LangChain4J to v1.14.1 to utilise more modern features. | |||