CMO R17 Release Notes

Last updated
Save as PDF

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

Welcome to the CMO Compliance R17 Release Notes.

This document details the client-reported issues that are included in the CMO Web Application R17 maintenance release. The following Release Notes cover resolved issues in the Web Application, as well as the mobile 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 R17 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: The Events Data Report pulled incorrect data into the report and inconsistently reported on correct information. For example, every other day the report was correct and the next consecutive day the report was incorrect.
Tracking code: CW-9555
Support Case: 2018-0131-429031
Affects Version(s): Update 25, 16.02.R2, 16.02.R17

Issue: User received error message and was unable to create an Incident Report, even though his Role had the ability to create an Incident Report.
Tracking code: CW-10160, CW-11318
Support Case: 2018-0319-439324, 2018-0319-439324
Affects Version(s): HF-6, 16.02.R17

Issue: The Edit Assignments pop up took over 90 seconds to load.
Tracking code: CW-11029
Support Case: 2018-0423-446491
Affects Version(s): Update 25, 16.02.R17

Issue: Parties Involved type of responses were sporadically cleared and removed from an Incident Management environment and were not found in the history/tracking.
Tracking code: CW-11094
Support Case: 2018-0614-458075
Affects Version(s): Update 25, 15.02.R17, 16.0, DataWarehouse, HF-6

Issue: Actions appeared in the wrong environment.
Tracking code: CW-11276
Support Case: 2018-0723-465899
Affects Version(s): Update 25, 15.02.R17

Issue: The calculation of password complexity was incorrectly calculated during user import.
Tracking code: CW-9349
Support Case: 2018-0316-438729
Affects Version(s): Update 25, 15.02.R17, 16.0

Issue: Errors occurred when running the Migration Launcher while performing upgrades from CMO R1 to CMO R16.
Tracking code: CW-11130
Support Case: 2018-0716-464282
Affects Version(s): Update 25, 15.02.R17

Mobile iOS Application

Issue: Error occured during sync from iOS to web.
Tracking code: CMM-11126
Support Case: 2018-0627-460709
Affects Version(s): Update 24, Update 25, 15.02.R17, 16.0, HF-6

Issue: The Executive Summary and Recommendations fields appeared as a comment type even though this response type was not enabled.
Tracking code: CMM-8217
Support Case: 2018-0125-427818
Affects Version(s): Update 24, Update 25, 15.02.R17, 16.0

Issue: When enabled, the Save Photos to Device setting causes the app to crash when a picture is taken and attached to an Event or Action.
Tracking code: CMM-11553
Support Case: 2018-0628-461188
Affects Version(s): Update 24, Update 25, 15.02.R17

Issue: Values other than the selected Date & Time appeared across several modules.
Tracking code: CMM-7071
Support Case: N/A
Affects Version(s): Update 25, 15.02.R17, 16.0

Mobile Windows Application

Issue: A pop up for a database backup appears upon logging into the application for initial sync.
Tracking code: CMM-12291
Support Case: N/A
Affects Version(s): Update 25, 15.02.R17, 16.0

Issue: User is prompted to take a backup (of the database) before running a sync, even when the Allow Backup and Restore on Mobile Business Rule is disabled.
Tracking code: CMM-12291
Support Case: N/A
Affects Version(s): Update 25, 15.02.R17, 16.0