31.2.0 Release Notes

Description & Highlights

ZenQMS 31.2.0 is a low-impact minor release. It includes a small number of bug fixes across several modules and a series of technical updates that make existing audit trail transactions for the Audit Reports and Observations module available directly within the self-service audit portals in ZenQMS (Settings -> Account -> Audit Trail).

Detailed Updates

  • Audit Trail Technical Enhancements - The user story below and related requirements represent a series of technical updates that make existing audit trail transactions for Audit Reports and Observations module available directly within the self-service audit portals in ZenQMS (Settings -> Account -> Audit Trail). Up until now, visibility into these audit trail subjects was only available through a HelpDesk request. These changes do not affect the audit trail source itself or Part 11 requirements. Please view the traceability matrix for the full list of cards included in this initiative.

    • ZENQ-8181: As a Quality Manager, I want to access human-readable audit trail events for all Audits Reports, Observations and Qsheet transactions so that I can ensure 21 CFR Part 11 compliance and demonstrate full traceability during regulatory inspections.

Bug Fixes

This release includes bug fixes across all priority levels. The fixes listed below represent issues classified as Major and Minor in the ZenQMS issue tracking system. Please view the traceability matrix for the complete list of cards included in this release.

  • ZENQ-8431 - [Main Dashboard]: When using bookmarked URLs to login users are automatically redirected back to the dashboard when attempting to navigate to other modules or items - Following login via a direct or bookmarked URL that did not include a specific view indicator, users were unable to navigate to other modules. Each attempt to open Documents, Training, Issues, or other sections briefly displayed the target module before automatically redirecting back to the Main Dashboard. This affected users whose login URL or browser bookmark pointed to the dashboard without a view level specified. A workaround was available: performing a full page refresh (F5) restored normal navigation for the affected session; users could also update their saved bookmark to include a specific view level in the URL path. All module data, records, and user permissions were not affected. The underlying cause has been resolved.

  • ZENQ-8435 - [UI/UX SuperEditor]: Super Editor access is automatically dropped when navigating away from the record tab before the Super Editor session timeout is reached - When a user activated Super Editor mode on an Issues or Change Controls record and navigated to another tab or part of the application, Super Editor access was automatically revoked upon returning to the record. The mode ended before the designated session timeout elapsed, requiring users to re-authenticate and re-activate Super Editor each time they needed to reference other records or modules during an editing session. Record data and field values were not affected. The underlying cause has been resolved.

  • DM-8498 - [Documents Module]: Global search filters are cleared when returning to the full table after opening a document record - When users performed a global search on the Documents full table and opened a document record from the search results, returning to the full table cleared the global search filters and reverted to the initial search state from the start of the user's session. Applied search terms and filter selections were not retained. Document data was not affected. The underlying cause has been resolved.

  • DM-8499 - [Documents Module] Training Grace Period cannot be set to 0 for existing Document Categories - Users were unable to set the Training Grace Period to 0 days on existing Document Categories. The field enforced a minimum value of 1 for categories already saved in the system, preventing administrators from configuring immediate training requirements for document updates across those categories. New Document Categories accepted a value of 0 without issue. Existing training records and document data were not affected. The underlying cause has been resolved.

  • DM-8500 - [Documents Module] Exported PDF file names are missing the Document Title, making it difficult to identify files after export - When documents were exported as PDFs, the resulting file names no longer included the Document Title. The naming convention changed after a prior release update, making exported files more difficult to identify and manage after download. This affected all PDF document exports and represented a high-frequency transaction. Document content and source data were not affected. The underlying cause has been resolved.

  • DM-8509 - [Documents Viewer]: Current page position in the WebViewer is lost when switching tabs - When users navigated away from a Documents Viewer tab to another open tab and then returned, the viewer reset to the first page of the document and the user's current page position was lost. This affected all users reading multi-page documents while navigating across open tabs. Document data was not affected. The underlying cause has been resolved.

  • DM-8510 - [Documents Full Table]: Column width adjustments fail to persist after saving views or navigating between tabs - Custom column width adjustments made on the Documents Full Table were not retained after saving a view or switching between open tabs. Column widths reverted to their default sizes upon return, discarding any user-configured layout. Saved filter configurations and document data were not affected. The underlying cause has been resolved.

  • PDF-1072 - [PDF Export] Digital signature fails intermittently when the signature and timestamp token exceeds the reserved 13.000-byte buffer, causing documents to be exported unsigned - Under specific conditions, PDF exports with x509 digital signature certificates produced documents without the x509 digital signature certificate applied. The failure was intermittent - the same document could complete signing successfully on one export attempt and fail on another, depending on which trusted timestamp authority processed the request. Document content was not affected by failed x509 signing attempts, and source data integrity was maintained throughout. The reserved signature buffer has been increased to accommodate larger timestamp token responses, and the system now rotates to an alternate trusted timestamp authority when an initial x509 signing attempt cannot be completed. The underlying cause has been resolved.

  • PDF-1074 - [PDF Conversion] Legacy Form Checkboxes Render Multiple Times After PDF Regeneration - When documents built using Legacy Form templates were regenerated as PDFs, checkbox fields displayed multiple times in the same location rather than once. The resulting exported PDF showed visual corruption in the checkbox areas of the document. This affected Legacy Form documents containing checkbox fields that underwent PDF regeneration. Documents not built using Legacy Form templates were not affected, and source document content and form field data were not affected. The underlying cause has been resolved.

  • TRAIN-2188 - System fails to delete or retire documents, unassign users, or remove a document from a course when incomplete training records on the document contain quiz attempts or answers - Under specific conditions, administrative operations in the Training module failed with an error and could not be completed. Affected operations included retiring a document, removing a user's training assignment from a document, removing a document from a Training course, and updating a document's retraining interval. This occurred when the document or course had training records in an incomplete state that contained associated quiz attempt data. Training records without quiz attempt data were not affected. Completed training records, historical quiz results, course configurations, and document data were not affected. Any training records left in an affected state as a result of this issue have been identified and corrected as part of this release. The underlying cause has been resolved.

  • TRAIN-2266 - [Role Management] Incomplete Training Records persist for user with failed attempts on training challenge questions if they are removed from a role assigned to a course including the document with failed attempts - When a user was removed from a role assigned to a course that included documents on which the user had failed training challenge question attempts, the user's incomplete training records for those documents were not removed. The affected users continued to see pending training assignments on their Dashboard and Training Dossiers for documents and courses they were no longer assigned to. This occurred in specific cases where the user held incomplete training records containing failed quiz attempt data at the time of role removal. Completed training records and historical quiz results were not affected. Course configurations, document data, and other users' training records were not affected. Any orphaned training records resulting from this issue have been identified and corrected as part of this release. The underlying cause has been resolved.

  • WF-327 - [Change Controls]: Chat log data is no longer visible after navigating back to the Change Control from a related task - When a user opened a task linked to a Change Control record and then returned to the Change Control tab, the Chat Log section no longer displayed its entries. After brief page reload occurred upon returning to the tab, after which the Chat Log appeared empty. Chat log data was not deleted or modified; entries were visible again after a full page refresh. All Change Control records with Chat Log entries were affected when navigating to and from linked tasks. Source data was not affected. The underlying cause has been resolved.

  • WF-328 - [Workflows] Due Date History window formatting is too narrow - The Due Date History popup window in Issues and Change Controls modules displayed at an incorrect, narrower-than-expected width. All history data remained accessible and the feature remained fully functional; only the visual layout of the window was affected. Due date history data and all workflow records were not affected. The underlying cause has been resolved.

Please view the traceability matrix for more details on the full list of enhancements and bug fixes included in the release.

Schedule

To minimize disruption, the 31.2.0 release deployment to sandbox and production are scheduled separately. Both will occur outside top hours, to provide as little interruption to normal operations as possible.

Sandbox

Date: 07-JUL-2026

Time: 8:00 AM EDT / 12:00 PM UTC

Downtime: No downtime

Production

Date: 08-JUL-2026

Time: 08-JUL-2026 5:00 AM EDT / 9:00 AM UTC

Downtime: No downtime

Impact

This release impacts users across the following modules: Audit Reports, Change Controls, Documents, Issues, Tasks, Training, Workflows.

Documentation

This release is being managed through change control 301-133. You can download a copy of the first stages of the system release record, including the requirements and testing traceability matrix for release notes here 31.2.0 System Release Record 301-133 Release Notes. Requirements and Testing Traceability Matrix (Summary for Release Notes).xslx (for major and minor release) is also uploaded to the auditor share account and clients can download it in excel format. An entire release record will be available for review after the release is completed, in the auditor share account.

An updated copy of the URS/UAT template will be available in your Auditor Share Account.

We expect no downtime.

Version Details

ZenQMS comprises a microservice architecture that breaks up large functions into smaller services. This reduces risk in the development and release process. As such this flagship release version is actually composed of the releases of the individual services components. It is entirely possible for a component service to not change versions in a release cycle even if other components do. Here is the summary for this release.

ZenQMS Release 31.2.0 contains the following “FixVersions”. We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.

"DM 31.2.0","PDF 31.2.0","TRAIN 31.2.0","WF 31.2.0","ZENQ 31.2.0"

Updated Modules

  • Audit Trail

  • Audits

  • Change Control

  • Documents

  • Issues

  • PDF generation service

  • Training

  • Workflows

Unchanged Modules

  • Account Backup

  • Administration

  • AI Features

  • Daily Summary emails

  • Import/Export Data service

  • Insights

  • Integrations

  • Login/Authorization

  • Notifications emails

  • Public API

  • Reports

  • Settings

  • Tasks

  • ZenSign

Important Notes

  • This announcement plus the banner announcement in the application to ALL users is our formal announcement for the release.

  • You will be able to log into https://test2.zenqms.com/ and try out the changes from 31.2.0 release ahead of 08-JUL-2026. This environment was refreshed on 20-MAY-2026 with your latest production data and will be available for you to login starting 30-JUN-2026.

  • To minimize disruption, the 31.2.0 release deployment to sandbox and production are scheduled separately. Both will occur outside peak hours to provide as little interruption to normal operations as possible. We expect zero downtime. This release introduces a series of bug fixes across multiple modules and technical updates to the Audit Trail that make existing audit trail transactions for Audit Reports and Observations available directly within ZenQMS (Settings -> Account -> Audit Trail). All changes in this release are low impact and can be explored at your convenience in https://test2.zenqms.com/ ahead of the production deployment on 08-JUL-2026.

  • Beginning in November 2025, ZenQMS is adopting a new traceability matrix format for its software updates. See this article for details.

  • To better understand the different stages of feature availability at ZenQMS - Beta, Limited Availability, and General Availability - please see the dedicated support article.

  • Deployment (as always) is handled by the ZenQMS team.

Published on 24-JUN-2026

Enlarged view