⭐️ Trip Policies: Trip Policies are a new tool to help balance operating costs with driver flexibility. They can help empower your drivers to make good business decisions without leaving your organization in the dark about their choices, and they can help protect profitability when unexpected turns happen out on the road.
With this mobile app release, we’ve created the first two policies for this framework: Max Miles and Max Tolls. As part of each load or trip returned by your web services, you can enable one or both policies. When the driver goes to plan that trip, it’s checked against the active policies for that load and the results are displayed to the driver before the wheels start rolling.
The route used for policy evaluation includes both edits made by the driver—such as planned rest stops—as well as estimated mileage driven as part of previous stops, including out-of-route deviations that occurred while driving. If the planned trip exceeds the set thresholds at any point, the driver will see an indicator and an explanation of the violated policies.
The results of Trip Policies can also be viewed in Trip Planner Studio. This gives your dispatchers and back office personnel visibility into the choices the driver made while planning their trip.
If a driver knows the violation doesn’t pose a risk to the load, they can choose to mute that particular violation with a reason. This makes sure that additional violations that occur as the load progresses aren’t ignored or lost. When a driver mutes a policy, a Trip Planner Studio trip snapshot is created, and a web service request is made to your systems for optional processing or alerting. Historical trip snapshots are also available via Trip Planner Studio and the Trip Planner API.
🔧 Other changes
For detailed information about the new API available for enabling Trip Policies, see the What’s Changed section of our developer documentation.
✅ 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
The following items are server-side changes and are available without a mobile app update.
🐞 When fetching snapshots, Trip Planner API now returns routing options that were applied when the route was computed instead of the routing options that were set on the load or stop level by the client.
🐞 Fixed a bug where route requests sent to the Trip Planner API with `hazardous_types` set on the stop level may cause the routing request to fail.
🔧 Trip Planner API now creates a new snapshot of the load when any truck properties or routing options have been changed on the load by the customer web service.
🔧 Trip Planner Studio now indicates when a driver plans a trip with a different departure time or stop.
iOS
🐞 Fixed an issue where per-stop route options (including truck dimensions, weights, and restrictions set at the stop level rather than the load level) were applied to the leg after that stop rather than the leg before. However, the route options were honored as documented for the actual navigated guidance route.
🐞 Fixed an issue that could cause in-motion locking to treat duty status as unknown if the Geotab integration was in use but the driver had not yet tapped into the Geotab portion of the app
🐞 Fixed an issue where a lock screen would overlay load details when using navigation and arriving at a destination (iPad only)
🐞 Fixed an issue where spinners could remain when pulling down to refresh on load list or message list
🐞 Fixed an issue where Trip Planner would refresh/redraw unnecessarily, leading to a brief flash
🐞 Fixed an issue a stop would not show up as current in some workflow scenarios
Android
🐞 Fixed an issue where per-stop route options (including truck dimensions, weights, and restrictions set at the stop level rather than the load level) were applied to the leg after that stop rather than the leg before. However, the route options were honored as documented for the actual navigated guidance route.
🐞 Fixed layout bug for options list field in forms with multiple line labels
🐞 Fixed crash on dashboard that happens with the Galaxy Fold
🐞 Fixed a bug with date/time form field where editing time filed but not date does not save time changes
🐞 Fixed bug when workflows on the dashboard don’t update properly due to current load change
🐞 Fixed a crash that sometimes happens when you login very quickly after previously logging out
🐞 Fixed a bug with how unread messages are counted for threaded messages
🐞 Fixed a layout issue that happened on the Payroll screen for very long labels
🔧 Updated the Android target SDK as required by Google
