TMS Summer ’26 Release Patch Information
Summer ‘26 Patch 1
Enhancements to Trip Plan error messaging provide more specific error information for troubleshooting Trip Plans in the Fleet Management Console.
Updates to the Samsara integration allow for greater control to determine the start and completion of routes based on the geolocation of Fleet Assets. When routes are created or updated and sent to Samsara, the following fields are assessed to determine the appropriate functionality.
Set new configuration fields on TMS Admin → Configuration as required.
Start Samsara Route on Departure
Complete Samsara Route on Arrival
See specific field setting information under TMS Admin Fleet Management configuration.
The Rand McNally API via MileMaker provides the total distance on the Load Map between Stop locations using entered Stop Type information in the Load Detail LWC.
Corrects an issue in the VALIDATE and GET requests to correctly read city names and zip codes with spaces, such as two-part named cities and Canadian zip codes, instead of returning an empty value.
Enhanced standard error Toast messages to indicate that a location field, such as zip code and city name, is required to retrieve calculated distance.
Enhancements to the SMC3 EVA quoting operation more efficiently requests Carrier quotes and reduces the time users spend waiting for quotes to return to the TMS.
Enhancements for matching Carrier Quotes to invoices.
Note this enhancement is required for installing the Summer ‘26 Accounting Seed Bridge package.
Summer ‘26 Patch 2
Adds efficiency updates to the Trucker Tools integration reducing the number of asynchronous Apex executions that are counted towards an organization’s Salesforce daily limit.
The following enhancements to the SMC3 EVA integration provide increased accuracy and reduced errors when quoting and tendering Loads to Carriers.
The Load Bill of Lading Number field is more accurately added to Load records from SMC3 EVA integration responses.
Additional checks to confirm the appropriate Customer API Access ID field matches through the process of retrieving rates to tendering to Carriers.
Summer ‘26 Patch 3
The Broker SCAC is required when using the SMC3 EVA integration for tendering Loads and retrieving quotes, Load statuses, and Load documents. Enhancements to the SMC3 EVA integration response operation now takes the Broker SCAC on the Carrier Transportation Profile instead of the Carrier SCAC and includes it in the header URL request as well as in the BillTo field in the body request.