30.3.1 Release Notes

Description

The 30.3.1 patch release addresses a set of bugs identified following the 30.3.0 release that impacted functionality across Documents, Training, Issues, Change Controls, and AI Features. This patch was prioritized and fast-tracked to resolve the reported issues as quickly as possible.

 

Detailed updates include:

  • DM-8195 - [Documents Training] Duplicate training records created for documents with multiple authors when: document is assigned to a course OR user is activated OR user is added to a group already assigned to the document - When documents with multiple authors were assigned to a course, or when users were activated/reactivated or added to a group assigned to such a document, the system created multiple duplicate training records per user instead of one. The fix restructures the training record query to eliminate the author-driven row duplication, ensuring exactly one training record is created per assigned user regardless of how many authors a document has.

  • AI-103 - AI Features: Enabling AI features is possible with incorrect user and email - When administrators attempted to enable AI Features in Settings, the system accepted and activated the feature even when incorrect credentials were entered in the configuration panel. The fix ensures that credential validation is enforced at submission time, so the feature can only be enabled with correct credentials, and the action is accurately recorded in the audit trail.

  • DM-8192 - Document Custom Fields of type User/Role Multi-Select silently fail to save new selections on update - When users updated User or Role Multi-Select custom fields on a document and saved their changes, the new selections appeared to be accepted but were not persisted - the field reverted to its previous state when the page was manually refreshed. This affected both account-level and category-level custom fields of these types. The fix ensures that selections made in User and Role Multi-Select fields are correctly saved and immediately reflected without requiring a page refresh.

  • IM-1785 - User single/multiple selection fields not displaying selected users until page refresh in Issues and Change Control modules - In the Issues and Change Controls modules, users who selected values in User Single Selection or User Multiple Selection custom fields experienced a display inconsistency where the chosen user did not appear immediately after selection, requiring a page refresh to confirm the saved state. For User Multiple Selection fields, the issue also caused the field to appear empty when revisiting a closed stage after workflow approval, even though the data was saved correctly. The fix ensures that selected user values are rendered immediately upon selection and remain visible when navigating between stages.

  • IM-1790 - [Due Date Extension] Adding an additional workflow step to a Due Date Extension request prematurely closes the configuration window - When users configured a Due Date Extension request and attempted to add an additional workflow step, the configuration window closed prematurely before the step could be completed or saved. The fix ensures the configuration window remains open when additional workflow steps are added, allowing users to complete the Due Date Extension configuration as intended.

  • IM-1782 - [Linked Items] Item names are truncated in the "Linked Item" search dropdown when linking items in Issues, Change Controls and Documents Module - When users searched for items to link within Issues, Change Controls, or Documents, item names with longer titles were visually cut off in the search dropdown, making it difficult to distinguish between similarly named records. The fix adds a tooltip to accommodate full item names across all three modules.

  • ZENQ-7956 - [Linked Items] Search results in the linked items dropdown cleared unexpectedly if not selected immediately - When users typed a search term in the linked items dropdown, results appeared briefly but were then cleared and replaced with the full unfiltered list if no selection was made within a short interval. The fix ensures search results persist in the dropdown until the user makes a selection or manually clears the field.

Schedule

Date: 26-FEB-2026
Time: 6 am EST / 11 am UTC
Downtime: No downtime

 

Impact

This release impacts users across the following modules: Documents, Training, Issues, Change Controls, Tasks, and AI Features.

 

Documentation

This release is being managed through change control 301-125. 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 30.3.1 System Release Record 301-125 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 30.3.1 contains the following "FixVersions". We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.

"AI 1.1", "DM 4.1", "IM 7.13", "ZENQ 28.2"

 

Updated Modules

  • AI Features

  • Change Controls

  • Documents

  • Issues

  • Tasks

  • Training

Unchanged Modules

  • Account Backup

  • Administration

  • Audit Trail

  • Audits

  • Daily Summary emails

  • Import/Export Data service

  • Insights

  • Integrations

  • Login/Authorization

  • Notifications emails

  • PDF generation service

  • Public API

  • Reports

  • Settings

  • 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.

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

Enlarged view