Search
Close this search box.

GPS Tracking Improvements

Driver Visibility Simplified

A lack of complete GPS data got you wondering if your shipments are hiding in the shadows or out saving the delivery day? 🧐 Visibility into driver tracking shouldn’t require Bruce Wayne’s R&D tech.

Β 

Introduced in version 24.3, along with improvements coming in CXT Driver 3.6.5, an enhanced level of GPS guidelines will allow operators to exercise greater control of driver workflows by requiring GPS usage in the Driver App. No need for sonar or hacking city traffic cams; with just a few clicks, you can improve GPS data collection to have a full view of their itinerary each day.

Β 

And here we go! Let’s check out the latest that’s coming in 24.3.

movie tracking driver tracking enhancements
CXT Software Operations App background GPS settings

How It Works

Whether on an iOS or Android device, there are multiple levels of access to location or GPS data that a driver can allow. To continually provide accurate GPS data, it is critical that the driver’s device has the proper options selected. While you can’t control how a driver uses their device, you CAN control how they interact with the Driver App if the appropriate settings are not in use.

Β 

Previous versions of the Operations App enabled you to simply select “GPS Required” in the Mobile Option Set. Drivers would be prompted to allow the Driver App the location access of their choosing, which resulted in many opting for “While Using the App,” leaving gaps in location data while the app was not actively in use or running in the background.

Β 

A new level of permission granularity is now available to “Require Background GPS.” This option makes it necessary for drivers to select “Always” (iOS) or “Allow all the Time” (Android) for location access in order to collect a continuous stream of GPS data.

Β 

What happens when the right option isn’t chosen on the device? Drivers will be able to access the app but their workflow within the Driver App will appear grayed out. They will be unable to interact with their itinerary to confirm new work, access or update shipments, or move through their workflow until the proper location access is granted. πŸ“΅

Β 

Need to assign different settings to a certain driver or a fleet? We’ve got you covered. With Mobile Option Sets, you can configure specific settings to various option profiles and then elect which profile a driver is subject to, or simply select the GPS option on the individual driver’s record.Β 

Why It Matters

Gaps in location data due to the lack of GPS collection while the Driver App is in the background can leave many unanswered questions. In a time when planning and optimizing are critical factors for improving operational efficiency, needing a comprehensive picture of driver movement throughout the day – or dark night – is necessary. Having the full understanding of driving patterns and routines can help you uncover impactful insights to:

Β 

  • Compute the most efficient routes
  • Understand delays and identify ways to improve on-time performance ⏱️
  • Maintain transparency between dispatchers and drivers
  • Offer accurate tracking and ETA information to consignors and consignees πŸ—ΊοΈ

Β 

With a simple change in device settings, this additional layer of location data can be the real hero in identifying itinerary enhancements and improving driver accountability. It’s the GPS data you and your clients deserve and need!

Let's Get Serious about GPS

The full functionality of “Require Background GPS” will be available with version 24.3 in conjunction with the latest CXT Driver 3.6.5. πŸ“±

Β 

To configure this setting in the Operations App, navigate to Maintenance > Mobile Option Sets > GPS Sync and enable “Require Background GPS.” If you need additional assistance, please reach out to our Support Team. Call us, email us, or submit a ticket on the Support Portal.Β 

24.3 Release Updates

What's New πŸ“°

  • Implemented an additional Mobile Option Setting under “GPS Required” called “Require Background GPS” that will allow carriers to enforce stricter GPS requirements for their drivers. Requires CXT Driver 3.6.5.
  • Implemented logic for clickable URL links, phone numbers, and email addresses to be added within the Client Portal Broadcast Messages, so they can be easily utilized by clients.
  • Created new Max Dim Weight enforcement options available on the Global Options>Dispatch tab and the Operations Vehicles record that allows customers to either ignore, warn, or enforce max dim weights when dispatching orders/stops that would exceed the associated vehicle’s weight.
  • Implemented a change to the basic route optimization, so completed stops would no longer be listed with a sequence of 0. Completed stops will now display in the order in which they were completed in and the subsequent optimized stops will appear in the proper sequence order from there.

What's Improved πŸ“ˆβ€‹

  • Performance improvements to the Shipments panel on the Visual Dispatch Board.
  • Added a Parcels tab to the Recurring Orders form, so static parcels can be utilized on posted orders.
  • Added two new columns to the on demand Visual Dispatch Board for Total Parcel Dim Weight and Total Parcel Weight, so users can more clearly see all weight breakdowns.
  • Added SMS text message alerts to the audit log for orders and stops, so customers can confirm when notifications are sent out to their clients.
  • Added User permissions to Maintenance>Users>Tools within the classic Operations App for Barcode and Import Configuration and Tracking Configuration, so the Client Portal Setting permissions are feature parity with the Operations application.
  • Adjusted logic to increase user-friendliness of HTML headers within Message Formats, so more customers can benefit from customized HTML status event emails for their clients.
  • Improved Client Portal Settings> Customization page performance to increase speeds.
  • Improved pop up messages within the Client Portal when the internet user’s “other allowed customers” are listed as Inactive or Blacklisted.
  • Adjusted enforcement within the Client Portal for internet users that have blacklisted and inactive customers enabled within their “Other Allowed Customers” list.
  • Reimplemented the pop up warning to Client Portal users when navigating away from the Place Order page to let them know that the order data will be cleared out if they leave without placing the order.
  • Added a pop up warning for users when attempting to open a PNG file in the classic Operations App’s Maintenance>Images to let them know they can only be opened in the modern Operations app.
  • Enforced logic within the Route Planning form to restrict special characters in the Route ID field, so users will not have an issue when editing the route.

What's Fixed πŸ› β€‹

  • Fixed issue from Google ending support for pin overlay display in X Tracking.
  • Fixed an issue with some 2D barcode scan configurations failing to populate data within the Client Portal order entry form.
  • Fixed issue with credit card transactions syncing with QuickBooks Online if the card was being authorized while invoices were actively syncing.
  • Fixed an issue with older stops not displaying correctly in the Driver App.
  • Fixed an issue where overridden distance values were not being properly utilized on subsequent orders when the order contained a manually entered address from within the Client Portal.
  • Fixed an issue with the formatted info display on the Standard 4×6 shipping label when generated within the Client Portal.
  • Fixed an issue with the Advanced Find permissions so they more clearly control a users ability to create, read, and edit queries.
  • Fixed issue with importing orders through the legacy API when there were missing parcel weight values.
  • Fixed an issue on the Visual Dispatch Board where users were receiving the “Split/Reassign” pop up after dispatching multiple orders using the Dispatch hotkey and only viewing Unassigned orders.
  • Fixed an issue within the Client Portal where users were not able to create parcels with a standard length of 0 when the required parcel type enforcement was enabled.
  • Fixed a rounding issue with on-demand orders when total charges included more than two decimal places.
  • Fixed an issue with recording the correct user when deleting deductions in the Human Resources audit log.
  • Fixed an issue with the Find Subscription’s next run time display.
  • Fixed issue with placing overnight orders in deprecated X Internet when the Order Type was limited to “Today No Rollover”.
  • Fixed an issue that could occasionally cause some dispatched orders to not display the dispatched timestamp when using some workflows.
  • Fixed issue within the Client Portal where internet users were able to place an order for an inactive or blacklisted customer if they were enabled on the internet user record’s “other allowed customers” list.
  • Fixed an issue with email addresses in the HR record not accepting a trailing underscore character.
  • Fixed an issue with uploading attachments in the Driver App if the job is completed prior to the attachment upload being finished.
  • Fixed Visual Dispatch Board right-click options to better show which options only apply to bulk actions (multi-row selections).
  • Fixed an issue where posted recurring orders that are pre-assigned to a driver were not receiving the Dispatched date/timestamp and therefore not displaying the caution icon when a driver did not confirm the job.

Works in Progress 🏭

  • Drivers utilizing Android 13+ OS devices receive an error when attempting to open non-picture/media files, such as PDF files or other file-based documents.
  • An unexpected error is received while adding items to an order in the classic Operations App.
    Workaround: To avoid this issue, select an item for every row selected on the Order’s Charges tab or select the row headers and completely remove the row created.
  • Subscription-based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field, as it is not supported.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign updated Lat/Lon values.
  • Internet User columns do not always sort as expected in the classic Operations App.
    Workaround: Click on any cell besides the header or the column that is selected, then click on the column again to sort in the other order.
  • An error occurs in the Operations App when a user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Operations Monitor – Help – View Manual results in a run-time error ’13’ type mismatch.

What's Coming πŸŽβ€‹

  • Routed capabilities in the revamped Visual Dispatch Board
  • Automate credit card processing for classic Operations App users
  • New Required Driver Input settings to enforce photo or file attachments at specific points of a driver’s on-demand or routed workflow

Ready to Get Started? πŸš€

Let's Meet! 🀝

Explore the power of our solutions for your logistics needs! Schedule a chat at your convenience, and let’s elevate your operations.

Ah snap! It looks like something is missing.
Please refresh the page and try again.

Refresh


If you are still seeing this message after refreshing, please contact us
at 602-265-0195 or [email protected].

Let's Chat! πŸ“ž

Let's Chat! πŸ“ž

Leave us your details and we'll be in touch soon.

Submission received!

Submission received!

Thank you for opting in.

Let's meet! Request a
guided demo.

Let's meet! Request a
guided demo.