July 2024 - Dashboard Release Notes
- 1 NEW FEATURES
- 2 CHANGES
- 2.1 OWASP HTML Sanitizer - Upgraded
- 2.2 Multilingual - Multiple Improvements To i18n Translation Keys - Card Charts
- 2.3 User ‘About’ Screen - Date Format Change
- 2.4 Multilingual - Language String Name Format Change
- 2.5 Incompatibility - Amazon ElastiCache For Redis
- 2.6 Table Chart Sorting - When Clicking 2nd Column Heading
- 2.7 Browser Debug Tool - Invalid Post Message Error Handling
- 2.8 Chart Editor Screen (Preview Mode) - Unable to Drill Down On A Table
- 2.9 Schedule Editor Screen - Filter Values Not Showing
- 2.10 Gold Dashboard - Spelling Mistake Corrections
- 2.11 Performance of Chart Displays - Patch Item for 2024_07.1
- 3 SCHEMA CHANGES
Table of Content Key
Customer Requested tickets are highlighted with this icon
Notifications
Below are key notifications to be aware of before upgrading your dashboard.;
Aug 28, 2024 - we issued a Patch release (2024_07.1) to address pi#2594
This release contains x2 Schema changes.
NEW FEATURES
Organisations - Sorting By Position (Rather Than Alphabetically) | pi#2435 | 30519 | |
---|---|---|---|
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:
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. Ordering explained:
|
Sankey & Chord Charts - Add Numeric Weight Column | pi#2375 | 30595 | Charts |
---|---|---|---|
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:
Play the video below to see this in action;
For more information on Sankey Charts, please see our Creating & Formatting pages.
|
Multilingual - i18n Support - Additional Items Included | pi#2498 | - | |
---|---|---|---|
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
For a full list of all the items added, please expand the list below; default.button.reload.discard.title=Reload data and discard changes default.errors.licence.capacity.id=ID
|
PDF Export - Performance Improvement For Single Chart PDF Export (BETA) | pi#2420 | 29822 | PDF Export |
---|---|---|---|
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
|
CHANGES
OWASP HTML Sanitizer - Upgraded | pi#2481 | - | Sanitizer |
---|---|---|---|
The OWASP HTML Sanitizer has been upgraded to resolve a reported Guava security vulnerability.
|
Multilingual - Multiple Improvements To i18n Translation Keys - Card Charts | pi#2408 | 30255 | Multilingual / Card Charts |
---|---|---|---|
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:
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:
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.
|
User ‘About’ Screen - Date Format Change | pi#2264 | - | Library / Users About Page |
---|---|---|---|
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:
|
Multilingual - Language String Name Format Change | pi#2503 | 31248 | |
---|---|---|---|
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)
|
Incompatibility - Amazon ElastiCache For Redis | pi#2434 | 29803 | Redis |
---|---|---|---|
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.
|
Table Chart Sorting - When Clicking 2nd Column Heading | pi#2488 | 31473 | Table Sorting |
---|---|---|---|
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.
|
Browser Debug Tool - Invalid Post Message Error Handling | pi#2503 | 31248 | Embedding / Browser Debug Tool |
---|---|---|---|
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.
|
Chart Editor Screen (Preview Mode) - Unable to Drill Down On A Table | pi#2500 | - | Drill Down / Chart Editor |
---|---|---|---|
Users were being prevented from being able to drill down whilst previewing a Table Chart (in the Chart Editor).
|
Schedule Editor Screen - Filter Values Not Showing | pi#2487 | - | Schedule 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.
|
Gold Dashboard - Spelling Mistake Corrections | migrations#55 | - | Gold Repository |
---|---|---|---|
Minor spelling corrections in the Gold Repository
|
Performance of Chart Displays - Patch Item for 2024_07.1 | pi#2594 | 32555 | Performance |
---|---|---|---|
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.
|
SCHEMA CHANGES
Description | GitLab | ZenDesk | Column |
---|---|---|---|
Column ‘position’
| pi#2435 | 30519 | position |
Column ‘data_source_item_id’
| PI#2459 | - | data_source_item_id |
CUSTOMER NEWS - Our August 24 Release Is Now Available - Download It Now!