CMO R22 Release Notes

Last updated
Save as PDF

This document details the resolved issues that are included in the CMO R22 Web Maintenance and Mobile Maintenance Projects.

Welcome to the CMO Compliance R22 Release Notes.

This document details the client-reported issues that are included in the CMO Web Application R22 maintenance release. The following Release Notes cover resolved issues in the Web Application, as well as the mobile Andriod, iOS, and Windows apps that affect versions Update 25 and Version 16.0. The individual tickets will detail the applicable versions.

Visit the Client Success Portal at success.mitratech.com/CMO to view supplemental CMO Help Articles.

Resolved Issues

This section describes the issues that are resolved in the CMO Compliance R22 maintenance release. Each resolved issue is documented in the format:

A description of the issue
Internal tracking code
Salesforce case number, if applicable
Affected Version

Web Application

Issue: Projects (entities) are not showing up in a particular users's Monitoring tab even though the projects were assigned to him.
Tracking code: CW-14359
Support Case: 2018-0911-476096
Affects Version(s): 15.02.25, 16.0, R22

Issue: Client received error while running the Migration Launcher to migrate from R19 to R20.
Tracking code: CW-14807
Support Case: 2018-1217-496191
Affects Version(s): 15.02.25, R22

Issue: The incorrect pop-up was appearing when clients imported Actions using the Action Excel Import.
Tracking code: CW-12798
Support Case: 2018-1009-482069
Affects Version(s): 15.02.25, R22

Issue: The incorrect Org Unit logo appeared on the Event (Detailed) Report.
Tracking code: CW-14827
Support Case: 2018-1212-495434
Affects Version(s): 15.02.25

Mobile iOS Application

Issue: Potential Severity response and risk level is not displayed on the web application, and is triggering the incorrect workflow on the iOS application.
Tracking code: CMM-15510
Support Case: 2018-1206-494082
Affects Version(s)Issue: 16.0

Issue: User cannot progress through the form after assigning a risk score because the correct workflow is not triggered.
Tracking code: CMM-15548, CMM-14804
Support Case: 2018-1206-494082
Affects Version(s)Issue: 16.0