--- title: "Winter '26 Revenova TMS Patch Information" slug: "winter-26-revenova-tms-patch-information" tags: ["Winter '26", "Admin", "End User"] updated: 2026-11-09T14:32:38Z published: 2026-11-09T14:32:38Z canonical: "documents.revenova.com/winter-26-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. # Winter '26 Revenova TMS Patch Information ## TMS Winter ’26 Release Patch Information ### **Winter ‘26 Patch 1** Additional Handling Unit, Packaging Unit, and accessorial support is added for quoting with [Banyan](/previous-releases/docs/winter-26-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](/previous-releases/docs/winter-26-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](/previous-releases/docs/winter-26-batch-processes) batch process allows for more efficient handling of retrieving Load documents from [Banyan](/previous-releases/docs/winter-26-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**. Multiple improvements to the [Fleet Management Console](/previous-releases/docs/winter-26-fleet-management-console-views) provide more efficient view and query results when searching for records. Updates include the following changes. - Clarified messaging on the Fleet Management Console provide users additional information when displaying record results. - Query enhancements improve the efficiency when returning results in the Fleet Management Console. - Relabeled the TMS Admin → [Configuration](/previous-releases/docs/winter-26-fleet-management) *Datatable View Query Limit* field to *Console View Limit*. - Improved handling of the [DAT](/previous-releases/docs/winter-26-dat), [Trucker Tools](/previous-releases/docs/winter-26-trucker-tools-load-board-truck-postings), and the [LoadAndTruckPostingManagementJob2](/previous-releases/docs/winter-26-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. - Multiple enhancements to the [Load Configuration](/previous-releases/docs/winter-26-load-configuration), [Load Detail](/previous-releases/docs/winter-26-load-detail#multiple-pickupdelivery-stops), [RateIQ](/previous-releases/docs/winter-26-rateiq), and [Quote Wizard](/previous-releases/docs/winter-26-quote-wizard-setup#load-entry-page) LWC prevents Stop field data from automatically clearing when changing or updating Load Stops. The new ![The button to clear stop fields.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Stop Remove Fields Button - 1.jpg) button removes all customer Account information when creating or editing stops. - Enhancements to the [Project44 Unified Tracking](/previous-releases/docs/winter-26-container-tracking) integration correct multiple issues when processing container tracking updates. - Enhancements to the [PC Miler](/previous-releases/docs/winter-26-pc-miler) integration prevents Zone search functionality in the [Fleet Management Console](/previous-releases/docs/winter-26-fleet-management-console-views) from timing out with large requests. ### **Winter ‘26 Patch 2** - Corrects an issue where Stops and Stop order were incorrectly updating when an interim Stop was added to a Load. ### **Winter ‘26 Patch 3** - Corrects a permission issue to address Salesforce security changes for [Artimus™](/previous-releases/docs/winter-26-artimus-ai) users. #### AR Balance Calculation Performance Enhancement A new configuration option, **Use Queueables for: AR Calculate Balances**, is added to **TMS Admin →** [**Configuration**](/previous-releases/docs/winter-26-platform-events). 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/winter-26-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. ### **Winter ‘26 Patch 4** - Adds enhancements to the TMS to better handle issues encountered with the [PerformanceIQ](/previous-releases/docs/winter-26-performance-iq) LWC. See additional related Salesforce information [here](https://help.salesforce.com/s/articleView?id=005318663&type=1). ### **Winter ‘26 Patch 5** - Multiple enhancements to the REST EDI architecture address the following issues encountered when using the [EDI Order Update Console](/v1/docs/edi-order-update-console). - Load References values included on inbound EDI 204 Transaction are no longer automatically cleared. - EDI 204 Transactions that do not contain Hazmat Line Items no longer trigger an error in the Console. - Improved Account matching for Customer **Bill To** fields included on inbound EDI 204 Transactions no longer creates duplicate Account records. - Retrying inbound EDI 204 Transactions from a *Pending* **Status** no longer includes the outbound EDI 204 transaction in the GET endpoint queue. - When replacing Stops in the Console, the **Appointment Required** field no longer causes an error. ### **Winter ‘26 Patch 6** - The Revenova REST EDI service is enhanced to customize the retrieval of EDI Transactions from customer orgs. An additional configuration is added to the [GET](https://documents.revenova.com/apidocs/retrieves-queued-outbound-edi-events-1) endpoint when trading partners retrieve (outbound) EDI Transactions from the TMS. As trading partners retrieve EDI Transactions, the EDI Transaction **Status** is updated from *Pending* to *Success*. This default functionality is unchanged. - With the new configuration, trading partners may retrieve *Pending* EDI Transactions from the TMS. The **Status** is only updated to *Success* once the trading partner calls the PATCH endpoint to update the **Status** to *Success* for each EDI Transaction they receive. Use caution as any EDI Transactions that do not have the **Status** updated via the *PATCH* endpoint remain in a *Pending* state and may be retrieved multiple times by the trading partner. ### **Winter ‘26 Patch 7** - The current REST and legacy SOAP EDI processing handles a number of issues encountered with inbound EDI 204 Load Tenders. - Load Tenders that share a **Trading Partner ID** are now matched by the **SCAC** value included in the `referenceNum` element. This reduces the incidents of encountering an “Unrecognized Trading Partner” error. The TMS processes the **SCAC** values and includes them in the EDI Location matching process. - Corrects an issue with inbound EDI transactions and processing Load References incorrectly resulting in overwriting Load Reference fields. EDI Load References are correctly prioritized when they are included in an EDI Transaction followed by the “standard” values included in the transaction. Previously, the **Container/Trailer Number**, **Order Number**, and **Bill of Lading Number** fields were overwritten by the values in the transaction. - EDI 204/404 Transactions that contain duplicate **Order Number** values no longer cause EDI Load Tenders to fail. For update transactions, the existing **Order Number** value is kept. - While processing inbound EDI transactions, when two delivery Stops share the same customer Accounts with two EDI Location records that include the same Contact name, an error occurred when trying to update the associated Contacts. De-duplication is checked after all Stops are processed to prevent this error. When the same Contact is included on multiple Stops for the same Account, one Contact is saved and updated with the *Shipping* and *Receiving* **Transportation Role**. - Enhanced email address validation prevents invalid email addresses received in inbound EDI transactions from failing to save on Contact records. Email addresses are trimmed of unnecessary characters and validated as a correctly formatted address. Only the first email included in the inbound EDI transaction is processed. - Hazmat Contacts without a name no longer cause the entire Load Tender to fail. Matching occurs by **Phone** and **Email** if possible. ## PayIQ Winter ‘26 Release Patch Information ### **Winter ‘26 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.