TMS Fall ‘25 Release Patch Information
Fall ‘25 Patch 1
The LoadAndTruckPostingManagementJob2 is corrected to send a failure email for each Load Posting that fails in a batch.
Corrects an issue where user Truckstop credentials were unauthenticated and required re-authenticating.
When the TMS calls the DAT integration to return current market rates, a check is made to determine which set of credentials to include. This check prevents DAT from returning a 403 error when requesting rates.
Changes to the Fleet Management module corrected an issue that resulted in the Trimble integration returning a “Trip is in Completed Status” error. This fix impacts how the Trip Plan Segment Status field updates for both Catena and Samsara integration users.
Set the following values for the appropriate business use case. Navigate to TMS Admin → Configuration, Global Settings.
Set the Delivered Load Trigger field based on the following recommendations. The Trip Plan Leg Departure Date/Time logic is distinct for each integration.
Catena: Set the Delivered Load Trigger to Last Stop Arrival Date to set the Load Status as Delivered when the Driver arrives at the last Stop on a Trip Plan Segment.
This setting automatically updates the Departure Date/Time field on the last Leg on the Segment.
If another trigger is selected, the Departure Date/Time field on the last Leg of a Segment must be set manually to update the Segment Status to Pending Final, and the Load Status to Delivered.
Samsara/FMJ3: Set the Delivered Load Trigger to Last Stop Departure Date.
The Samsara integration updates the Departure Date/Time field when the Driver leaves the final Stop.
An issue is corrected when the LoadPricingWorkbenchExportJob attempted to retrieve Carrier Quotes with the Banyan integration and failed without alerting the user. Both the initial Quote request to Banyan and the error handling emails are corrected.
Corrects an issue where custom fields added to the Load TMS16, TMS17, or TMS18 field sets caused a “Revenova Output Field” error on the Load Banner.
Corrects an issue with the Samsara integration where Trip Plan Arrival and Departure Dates were not updating on the Trip Plan.
Additional filtering is added for quote information loaded from LaneIQ Network.
Multiple integrations are updated to account for the appropriate week and year formatting.
Fall ‘25 Patch 2 is unavailable.
Fall ‘25 Patch 3
After installing Fall ‘25 Patch 3, navigate to TMS Admin → Configuration, select the Reset Reference Data button ONCE and wait for the email indicating completion. This process updates all Trip Event records that do not have an associated Trip Plan Leg.
Corrects multiple issues that prevented the Trip Plan columns from displaying the number of associated Trip Plans for Driver, Fleet Asset, and Load records. The Trip Events and Trip Plans modules correctly display information in the Fleet Management Console.
The Freight Plan Console is enhanced to allow for improved visibility of Customer Loads.
Carrier Quote Request documents are set to the language on the Transportation Profile for the Carrier.
Corrects an issue when building Trip Plan Segments from the Trip Builder. The Due Out Date, Due Out Time, Appointment Date, and Appointment Time fields are set correctly when creating Segments in the Trip Builder.
Freight Plan Carrier Load quoting is supported when returning rates from the Banyan integration. If the Carrier API Login Group field has no value or there is no customer on the Load, the Global Transportation Profile is used to determine the Carrier API Login Group value.
Corrects an issue when viewing Loads in the Freight Plan Console. The Console displayed previous Loads instead of the currently selected Loads.
Corrects an issue with the Fleet Management Console Appointment views that incorrectly removed the Load Expected Ship Date field value when saving in certain scenarios.
A SOQL query issue was identified when generating approximately 200 approved Customer Invoice records that caused invoices to stop processing and move to an On Hold status.
To prevent this issue, there is a limit of 185 Customer Invoice records that may be processed in a single operation. Any remaining Customer Invoice records are processed the next time the CustomerInvoiceGenerationJob runs. The following actions occur when more than 200 Customer Invoice records are selected on the Customer Invoices list view.
When the Generate & Send button is clicked, invoices are processed in batches of 185.
When the Generate & Print button is clicked, an error is presented to the user: “Too many invoices selected. You can select a maximum of 185 invoices at a time.”
The logic controlling the LoadAndTruckPostingManagementJob2 is adjusted to better handle posting Loads to the DAT Load Board. Load Posting records with a Posting Status value of Unposted are not included when sending un-post requests to Load Boards from the Load List View.