--- title: "Fall '25 Revenova TMS Patch Information" slug: "fall-25-revenova-tms-patch-information" tags: ["Admin", "End User", "Fall '25"] updated: 2026-08-07T20:40:14Z published: 2026-08-07T20:40:14Z canonical: "documents.revenova.com/fall-25-revenova-tms-patch-information" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Fall '25 Revenova TMS Patch Information ## 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](/previous-releases/docs/fall-25-truckstop) credentials were unauthenticated and required re-authenticating. - When the TMS calls the [DAT](/previous-releases/docs/summer-25-dat-freight-and-analytics) 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](/previous-releases/docs/fall-25-trimble-maps) 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](/previous-releases/docs/fall-25-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](/previous-releases/docs/fall-25-catena-eld-aggregator): 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](/previous-releases/docs/fall-25-fleet-management-with-samsara)/FMJ3: Set the **Delivered Load Trigger** to L*ast 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](/previous-releases/docs/fall-25-batch-processes) attempted to retrieve Carrier Quotes with the [Banyan](/previous-releases/docs/fall-25-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](/previous-releases/docs/fall-25-field-set-summary#load) caused a “Revenova Output Field” error on the [Load Banner](/previous-releases/docs/fall-25-load-banner). - Corrects an issue with the [Samsara](/previous-releases/docs/fall-25-fleet-management-with-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](/previous-releases/docs/fall-25-laneiq-network). - Multiple integrations are updated to account for the appropriate week and year formatting. - [DAT](/previous-releases/docs/fall-25-dat) - [EFS](/previous-releases/docs/fall-25-efs) - [Comdata](/previous-releases/docs/fall-25-comdata) - [TextLocate](/previous-releases/docs/fall-25-textlocate) > [!NOTE] > *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](/previous-releases/docs/fall-25-freight-plan-console) Carrier Load quoting is supported when returning rates from the [Banyan](/previous-releases/docs/fall-25-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](/previous-releases/docs/fall-25-freight-plan-console). The Console displayed previous Loads instead of the currently selected Loads. - Corrects an issue with the [Fleet Management Console](/previous-releases/docs/fall-25-fleet-management-console-views#appointment-views) 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](/previous-releases/docs/batch-processes) runs. The following actions occur when more than 200 Customer Invoice records are selected on the [Customer Invoices list view](/previous-releases/docs/customer-invoice-batch-generation-4#send-batch-invoices-by-email). - 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](/previous-releases/docs/fall-25-batch-processes) is adjusted to better handle posting Loads to the [DAT Load Board](/previous-releases/docs/fall-25-dat). 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](/previous-releases/docs/fall-25-load-list-view). ### **Fall ‘25 Patch 4** > [!CAUTION] > **NOTE:** Customers that did NOT install Fall ‘25 Patch 3 must complete this step once Fall ‘25 Patch 4 is installed. Customers that completed the Reset Reference Data step when installing Fall ‘25 Patch 3 do not need to complete the step again. > > > > After installing Fall ‘25 Patch 4, 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. Additional Handling Unit, Packaging Unit, and accessorial support is added for quoting with [Banyan](/v1/docs/banyan). Loads tendered via Banyan also update the Load **Expected Delivery** and **Expected Ship Date** fields returned from the Carrier. Complete the following steps to add support for this new functionality when quoting and tendering with Banyan. > [!WARNING] > **Warning:** Only customer orgs using the Banyan integration should complete the steps below. - Add picklist values to the **Handling Units** and **Packaging Units** fields on the following objects as shown below (including spaces). 1. Navigate to **Setup → Object Manager** and search for the each of the objects listed below. 2. Click the *Fields & Relationships* tab. 3. Select the **Handling Units** field. 4. In the *Values* section click the **New** button. 5. Add the picklist values listed below to the box. Note that picklist value API Names must match exactly as listed below (including spaces and plural values). 6. Click **Save**. - Repeat steps 3 through 6 above for the **Packaging Units** field. - Repeat the steps above for each of the objects listed below. **Objects** - Commodity - Line Item - Rate Entry Calculation **Picklist Values** - Accessorials - Attachments - Buckets - Bulkheads - Chests - Each - Envelopes - Feet - Firkins - Gaylords - Loose - Octabin - Pails - Plastic Jerricans - Racks - Slip Sheets - Super Sacks - Totes - Trailers - Trunks - Tubs - Unpackaged - Vehicles > [!NOTE] > Note that picklist value API Names must match exactly as listed (including spaces and plural values). **Limited Access Accessorial Records** - Create Accessorial records for the new limited access accessorial types. 1. Navigate to **TMS Admin → Configuration**. 2. Select the *Accessorials* link. 3. Click the **New Accessorial** button. 4. Enter a **Name** value. See the list below. 5. *Check* the **Limited Access** field. 6. Enter field information for the remaining Accessorial record fields as necessary. 1. *Check* the **Enabled** field. 2. The **Type** is *Pickup* or *Delivery*. 3. To support both pickup and delivery Stop locations, create an accessorial record for both. 7. Click **Save**. 8. Select the *Related* tab for the new accessorial record. 9. From the *API Accessorial* list, click the **New** button. 10. Select *Banyan* in the **API Provider** field. 11. Enter a value for the **Code** field. Any value is valid. 1. The **Code** field is required, but the Banyan integration uses the Subcode to determine the accessorial charge. 12. Enter the appropriate **Subcode**. 13. Click **Save**. - Repeat the steps above for the remaining accessorial support. **API Accessorial Record Values** | Accessorial Name | Code | Subcode | | --- | --- | --- | | Hospital/Medical Facility | Enter any value | HMED | | Prison | Enter any value | PRIS | | Shopping Center/Mall | Enter any value | SHCM | **Load Accessorial** - Create a new Load Accessorial record for TankerEndorsdedDriverRequired. 1. Navigate to **TMS Admin → Configuration**. 2. Select the *Accessorials* link. 3. Click the **New Accessorial** button. 4. Enter a value in the **Name** field. 5. Enter field information for the remaining Accessorial record fields as necessary. 1. *Check* the **Enabled** field. 2. The **Type** is *Load*. 6. Click **Save**. 7. Select the *Related* tab for the new accessorial record. 8. From the *API Accessorial* list, click the **New** button. 9. Select *Banyan* in the **API Provider** field. 10. Enter a value for the **Code** field. Any value is valid. 1. The **Code** field is required, but the Banyan integration uses the Subcode to determine the accessorial charge. 11. Enter *TankerEndorsdedDriverRequired* in the **Subcode** field. 12. Click **Save**. - The [Banyan](/v1/docs/banyan) integration is enhanced for better handling of the Load **API Load ID** field. This field determines Load tracking and document retrieval for the Banyan integration. - Improvements to the [BanyanJob](/v1/docs/batch-processes) batch process allows for more efficient handling of retrieving Load documents from [Banyan](/v1/docs/banyan#get-load-documents). A single document is processed individually with each pass of the job before moving on to the next document. Any documents greater than 12 MB generate an error. A document is added to the Load with the text, “The document from Banyan for this carrier was too large for Salesforce to import. Please go to Banyan’s web site to get this document.” - Complete the following steps to configure the Banyan integration. - Navigate to **TMS Admin → Credentials**, Global Services and select the *Banyan* card. - Enter the following value into the **Proxy URL** field: https://api.revenova.com:8087 - Navigate to **Setup** and search for *Remote Site Settings*. - Click the **New Remote Site** button and enter the following field values. - **Name:** *Revenova Banyan Proxy* - **Remote Site URL:** https://api.revenova.com:8087 - **Active:** *Checked* - Click **Save**. - Improved handling of the [DAT](/v1/docs/dat), [Trucker Tools](/v1/docs/trucker-tools-load-board-truck-postings), and the [LoadAndTruckPostingManagementJob2](/v1/docs/batch-processes) batch process for managing authentication tokens. These enhancements address issues requiring users to frequently reauthenticate their credentials when using Load Board and Truck Posting integrations. ### **Fall ‘25 Patch 5** - Enhancements to the [Project44 Unified Tracking](/previous-releases/docs/fall-25-container-tracking) integration correct multiple issues when processing container tracking updates. #### AR Balance Calculation Performance Enhancement A new configuration option, **Use Queueables for: AR Calculate Balances**, is added to **TMS Admin →** [**Configuration**](/previous-releases/docs/fall-25-global-settings#configurable-fields). This setting is designed to improve performance scalability for clients with large volumes of customer Transportation Profiles, Loads, Customer Quotes, or Customer Invoices. When *Checked*, AR balance calculation performed by the **ARCalculationJob** offloads some of its processing to a [Salesforce Queueable Apex](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_queueing_jobs.htm) process to minimize congestion in the Platform Event processor. When should this be enabled? - Enable this setting when experiencing performance degradation or processing delays when running the [**ARCalculationJob**](/previous-releases/docs/fall-25-batch-processes). - If you are unsure whether this setting is appropriate for your organization, please contact Revenova Support before enabling it. Important Considerations - Review Salesforce Async Apex usage and limits before enabling this feature, as this feature increases Salesforce **Daily Async Apex** usage. - Estimated additional Daily Async Apex consumption is approximately: **Number of Customer Transportation Profiles ÷ 10, per ARCalculationJob run** For example, an organization with 60,000 Transportation Profiles for customer accounts consumes approximately 6,000 additional Async Apex executions each time the ARCalculationJob runs. Operational Considerations - Organizations that enable this feature will see an increase in Queueable jobs listed in Setup → Apex Jobs. - These jobs appear under the Apex class name InsertApiQuoteLogsJob. - This behavior is expected and does not indicate quote log processing activity. This setting is not enabled by default. It should only be enabled to address AR calculation performance issues. ### **Fall ‘25 Patch 6** - Adds enhancements to the TMS to better handle issues encountered with the [PerformanceIQ](/previous-releases/docs/fall-25-performance-iq) LWC. See additional related Salesforce information [here](https://help.salesforce.com/s/articleView?id=005318663&type=1). ## PayIQ Fall ‘25 Release Patch Information ### **Fall ‘25 Patch 1** - Corrects an issue that prevented Pay Header records from generating for a Driver or Fleet Asset that is paid from a Load. Trip Plans with multiple eligible Legs did not create a Participant match if they fell on a batch boundary.