CMO R26 Release Notes
Welcome to the CMO Compliance R26 Release Notes.
This document details the client-reported issues that are included in the CMO Web Application R26 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 26 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 R26 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: Resolved issues causing server errors while users would navigate the web application
Tracking code: CW-16417
Support Case: 2018-0903-474610
Affects Version(s): 15.02.25R8
Issue: User can generate a configuration summary report without triggering an internal server error.
Tracking code: CW-17067
Support Case: 2018-1029-486409
Affects Version(s): CMO 16.00
Issue: Resolved an issue preventing the deactivation of a user using the XML tag during an HR Import
Tracking code: CW-18250
Support Case: 2019-0328-517225
Affects Version(s): 16.01.99439
Issue: User can download "Incident Report" from event list page using "Print" button and report shows finding as closed.
Tracking code: CW-18085
Support Case: 2018-1206-494093
Affects Version(s): 16.00.99133.R19
Issue: Resolved a server migration issue when upgrading from a 1502 instance to v16 R24
Tracking code: CW-17601
Support Case: 2019-0308-512535
Affects Version(s): 15.02.25R17
Issue: Resolved issues causing multiple server errors preventing users from navigating the application.
Tracking code: CW-16417
Support Case: 2018-0903-474610
Affects Version(s): 15.02.25R8
Issue: User is now able to create an event and make it confidential for a particular user by using the API POST request.
Tracking code: CW-17835
Support Case: N/A
Affects Version(s): 16.01.99485
Issue: The “Unknown ID [U^XXXX]” tag was displayed instead of profile name for the ”Profiles” option on event dialog.
Tracking code: CW-17462
Support Case: N/A
Affects Version(s): 16.01.99449
Issue: Resolved an issue that prevented the OSHA 300A report from populating the field "Annual Average Number of Employees".
Tracking code: CW-16654
Support Case: 2019-0218-508264
Affects Version(s): 16.00 R22
Issue: Resolved an issue that would prevent a Template Export if an answer contains validation schema with the same question or section.
Tracking code: CW-16125
Support Case: N/A
Affects Version(s): 16.01.99482
Issue: Resolved issues causing slow load times when working with Incidents, Hazards, and other events.
Tracking code: CW-17579
Support Case: 2019-0219-508524
Affects Version(s): 15.02.98429
Issue: A blank event title can no longer be created while using the create event POST request.
Tracking code: CW-17649
Support Case: N/A
Affects Version(s): 16.01.99461
Issue: Resolved a bug that would cause Events to be deleted when creating new Events through the “Save & Copy” feature
Tracking code: CW-17694
Support Case: 2018-1122-491607
Affects Version(s): 15.02.25R24
Issue: “Edit” and “View” buttons are now properly displayed on the “Event Permissions” window
Tracking code: CW-17822
Support Case: N/A
Affects Version(s): 16.01.99485
Issue: The “Event due date” field no longer displays as “Event start date” as a validation in the response while creating an Event using API call POST request.
Tracking code: CW-17848
Support Case: N/A
Affects Version(s): 16.01.99482
Issue: The revision number on form templates will now be maintained when importing a form in a draft state.
Tracking code: CW-18144
Support Case: N/A
Affects Version(s): 16.01.99508
Issue: When a user generates a configuration summary report, all steps and form permissions related to each stage in each event workflow are now successfully rendered.
Tracking code: CW-17928
Support Case: N/A
Affects Version(s): 16.00.99560.R25
Issue: The DimOrgUnit table in “CMO PROD DW” - database accurately populates the _IsActive_ and _DIMParentOrgUnitID_ columns.
Tracking code: CW-18005
Support Case: 2019-0320-515465
Affects Version(s): 15.02.99554.R25, 16.00 R22
Issue: Resolved an issue where reports for actions for completed date were showing incorrectly.
Tracking code: CW-18071
Support Case: 2019-0319-514847
Affects Version(s): 15.02.25R5
Issue: Resolved an issue where duplicate entries would be displayed in the event, action, findings, and risk filters.
Tracking code: CW-18498
Support Case: N/A
Affects Version(s): 16.01.99534
Issue: User is now able to add item without any character to lookup table via POST API request.
Tracking code: CW-18649
Support Case: N/A
Affects Version(s): 16.01.99546
Issue: User now receives a validation message if duplicate values are sent to lookup table via API POST request.
Tracking code: CW-18662
Support Case: N/A
Affects Version(s): 16.01.99546
Issue: Resolved an issue where attachments weren’t attaching to emails configured within the Form Template when "Include Attachments from this Section" was checked.
Tracking code: CW-18785
Support Case: 2019-0409-519853
Affects Version(s): 16.01
Mobile iOS Application
Issue: Application will no longer be stuck on a loading screen if a user taps the “API Call Trigger” button while there is no VPN connection
Tracking code: CMM-17450
Support Case: N/A
Affects Version(s): 16.01.99526
Issue: Resolved issues preventing the application from populating “Drop Down” response fields configured with the “Previous Form” type.
Tracking code: CMM-17439
Support Case: N/A
Affects Version(s): 16.01.99526
Issue: Android users can navigate to the “H&S - Safety Interaction” form without triggering an application crash.
Tracking code: CMM-16698
Support Case: N/A
Affects Version(s): 16.00.99528.R25
Issue: Resolved an issue that prevented users from completing workflow driven events on the iOS application.
Tracking code: CMM-16674
Support Case: 2019-0306-511910
Affects Version(s): 16.00.99266.R22
Issue: The Screen will remain focused on the “API Call Trigger” button when the user clicks it, and no longer moves to the top of the form.
Tracking code: CMM-17849
Support Case: N/A
Affects Version(s): 16.01.99492
Issue: Application no longer becomes unresponsive and a list of users available for selection is displayed on clicking on the "Responsible" field on the 'New/Edit Action' window.
Tracking code: CMM-17609
Support Case: 2019-0404-518761
Affects Version(s): 16.00.99266.R22
Issue: Resolved issues that would trigger the error "Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference" upon adding category/type on the “New Event” screen
Tracking code: CMM-16883
Support Case: N/A
Affects Version(s): 16.01.99434
Issue: Windows application no longer crashes when a user clicks on the heatmap image displayed for 'Heatmap' response type.
Tracking code: CMM-14082
Support Case: 2019-0325-516147
Affects Version(s): 16.00 R22
Issue: Resolved an issue that prevented users from syncing their workflow dependent event from the web application to the mobile device.
Tracking code: CMM-15446
Support Case: N/A
Affects Version(s): 16.00.99245.R21
Issue: The "Likelihood" options for "Potential Severity" are now properly displayed on selecting "Consequence" when "Show Likelihood after Consequence has been selected" check box is disabled.
Tracking code: CMM-16062
Support Case: N/A
Affects Version(s): 16.00.R23
Issue: Users can no longer add duplicate entries in the party involved response type.
Tracking code: CMM-16769
Support Case: N/A
Affects Version(s): 16.00.99453.R24
Issue: The logged in user is no longer displayed twice in the List of users displayed on party involved response type of an event.
Tracking code: CMM-16790
Support Case: N/A
Affects Version(s): 16.00.99453.R24
Issue: Resolved issues triggering an application crash when a user tried to add a value to the “DropDown Editable” response type.
Tracking code: CMM-17056
Support Case: N/A
Affects Version(s): 16.01.99492
Issue: Resolved issues triggering an application crash when a user taps the “Form” response type.
Tracking code: CMM-17197
Support Case: N/A
Affects Version(s): 16.01.99501
Issue: Sync times for the Windows Application have been significantly reduced to improve the user experience
Tracking code: CMM-17307
Support Case: 2019-0326-516460
Affects Version(s): 16.00 R24
Issue: The user can no longer save an action without selecting any values for mandatory “Org Unit” or “Entity” fields.
Tracking code: CMM-10999
Support Case: 2019-0211-506590
Affects Version(s): 16.00 R22
Issue: The application should no longer crashes upon adding category/type on 'New Event' screen
Tracking code: CMM-16883
Support Case: N/A
Affects Version(s): 16.01.99434
Issue: “Drop Down” response fields configured with “Specific Form” type now properly fetch exact values selected for the previous event.
Tracking code: CMM-17494
Support Case: N/A
Affects Version(s): 16.01.99534
Issue: Resolved an issue where the Windows Application would become unresponsive upon selecting a Responsible user for an Action.
Tracking code: CMM-17609
Support Case: 2019-0404-518761
Affects Version(s): 16.00.99266.R22
Issue: The proper error message will now trigger on an API Call with leading response if Response fields are not configured/mapped.
Tracking code: CMM-17663
Support Case: N/A
Affects Version(s): 16.01.99526
Issue: Involvement Types specified in the Web Application are now accurately reflected on the Android Application.
Tracking code: CMM-17935
Support Case: 2019-0416-521233
Affects Version(s): 16.00.99545.R25