Release Notes for CloudHawk iOS v8.05.841/UI v4.10.003
Application Replacement Procedure to Version 8.05.041
ALL previous Android versions MUST be deleted, and the new 8.05.841 version must be downloaded to ensure proper compatibility and installation. Carriers should ensure all driver data has been synced, and all log certification procedures have occurred prior to deletion/upgrade. We recommend that drivers completely log out of the application before performing the deletion/reinstallation.
Important Update: (More actions related to incorrect violation notifications for drivers)
The development team has made enhancements to the expected behavior between the mobile application’s interaction with the database. Recently, we have seen a reduction in the number of false violation notifications after this change was implemented. As we continue to address outstanding issues related to false violation notifications, it is essential that we immediately receive any reports from drivers/carriers. If drivers experience false violation notifications after installing Version 8.05.841, please let your customer support representative know via the ticket submission platform. From this point forward, any previously submitted tickets related to false violation notifications can be considered outdated. To expedite and facilitate new concerns, our team will only investigate issues related to the newest Version 8.05.841. While this may not have addressed all incorrect violation notification issues, this is a next step in fully solving this
issue.
|
Item |
Platform |
Description |
|
1 |
iOS |
Fixed errors that could occur with the “7-day email schedule if not inspected within 7 days” functionality. |
|
2 |
iOS |
Fixed an issue with the Next Break violations not functioning properly. |
|
3 |
iOS |
Unidentified Driving records no longer remain active after assuming portal-assigned records. |
|
4 |
iOS |
Fixed errors that could occur when clearing a Positioning Malfunction. |
|
5 |
iOS |
A Power Malfunction alert/notification will no longer remain uncleared after 24 hours. |
|
6 |
iOS |
Fixed an issue where an Engine Synchronization Malfunction would not trigger properly. |
|
7 |
iOS |
Fixed an issue where, when exporting the PRINT-DISPLAY LOGS (Canada), an error would appear indicating that the field value entered did not meet the expected length requirements even when it did. |
|
8 |
iOS |
Fixed an issue where the application could close unexpectedly when a driver performed any of these actions:
|
|
9 |
iOS |
Fixed an issue where 30-minute Break violations were occurring intermittently across the application. |
|
10 |
UI |
Fixed an issue where FMCSA Data would display the same date and start time for multiple records on multiple dates. |
|
11 |
UI |
Fixed an issue where an incorrect record count could show when displaying FMCSA documents. |
|
12 |
UI |
Fixed an issue where FMCSA documents would not show the mandatory Driver ID field. |
|
13 |
UI |
The Violations Reporting now displays records from the last 7 days as a default. |
|
14 |
UI |
New filters and columns have been added to the Violations Reporting module. |
|
15 |
UI |
You can now upload documents related to a violation using the new upload icon in the Actions field of the Violations screen. |
|
16 |
UI |
The list of recent uploads on the Uploads menu for logs now includes the date and time when the log was uploaded. The list is also sorted by date/time now, most recent first. |
|
17 |
UI |
Added a new status function to the Violations Reporting module. |
|
18 |
UI |
The FMCSA Documents module is now restricted to be visible only to the administrator. |
|
19 |
UI |
Added a hyperlink to jump to the driver’s logs from a violation in the Violations Reporting. |
|
20 |
UI |
Fixed an issue where errors and upload status messages were not being shown correctly when uploading large files in the Violations Reporting module. |
|
21 |
UI |
You can now mark violations as Reviewed. |
|
22 |
UI |
Fixed an issue where MOA users would get a 500 error when clicking on the Notification module in the left navigation bar. |
|
23 |
UI |
A new FMCSA Documents module has been added so you can
|
|
24 |
UI |
IFTA reporting has been renamed to State Mileage. |
|
25 |
iOS |
Fixed an issue where Canadian drivers could not edit 8-14 day-old Logs. |
|
26 |
iOS |
Fixed an issue where some vehicle miles were missing from the Logbook. |
|
27 |
iOS |
Fixed an issue where the selected location was not appearing in Logbook modules. |
|
28 |
iOS |
Fixed an issue where Vehicle Profile information was missing after returning to the Vehicle Profile module. |
|
29 |
iOS |
Fixed an issue where drivers could not log out of the application if there were more than 50 pending transfers to be certified. |
|
30 |
iOS |
Fixed an issue where users were unable to add Logs manually. |
|
31 |
iOS |
Fixed an issue where the application would not change to ON and DRIVING automatically. |
|
32 |
iOS |
Fixed an issue where the Ontario ruleset was not reflecting the proper accumulated driving times in a cycle. |
|
33 |
iOS |
Fixed a stray ECM Disconnect popup that would appear during logout. |
|
34 |
iOS |
If the ECM is connected during login, the application now moves to the Home page. |
|
35 |
iOS |
The application no longer crashes when tapping “Upload Debug Info”. |
|
36 |
iOS |
Fixed an issue where the application would crash if 16 mph was used as the speed that changed the driver’s status to Driving. |
|
37 |
iOS |
Fixed an issue where users were sometimes unable to log in to the application. |
|
38 |
iOS |
The application no longer crashes when upgrading from an older version. |