We are pleased to announce the 26.2.0 minor release! Please reference this article for details on our new approach to version numbering.
With this release we have performed a major rework on the backend of how Issues, Change Controls, and Tasks are converted to PDF. You will see a series of Stories listed in the attached traceability matrix for these. These will replace existing stories and requirements for this feature, but there is very little visible change. There are some small UI improvements in the Header of the PDF and some performance improvements you might notice. Otherwise, you should expect Issues, Change Controls, and Tasks to largely function the same. The impact in the application is relatively small here, this is more of a documentation and validation impact.
We are also fixing bugs in the Training, Documents, Issues, and Tasks modules, as well as bug fixes in PDF generation and the Account Audit Trail.
Anyone using Issues, Change Controls, or Tasks converting to PDF are impacted.
There are bug fixes in the Training and Documents modules, see the traceability matrix for the full details to judge if you are impacted.
We are also making note of some "Pre-release" code changes we are making. You will see these noted as "Pre-release support for [feature name]" in the traceability matrix. This is code that is being deployed, but not accessible by any users, for upcoming features. We are adding to the traceability matrix to document the deployment and validation of this. We will perform validation that these features are not available to users and have not impacted any other areas of the application as a part of our OQPQ testing. Again, these are documented in the traceability matrix, but there is NO impact to any users at this time.
This release is being managed through change control 301-62. 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: 26.2.0 System Release Record 301-62 Release Notes. An entire release record will be available for review after the release is completed, in the auditor share account.
We expect up to 1 hour of downtime.
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 26.2.0 contains the following “FixVersions”. We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.
DM 1.1, IM 6.2, MIG 4.5, PDF 7.0, ZenSign 0.1, TM 5.5, TRAIN 2.3, ZENQ 25.3
- Change Control
- PDF generation service
- Daily Summary emails
- Import/Export Data service
- SSO configuration
- Our versioning format has changed, please visit this article for more details
- This announcement plus the banner announcement in the application to ALL users is our formal announcement for the release.
- We are deploying to sandbox.zenqms.com 1 day before app.zenqms.com. Sandbox deploy will occur Friday 08-DEC and production will occur Saturday 09-DEC.
- Deployment (as always) is handled by the ZenQMS team.