June 2023 Dashboard Release Notes
Release Name - pi.2023_06_29
Release Date - Jun 28, 2023
Release Name | Release Date | Description |
---|---|---|
pi.2023_06_29 | Jun 28, 2023 | Initial Release |
pi.2023_06_29.1 | Aug 11, 2023 | Resolves an issue where a non super user administrator could not save changes made in the User Access screen. Also resolves an issue when a standard administrator user could not save themes. |
pi.2023_06_29.2 | Aug 14, 2023 | Added additional audit for category information when auditing chart fetch. |
Always use the latest point release (if available) for any major version as it will contain important changes.
We are pleased to present our latest offering of pi - our June 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.
Before upgrading, we always recommend that you review ALL release notes, from the version you are considering upgrading from and to. This is essential should there be a material change that could impact you or your customers. Where possible, upgrading to a test instance first can be helpful.
Before attempting an upgrade, you should always backup your repository. This allows you to quickly roll back should you wish or need to. You can find more information on how to do that here.
Here is what is included in the release.
- 1 Added
- 1.1 Add Roles to a Schedule
- 1.2 Vertically align text in Card Charts
- 1.3 Change vertical alignment of text within table cells
- 1.4 Exclude chart from cache
- 1.5 The ‘Name’ field for objects with camelCase or PascalCase column titles are automatically parsed into their space separated equivalents
- 1.6 Category ID is recorded in the ‘detail_info’ field for ‘Chart Fetch From DB’ audit
- 2 Changed
- 3 Fixed
- 4 Schema Changes
Added
Add Roles to a Schedule | GitLab #1558 | ZenDesk 23308 | Scheduler |
We have added the ability to add roles to a schedule, allowing all of the users within that role to receive an email when the schedule is sent out. There is a 2nd panel within the ‘Recipients and Recurrences’ table which allows you to configure this.
The users added from the role will not include the dashboard super admin user
Any duplicates within separate roles or roles and individual users will be added anyway, meaning a user may receive 2 or more emails if configured as such
If a role does not have collaborate permission, then it will not appear in the drop down list
If a role contains users which do not have an email, the role will appear in red and you will see a warning in the tooltip
Upon deleting a role, the role link to the schedule will be deleted too
You are now able to save a schedule if it has a role added, but no individual user or external email added
Vertically align text in Card Charts | GitLab #1554 | ZenDesk 22965, 22242 | Card Charts |
It is now possible to vertically align text elements in card charts.
This can be achieved by selecting a text element in the card chart in the chart editor panel, opening the advanced options and selecting a setting for the “Vertical Align” field.
When selecting an option (top, middle, or bottom), the text in the given text box will align to the relevant location.
Change vertical alignment of text within table cells | GitLab #1691 | ZenDesk 25645 | Tables |
Previously, the vertical alignment of text within a table cell is fixed at being centred.
Now, a new CSS class has been added (under the “Table” tab of the theme settings screen) that allows you to override this default. The new class is called “.pi-style__table-body-cell .ag-cell-wrapper” and the vertical alignment can be dictated with the “align-items” property. A value of “flex-start” will vertically align the text to the top of the cell, “flex-end” will align it to the bottom, and “center” will act the same as the current default.
This feature is applicable to global themes only. A future change for this to be possible for individual charts is currently being considered.
Exclude chart from cache | GitLab #1567 | ZenDesk 23947 | Chart Editor |
It is now possible to exclude charts from the cache to ensure that they always reload data from the database when they are displayed. This means that data will be up to data when drilling to charts and tables, data will be updated where it has changed on the next level. Changes submitted in editable tables will also be visible when drilling up to the chart above.
To choose to exclude a chart from the cache you can tick the “Exclude Chart From Cache” option in the chart editor configuration tab.
The ‘Name’ field for objects with camelCase or PascalCase column titles are automatically parsed into their space separated equivalents | GitLab #1074 | ZenDesk 19886 | Data Connections |
Previously, when adding a table from a Data Connection the ‘Name’ field is auto-populated with a space separated equivalent of any columns written in snake_case.
Now, this auto-parsing behaviour has been extended to include columns written in both camelCase and PascalCase.
Category ID is recorded in the ‘detail_info’ field for ‘Chart Fetch From DB’ audit | pi#1801 & #1992 | 26342 | Audits |
The Category ID for the relevant chart, the one that the chart in question is refreshed within, is now being recorded in the ‘detail_info’ column for the ‘Chart Fetch From DB’ audit.
Changed
Library Maintainance - Remove commons config library | GitLab #1684 | - | System Libraries |
Removed Apache Commons library which was included in the product, but no longer needed.
Library Maintainance - Upgrade a number of libraries to newer versions | GitLab #1685 | - | System Libraries |
As part of our commitment to security, we’ve upgraded a number of 3rd party libraries to newer versions.
Fixed
Unexpected characters appearing in CSV exports | GitLab #1566 | ZenDesk 24191 | CSV Exports |
Some users had reported seeing unexpected characters in CSV exports when opening them locally.
This was due to some programmes (including Microsoft Excel) using incompatible encoding for the data when opening the file. This has now been resolved by pre-pending the file with a byte order mark to ensure the programme uses UTF-8 as standard when opening the file.
Issues with saving user access screen | #1914 | 26978 | Administration |
Fixed an issue where a non super user administrator could not save changes made in the User Access screen.
Non super administrators cannot save themes after editing | pi#1936 | 27130 | Themes |
Fixed an issue when a standard administrator user could not save themes, unless they were the super administrator. This has been resolved.
Schema Changes
ORG_ADMIN added to USERS table | pi#1764 |
| Database |
ORG_ID added to the unique constraint of NAME in MIS_API_REQUESTS table | pi#1668 |
| Database |
ORG_ID added to the unique constraint of DISPLAY_NAME and DATA_SOURCE_ID in MIS_COLUMNS table | pi#1668 |
| Database |
ORG_ID added to the unique constraint of NAME in MIS_DATA_SOURCES table | pi#1668 |
| Database |
ORG_ID added to the unique constraint of DESCRIPTION in MIS_DEFINED_CHARTS table | pi#1668 |
| Database |
ORG_ID added to the unique constraint of NAME in MIS_DEFINED_FILTERS table | pi#1668 |
| Database |
ORG_ID added to the unique constraint of LABEL in MIS_CUSTOM_FONTS table | pi#1668 |
| Database |
A new unique constraint of ORG_ID and ROLE_NAME added to MIS_ROLES table | pi#1668 |
| Database |
A new unique constraint of ORG_ID and NAME added to PI_SCHEDULES table | pi#1668 |
| Database |
A new unique constraint of ORG_ID and REPORT_NAME added to MIS_REPORT_ITEMS table | pi#1668 |
| Database |
A new unique constraint of ORG_ID and NAME added to PI_SCHEDULES table | pi#1668 |
| Database |
A new unique constraint of ORG_ID, NAME, USER_ID added to MIS_VARIABLES table | pi#1668 |
| Database |
A new unique constraint of ORG_ID, NAME, ROLE_ID added to MIS_VARIABLES table | pi#1668 |
| Database |
Column REPORT_NAME changed to varchar(1000) in MIS_REPORT_ITEMS table | pi#1668 |
| Database |
Column NAME changed to varchar(1000) in MIS_VARIABLES table | pi#1668 |
| Database |
Column ORG_ID set to be nullable and set to NULL if USER_ID and ROLE_ID are null in MIS_VARIABLES table | pi#1668 |
| Database |
Column PARENT_ID added to MIS_ORGANISATIONS table | pi#1763 |
| Database |
Column EXCLUDE_CHART_FROM_CACHE added to MIS_DEFINED_CHARTS table | pi#1567 | ZenDesk 23947 | Database |
A new table PI_SCHEDULE_ROLE_LINKS | pi#1558 | ZenDesk 23308 | Database |
Column ID added to PI_SCHEDULE_ROLE_LINKS int | pi#1558 | ZenDesk 23308 | Database |
Column VERSION added to PI_SCHEDULE_ROLE_LINKS int default 0 | pi#1558 | ZenDesk 23308 | Database |
Column ROLE_ID added to PI_SCHEDULE_ROLE_LINKS int default 0 not null | pi#1558 | ZenDesk 23308 | Database |
Column SCHEDULE_ID added to PI_SCHEDULE_ROLE_LINKS bigint default 0 not null | pi#1558 | ZenDesk 23308 | Database |
A new unique constraint of ROLE_ID, SCHEDULE_ID added to PI_SCHEDULE_ROLE_LINKS_TABLE | pi#1558 | ZenDesk 23308 | Database |
A new foreign key of SERIAL from MIS_ROLES added to ROLE_ID of PI_SCHEDULE_ROLE_LINKS | pi#1558 | ZenDesk 23308 | Database |
A new foreign key of ID from PI_SCHEDULES added to SCHEDULE_ID of PI_SCHEDULE_ROLE_LINKS | pi#1558 | ZenDesk 23308 | Database |
CUSTOMER NEWS - Our November 24 Release Is Now Available - Download It Now!