July 2015

New Version 1.2.0100 (446) for Android VMA

Hi all, Happy Wednesday! We hope you and the drivers are having success using the mobile app. NOTE: New version 1.2.0100 (446) released for ANDROID ONLY This new version is being released on Android first, the iOS version will follow in about a week. This new version has undergone extensive testing prior to release, so the drivers should have a better experience with this update than the last. What’s new in this version: Fix to problems caused by multiple delivery locations with identical names Fix index out of bounds errors Exceptions are now generated again for delivering to different location Prompt driver when adding a load to a run not yet completed Test Scanner function for identifying scan problems Reporting of iPhone model numbers Add driver expenses View unpaid expenses What drivers should do: A new version 1.2.0100 (446) of the mobile app is now available for download on Android phones Drivers with Android phones can download the update in the Google Play store, use button below Drivers with iPhones will continue using 1.2.0000 (421) until the new version comes out for iPhone next week [button link=”https://play.google.com/store/apps/details?id=m.transport.Android&hl=en” color=”silver” newwindow=”yes”] Android Download[/button]   We hope this briefing is useful to you. If there are any topics you’d like us to cover, or if we can improve the manuals, please let us know. Walt Venable Senior Application Engineer

New Version 1.2.0100 (446) for Android VMA Read More »

Potential Problem with 8-Digit VINs

How to Identify the error Loads that have already been delivered keep showing up in the Select Loads screen of the mobile app when you Refresh from Dispatch. What it means One of the loads that you delivered in the past is not recorded as fully delivered in the system. It may be that an exception came in and was not dealt with, so that even though the driver delivered the load one of the vehicles is still not delivered. When this happens, new loads that the driver picks up are added to the last run, and the vehicles from the last run(s) will continue to show up in the phone. What to do about it Get one or more of the load numbers that keep showing up in the driver’s phone. In the desktop app, go to Payroll/Run Details, do a Find on that Load number. Open the Run, if this is the correct problem then you will see vehicles from several loads in the “Vehicles Delivered” list. Now you have to examine the loads to see which one (or more than one) is still in the EnRoute state. Click “Modify” on the Run window, click on a line for a vehicle from one of the loads and click the “View Load” button. In the Load Details window, check the load status in the upper-right corner. If it’s EnRoute, this load must be Delivered before the Run can be Closed. Deliver the vehicles in the load that are not yet delivered (or if it’s actually enroute, wait for the driver to deliver it). This should automatically close the Run, but if it does not then click Modify on the Run Detail window again and change the Run Status to Closed. Now the driver can go into their phone, do Refresh from Dispatch, and see no vehicles assigned to them.

Potential Problem with 8-Digit VINs Read More »

Barcodes are Scanned but not Recognized

How to Identify the error Driver scans a barcode from the car’s door column and it is not recognized. What it means This may be due to the bar code having extra characters, the most common example being a vertical bar character “|” appended to the front of the barcode, like this: What to do about it Current versions of the app will try to ignore these extra characters, but if it makes a mistake the driver can work around it by selecting the VIN from the list (or enter the last 8 digits manually) instead of scanning.   The app should be catching all odd characters now, so if drivers have a problem of this type please obtain a photocopy of the barcode they were scanning so we can analyze it and improve the app.  

Barcodes are Scanned but not Recognized Read More »

Understanding Load Numbers

Loads are identified in the desktop and mobile apps by their Load Number. The load numbers are 8-digit numbers like “15040555”, which breaks down like this: 15040555 15: the last two digits of the year, so this load was created in 2015 04: the 2-digit month number, so this load was created in April 0555: load number this month, starting with 1, so this is the 555th load created in April 2015

Understanding Load Numbers Read More »