Description
The 31.0.2 patch addresses following bug fixes:
AUTH-1640 [Session Management]: Users are unexpectedly logged out and forced to re-authenticate during active sessions post-v31.0.0 release - Following the 31.0.0 release, users on SSO-enabled accounts were intermittently logged out of the system and required to re-authenticate during active sessions. The issue occurred under specific conditions on certain application pages and did not result in loss of underlying record or document data. During investigation, the root cause was identified as an unintended side effect of the fix deployed under IM-1771 in release 31.0.0. The code changes from IM-1771 were reverted in this release to resolve the session failure. The underlying cause of the session logout behavior has been resolved for SSO-enabled accounts. Please refer to the Impact section of these release notes for additional context on the revert and its effect on edit access behavior in Issues and Change Controls.
AUTH-1641 [Issues and Change Control]: PINs for signatures are not delivered or are immediately expired for SSO-enabled clients after v31.0.0 release - Following the 31.0.0 release, users on SSO-enabled accounts experienced an issue in the Issues and Change Control modules where signature PINs were either not delivered or were flagged as immediately expired upon receipt, preventing timely completion of signatures on quality records. The issue was limited to SSO-enabled accounts using application-generated PINs for electronic signatures, and did not affect the Documents module or non-SSO accounts. Underlying record data and previously completed signatures were not affected. The root cause was identified as an unintended side effect of the fix deployed under IM-1771 in release 31.0.0; the code changes from IM-1771 were reverted in this release to resolve the PIN delivery failure. Please refer to the Impact section of these release notes for additional context on the revert and its effect on edit access behavior in Issues and Change Controls.
ZENQ-8231 [Main Dashboard]: Users without read-only permissions cannot view or download records before signing in ad hoc workflow steps via Signatures Requested table - In the Main Dashboard, users assigned to ad hoc workflow steps who lacked direct read-only record permissions were unable to view or download the associated record prior to submitting their signature via the Signatures Requested table. This behavior was introduced in the new dashboard and did not reflect the intended experience, where signatories require the ability to review content before signing regardless of their read-only access level. The problem was affecting only the workflows from Training and Audits modules. Record data was not affected. The underlying cause has been resolved; users assigned to ad hoc workflow steps can now view or download the relevant record from the Signatures Requested table prior to signing.
DM-8333 [Documents Full Table]: Page number and key search reset after switching tabs or navigating away - In the Documents Full Table, the current page number and active search query were not preserved when users navigated away from the table and returned, or when switching between application tabs. Users were required to re-enter their search and re-navigate to their prior position each time they left the view. The underlying cause has been resolved; the Documents Full Table now retains its pagination state and search context across navigation and tab switches.
DM-8348 Date control for Target Effective Date and Target Approval Date (possibly more) generates error in Chinese language - When the application language was set to Chinese, users encountered an error when attempting to interact with date picker controls on document fields such as Target Effective Date and Target Approval Date. The date control failed to parse the currently displayed date value in Chinese locale format, preventing the field from being edited. The issue was limited to the Chinese language setting; users on other language settings were not affected. Document data was not affected. The underlying cause has been resolved; date picker controls now correctly handle Chinese locale date formats.
IM-1799 [Attachments]: Uploaded file names with special characters are distorted and attachments are inaccessible when clicking the link in-app - In the Change Controls, Issues and Documents modules, file attachments with special characters in the file name - such as trademark symbols or degree signs - were stored with distorted characters in the underlying file path, rendering the attachment link inaccessible when clicked in-app. The issue occurred under specific conditions where the file naming contained extended character sets, and was limited to attachments in these modules. Underlying file content was not altered; only the stored file name reference was affected. The underlying cause has been resolved; attachment file names containing special characters are now stored and resolved correctly, and in-app links open as expected.
MIG-695 During a migration, conditional custom fields are not imported correctly: instruction text/field dependencies imported, but field to field dependencies did not - During configuration migrations, field-to-field conditional dependencies were not imported into the target environment, even when other conditional logic elements such as instruction text dependencies processed correctly. The issue resulted in incomplete configuration imports requiring manual correction in the target environment. Configuration data in the source environment was not affected. This affected the internal tool used by ZenQMS Support team to migrate existing configurations into the system. The underlying cause has been resolved; field-to-field conditional dependencies are now correctly imported during migration alongside all other conditional logic elements.
ZENQ-8210 [Recently Viewed Items]: Tab names display as blank or cause errors when tab name is missing or empty - In the Recently Viewed Items sidebar section, entries for certain record types displayed as blank or produced errors when the associated tab name value was missing or empty. The issue affected a defined set of tab types where the display name field was not consistently populated, and did not affect the underlying records or data. The underlying cause has been resolved; the Recently Viewed Items component now handles missing or empty tab name values without error, and affected entries display correctly.
ZENQ-8212 [User Management]: User Table becomes unresponsive after adding or removing user roles in large member accounts - Under Settings → Account → Users, the Users Table became unresponsive and blocked all interaction following role assignment or removal actions on accounts with large user sets. The issue occurred due to a slow-running database query that did not perform efficiently at scale, and was limited to enterprise-scale accounts. No user data or role assignments were lost as a result of the freeze. The underlying cause has been resolved; the relevant query now executes within expected response times and the User Table remains responsive following role management actions on large accounts.
Schedule
Date: 07-MAY-2026
Time: 6 am EDT / 10 am UTC
Downtime: No downtime
Impact
This release impacts users across the following modules: Change Control, Documents, Issues.
During the investigation of AUTH-1640 and AUTH-1641, both issues were identified as having the same root cause: an unintended side effect of the fix deployed under IM-1771 in release 31.0.0. IM-1771 addressed a scenario where edit access to Issues and Change Controls remained locked by users who had logged out or experienced session timeouts.
In order to resolve the session logout and PIN delivery failures introduced by that fix, the code changes delivered under IM-1771 were reverted in this release.
As a result of this revert, the behavior originally addressed by IM-1771 has returned: in isolated cases, edit access to Issues and Change Controls may not be automatically released when a user's session times out or they log out. When this occurs, other authorized users can request edit control using the "Request Edit Control" option available within the record. A new bug, IM-1803, has been logged to track this issue and will be prioritized for resolution in an upcoming release.
Documentation
This release is being managed through change control 301-129. 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.0.2 System Release Record 301-129 Release Notes. An entire release record will be available for review after the release is completed, in the 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.0.2 contains the following "FixVersions". We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.
"AUTH 5.20.1", "ZENQ 29.0.1", "DM 4.2.1", "IM 7.14.1", "MIG 4.14.2"
Updated Modules
Change Control
Documents
Import/Export Data service
Issues
Login/Authorization
Settings
Unchanged Modules
Account Backup
Administration
AI Features
Audit Trail
Audits
Daily Summary emails
Insights
Integrations
Notifications emails
PDF generation service
Public API
Reports
Tasks
Training
ZenSign
Important Notes
This announcement plus the banner announcement in the application to ALL users is our formal announcement for the release.
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 06-MAY-2026