TruckMate 2025.3 New Features: Operations

An Export option has been added to the Report Selection window.

Previously, all reports defaulted to a PDF format. If this was not your preferred format, you would have to take extra steps to change the format.

Now, when you select a report to run, there is an Export dropdown menu:

Select this option to choose the default export format for the report:

The selected format is saved on a per-user basis.

Microsoft has announced that SMTP Basic Authentication will no longer be supported within Exchange and Office 365 as of April 30th, 2026. Because of this, TruckMate version 25.3 now supports both Basic Authentication and OAuth 2.0 Authentication.

You can continue to use Basic Authentication when you upgrade to TruckMate version 25.3. However, Trimble strongly recommends that you migrate over to using OAuth 2.0 if:

This will help avoid any interruptions to your emailing service. Support for OAuth 2.0 will not be back-merged to lower versions of TruckMate, so an upgrade to 25.3 or higher is needed to use these features.

On the Email Setup > Servers tab in Codes Maintenance, there are now two available options:

When you upgrade, all existing services will be configured as Simple Authentication. They will continue to use their current settings. However, if you want to upgrade to OAuth 2.0 Authentication, you can now create a new server.

You can now set up automatic retry settings for Migration Database Wizard.

There are some database migration errors that can be fixed by restarting the migration process. To enable the wizard to fix these issues automatically, you can set:

The default settings are:

You can now assign names to attachments that are sent out through Dawg processes.

Previously, files sent by The Dawg would either use the name of the report or the name of the Dawg itself. This could cause unclear labeling for batch files.

Now, you can choose the name used for file attachments. You can define file or report names for:

In Security Configuration, the User fields on the Security, Administration, and API TruckMate Credentials tabs have been changed from dropdown lists to searchable picklists. This makes it easier to find specific users if you have a lot of users in your system.

Several changes have been made to Mileage Server to improve its overall running state.

Records would sometimes get stuck in an LCK status, even though the job had already been completed. To resolve this issue and improve Mileage Server overall, these changes have been made:

The way Mileage Server handles requests that have a PENDING zone as the Start, From, End, or To zone has been changed.

Previously, the mileage service kept jobs with a PENDING zone in the queue. It would then try to process the record. This would result in an ERR status because the PENDING zone is not validated to a specific location.

Now, before a record is submitted to the MILESERVER_JOB table, the system scans the record to see if it has a PENDING zone. If it does, the mileage service will not create a job for the request.

This change will result in a major reduction of mileage jobs being posted to the service. This will improve system performance for valid mileage jobs.

This change only applies to Mileage Profiles where the behavior is "Zone (City)". Using "Zip Code" and "Street Address" is unchanged because these workflows use different rules for gathering mileage information for jobs.

The way Mileage Server handles GENETA (new ETA calculations) when they cannot be completed has been changed.

Previously, if a job could not be completed for a valid reason, the system would insert a record with an ERR status. However, the error was not always valid.

These are the new standards for ETA jobs:

A change has been made to how Mileage Server handles job purging.

Previously, OK jobs would automatically be purged immediately (if enabled via mileage settings). ERR, LCK, and NEW jobs needed to be manually cleared when they needed to move. This caused unnecessary jobs to remain in the table for a long time.

Now, the mileage service will automatically purge all records after a set time period, regardless of status. The time period is set by a new application configuration option (app config) called MILESERV.EXE - Auto Purge MS Records.

The default value is seven days. This means that when the SUBMIT_TIME of a job exceeds seven days, the system will automatically purge it.

The Trimble Maps Web Services mileage mode now supports the HighwayOnly and Region properties for each mileage call. This makes sure mileage jobs are calculated correctly when using regions other than North America.

Mileage Server can now recover on its own after a DB2 outage.

If Mileage Server loses connection to the DB2 server, both the mileage distributor and mileage workers lose connection. Previously, once the DB2 connection was restored, the distributor could reconnect, but the workers could not. This prevented mileage from being processed until the service was manually restarted.

Now, both the distributor and the workers can recover on their own after a disconnect.

MobileComm’s dialer thread log files are now automatically started when logging is enabled for the service.

The Mobile Communications service has dialer threads that communicate with third parties. This communication method is available on all Communications Manager vendors, but it was not enabled by default.

Now, when logging is enabled for the MobileComm service, logging is also automatically started for the individual dialer threads. This ensures that communications between TruckMate and the third party are captured in more detail.

For SaaS (software as a service) customers, this gives Trimble more insight into the service itself. Trimble can view the service’s health and get early warnings of any potential problems with the MobileComm service.

Changes were made to how the Drivers tab grid in Dispatch and Multi Mode Dispatch runs queries to retrieve hours of service data.

These grids have calculated fields that are driven by events. As these fields calculate, a query is run to retrieve hours of service data from a table. This query runs on every visible row, which could cause significant performance issues.

This query has been rewritten to be more efficient. The changes to the query improve system performance when working on Drivers grids.