This release focuses on bug fixes and improving usability for Provider Users.
Provider Users
Issue Fixed: Field Service Managers Portal Users Experiencing Error Messages
Previously, some Field Representative e-Dashboard (FReD) Portal users received error messages when performing asset searches with Serial Number or Unit Number if the matching asset had more than one open, active case.
This issue has been resolved, and all FReD Portal users can now search for assets by Serial Number or Unit Number as expected, giving them access to critical asset information for any case they might be working on.
Purchase Order Number Added to Search Page Options
With this release, we made it easier for Service Providers and Fleet Users to find cases they care about by adding the ability to search using a Purchase Order Number.
Currently, users can only search for cases by Case ID, Repair Order Number, and Tag Number. With the new PO Number search option, users will be able to quickly find cases by matching the Purchase Order Number field from a case in their search results.
See also: Use the Search Page.
New User Permission Options Added for External Interface Logs
With this release, we added new permission options for External Interface Logs on the Case platform. This update gives Dealer Admins more control over who has access to potentially-sensitive information in the API logs on the External Interface Logs page.
Once this update goes live, user permissions allowing access to External Interface Logs will be enabled for all existing users, and they will continue to have access to the logs just as before. You do not need to do anything if you’d like your users to retain the access they’ve previously had. However, if you’d like to modify settings, Dealer Admins can navigate to the Permissions tab from the Edit User page to change permissions as needed.
All new users added to the platform after this release will be denied access to the External Interface Logs by default. You will need to manually enable the permission for those users to access a detailed view of an API log.
NOTE: Logs are made available to users for 60 days, after which they will no longer be accessible.
Comments
0 comments
Please sign in to leave a comment.