2020.1P4 addresses a problem where a very limited number of files were not uploaded to our Amazon S3 bucket. This caused some files to appear like they existed as an attachment to an item but upon clicking were not downloaded.
This release is being managed through change control 301-7. Due to the possible impact on data integrity we are treating it as a ‘Critical’ patch per the Quality Technical Agreement. As a result we will be releasing this patch as soon as QA completes testing protocols. You can download a copy of the 2020.1P4 Requirements & Testing Traceability Matrix
We do not expect any downtime.
CCM-1520: Too many API calls on morpheus and ui when creating/deleting attachments
IM-799: Too many API calls on morpheus and ui when creating/deleting attachments
TM-157: Too many API calls on morpheus and ui when creating/deleting attachments
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 comprised 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 2020.1P4 contains the following “FixVersions”. We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.
CCM 2.4 - Change Control Module
IM 1.2 - Issues Module
TM 1.2 Tasks Module
ZENQ 19.3 - Flagship application and all other modules/components that are not Change Control, Issues, Tasks, Reports, or Settings
AUTH 2.1 - Authorization service
PDF 1.3 - PDF generation service
Reports 2.0 - Reports Module
This announcement plus the banner announcement in the application to ALL users is our formal announcement for the release.
Deployment (as always) is handled by the ZenQMS team-- so don’t worry!