Mobile App 1.57

July 2, 2024

⭐️ Media Library Search: We’re excited to introduce a powerful new search functionality within Media Libraries This feature allows users to quickly and efficiently locate specific media items by title. Whether searching for photos, videos, or documents, drivers can simply enter relevant terms into the search bar to find what they’re looking for without scrolling through extensive lists.

⭐️ Show/Hide Form Editor: Form messages are critical to your business, particularly when drivers are performing actions on loads, stops and custom screens, but sometimes the form contains no fields for the driver to complete. In these cases, you now have the option to hide the form editor and enable your driver to send a message without ever seeing the form. 

When the form editor is hidden, drivers tap the action button and instead of seeing a form, they see a confirmation message letting them know their message has been sent. There are no changes to how messages are received by your backend. The show_form_editor flag is enabled by default, but you can disable it when creating transaction-editor actions, whether via the API or in App Manager. 

If you hide the form editor but your form fails to pass client-side or server-side validation, the form will be displayed to the driver, despite the show_form_editor setting, to give the driver an opportunity to correct invalid fields.

⭐️ User Refresh API: There are situations where you may need to update a driver’s app experience immediately, without relying on driver interaction to trigger a refresh. This is especially important for compliance and safety cases: for example, you may want to remove access to features if a driver’s logs are not verified or display an updated dashboard to inform a driver when they enter a no travel zone due to adverse weather.

The User Refresh API allows you to make those updates to the driver’s app experience in real time by sending an API request to Eleos. These updates ensure that critical information is immediately visible to drivers. The updates are delivered via push notifications and therefore requires drivers to have that mobile app permission enabled to receive the updates.

You can read more about how to leverage the new API in the documentation.

⭐️ Deep Link to Load: You can now link mobile app users directly to loads using the fleetmobile.app domain with this URL structure: https://fleetmobile.app/[division_code]/loads/[order_number]

Linking to a load that isn’t present in the user’s load list will prompt a Loads sync. If the linked load isn’t present in the response, a message will be displayed to the user indicating the load could not be found.

Users who do not have your mobile app installed will be instructed that they need to have your app installed to view the linked load.

Learn more about linking directly to loads

iOS

🐞 Fixed a bug on iPad where menus with a single item were not tappable. 

🐞 Fixed a bug where an authentication verify request was not sent off when navigating back to the dashboard. This behavior now matches the Android implementation.

Android

🔧 HOS Clocks Separated by User: When the app displays hours of service for multiple drivers, each driver’s clocks are now separated by a horizontal line, so that they are more easily viewed by drivers. This feature is only supported for HOS data shared via OpenCab.

🐞 Prefilling LOAD-NUMBER Field: Fixed a parity issue with the LOAD-NUMBER form field on document scan metadata forms to allow it to be prefilled with custom values. Previously, it was limited to load.order_number.

✅ As usual, this version of the Platform mobile app is designed to be backwards-compatible with your existing web services and doesn’t require server changes prior to being deployed. If a future version introduces a backwards-incompatible change, we’ll note that in this portion of the release notes.

Server and App Editor

The following items are server-side changes and are available without a mobile app update.

⭐️ Disable Telematics Login: Some telematics providers only support drivers accessing their telematics mobile applications from one device. To meet this requirement, we’ve introduced the enable_telematics_login flag to control your drivers’ ability to login to their telematics provider’s mobile application via their Eleos-powered mobile app. 

You can leverage the new flag along with the existing Eleos-Mobile-Managed-Device-Id to prevent drivers from accessing their telematics from non-company-managed devices. The flag defaults to true so that drivers continue to have access to their telematics applications without any changes to your web services. When the flag is set to false, drivers will continue to have visibility to their HOS data, the HOS card will not sign them into their telematics application on personal devices when tapped. 

You can learn more about the details of the flag in the User Authentication section of the documentation.

🔧 App Manager Rename: Internally and externally, people referred to our web interface by many different names. We’ve standardized the name of our web interface to “App Manager” to reduce confusion and ensure consistency in our communication. You’ll start seeing the name App Manager within the interface for the drop down selector between App Manager and Document Hub, as well as communications with Eleos Support and Product emails. 

⭐️ Copy Forms and Actions: You can now copy Form and Action components from one environment to another with the App Manager. This is particularly useful for editing and testing components in a staging environment and then copying them to a production environment. By not having to  manually replicate changes, you can be assured that components are copied accurately, reducing errors and saving time.

There are cases where copying an action or form can have downstream effects, so we’ve called those out with various warning messages. If a component with the same code already exists in the target environment, a warning message will inform you that the existing component will be overwritten. If the component does not exist in the target environment, no warning is shown. Additionally, if the action or form references a component that isn’t present in the selected environment, you will receive a warning about the missing references. 

⭐️ Component Linking for Forms: You can now easily see which Actions, Custom Screens and Menus reference the form you are editing. This ensures you are informed about the potential downstream impact the changes to a form will have on other components that use the form you are editing. This helps maintain a clear understanding of component dependencies, reducing the risk of unintended changes affecting your application.

⭐️ Hide Disabled App Manager Users: We’ve added the ability to toggle between showing and hiding disabled users within App Manager’s Users management screen. 

By default, disabled users are hidden. At the top of the page, you’ll find a new toggle titled “Disabled Users.” This toggle allows you to control the visibility of disabled users separately in the Hub Users and Division Administrators sections. When the toggle is set to “Show,” disabled users will be displayed. When set to “Hide,” they will be hidden from view.

This enhancement simplifies user management by allowing you to focus on active users while still providing easy access to disabled user information when needed.

⭐️ Trip Planner Studio: Driver’s Location at Time of Reroute: It’s helpful to know when drivers are rerouted, whether it’s due to traffic congestion or because they took a wrong turn, but until now Trip Planner Studio wasn’t able to show you where a driver was at the time of the reroute. To assist in troubleshooting, App Manager users can now see the driver’s location, denoted by an orange  dot, on all navigation-related historical snapshots.

🔧 On February 28, added x-forwarded-for header to Authentication request that includes the source IP address of the original requester.

🔧 On June 5, we updated the Error API to return additional information around schema_errors in the new schema property. A type of other was also added for different types of schema errors that occur.

🐞 Fixed a bug where duplicate restrictions warnings were displayed while in navigation.

🐞 Fixed a bug where the HOS card in the mobile app would incorrectly display the “No HOS service information is available” error message when we were unable to connect to Geotab for a driver’s HOS data. 

🐞 Fixed a bug where missing trailer counts in Build a New Route would cause the page to crash and display a white screen.

Sign up for release note updates

Headquarters
2002 W Wahalla Lane
Phoenix, AZ 85027

QA & Support
142 Thomas Green Blvd
Suite 200
Clemson, SC 29631

×
×

Cart

Client Summit 2026 registration now open!