This release focuses on issue fixes and improving usability for Provider Users.
- Provider Users
- New Response Modals for Operations
- Issue Fixed: Calendar Not Displaying Information when Language set to French
- Issue Fixed: VMRS Codes Not Persisting on the Edit Operation Page
- Unit Number Added to Service Request Page
- Unit Number Added to Assigned Inspections Page for Case Mobile
- Operation Variation Description Added to Case Mobile
- Added Complaint, Cause, and Correction for Mobile Operations Page
- Log Improvements for User and System Notes
New Response Modals for Operations
We improved the user experience for Fleet Users by adding new Operations response modals that will allow them to respond to an operation in a more user-friendly way. Now when a Fleet User responds to an operation that has been sent to them for approval, they will see three new modals and will be able to add comments, or reasons, why they made their choice before submitting their choice.
Any comments left by Fleet Users will be viewable to Service Providers in a new Approval Status table found on the Edit Operation page, just above the User & System Notes section. This will help inform them as to why an operation has been deferred.
With this release, users can expect to see the following modals when responding to an operation:
- “Approve Operation”
- “Defer Operation”
- “Decline Operation”
Issue Fixed: Calendar Not Displaying Information when Language set to French
Previously, some Service Providers experienced issues where their calendars failed to display information when their default language was set to French.
This issue has been resolved so that the information in the user’s calendar will display as expected.
Issue Fixed: VMRS Codes Not Persisting on the Edit Operation Page
Prior to this release, some Service Providers encountered issues on the Edit Operation page where the information entered for VMRS codes was failing to persist after they clicked the SAVE & PREVIOUS and SAVE & NEXT buttons.
This issue has been fixed, and the VMRS fields will save and persist after a user clicks these buttons, as expected.
Unit Number Added to Service Request Page
With this release, we made it easier for Fleet Users and Service Providers to know the Unit Number associated with a Service Request.
Once a service request is created, users will now see the Unit Number populate in the Asset Info section of the Service Request page.
See also: Create a Service Request
Unit Number Added to Assigned Inspections Page for Case Mobile
With this release, we made it easier for Service Providers to know the Unit Number of the asset they’ve been assigned to inspect or service when using Case Mobile.
Service Providers will now see the Unit Number of the asset they’re working on on the Assigned Inspections page for quick reference, giving them the confidence to know the asset they’re servicing is due for maintenance.
See also: Perform and Assign Inspections
Operation Variation Description Added to Case Mobile
We made it easier for Service Providers using Case Mobile to view Operation Variation Descriptions when adding an operation.
Users will now see a list of Variations, if applicable, under the Operation when on the Service Variant page. This way, they can easily select the appropriate variation needed.
Added Complaint, Cause, and Correction for Mobile Operations Page
Previously, when an operation had a Complaint, Cause or Correction captured either by Mobile or Web versions of Case, the information would not display on the Operation Mobile view.
With this release, we made it possible for Mobile Case users to know if the Complaint, Cause, and Correction has been completed so that they’ll see whether they need to add or edit the information. This will give users peace of mind knowing the information they’re working with is accurate.
Log Improvements for User and System Notes
With this release, users will see any historical changes done to the Cause and Correction fields on the User and System notes of an operation.
A new message will now appear on the User and System notes with the timestamp, user info, and a message saying: “Cause or Correction was changed from ‘xxxxx’ to ‘yyyyyy’" This way, users can track all the work that has been done to complete the operation.