PersivX v1.8

Releases in the v1.8 series, newest first.

v1.8.823 Nov 2026
  • New Feature: Report usage for report admins: opens, viewers, time spent and each viewer's activity over the last 7 days to a year. Open it from the chart icon next to the pin in All Reports, or Usage in a report card's menu.
  • Bug Fix: Scheduled deliveries and PDF prints of reports that have never been published were recorded as people opening the report.
  • Security: The time spent on a report can only be recorded against your own visit; any signed-in user could change it for others.
v1.8.723 Nov 2026
  • New Feature: Governance rules can match a column against a user attribute (or user id, or group): "Rows where region holds the user's Region". An attribute can hold several values separated by commas. Before, Equals Column Value always compared with the user's email, whatever was chosen.
  • Enhancement: In the governance editor, Equals Column Value gets its own line, so the table and column are readable, and says what it compares with.
v1.8.623 Nov 2026
  • Enhancement: A clearer data governance editor: each rule reads "When the user … / Only for rows where …", rules are dragged by a handle, and a rule with a missing value or column can't be saved.
  • Bug Fix: Visuals on datasources with masking or row rules failed after 1.8.0 with "table cte_pxdg_… doesn't exist".
  • Bug Fix: Row-visibility rules now apply on their own. They used to apply only when the table also had a column-masking rule, and "All rows hidden" showed every row when no rule matched.
  • Bug Fix: Rules for a user group and for a user attribute never took effect, and emails only matched when typed exactly (no space after a comma, same capitals).
  • Bug Fix: Removing a rule or a condition and adding another could make the editor save the wrong rule's column.
v1.8.522 Nov 2026
  • Enhancement: The sign-in screen has the same soft background as Ask PersivX's.
  • Security: Queries written in a visual, in Explore Data or sent through the Data API must be a single read-only SELECT. Statements that change data or the database are refused with the reason, and recorded in the security log.
v1.8.422 Nov 2026
  • Bug Fix: In tables with flow buttons, a pinned column slid under the buttons when the table was scrolled sideways, hiding its first letters.
v1.8.322 Nov 2026
  • Security: Only a report's developers (or, with a release pipeline, its approvers) can open a version other than the published one. Anyone else following a link to an unpublished version sees the published report.
  • Security: Data API queries are limited per connected program, 600 a minute by default (RATE_LIMIT_API_PER_MINUTE).
  • Bug Fix: Switching a report to its unpublished version could produce a link with = after the report id that failed to open.
  • General Bug Fixes: Removed an unused table library and the pop-up animations, which no longer played. Pages no longer allow scripts from unpkg.com.
v1.8.222 Nov 2026
  • Enhancement: Latest Updates lists the ten newest features, and leaves out fixes and security changes.
  • Bug Fix: Chart legends set to a top position were drawn near the bottom of the chart, over the data.
v1.8.122 Nov 2026
  • Bug Fix: After signing in on a report, its top row could sit under the top bar, hiding tile titles, and the page couldn't be scrolled back.
  • Bug Fix: Multi-query visuals that join other visuals failed with "the configuration has been locked".
  • Bug Fix: Visuals whose what-if parameter put a number into a date placeholder failed with "Not a date". They work as before; values that could carry SQL are still refused.
v1.8.022 Nov 2026
  • Enhancement: Upgrading a server from v1.7 is done by one script. It backs up the database and settings, asks for each setting only you can decide (such as the Google Sheets key, the site address and where security alerts go), sets up the daily clean-up and backup jobs, restarts PersivX and checks that it works.
  • Bug Fix: The list of sites allowed to show reports in a frame (REPORT_EMBED_ALLOWED_ORIGINS) is read from the same settings file as the rest of PersivX. On installs that keep it next to the backend's settings, it was ignored and any site could frame reports.
  • Security: Custom Python scripts can't read files from PersivX's own folders (its settings or any organization's data) or from where its keys and backup passphrase are kept, even if such a folder is listed for them. Keep the files scripts need in a separate folder.
  • New Feature: Security alerts can be sent by email (SECURITY_ALERT_EMAILS), as well as or instead of a chat webhook.
  • Bug Fix: Scheduled-delivery failure alerts reach every recipient. With Microsoft Graph mail, or with both the owner and an admin to tell, they could fail to send.