Revenova TMS Installation Guide

Initial Summer ‘26 (26.3) TMS Installation

Use these instructions only if you’re installing Revenova TMS for the first time. See the Upgrading from a Previous Version section to perform the upgrade from the previous release.

Items in blue are optional and may be skipped if the feature is not used.

1. From Setup → Lightning Email Templates, toggle Folders and Enhanced Sharing to On.

2. Create a new Permission Set:

   1. From Setup → Permission Sets, select the New button at the top of the Permission Sets list.

   2. Label the new Permission Set as Manage Public Lightning Email Templates and Drag-and-Drop Content Builder.

   3. Select Save.

   4. Select the link for System Permissions and select the Edit button.

   5. Search for these two permissions and add them to the Permission Set:

      • Manage Public Lightning Email Templates

      • Access drag-and-drop content builder

   6. On the Permission Changes Confirmation modal, select Save.

   7. Assign the Manage Public Lightning Email Templates and Drag-and-Drop Content Builder Permission Set to the logged-in user completing the installation.

3. Obtain the URL and install the package using the Install for all Users option.

4. Wait a few minutes for the application to complete the installation process. You will receive an email once the installation is complete.

5. From Setup → Installed Packages, select the Manage Licenses link for the TMS package and assign licenses to users.

6. From Setup → State and Country/Territory Picklists, turn on Country/State Picklists. Start with the United States as the only country unless you have more information.

7. From Setup → Data Integration Rules, activate Geocodes for Account Shipping Address.

8. From Setup → Enhanced Email, confirm that the Enhanced Email setting is enabled.

9. From Setup → Flows, set up and activate the packaged TMS Auto-Reject Carrier Template as a new flow or use an equivalent method to invalidate unacceptable carriers:

   1. Select the TMS Auto-Reject Carrier Template flow.

   2. In the Flow Builder, select the Save As New Flow button.

   3. Set the Flow Label as “TMS Auto-Reject Carrier” and API Name as “TMS_Auto_Reject_Carrier”.

   4. Select Save, then Activate.

10. From Setup → Duplicate Rules, turn off Matching Rules and Duplicate Rules for Accounts and Contacts, as they can prevent auto-creation of accounts in the application.

11. From Setup → Session Settings, check the Use Lightning Web Security for Lightning web components and Aura components setting to ensure all components meet Salesforce security standards. If this feature is not enabled, all Lightning Web Components may encounter errors during use. Select Save.

12. From Object Manager, for each object listed, select the Edit button. Under the Optional Features section, check the box for Track Field History. Select Save.

    • Carrier Quote

    • Carrier Quote Accessorial

    • Claim

    • Container

    • Customer Quote

    • Customer Quote Accessorial

    • Customer Quote Tax

    • Driver

    • EPayment

    • Fleet Asset

    • Line Item

    • Load

    • Load Accessorial

    • Load Reference

    • Sales Tax

    • Stop

    • Transportation Profile

13. (For Fleet orgs) Enable Feed Tracking for the following objects. This enables the Chatter feature across Fleet Management.

    1. From Setup → Feed Tracking, select the following objects.

    2. Check Enable Feed Tracking.

    3. Select Save.

       • Driver

       • Fleet Asset

       • Load

       • Trip Plan

14. (For Artimus AI orgs) Set the Modes that use the Artimus AI feature for creating Load or Truck Posting records. From TMS Admin → Modes, check the AI Enabled field for all Modes that use the Artimus AI feature. A default AI Load Field Version is generated during Step 15.

    Note: Do not check this field for Modes that should not be used by the Artimus AI feature.

15. From TMS Admin → Configuration, select the Reset Reference Data button ONCE. Wait for this process to complete.

    1. This process deploys the Platform Event subscriber configuration settings for the following events.

       3. EDI Event

       4. Fleet Management Event

       5. Queued Transaction Event

       Note: A red error banner displays on TMS Admin → Configuration if any of the configuration settings are not installed. Navigate to Setup → Configuration to confirm that the Platform Events are configured correctly. If any Event is not installed, the following error is displayed.

       

16. From TMS Admin → Configuration, fill out all the fields in the Global Settings section with valid values.

17. Create a global Transportation Profile as the Global Default and set it in TMS Admin → Configuration.

18. From TMS Admin → Equipment Types, set the four load board equipment types by visiting and filling out all information on each Equipment Type record.

19. From Setup → Chatter Settings, enable Chatter.

20. From Setup → Trusted URLs, add a new trusted URL for ALK Maps:

21. Ensure these custom Account fields are displayed for TMS users and are properly secured:

    • TMS Type

    • Transportation Profile

    • DBA Name

    • Customer Sales Rep

    • Default Payment Method

    • Posting City

    • Posting State/Province

    • Time zone

22. Make sure the Transportation Role field is displayed for TMS users on the Contact page layout.

23. Provide appropriate CRUD (Create, Read, Update, Delete) access to each user profile for each TMS object.

24. Customize page layouts and Lightning Record Pages as appropriate for each profile.

Salesforce requires that user email addresses be verified to enhance accountability and security when sending emails. When an org is updated to the Salesforce Spring ’25 release, a reminder email is no longer sent. If you’re encountering issues with users’ ability to send email messages, confirm that the email address is verified. The Getting Started with Revenova article contains steps to confirm that an email address is verified. See additional Salesforce information here.

Please refer to the Getting Started with Revenova article and the Revenova Document Base for detailed descriptions, configuration settings, and customizations available in the application.

Upgrading from a Previous Version

Second Generation Managed Packages

Revenova is converting all supported packages from 1GP to Salesforce Second Generation Package Management. All packages must be converted to 2GP before upgrading the TMS package to 2GP.

In preparation for this upgrade, install the following conversion packages for any existing installed packages.

• TMS Accounting/Accounting Seed bridge Winter 26 package (Version 26.2).

• Sage Flat File

• Sage API

• Dynamics GP

Any third party packages that are not 2GP are not supported once the TMS is upgraded to 2GP.

Customers with the Accounting Seed package installed should complete the conversion package installation before installing the Summer ‘26 upgrade.

Release Summer ’26 (26.3) TMS Upgrade Instructions (ETC: 15 minutes)

Perform each set of upgrade tasks (EXCEPT for the package installation step, which can be skipped from any release to the latest) if you are upgrading from a release prior to the previous release.

Follow the upgrade steps from the oldest release to the newest release in release order for any upgrades that span multiple releases.

Accounting Package Compatibility

Prior to the TMS package installation, confirm there is a compatible accounting package version for the options below:

• Sage API (Age 300)

• Sage Flat File

• Dynamics GP

Contact Professional Services with any questions.

Accounting Seed customers must have BOTH the TMS and Accounting Seed Bridge packages before upgrading. Complete the TMS Upgrade installation before installing the Accounting Seed Bridge package. See the Accounting Seed Bridge installation instructions for more information.

Items in blue are optional and may be skipped if the feature is not used. Structural changes in red are required.

Security enhancements added to the Revenova package likely impact current User setup and should be validated in the sandbox before proceeding with a Production upgrade to prevent business disruption. See the Final Steps section below for identifying user permissions.

SFDC/TMS Pre-Configuration

Install and test in a sandbox environment BEFORE upgrading to the production environment.

You must have installed and completely configured the Spring ’26 Release before installing this release.

Salesforce requires that user email addresses be verified to enhance accountability and security when sending emails. When an org is updated to the Salesforce Spring ’25 release, a reminder email is no longer sent. If you’re encountering issues with users’ ability to send email messages, confirm that the email address is verified. The Getting Started with Revenova article contains steps to confirm that an email address is verified. See additional Salesforce information here.

For Accounting Seed customers, do NOT install this TMS release until you have obtained the Accounting Seed Bridge package URL as well. They must be upgraded simultaneously.

1. From Setup → Duplicate Rules, turn off Matching Rules and Duplicate Rules for Accounts and Contacts, as they can prevent auto-creation of accounts in the application.

2. From Setup → Data Integration Rules, activate Geocodes for Account Shipping Address.

3. From Setup → State and Country/Territory Picklists, turn on Country/State Picklists. Start with the United States as the only country unless you have more information. These picklists should be enabled unless there is a backward-compatibility issue with other packages or customizations.

4. From Setup → Session Settings, check the Use Lightning Web Security for Lightning web components and Aura components setting to ensure that all components meet Salesforce security standards. Select Save.

   Note: Thoroughly test any custom Lightning Web Components when enabling this setting. All TMS components are tested to support this functionality.

5. From the Object Manager, make sure no values were added to the Load object’s Sales Status or Load Status picklist fields or the Stop object’s Stop Status picklist field.

   Salesforce Note: To resolve issues when deleting items in the Lightning UI, change to Classic UI to perform the deletions.

Upgrade Installation Steps

1. Obtain the Summer ’26 installation URL and password from your Revenova representative.

   Install the upgrade:

   1. Choose Install for All Users.

   2. Select Upgrade.

   3. If prompted, check the Yes, grant access to these third-party web sites box.

   4. Select Continue.

   5. From Setup → Deployment Status, select the link to view the progress of the installation.

   6. Wait for the Installation succeeded email.

Upgrade Note: Several new objects and fields are included in the TMS Summer ’26 release. Set CRUD (Create, Read, Update, Delete) access for the objects and/or fields accordingly.

Warning

Upgrade installations do not add any objects or fields to custom permission sets. Add new fields as necessary to any custom permission sets. New fields are added automatically to Revenova packaged permission sets and do not require additional setup.

Custom permission sets are commonly used for the following Experience Cloud Sites:

• Appointment Request Email Loop

• Carrier Application

• Carrier Email Loop

• Customer Email Loop

• Fleet Email Loop

2. From TMS Admin → Configuration, select the Reset Reference Data button ONCE and wait for the email indicating completion.
   This process completes the following tasks:

   2. Two functions are completed for the Samsara credential card Require Arrival In Sequence field.

      2. The value of the field is copied to the new TMS Admin → Configuration field, Require Arrival In Sequence.

      3. The field is removed from the Samsara credential card.

      4. NOTE: This step is completed to account for users that installed Spring ‘26 Patch 2 for the Samsara functionality.

   3. All Accessorial records with an API Provider field value of WWEX SpeedShip are updated as described below. No new API Accessorial records are created.

      2. All API Accessorial records with a Code field that matches any of the following codes is updated to the following values (Existing Code → New Code).

         2. AIRDEL or AIRUP → AIRPORT

         3. CONDEL or CONPU → CONSTRUCTION

         4. LTDDEL or LTDPU → LIMITED_ACCESS

         5. RESDEL or RESPU → RESIDENTIAL

         6. CNVDEL or CNVPU → TRADESHOW

      3. The Accessorial Location Type field is Checked for each matching API Accessorial Code.

   4. Completes a migration configuration for the AR Calculate Balances field setting on TMS Admin → Configuration.

      2. Any customers that enabled this feature from previous patches (Fall ‘25 Patch 5, Winter ‘26 Patch 3, or Spring ‘26 Patch 1) must complete the Reset Reference Data step of the Upgrade Installation before running the ARCalculatorJob for the first time after upgrading to Summer ‘26.

      3. This feature was enabled with the TMS Admin → Configuration setting Use Queueables for: AR Calculate Balances.

Note: Any errors encountered while running the Release Update Job are sent to the email address of the User running the job. Errors can also be found in the Apex Jobs view.

3. Complete the following steps for the WWEX Speedship enhancements. Note that the WWEXSpeedship value may not be present. If the value is already deleted, continue to the next picklist value.

   2. Remove the obsolete picklist values from the following field.

      2. Navigate to Setup → Object Manager.

      3. Choose the API Accessorial object and select the Fields & Relationships tab.

      4. Select the API Provider field.

      5. Scroll to the Values section.

      6. Click the Del link for the WWEXSpeedship value (API Name WWEXSpeedship).

      7. Confirm the delete.

      8. Choose the Replace value on records with radio and select WWEX Speedship from the picklist.

      9. Click Save.

      10. Click the Del link for the Worldwide Express value (API Name Worldwide Express) if it exists.

      11. Confirm the delete.

      12. Choose the Replace value on records with blank value radio.

      13. Click Save.

   3. Revenova recommends deleting any API Accessorial records with an API Provider field with no value.

Optional Brokerage and Fleet Setup

Freight Brokerage and Fleet orgs should complete the following optional steps as requested:

3. SMC3 EVA users must complete the following actions. See documentation for configuring functionality for the SMC3 EVA integration.

   1. Current SMC3 EVA customers must complete the following action to reset the API connection.

      1. Navigate to TMS Admin → Credentials.

      2. Choose the Global Services tab.

      3. Select the SMC3 EVA card.

      4. Confirm credentials are included in the fields. Existing users do not need to add any additional information.

      5. Click Save.

      6. Choose the SMC3 EVA card.

      7. Confirm the Callback Endpoint Created field is Checked.

   2. Add the following fields to the appropriate Lightning Record Pages (LRP). Navigate to a Vendor Invoice record.

      1. Select Setup → Edit Page.

      2. Drag the following fields onto the LRP.

         1. Discount Percent

         2. Incoming Net Freight Charge

         3. Transaction Id

4. Configure the customer org to use four LWCs (RateIQ, Customer Shipment Tracking, Text to Load, and/or Text to Truck Posting) in a Gmail or Outlook email inbox. Complete the following steps to access the LWCs. See additional setup and configuration information here.

   1. Enable the Gmail integration and/or the Outlook integration in the customer org.

   2. Create and customize an Email Action Pane.

      1. Assign the Email Action Pane to the appropriate user Profiles or set as the org default.

   3. Google email users must install the Salesforce browser extension for Chrome.

   4. Outlook email users must install the Salesforce extension.

5. The new Payment Terms feature auto-populates the Carrier Payment Terms fields into newly-created Carrier Quote records when they are populated on the corresponding Carrier Transportation Profile. No existing records are back-populated.

   1. Create Payment Terms records as necessary. Select the desired Payment Terms on the appropriate Transportation Profiles.

   2. The Payment Terms feature supports the global Transportation Profile for adding Payment Terms to each Carrier Quote. If desired, add The Payment Terms feature to the global Transportation Profile.

      1. Navigate to the global Transportation Profile.

      2. Select Setup → Edit Page.

      3. Choose the Fields tab.

      4. Find the Carrier Payment Terms field and drag it onto the page where desired.

      5. Click Save. Activate the page, if necessary.

      6. Find the Carrier Payment Terms field.

      7. Choose the appropriate Payment Terms record.

      8. Save the global Transportation Profile.

6. Complete the following steps to configure accessorial charges for the WWEX Speedship integration.

   1. Navigate to TMS Admin → Accessorials.

   2. Configure accessorial charges to properly send and receive information from WWEX Speedship.

   3. See the linked information for Accessorial Code, API Accessorial, and Location Type settings.

Final Steps

1. Revenova has included additional security functionality for many fields in the TMS.

   1. See the Required Field Scanner LWC to search by user and determine if additional objects and fields are required for customer permission sets.

      1. Navigate to TMS Admin → Required Field Scanner.

      2. Set or adjust User permissions as necessary.

   2. The TMS Baseline Required Fields permission set contains all impacted field permissions. It is not recommended to assign this permission set to all users, as it may provide unwanted permissions to fields.

      • Fields are added to the permission set with each TMS release.

2. Confirm all required TMS batch jobs are running and/or scheduled. See the Batch Processes article for suggested run times.

Release Summer ’26 Field/Field Set Modification Summary - TMS

Field Note: Review fields added by the installation and set CRUD access as needed.