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. 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: 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 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

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 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 batch process allows for more efficient handling of retrieving Load documents from Banyan. 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 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 Datatable View Query Limit field to Console View Limit.

• Improved handling of the DAT, Trucker Tools, and the LoadAndTruckPostingManagementJob2 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, Load Detail, RateIQ, and Quote Wizard LWC prevents Stop field data from automatically clearing when changing or updating Load Stops. The new button removes all customer Account information when creating or editing stops.

• Enhancements to the Project44 Unified Tracking integration correct multiple issues when processing container tracking updates.

• Enhancements to the PC Miler integration prevents Zone search functionality in the Fleet Management Console 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.

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.