--- title: "Spring '26 Revenova TMS Patch Information" slug: "spring-26-revenova-tms-patch-information" tags: ["Spring '26", "Admin", "End User"] updated: 2026-11-17T14:02:03Z published: 2026-11-17T14:02:03Z canonical: "documents.revenova.com/spring-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. # Spring '26 Revenova TMS Patch Information ## TMS Spring ’26 Release Patch Information ### **Spring ‘26 Patch 1** - Corrects a SOQL query issue encountered when opening the [Fleet Management Console](/previous-releases/docs/spring-26-fleet-management-console-views) with many views. The following enhancements are included for the Fleet Management Console. - Enhancements to the Fleet [Appointment List](/previous-releases/docs/spring-26-appointment-setting) prevent an error when managing appointments in the Fleet Management Console. - Enhancements to Fleet Notification Types corrects an issue with a mismatch with certain Travel Credentials for the following picklist values. - FAST - Free and Secure Trade - SF-86 - Gov’t Security Clearance - The **Acknowledged By** field is correctly populated when the user first opens the [Trip Event Viewer LWC](/previous-releases/docs/spring-26-trip-planning#trip-event-viewer). - Once a Notification is resolved, it is removed the next time the Fleet Management Job runs. - Notifications no longer generate duplicate instances of a notification each time the Fleet Management Job runs. Existing notifications are instead updated rather than duplicated. - Corrects an issue with the [TexttoLoad LWC](/previous-releases/docs/spring-26-artimus-ai-lwcs#text-to-load-lwc) when attempting to create a Customer Quote for [Artimus™](/previous-releases/docs/winter-26-artimus-ai) users. - When quotes return below the threshold and the **Send Customer Email** field is not *Checked*, Artimus™ correctly processes the Load and does not send the Quote. #### AR Balance Calculation Performance Enhancement A new configuration option, **Use Queueables for: AR Calculate Balances**, is added to **TMS Admin →** [**Configuration**](/previous-releases/docs/spring-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/spring-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. ### **Spring ‘26 Patch 2** The following addresses an issue with the Samsara integration. - Corrects an issue with the [Samsara](/previous-releases/docs/spring-26-samsara) integration for round trip Loads on a Trip Plan that begin and end at the same location incorrectly populating the Arrival Time for the last leg of the Trip Plan. When enabled by completing the steps below, a Trip Plan Leg is only be updated by Samsara when the previous Trip Plan Leg is completed. A Trip Plan is considered complete when the Actual Arrival or Actual Departure Timestamp is populated to update the Trip Plan Leg **Status** to *Completed*. - Complete the following steps to enable this functionality. - **Configuration Instructions** - Navigate to **TMS Admin → Credentials**. - Choose the *Global Services* and find Samsara in the list. - Click the **Samsara** link to open the credential card. - Check the **Require Arrival In Sequence** field. - Click **Save**. The following enhancements are included for [Fleet Management Job 3](/previous-releases/docs/spring-26-fleet-management-job) to manage the integration with [Samsara](/previous-releases/docs/spring-26-samsara). - The portion of the job that retrieves Driver Log Summaries from Samsara is separated from other functions to always retrieve the summaries. - The email notification process sends error notifications once the job is completed. The following Fleet Management Console functionality was addressed. - Corrects an issue with the ascending/descending record sort order in [Fleet Management Console](/previous-releases/docs/spring-26-fleet-management-console-views) views. Two issues were addressed for the [SMC3 EVA](/previous-releases/docs/spring-26-smc3-eva) integration. - Corrects an issue with the SMC3 EVA integration when requesting rates with a Global Transportation Profile. - Enhancements to the SMC3 EVA integration allow for better error handling when receiving and processing documents. ### **Spring ‘26 Patch 3** - Corrects an issue with document polling sessions when receiving documents via the [SMC3 EVA](/previous-releases/docs/spring-26-smc3-eva) integration. - **Navigate to Setup → Security → Sharing Settings**. - From the **Manage sharing settings for:** picklist, choose the Load object. - Find the *Sharing Rules* section and click the **New** button for Load Sharing Rules. 1. Enter a **Label** and **Rule Name**, such as *API*. 2. Enter the following **Criteria**. 1. **Field**: Select a Load field, such as **Entry Number**. 2. **Operator**: *not equal to* 3. **Value**: any random string of characters, such as *xzyasdf123*. - Set the **Share with** field to [*API Site Guest User*](/previous-releases/docs/spring-26-email-loop-setup#api-guest-access). - Set the **Access Level** field to *Read Only*. - Click **Save**. ### **Spring ‘26 Patch 4** - Updates a configuration field for the [PerformanceIQ](/v1/docs/performance-iq) component to prevent an issue when parsing long strings. - Updated the logic for processing inbound documents from [SMC3 EVA](/v1/docs/smc3-eva) to prevent Queued Transactions from generating incorrectly. - *Complete the Sharing Setting configuration steps from Patch 3 if not already completed.* ### **Spring ‘26 Patch 5** - Adds enhancements to the TMS to better handle issues encountered with the [PerformanceIQ](/previous-releases/docs/spring-26-performance-iq) LWC. See additional related Salesforce information [here](https://help.salesforce.com/s/articleView?id=005318663&type=1). - 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. - Corrects an issue with the [Deadhead Calculator](/v1/docs/deadhead-calculator) picklist selection. - Corrects an issue encountered when viewing the [PerformanceIQ](/previous-releases/docs/spring-26-performance-iq) component in high volume orgs that generated errors. ### **Spring ‘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. ### **Spring ‘26 Patch 7** - Adds efficiency updates to the [Trucker Tools](/previous-releases/docs/spring-26-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. - 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. - The [Rand McNally](/previous-releases/docs/spring-26-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](/previous-releases/docs/spring-26-load-detail). - 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. ## PayIQ Spring ‘26 Release Patch Information ### **Spring‘26 Patch 1** - Implemented additional checks to monitor flexipage changes to the PayIQ Program Lightning Record Page. An issue was discovered that prevented users from adding filters to the Load Filter Editor component. ### **Spring‘26 Patch 2** - Fuel Card and EPayment transactions that occur on the final day of a Pay Period were not correctly added to a Participant’s Pay Header. - Fuel Cards and EPayment transactions are more accurately matched to the appropriate Pay Header record when created on the final day of a Pay Period. The **CreatedBy** date field on the record is compared to the Salesforce Organization timezone to determine whether or not to include the transaction on the Pay Header.