30.3.0 Release Notes

Alina Cobarzan • Created • Last updated
Update 02-FEB-2026:
Minor scope changes:
- DM-8070 PDF Viewer displays incorrect document when navigating between Main Document and Draft Review due to cached state was included in the release scope.

Description & highlights

This release focuses on evolving the Main Dashboard experience, to guide users towards the actions they need to take faster & more easily, by bringing together data across modules into a unified, user-friendly interface. This new dashboard is designed to boost visibility for Item Owners and Super Users by consolidating metrics for training, documents, audits, observations, issues, change controls and tasks into easily digestible charts and tables. A new donut chart is also available for Signature Statuses, allowing users to quickly prioritize pending signatures based on their age (less than 1 day, 1–3 days, or older than 3 days) and act on them directly from the table.

 

An upgrade for Item Owners managing SCORM trainings in ZenQMS is also introduced with this release. SCORM packages can now be added and managed just like any other document, unlocking the full power of the Documents module for SCORM content, including adding scorm to courses, managing trainee compliance & more.

 

Another enhancement is the release of AI-powered table Filters. This feature allows users to search for & find their quality assets faster by generating complex table filters using natural language prompts across Documents, Change Controls, Issues, and Tasks.

 

Another notable area of improvement is the enhanced clarity in Document Retirement Reason Tracking: Users can introduce a new "Retirement Reason" column in the Documents Archive Table to distinguish between documents that are "Superseded" (replaced by a new version) and those that are "Obsoleted" (no replacement).

 

Detailed updates include:

  • All Modules at a glance on Main Dashboard: This update introduces the new Main Dashboard structure, including a UI toggle that lets users easily switch between the Classic and New dashboard experiences until Classic dashboard will be deprecated in the next major release. The new dashboard is designed to better support Item Owners and Super Users by providing improved visibility into assigned items across all modules.

    • ZENQ-6833: Add Informative Tooltips to Main Dashboard Bar Chart for Module Descriptions - Informative tooltips have been added to the Main Dashboard bar charts, providing users with clear descriptions of what each module displays. The tooltip content dynamically updates based on the selected dashboard view (My, Direct Reports, Company), helping users quickly understand the context and data shown for Training, Documents, Audits, Issues, Change Controls, and Tasks.

    • ZENQ-7194: Preserve selected dashboard view (My, Direct, Company) in the page URL - The Main Dashboard now preserves the selected view (My Dashboard, My Direct Reports, or My Company) in the page URL using a path parameter. This makes it easier to bookmark, share, and return to a specific dashboard view, improving navigation and user experience.

    • ZENQ-7403: Update Main Dashboard Table Header to Match New UI Standard - Dashboard table headers have been updated to match the new UI standard. After selecting a chart, the details table header now clearly reflects the applied filter and uses consistent, pluralized module names (except for Training), ensuring clarity and alignment with navigation labels.

    • ZENQ-6675: Implement Toggle to Switch Between Classic and New Main Dashboard - A UI toggle has been implemented on the Main Dashboard, allowing users to easily switch between the Classic and New dashboard experiences. The toggle is available across all dashboard views and is managed behind a feature flag, giving users flexibility and control over their preferred interface.

    • ZENQ-7444: Improve Main Dashboard Bar Chart readability with bold text labels - Main Dashboard bar chart readability has been improved by making key text labels bold. The "View all" link and the percentage compliant figures now stand out with bold formatting, making important information easier to spot at a glance.

    • Signature visibility: The main dashboard now features a new donut chart visualization for signature statuses, categorizing signatures based on their age: less than 1 day old, 1–3 days old, or older than 3 days. This dynamic chart updates in real time as signatures age and is visible in the “My Dashboard” and “My Direct Reports” views, helping users quickly identify which signatures need attention. In the “My Company” view, a placeholder is shown instead of the chart.

      • ZENQ-7402: Update ‘Signature Needed’ Pie Chart on Main Dashboard for Better Usability - The ‘Signature Needed’ pie chart on the Main Dashboard has been updated for better usability, including a wider “Signature Past Due” segment, larger numbers, updated labels, and a clickable center area for improved interaction.

      • ZENQ-7328: Display "Signatures Due Now" donut chart with real data retrieved from the server - The “Signatures Due Now” donut chart now displays real, live data from the server, accurately reflecting pending signatures by age (<1 day, 1–3 days, >3 days).

      • ZENQ-7329: Display "Signatures Due Now" chart table with live data retrieved from the server - After clicking a segment of the donut chart, a detailed table appears below, showing live data for the selected segment.

      • ZENQ-7330: Allow users to export "Signatures Due Now" chart table data - Users can now export the “Signatures Due Now” table data in CSV or Excel format, with exports reflecting any filters applied in the UI.

      • ZENQ-7430: Display module type in the “Type” column of the Signatures Needed table (except for documents module types) - The “Type” column in the Signatures Needed table now displays the module type (e.g., Issues, Change Controls, Tasks, SCORM, etc.), except for document module types, making it easier to identify the source of each signature.

      • ZENQ-7434 Implement new UI for Approve/Reject/Delegate actions in the “Signatures Due Now” table - A new UI has been implemented for Approve, Reject, and Delegate actions directly in the “Signatures Due Now” table. These actions are context-aware, only appearing when the user has the appropriate permissions, and trigger the correct modals or record views.

      • ZENQ-7476 Implement support for Approve / Reject / Delegate actions on Documents Signatures in the “Signatures Due Now” table - Users can now Approve, Reject, or Delegate signatures for Documents directly from the table, with permissions enforced and the UI updating in real time.

      • ZENQ-7477 Implement support for Approve / Reject / Delegate actions on Issues & Change Controls Signatures in the “Signatures Due Now” table - Users can now Approve, Reject, or Delegate signatures for Issues and Change Controls directly from the table, with permissions enforced and the UI updating in real time.

      • ZENQ-7478 Implement support for Approve / Reject / Delegate actions on Tasks Signatures in the “Signatures Due Now” table - Tasks signatures can now be Approved, Rejected, or Delegated from the table, with delegation limited to users with the correct permissions.

      • ZENQ-7479 Implement support for Approve / Reject / Delegate actions on SCORM Signatures in the “Signatures Due Now” table - SCORM signatures can be Approved or Rejected from the table (delegation is not available for SCORM).

      • ZENQ-7480 Implement support for Approve / Reject / Delegate actions on Events, Tests & Audits Signatures in the “Signatures Due Now” table - Events, Tests, and Audits signatures now support Approve, Reject, and Delegate actions, with delegation rules tailored to each module and dashboard view.

      • ZENQ-7411 Signatures Needed table to have more details in the Type column - The Signatures Needed table’s “Type” column now provides even more detail, including subtypes for each module (e.g., Document Approval, Issue - Stage Transition, SCORM - Launch, etc.), and supports filtering and sorting on all columns.

    • Timely completion and unified view across Documents, Change Control, Issues, and Tasks modules: Item owners can easily track past due, at risk, and compliant statuses of items across all modules in on place, ensuring on-time completion. This ensures the dashboard provides a unified, up-to-date view of key metrics across all major modules.

      • ZENQ-7393 Implement new UI on Main Dashboard for Documents Barchart and Drill Down Table

      • ZENQ-7408 Implement new UI on Main Dashboard for Issues/Change Controls Barchart and Drill Down Table

      • ZENQ-7409 Implement new UI on Main Dashboard for Tasks Barchart and Drill Down Table

      • ZENQ-7364 Integrate filters and search functionality on Issues/Change Controls Tables - this allows users to quickly find and narrow down relevant records based on their criteria.

      • ZENQ-7540 Enable Sorting by Review Date in Documents Table on New Main Dashboard - The Documents table now supports sorting by the "Review Date" column, in addition to sorting by "Name," enabling users to prioritize documents that are nearing review more efficiently.

    • Training visibility: The new Main Dashboard now includes training bar charts that visually represent the status of all training assignments (Documents, SCORMs, OJTs, Group and Personal Events, Tests) for the logged-in user. The charts use red, yellow, and green bars to indicate overdue, at-risk, and completed assignments, respectively, with the width of each bar reflecting its proportion of the total. Users can toggle between viewing raw numbers or percentages, and special rounding rules ensure clarity even in edge cases. If there are no assignments, a grey bar with a "No Assignments" message is shown.

      • ZENQ-6981: My Training Dashboard View: training bar charts count values should accurately reflect user's training records - assignments are split into Red (Past Due), Yellow (At Risk/Coming Due), and Green (Compliant/Not Due Yet).

      • ZENQ-6982: My Direct Reports Dashboard View: training barcharts count values should accurately reflect the training status of direct reports

      • ZENQ-6983: My Company Dashboard View: training barcharts count values should accurately reflect trainees training status - display the training status of all trainees in the company, with access controlled by permissions.

      • ZENQ-7401: Update Training Table link text from “Execute” to “Train Now” for better clarity

      • ZENQ-7462: Default sorting for Training Items by Due Date (ascending) across all Dashboard views

      • ZENQ-6987: My Training Dashboard View: populate Drill Down tables with accurate data

      • ZENQ-6988: My Direct Reports View: populate Drill Down Tables with accurate data

      • ZENQ-6989: My Company Training Dashboard View: populate drill down tables with accurate data

      • ZENQ-7218: Show/Hide 'Complete' action on Execute column based on the training item type, status, selected view

      • ZENQ-7219: Users can download training assignments from the main dashboard drill down tables, based on specific permissions

      • ZENQ-7220: User can Preview SCORM after completion from the Main Dashboard Training drill down tables

      • ZENQ-7221: Show 'No Retraining' on Due date column for documents and SCORMs with NEVER as Retraining Interval on which user has already trained

      • ZENQ-7223: Enable user to include in the training drill down tables additional completed training records

      • ZENQ-7225: Click on Training Item name/ID should open the item based on user's permissions and training item type

      • ZENQ-7226: Export Training Drill Down table from Main Dashboard

      • ZENQ-7227: Download Training Certificate from Training Drill Down Tables

      • ZENQ-7228: Open User Profile when clicking on User Name/Supervisor Name

      • ZENQ-7301: Adjust Drill Down Tables Headings/Titles and move Execute column first

      • ZENQ-7342: Turn Item Type filter into dropdown menu with defined values

    • Audit Reports and Observations visibility: The main dashboard now features a bar chart section that visualizes counts and percentages of audit reports and observations, split by status (past due, coming due, not due yet). This chart is available in all three dashboard views: My Dashboard, My Direct Reports, and My Company Dashboard. Clicking on a bar or the "View All" link opens a drill-down table that combines audits and observations, with columns for item type, ID, site, state, lead auditor, target, scheduled date, and observation-specific details. This update provides a unified, interactive view for tracking audit and observation statuses across the organization.

      • ZENQ-7502 Counts should accurately reflect data based on the selected view - Bar chart counts for audits and observations now accurately reflect the data based on the selected dashboard view (My Dashboard, My Direct Reports, My Company), ensuring users see the correct numbers for Past Due, Coming Due, and Not Due Yet items.

      • ZENQ-7504 My Dashboard View: click on bar charts/view all link should load drill down table populated with accurate data for the logged in user.

      • ZENQ-7515 My Direct Reports view: click on bar charts/view all link should load drill down table populated with accurate data for the user and their direct reports.

      • ZENQ-7516 My Company view: click on bar charts/view all link should load drill down table populated with accurate data for all users in the company, respecting permissions.

      • ZENQ-7529 User can download an audit or observation PDF from the new main dashboard tables.

      • ZENQ-7530 Add “Export View” feature to be able to export audits and observations tables from the New Main Dashboard, based on selected columns, sorting and filters applied.

      • ZENQ-7531 Open Edit Audit/Edit Observation page by clicking the Item ID from the drill-down table.

      • ZENQ-7533 Value from Audit State column should be hyperlinked (based on permissions), providing direct access to relevant audit actions or details.

      • ZENQ-7545 Auditee Site value should be hyperlink directing to the QSheet page.

      • ZENQ-7578 Update texts from the tooltips shown when hovering on the "info" icon explaining exactly what audits and observations are included in each dashboard view.

  • Leveraging Documents Module capabilities for managing SCORM training packages: This release introduces a major upgrade for Item Owners managing SCORM trainings in ZenQMS. SCORM packages can now be added and managed just like any other document, unlocking the full power of the Documents module for SCORM content. This means you get richer metadata, improved configurability, and streamlined lifecycle management for your SCORM trainings - all in one place. With this enhancement, Item Owners can leverage familiar document workflows (like periodic review, draft review, and suggested edits), benefit from a unified training management experience, and enjoy easier reporting and compliance tracking. While end users taking SCORM trainings will see little change, administrators and training managers will find it much easier to configure, track, and maintain SCORM content, driving higher adoption and efficiency across your organization.

    • TRAIN-1547 [SCORM Document Creation] Update the 'Create new Document' page to accommodate creation of a new SCORM item - This change updates the 'Create New Document' page to support the creation of SCORM items directly within the Documents module. When the relevant feature flag is enabled, users selecting "+SCORM" from the menu are redirected to a unified document creation page, streamlining the process and aligning SCORM creation with standard document workflows. This ensures a consistent user experience and supports a progressive rollout of SCORM integration.

    • TRAIN-1634 [SCORM Document Creation] Upload revision OR Select from Marketplace Catalog - With this update, users can now upload a SCORM package or select one from a marketplace catalog when creating or editing a SCORM document. The interface provides clear options for uploading valid SCORM .zip files or choosing from available catalog entries, with error handling and helpful messages for invalid uploads. This makes it easier and more flexible to add SCORM content to documents.

    • TRAIN-1677 [SCORM Document Lifecycle] Inherit the SCORM package or selection from catalog when upversioning the SCORM document - This story ensures that when a SCORM document is upversioned (major or minor revision), the associated SCORM package or catalog selection is inherited by the new draft version. Users can preview the inherited SCORM content, and the version history accurately reflects the current revision, maintaining continuity and reducing manual rework during document updates.

    • TRAIN-1551 [SCORM Document Viewing/Editing] Accommodate View/Edit documents page for SCORM type - The View/Edit documents page is now adapted to accommodate SCORM-type documents. When creating or editing a SCORM, users are redirected to a familiar interface with certain fields hidden or adjusted specifically for SCORM (e.g., training fields are always enabled and some document security options are hidden). Tooltips and field behaviors are tailored to clarify that all SCORM items are inherently training documents, simplifying the process for users.

    • TRAIN-1552 [SCORM Document Viewing/Editing] Include "Preview SCORM" button in the PDF Viewer to support previewing SCORM content directly from document viewer - This change introduces a "Preview SCORM" button in the document viewer, replacing the default PDF viewer for SCORM files. Users can now preview uploaded or selected SCORM packages directly from the View/Edit page, with clear messaging and a dedicated preview experience. This ensures SCORM content is accessible and testable in a way that fits seamlessly into the existing document workflow.

    • TRAIN-1679 [SCORM Document Viewing/Editing] Permissions for Preview button under View/Edit document page - Permissions for the "Preview SCORM" button on the View/Edit documents page are now enforced. Only users with specific roles or permissions (such as Account Super Users, document authors, workflow participants, or those with certain document category permissions) can see and use the preview functionality. This ensures that SCORM previews are only accessible to authorized users, supporting compliance and content security.

    • TRAIN-1725 [SCORM Document Viewing/Editing] Add conditional preview access for completed SCORM training for users that are assigned to train directly or through a course -The "Preview" button for SCORM training documents is now conditionally enabled based on training completion. Users assigned to train (directly or via a course) will only see the preview option once they have successfully completed the training. Until then, the button is disabled with a tooltip explaining the restriction, aligning the user experience with compliance requirements and learning flow best practices.

    • TRAIN-1554 [SCORM Document Lifecycle] Hide "Compare Versions" button for SCORM Version History - This update hides the "Compare Versions" button in the Version History slider for SCORM-type documents, since comparing different SCORM packages is not meaningful. The button remains visible for other document types, ensuring the UI is logical and tailored to the capabilities of each document type.

    • TRAIN-1555 [SCORM Document Lifecycle] Draft Review for SCORM supports download and sequential review on local device - The Draft Review workflow for SCORM documents is now specialized: collaborative options like "Edit Online" and "Annotate on Screen" are removed, leaving only the option to download and review sequentially on a local device. Uploading new revisions is restricted to valid SCORM ZIP files, and the "Compare Selected Documents" button is hidden for SCORM, streamlining the review process for this content type.

    • TRAIN-1670 [SCORM Document Lifecycle] Review/Retire - Periodic Review SCORM - This change enables users to perform periodic review and retirement actions for SCORM documents, mirroring the options available for standard documents. Users can mark items as obsolete, current, or requiring updates (major/minor upversion), with workflows and comments enforced for each action, ensuring SCORM documents follow the same lifecycle management as other document types.

    • TRAIN-1838 [SCORM Training Management] Create retraining modal inside the Training tab when the user fails the SCORM training - When a user fails a SCORM training (does not meet the passing score), a modal now appears in the Training tab, clearly informing them of the failure and providing a "Retake Training" button. The user must retake the training to proceed, and the number of attempts is incremented, ensuring a clear and compliant retraining flow.

    • TRAIN-1553 [SCORM Training Management] View SCORM registration data in new Training tab section - A new "SCORM Registration Data" tab is added to the Training section for SCORM documents, allowing owners to view, manage, and export detailed registration data (including trainee, supervisor, completion status, score, and attempts). Group actions like "Reset Attempts" and export to CSV/Excel are also supported, giving owners better oversight of SCORM training progress.

    • TRAIN-1558 [SCORM Training Management] Training page updated to display SCORM-specific information - The Training tab for SCORM documents now displays SCORM content directly (using Rustici integration) instead of the PDF viewer, and removes the challenge questions section. The "Complete Training" button is only enabled after the SCORM module reports a "Passed" status, ensuring users can only complete training after meeting SCORM requirements.

    • TRAIN-1793 [SCORM Training Management] Group Actions > "Reset Attempts For Selected Users" - Admins can now reset training attempts for selected users in the SCORM Registration Data section, provided they have the right permissions. This action only affects non-completed training records, and a confirmation modal ensures users understand the impact. Audit events are generated for traceability, and exports reflect the reset actions.

    • TRAIN-1803 [SCORM Tables & Reporting] SCORM registration exports now include supervisor information - Exports of SCORM registration data now include the supervisor name for each user, providing more complete information in CSV/Excel exports and aligning the exported data with what’s shown in the UI.

    • TRAIN-1556 [SCORM Permissions & Roles] Access to the "Select from Marketplace Catalog" option should be controlled by permissions so that only authorized users can select SCORM packages from the catalog - The "Select from Marketplace Catalog" option for SCORM documents is now permission-controlled. While all users can see the dropdown, only those with specific permissions can edit and select SCORM packages from the catalog, ensuring proper access control.

    • TRAIN-1557 [SCORM Permissions & Roles] Update “Where is this role used“ section from Account Roles/Permissions and “Merge roles“ functionality to correctly handle Document (File Review) and Document (SCORM) items - The "Where is this role used?" section and role merging functionality now accurately distinguish between File Review assignments for standard documents and SCORM items. Counts and assignments are split and displayed separately, ensuring transparency and preventing duplication when merging roles.

    • TRAIN-1560 [SCORM Tables & Reporting] Add a new columns under Documents Full Table and Archive Full Table for identifying SCORM type - Two new columns, "File Extension" and "Content Type," are added to the Documents Full Table and Archive Full Table. These columns allow users to filter and identify SCORM and non-SCORM items more easily, and are included in exports, improving reporting and data management.

    • TRAIN-1813 [SCORM Tables & Reporting] SCORM document type filter available in Dossiers and Dashboards - SCORM items now appear as "SCORM" in all relevant UI filters (Dossier, Main Dashboard, My Training Dashboard), making it easy for users to filter and identify SCORM-based trainings separately from other documents. This label is consistent across API responses, UI elements, and exports.

    • TRAIN-1894 [SCORM Tables & Reporting] Update backup CSVs to include the new columns added in Documents Full Table and Archive Full Table - The backup CSV files generated for Documents and Archive Documents now include the new "Content Type" and "File Extension" columns, ensuring that backup data matches the UI and supports better data recovery and analysis.

    • TRAIN-1675 [SCORM UI Updates] Download icon behavior updated for SCORM documents across application - Download options for SCORM documents are now gated based on content source and user permissions. For SCORMs from the Marketplace, the "Download Original File" option is disabled with a tooltip, while for uploaded SCORMs, only users with specific permissions can download the original file. This ensures compliance with licensing and security requirements.

    • TRAIN-1893 [SCORM UI Updates] Legacy SCORM Full Table hidden when using Documents-based SCORM - For members using the new SCORM integration in the Documents module, the legacy SCORM Full Table is hidden and users are redirected to the Documents Full Table. This streamlines navigation and ensures all SCORM items are managed in one place.

    • TRAIN-1900 [SCORM UI Updates] Remove 'Training Challenge Questions' section from Export to PDF when type SCORM - When exporting SCORM documents to PDF, the "Training Challenge Questions" section is now removed, and the export option is renamed to "Training Summary." This ensures exports are relevant and tailored to SCORM content, while exports for standard documents remain unchanged.

  • AI-powered Advanced Filtering is now available to all customers! Admins can enable or disable AI features for their account, and users can leverage natural language to generate complex table filters across Documents, Change Controls, Issues, and Tasks modules. This release also brings expanded support for custom fields, enhanced security, and robust feedback and evaluation tools.

    • Admins now have a dedicated UI in Account Settings to enable or disable AI features for their organization. This includes a clear opt-in process, terms of service acceptance, and granular control over which AI features are available to users.

      • AI-79 AI opt in page: UI for customers to sign TOS & choose which AI features to turn on - Delivered the AI opt-in page, allowing super users to accept TOS and toggle AI features on/off for their account.

    • Smart column search to find items easily powered by Artificial Intelligence - Users can leverage natural language to generate complex table filters across Documents, Change Controls, Issues, and Tasks modules, including support for custom fields

      • AI-4 Generate Advanced Filters on Documents Full Table with AI - Users can now generate advanced filters on the Documents Full Table using natural language prompts. By describing what they want to see, users can quickly create complex filter sets, making it easier to find relevant documents without manually configuring each filter..

      • AI-32 Generate Advanced Filters with AI based on user natural language prompts referencing custom fields - AI-powered advanced filtering now supports custom fields in the Documents Full Table. Users can reference custom fields in their natural language prompts, and the AI will generate the appropriate filters, expanding the flexibility and power of AI-driven search.

      • AI-46 Allow Custom Fields Single Select/Multiple Select type to be set with operators different than "Equals" and "Not Equals" - The AI filtering feature now supports a wider range of operators for custom fields of type single select and multiple select, including “contains,” “not contains,” “starts with,” and “ends with.” This makes it easier for users to create more nuanced and flexible filters using natural language.

      • AI-19 Enable users to give feedback on AI-generated Advanced Filters - A feedback section has been added to the AI-generated advanced filters experience. After generating filters with AI, users can quickly provide thumbs-up or thumbs-down feedback and, if needed, add comments to help improve the quality and accuracy of future AI results.

      • AI-40 Add link to helpdesk article about how to generate filters with AI on Advanced Filters slider from Documents Full Table page - A help link has been added to the AI advanced filters slider in the Documents Full Table. Clicking the “?” icon below the prompt input opens a support article explaining how to use AI to generate filters, making it easier for users to get started and learn best practices.

      • AI-11 UI changes for AI Advanced Filters features in full Documents table - The Documents Full Table now features a dedicated input box and “Generate Filter” button on the Advanced Filters slider, allowing users to type natural language queries and have the AI turn them into advanced filters. This update streamlines the process of building complex filters.

      • AI-13 Show loading visual indicator while user's prompt is being processed and filters are being generated/updated - While the AI processes a user’s prompt and generates or updates filters, users will see a clear loading animation, improving transparency and user experience.

      • AI-35 Generate AI advanced filters based on the columns from Change Controls Full Table - introduces AI-powered advanced filtering to the Change Controls Full Table, allowing users to generate complex filters using natural language prompts. Users can now create filters based on any existing column, including both standard and custom fields, with support for a wide range of operators (e.g., contains, equals, greater than). The feature also includes a feedback mechanism and supports conditional custom fields, making it easier and more intuitive to find relevant change controls by simply describing what you’re looking for in plain English.

      • AI-68 Change Controls/Issues/Documents Full Table: Enable filtering by "category" through AI processing of NLQ - Enables users to generate advanced filters using natural language prompts that reference category names in Change Controls, Issues, and Documents Full Table. Previously, AI could not process category-based queries due to internal GUID mapping, but now the system intelligently matches user-specified category names to their internal IDs and applies the correct filters. This enhancement allows users to intuitively filter records by category - regardless of whether the category column is displayed - making AI-powered filtering more natural, accurate, and user-friendly across all core modules.

      • AI-44 Generate advanced filters with AI on Issues Full Table - brings AI-powered advanced filtering to the Issues Full Table, enabling users to generate and apply complex filters using natural language prompts. With this enhancement, users can describe the criteria they want—such as specific columns, values, or conditions—and the AI will automatically create the corresponding filters. The feature supports all standard columns and includes a feedback option, making it easier and more intuitive to find and analyze issues without manually building advanced filters.

      • AI-50 Generate advanced filters with AI on Tasks Full Table - introduces AI-powered advanced filtering to the Tasks Full Table, allowing users to create and apply detailed filters simply by describing what they need in natural language. Users can now generate filters based on any standard column in the Tasks table, making it much easier to find and analyze tasks without manually configuring filter criteria. This enhancement streamlines the workflow and brings a more intuitive, conversational experience to task management.

  • Document Retirement Reason Tracking: This release introduces enhanced clarity and consistency to document retirement tracking in the Documents Archive Table. The changes add a new “Retirement Reason” column to distinguish between documents retired as “Superseded” (replaced by a newer version) and those retired as “Obsoleted” (no replacement). The updates ensure this distinction is reflected throughout the UI, exports, imports, and account backups, providing users with more accurate and actionable document lifecycle information.

    • DM-7355 Documents Archive Table: Add new document sub-status to distinguish retired documents between obsolete and superseded - A new “Retirement Reason” column has been added to the Documents Archive Table, allowing users to see whether a retired document was “Superseded” by a newer version or “Obsoleted” without replacement. This distinction is filterable, sortable, and included in exports, giving users better insight into document status.

    • DM-7950 [FlatFile Configuration Migration] Update FlatFile Document Importing process so it sets the correct "Retirement Reason" for Documents - The Flatfile document importing process now supports the new “Retirement Reason” logic. When importing retired documents, the system will automatically set the correct sub-status (“Superseded” or “Obsoleted”) based on whether a newer version exists, ensuring imported data aligns with the updated retirement tracking. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

    • DM-7952 Add the new "Retirement Reason" column/field/data to the Account Backup - The “Retirement Reason” field and its values (“Obsoleted” or “Superseded”) are now included in the Account Backup. This ensures that backup data fully reflects the new document retirement distinctions for improved data integrity and restoration.

    • DM-7951 Rename sub-type "Obsolete" to "Obsoleted" in Documents Archive Table - To maintain consistent terminology, the sub-type “Obsolete” has been renamed to “Obsoleted” throughout the Documents Archive Table, UI, and exports. This update aligns the language with the existing “Superseded” term and ensures clarity for users.

  • New or updated Reports Added to the Reports Module:

    • REP-687 [Settings: Reports] Create Report "Tasks: Tasks Full Table Report" - A new "Tasks: Tasks Full Table Report" is now available under the Reports page, allowing users to directly download a comprehensive export of all task-related data, including the new Task Assignee Response field.

    • REP-688 [Settings: Reports] Update "Documents: Document Category Workflow Settings Report" ZenSign Update - The report has been updated to include ZenSign settings, specifically the "Allow External Assignee" field.

    • REP-689 [Settings: Reports] Create Report "Documents: Document File Attachments Report" - A new report is now available, providing users with a detailed export of all external file attachments linked to documents, including the total number of attachments per document.

    • REP-699 [Settings: Reports] Update "Documents: Documents Archive Table Detailed Report" SCORM Update - The report has been enhanced to include a new "Content Type" column, supporting the addition of SCORM files in the Documents module.

    • REP-700 [Settings: Reports] Update "Documents: Documents Full Table Detailed Report" SCORM Update - The report now features a "Content Type" column, enabling users to distinguish between different file types, including newly supported SCORM files.

    • REP-701 [Settings: Reports] Update "Training: SCORM Training Report" SCORM Update - The report has been updated to capture results from both legacy and new SCORM files in the Documents module. The report now includes all relevant columns to track SCORM training completion, scores, and attempts, supporting robust training compliance tracking.

  • We continued to enhance the recording of audit events for key actions across the app, by updating the system to log audit trail metadata immediately during each transaction - rather than relying on a background worker. This improvement ensures better transparency, faster compliance reporting, and a more responsive experience for administrators. We will implement these updates on a service-by-service basis over the next several releases. In version 30.3.0, we are applying these changes to the following areas:

    • IM-1708 Update audit events for ISSUES/CHANGE CONTROL/TASKS COMMENT CREATION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1713 Update audit events for CHANGE CONTROL/ISSUES/TASK WORKFLOW STEPS EXECUTION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1716 Update audit events for ISSUES/CHANGE CONTROL CATEGORY CREATION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1717 Update audit events for ISSUES/CHANGE CONTROL CATEGORY VERSION DELETION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1718 Update audit events for ISSUES/CHANGE CONTROL CATEGORY VERSION RETIREMENT to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1720 Update audit events for ISSUES/CHANGE CONTROL CATEGORY RESTAURATION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1721 Update audit events for ISSUES/CHANGE CONTROL CATEGORY BULK DELETION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1722 Update audit events for ISSUES/CHANGE CONTROL/TASKS CATEGORY PDF OPTION CHANGES to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1723 Update audit events for ISSUES/CHANGE CONTROL CATEGORY ROLE& PERMISSION CHANGES to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1724 Update audit events for ISSUES/CHANGE CONTROL/TASKS COMMENT DELETION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1725 Update audit events for ISSUES/CHANGE CONTROL CATEGORY UPDATES to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • IM-1726 Update audit events for ISSUES/CHANGE CONTROL/TASKS COMMENT UPDATE to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-323 Update audit events for TASK USER UNASSIGNMENT to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-324 Update audit events for CANCELLING TASK WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-325 Update audit events for LAUNCHING TASK DELETION WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-326 Update audit events for CANCELLING TASK DUE DATE WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-327 Update audit events for LAUNCHING TASK WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-328 Update audit events for TASK STATUS UPDATE to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-329 Update audit events for TASK CREATION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-330 Update audit events for TASK COMPLETION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-331 Update audit events for TASK SUPER-ADMIN MODE ACTIVATION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-332 Update audit events for TASK DELETION to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-333 Update audit events for LAUNCHING TASK COMPLETION WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-334 Update audit events for TASK UPDATE to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-335 Update audit events for TASK USER ASSIGNMENT to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-336 Update audit events for CHANGING TASK DUE DATE to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TM-337 Update audit events for LAUNCHING TASK DUE DATE WORKFLOW to capture metadata directly in Morpheus API, reducing the time required for information to appear in UI Audit Trail Table

    • TRAIN-1940 Update audit events for SCORM items to capture metadata directly in SCORM API, reducing the time required for information to appear in UI Audit Trail Table

  • Other enhancements across the application aimed at enhancing user experience, improving system functionality, and ensuring data integrity across various modules. These updates address key areas such as workflow management, document handling, and user interface enhancements:

    • DM-7919 [Documents Workflows] Allow Ad Hoc steps to be placed anywhere in the workflow between Authors and Always Last steps - This update lets users place Ad Hoc signature steps at any point after the Author steps, not just at the end. Users can insert Ad Hoc steps between configured workflow steps, running them simultaneously with category steps, or after all category steps, running sequentially. Steps set to run “Always last” will execute at the very end, after all category and Ad Hoc steps. This change offers greater flexibility for custom approval processes.

    • ZENQ-7183 User logout (manual or due to inactivity) needs to be captured in the visible Account Audit Trail table - Logout events - both manual logouts and automatic session timeouts - are now captured and displayed in the visible Account Audit Trail table. This ensures full traceability of user sessions, with clear differentiation between manual and timed-out logouts, and includes these events in audit trail exports for compliance and reporting. -

    • ZENQ-7717 [Settings -> Configuration] All Category tables should default to filter on Active Categories - All category tables in Settings → Configuration (Documents, Change Controls, Issues) now default to filtering on Active Categories only. This reduces clutter for admins by hiding Draft and Retired categories unless specifically requested, making category management more streamlined and user-friendly.

    • API-73 Public API: Endpoint to search items (Issues/Change Control/Custom Modules) based on basic fields - A new public API endpoint, /v2/items/search, has been introduced to allow users to search for Issues, Change Controls, and Custom Modules based on basic fields such as title, key, category, assignee, and date ranges. The endpoint supports advanced filtering with AND/OR logic, pagination, and sorting, and only returns data accessible to the API token. This makes it easier for integrations and external systems to retrieve and filter items programmatically.

    • API-76 Public API: Add support for external id on Users endpoint - The Public API now supports an external_id field on the Users endpoint, allowing integrations to associate ZenQMS users with identifiers from external systems. Users can be created and updated with an external_id, and this field is included in all user retrieval responses. The system enforces uniqueness for external_id and ensures no breaking changes for existing API consumers.

    • MIG-599 [FlatFile Configuration Migration] Create Roles - Account Permissions tab migration template - A new "Roles: Account Permissions" tab has been added to the Excel Migration Template, allowing admins to pre-configure roles and map them to specific account-level permissions before migration. This tab streamlines the setup of role-based access controls and ensures all roles and permissions are clearly defined and ready for import. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

    • MIG-600 [FlatFile Configuration Migration] Create Roles - Account Permissions validations and submit - The FlatFile import process now supports the "Roles: Account Permissions" tab, including robust validations for role names, descriptions, and permissions. When importing, the system checks for duplicates, enforces naming conventions, and ensures only valid permissions are assigned, guaranteeing that only fully validated roles are created in the ZenQMS app. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

    • MIG-601 [FlatFile Configuration Migration] Create Roles - Legacy Permissions tab migration template - A new "Roles: Legacy Permissions" tab has been introduced to the migration template, enabling admins to define and migrate legacy role permissions that still exist in the system. This ensures that all historical access configurations are preserved and can be seamlessly migrated alongside current roles and permissions. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

    • MIG-602 [FlatFile Configuration Migration] Create Roles - Legacy validations and submit - The FlatFile import process now recognizes and validates the "Roles: Legacy Permissions" tab, allowing admins to import legacy permissions for roles with schema enforcement and dynamic dropdowns for valid permissions. The process ensures all-or-nothing validation, preventing partial imports and maintaining data integrity for legacy access controls. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

    • MIG-572 [FlatFile Configuration Migration] Improve validation for duplicate lines of exact data in FlatFile import so that unintentional duplicates can be clearly identified and removed before submission - The FlatFile import process now includes enhanced validation to detect and highlight duplicate rows containing identical data. Users are prevented from submitting templates with duplicate entries and receive clear error messages and visual cues, making it easier to identify and resolve data issues before import. Note: this only affects the tool used internally by ZenQMS Support team to migrate existing configurations into the system.

       

Key critical and major bug fixes include:

  • DM-7980 [Sequential Draft review] Comments from Reviewers are shown next to the wrong people or dates in the Draft Document Review -> Revision History - When users completed a sequential draft review, comments added in the comment box were mismatched to other users and incorrect dates, causing confusion at the review level. This was resolved by ensuring that comments are now correctly attributed to the right users and dates during the review process.

  • DM-8040 [Documents Upversion] Error displayed when trying to create a new draft version of a document when a certain timestamp (with microseconds) is present on “last_no_action_needed_review_completed_at` database column - A data issue affected documents where the last_no_action_needed_review_completed_at timestamp had incorrect microseconds, potentially impacting downstream processes. The fix ensures that timestamps are now stored with the correct precision, preventing future inconsistencies.

  • TRAIN-1986 [Training Tests] Removing a Group/Role from test assignments via “Group Actions → Remove Selected Users” might also unintentionally remove it from other tests - When removing a Group/Role from test assignments using Group Actions → Remove Selected Users, the Group/Role was also being removed from other tests where it was assigned. This has been corrected so that the removal now only affects the specific test you are editing. Other tests that use the same Group/Role will keep their assignments unchanged.

  • CCM-1943 [Custom Fields] When trying to select a user or role in a custom field of type User/Role Selection, typing a name in the search box does not filter the list as expected - Searching for users or roles in selection lists wasn’t working as expected, sometimes showing too many or too few results. This has been fixed, so you’ll now see the right results when searching, making user selection faster and easier.

  • DM-7925 [Documents PDFs] Exported PDF does not correctly include or exclude components from "Select Components to Export" slider - When exporting documents to PDF, some options you tried to exclude were still being included, which was confusing. Now, your export will always match your selections, so you get exactly the information you want in your PDF.

  • DM-7935 [Documents Upversion] Cannot perform upversion if a document was migrated and only had a minor version (no major version) - For documents imported into the system, the “Immediate Retraining Required” setting was sometimes inconsistent, leading to uncertainty about training needs. This is now fixed, so training requirements are always clear and consistent for all imported documents.

  • DM-7953 [Documents Training] Due Date not set correctly for users assigned to train on documents created through Batch Upload, with Effective Date based on a number of days from Approval - Due Date should be set taking into consideration Grace Period (setup on the category level) and Effective Date (in this context, calculated based on the document approval date + value from Days From Approval field).

  • DM-7987 [View/Edit Documents] Documents custom fields fail to update when editing documents immediately after being created, resulting in just 1 field being updated although multiple are edited - this was mainly a concurrency problem that is now solved by saving all data in one singular transaction rather than individual transactions for each field.

  • DM-7992 [Documents Reviews and Suggested Edits] General user is not able to see the eye icon to open and see the retirement comments when he is added as part of the retirement workflow - the fix ensures that workflow users have access to comments/reviews performed by other users in the same workflow.

  • DM-7995 [Documents permissions] Authors only permission of documents should not allow changing the document category to a new one for Approved/Effective documents - the fix ensures that Document Authors are not able to move documents to a different category unless they have additional permission “Can Edit Document Details, Category Defaults, Custom Fields, and Links/Attachments” or they are SuperUsers.

  • DM-8001 [View/Edit Documents] Updating documents custom fields too quickly won't always update the values shown in the full table - this was a concurrency problem that is now solved by saving all data in one singular transaction rather than individual transactions for each field.

  • DM-8006 [Doc Review] When creating a new major version and selecting “Keep review date” during a minor upversion, the next review date for the major version was incorrectly calculated using the previous version’s date instead of the new version’s effective date - the fix ensures the next review date for major versions is based on the current version’s effective date plus the document-level review interval, not on any previous version.

  • DM-8044 [Document Periodic Review] Users can cancel completed Periodic Reviews when having same flow open in multiple browser windows - the fix ensures that already completed reviews cannot be deleted.

  • TM-340 [Task Due Date] System incorrectly blocks setting a task’s due date to today - The function validating the time did not standardize the value from the date picker, causing issues across time zones and preventing selecting today's date as the due date.

  • TRAIN-1928 [Email notifications] Clicking on training links inside the app OR from email notifications should always open the correct training tab and validate user access, so they can easily complete assigned training without errors - Previously, users were redirected to the Main Dashboard instead of the Take Training tab, which allows them to complete training without extra steps.

  • ZENQ-7589 [New Main Dashboard][Signatures Needed] “Super Editor Access” type not displayed in “Signatures Needed” table until another workflow (e.g., Delete) is launched - applies to Issues, Change Controls, and Tasks - the fix ensures that all types of workflows are correctly captured on New Main Dashboard, Signatures Needed section.

  • ZENQ-7591 [New Main Dashboard][Signatures Needed] “Change Control - Delete” and “Task - Delete” subtypes not displayed in “Signatures Needed” table - shown only as “Change Control” or “Task” - the fix ensures that all types of workflows are correctly captured on New Main Dashboard, Signatures Needed section.

  • ZENQ-7698 [New Main Dashboard] Signatures Needed table does not update automatically after completing an action on an item - the fix ensures that data displayed on charts and tables is always up to date.

  • ZENQ-7711 [New Main Dashboard] Signatures Needed section on New Main Dashboard does not refetch after switching tabs inside the application, resulting in possible outdated information being displayed on dashboard - the fix ensures that data displayed on charts and tables is always up to date.

  • ZENQ-7712 [New Main Dashboard] Signatures Needed table unable to filter, search and resize columns - functionality that allows searching, filtering and resizing columns was added to Signatures Needed table

  • ZENQ-7714 [New Main Dashboard] Signatures Needed action columns do not update when switching from My Direct Reports to My Dashboard - the fix ensures that data displayed on charts and tables is always up to date.

  • ZENQ-7570 [New Main Dashboard] Company Dashboard cannot be accessed by users who have the permission “Can See Training Records for Whole Company" but are not a superuser - the fix ensures that Company Dashboard is accessible to users with right permissions.

  • ZENQ-7715 [New Main Dashboard] System is filtering the sub-type when it should be filtering the type for the active workflow column - the fix ensures that Active Workflow column always displays the same information that is visible on Document View/Edit page regarding the current workflow that is in progress.

  • ZENQ-7718 [New Main Dashboard] Tasks incorrectly visible to stage assignee instead of only task assignee - the fix ensures that Tasks barchart from Main Dashboard → My Dashboard view displays only the tasks where current user is set as Task Assignee.

  • ZENQ-7677 [New Main Dashboard] Item types values are not localized on the new main dashboard - training drill down table - the fix ensures that all strings and labels are localized and available in the preferred language selected by the end user.

  • ZENQ-7769 [New Main Dashboard] Completed Training Records are not included in the exported file of the training drill down table, if "Show Completed Training Records" link has been clicked on before export - the fix ensures that Excel/CSV exports now reliably contain all completed training records visible in the drill-down table

  • DM-8070 PDF Viewer displays incorrect document when navigating between Main Document and Draft Review due to cached state - When switching between the Main Document (Awaiting Approval) view and the Annotation Draft Review, the PDF viewer sometimes reused a previously loaded PDF, showing the draft in the main view or the main document in the draft view until the page was refreshed. The fix ensures that the viewer now refreshes correctly, clears any cached state on view changes, and always loads the appropriate PDF version for each context.

 

Upcoming Features (Pre-release Support) 

This release includes updates to support new features planned for future releases. These changes do not affect current application functionality. All updates are fully validated to ensure there is no unintended impact on your experience.

  • INT-32 Pre-release support for adding Prismatic embedded marketplace - 30.3.0 Release - This change provides pre-release support for the Prismatic embedded marketplace by pushing related code behind feature flags in the current release. The update ensures that, with the feature flag off, existing functionality remains unaffected. This groundwork allows for safe future rollout and testing of the integrations marketplace without impacting current users, with further development and validation to be handled in subsequent releases.

  • TRAIN-1975 Pre-release support for enhancements on Training Certificates - 30.3.0 Release - This change provides pre-release support for upcoming enhancements to Training Certificates by pushing all related improvements behind feature flags in the 30.3.0 release. With the feature flag disabled, current training certificate functionality is unaffected, ensuring stability for users. This approach enables safe future rollout and testing of certificate enhancements - including improvements for documents, tests, OJT, and events - while keeping the new features hidden until they are fully validated in subsequent releases.

  • WF-59 Pre-release support for Custom Modules - 30.3.0 Release - This update introduces pre-release support for Custom Modules by placing all related code behind a feature flag in the 30.3.0 release. With the feature flag turned off, existing system functionality remain unchanged, ensuring a safe and non-disruptive deployment. This foundational work sets the stage for future rollout and testing of Custom Modules, allowing for further development and validation in upcoming releases without impacting current users.

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

 

Schedule

Due to the impact on users of this release and the time it will take to perform this update, we will apply the updates to sandbox and production separately. Both will occur outside top hours, to provide as little interruption to normal operations as possible.

 

Sandbox

Date: 10-FEB-2026

Time:  8 am EST / 1 pm UTC

Downtime: No downtime

 

Production

Date: 11-FEB-2026

Time: 11-FEB-2026 8pm EST / 1 am UTC (12-FEB)

Downtime: No downtime

 

Impact

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

 

The New Main Dashboard is supported for general availability starting with the 30.3.0 release. To help minimize impact and allow clients to transition at their own pace, the legacy main dashboard will continue to be offered for a limited period going forward. During this period, clients will continue being able to choose their preferred rollout approach, across two options.

 

Option 1: Enable the new main dashboard for all users with toggle access (allowing users to switch between old and new dashboards)

 

Option 2: Enable the new main dashboard for all users (No ability to switch to old dashboard)

 

PLEASE REACH OUT TO THE HELPDESK IF YOU WANT EITHER OPTION 1 or 2 implemented in your Sandbox or Production account prior to 31.0. By default, all account super admins will have access to toggle between the old and new dashboard.

 

The transition period that includes the legacy dashboard will end with our next major release, at which point the legacy dashboard will no longer be available and all users will only be able to use the new main dashboard. A follow up communication will be provided as well with six weeks' notice prior to the next major release.

 

Embedding SCORM training items into the Documents Module is released in 30.3.0 with a phased rollout approach to ensure a smooth transition. Existing clients currently using SCORM training will continue using the current SCORM interface without any disruption. New clients, as well as existing clients creating SCORM items for the first time after the 30.3.0 release, will automatically benefit from the enhanced SCORM as Documents functionality, which provides richer metadata, improved configurability, and streamlined lifecycle management. This phased approach allows us to gather feedback and refine the migration strategy before transitioning existing SCORM users to the new experience.

 

Documentation

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

"AI 1.0","API 1.1","CCM 6.5","DM 4.0","IM 7.12","INT 0.1","MIG 4.13","REP 4.6","TM 6.6","TRAIN 4.0","WF 0.1","ZENQ 28.1","ZenSign 2.6"

 

Updated Modules

  • Account Backup

  • AI Features

  • Audit Trail

  • Audits

  • Change Control

  • Documents

  • Import/Export Data service

  • Integrations

  • Issues

  • Notifications emails

  • Public API

  • Reports

  • Settings

  • Tasks

  • Training

  • ZenSign

Unchanged Modules

  • Administration

  • Insights

  • Login/Authorization

  • PDF generation service

  • Daily Summary emails

 

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 test2.zenqms.com and try out the changes from 30.3.0 release ahead of 11-FEB-2026. This environment was refreshed on 19-JAN-2026 with your latest production data and will be available for you to login starting 28-JAN-2026.

  • To minimize disruption, we scheduled the 30.3.0 release deployment to sandbox and production separately. Both will occur outside top hours, to provide as little interruption to normal operations as possible. We expect zero downtime. This release introduces primarily new features and improvements that should not significantly impact your daily operations. You can immediately access the new functionality for testing at test2.zenqms.com. We encourage prioritizing testing the following features as they may have the most direct impact on your current workflows: New Main Dashboard experience, the changes introduced in Documents Archive Table that support distinction between obsoleted vs superseded documents and the new option in the Account Settings to enable/disable AI features at the account level. Other enhancements can be explored at your convenience.

  • 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