July 2024 - Dashboard Release Notes

Prior to this release, Organisations were sorted alphabetically. In this release we have introduced a new field ‘position’ to the Organisations Editor Screen, which allows the users to define the display position of the Organisation. All organisations will have a ‘position’ field and will be sorted by this field, with the lowest number having the highest priority.

If multiple Organisations have the same position, they will be displayed alphabetically in the system; otherwise, the defined position will be respected. From this release forward, all existing Organisations will have their position set to 1 by default.

Organisation Editor Screen:

Open

Below is a working example of how the position drives the ordering display;

The ‘Accounts’ Organisation has 4 children Organisations; Test, Marketing, Sales and Dev.

Open

Ordering explained:

• ‘Test’ Organisation is first in the list, with Organisation position=1

• ‘Marketing’ and ‘Sales’ both have Organisation position set to 2, therefore, they are sorted alphabetically; i.e. Marketing comes before Sales

• ‘Dev’ Organisation comes last in the list, as the Organisation was set as position=10

Prior to this release, the width of the links between the nodes in a Sankey Chart or Chord Diagram were determined by the number of times that link occurs. For example, a link between ‘A' and 'B’ would be given a weight of 100 only if there were 100 instances of that link in the data.

From this release, an additional ‘weight’ data object can be configured for these chart types. It is the value specified by this object that will be used to calculate the weight of each link rather than the count.

In the earlier example, a link with a weight of 100 might be comprised of a few rows of data rather than 100 - it could even be representative of a single row of data that has 100 weight associated with it.

This is best demonstrated in the video below, note that prior to the ‘Weight’ being added the “Coal” node had equally weighted links to the nodes of the next ‘State’ but afterwards their weights and therefore their widths diverge. The video also shows:

• The original behaviour of the count being used to generate the weight (“Oil” has 4 outgoing connections to “Direct Fuel Use”)

• The removal of the previous restriction that meant you could only define Colour Rules for one Data Object

• Changing the colour of the connections based upon their weight

Play the video below to see this in action;

For more information on Sankey Charts, please see our Creating & Formatting pages.

New key-value entries have been added to the messagesStatic.properties file, to enable translations for some previously untranslated items in the dashboard. These change will affect the following areas of the dashboard, but may not be limited to

• Error handling in the UI

• User Access

• Category Access

• Data Connection Table

• Object Creation Panels

We’re excited to offer a completely rebuilt PDF export functionality which is almost instant, and reflects any changes you make to charts on your screen. You can try it out by enabling the BETA feature BROWSER_PDF_EXPORT (within pancredit_parameters) and we’d love to hear your feedback and incorporate this into our upcoming releases.

The OWASP HTML Sanitizer has been upgraded to resolve a reported Guava security vulnerability.

We have improved the presentation of i18n keys for Card Charts in the language translation files (i.e.messagesUserEntered_en_GB.properties).

Prior to this release, the keys included HTML code and styling tags applied directly to the Card Chart key.

From this release, we have introduced the following changes:

1. The Key for Card Charts has been simplified by removing unnecessary HTML code

2. When generating a new language file, all the content related to the Card Charts will be put at the bottom of the file

3. Each Card Chart will have its own block of key value pairs, each separated by a comment that includes the Chart Title

4. Each Card Chart block will include the content from all hierarchies within the chart

5. Only Card Chart related keys will have Chart Title prefixed to it

Example of the output with multiple card charts:

Below are two examples of the new structure of the key, one without and the other with styles:

1. Example without styles:

Card+Three.Dev+and+Test=<div>Dev and Test</div>

• Card+Three - Encoded chart title

• Dev+and+Test - Encoded text value forming part of the key.

2. Example with styles applied:

New+Card.Styles+Test=<div style="text-align: center;"><span style="font-size: 26px; font-weight: bold; background-color: rgb(243, 144, 29); color: rgb(0, 0, 0);">Styles Test</span></div>

Newly generated language files will now include Card Chart Keys in the updated structure.

When upgrading, the existing files (with keys in the old format) will continue to work until a new language file is generated.

The Java 11 upgrade delivered in the June 24 release, brought with it an update to some of the default Java date formatting, therefore changes in the format of the dates presented in a User’s About page are present. The exact change, is dependentt upon your locale but as an example the en_GB format used previously now displays as:

But now the formatting appears like this:

Introduced automatic generated language strings for i18n files. We have tweaked the string format to a slightly improve the format of the Language (locale), for example English (United Kingdom)

Amazon’s ElastiCache for Redis does not allow the use of the CONFIG command which was causing an inability to use it alongside the Dashboard. This incompatibility has been resolved by disabling Keyspace Event Notifications which were previously being set to “Ex” through that restricted command.

Should you wish to mimic the past behaviour (it was being set to “Ex”) or indeed configure different behaviour, you are able to achieve this elsewhere in your infastructure - for example, it can be configured in the Redis configuration file or within the ElastiCache settings.

It was possible for the dynamic sorting of the second column in a table, to produce unexpected sorting results . It previously sorted by a different column entirely, one with an ‘order by’ in its object definition, which has been addressed.

Some 3rd parties (such as browser extensions) can send invalid post messages to the pi application. Prior to this release,, these were flagged as an error on the browser console. The severity level of these messages has now been downgraded to INFO and the messages has been amended to provide more relevant information.

Users were being prevented from being able to drill down whilst previewing a Table Chart (in the Chart Editor).

In a very specific case, when using the Scheduler Editor Screen with a report that included filters, the filter values would not populate when trying to edit them.

Minor spelling corrections in the Gold Repository

A performance issue was identified with the original July 24 release, specifically when displaying charts in the dashboard. To address this, the user access verification step has been optimized by enhancing the SQL query for improved efficiency.

Column ‘position’

• added to mis_organisations table

pi#2435

30519

Column ‘data_source_item_id’

• added to mis_category_objects, mis_report_filters, mis_user_restrictions, mis_role_restrictions, mis_filter_columns, pi_schedule_attachment_filter_values tables

PI#2459

-