--- title: "Spring '26 Revenova TMS Installation Guide" slug: "spring-26-revenova-tms-installation-guide" tags: ["Admin", "Spring '26", "TMS Admin"] updated: 2026-10-27T18:09:12Z published: 2026-10-27T18:09:12Z canonical: "documents.revenova.com/spring-26-revenova-tms-installation-guide" --- > ## 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 Installation Guide ## Initial Spring ‘26 (26.2) 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. > [!WARNING] > **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. 16. From **TMS Admin → Configuration**, fill out all the fields in the [Global Settings](/previous-releases/docs/global-settings) section with valid values. 17. Create a global Transportation Profile as the [Global Default](/previous-releases/docs/global-default-transportation-profile) 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:![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/image(21).png?sv=2026-02-06&spr=https&st=2026-07-28T21%3A20%3A38Z&se=2026-07-28T21%3A35%3A38Z&sr=c&sp=r&sig=VaDHCOOGu7%2F94kZ8E1tBhjb59fkFr1rPI2B5Cv3e46k%3D?sv=2026-02-06&spr=https&st=2026-07-28T21%3A28%3A52Z&se=2026-07-28T21%3A43%3A52Z&sr=c&sp=r&sig=V4JYhec%2F1UUcz1Q2UyuaXHyUXGwo9BhK7oRc9QhNxU4%3D?sv=2026-02-06&spr=https&st=2026-07-29T01%3A12%3A17Z&se=2026-07-29T01%3A27%3A17Z&sr=c&sp=r&sig=hej5PyDtHSLmPsj3EAyk42%2FTxfj2haA%2F%2F24xQXEItpw%3D) 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](/previous-releases/docs/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](https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/sfdx_dev_dev2gp.htm). 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. As conversion packages are released the version number will be added to this document for reference. - TMS Accounting/Accounting Seed bridge Winter 26 Conversion 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 Spring ‘26 upgrade. ### Release Spring ’26 (26.2) 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. > [!CAUTION] > No packages were created for the **Spring ‘26 TMS Analytics** and **Spring ‘26 TMS Accounting Seed Bridge** packages for the Spring ‘26 TMS release. Continue to use the existing releases for these packages until a future compatible release is provided. > > > > - For releases that include an Accounting Seed Bridge package, 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.** > [!WARNING] > 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](/previous-releases/docs/spring-26-revenova-tms-installation-guide#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 **Winter ’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**. > [!WARNING] > **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. > [!NOTE] > **Salesforce Note**: To resolve issues when deleting items in the Lightning UI, change to **Classic UI** to perform the deletions. #### Upgrade Installation Steps 1. Before installing the package, add the following picklist value: 1. Navigate to **Setup → Object Manager**. 2. Search for and select the Fleet Asset object. 3. Choose the Fields & Relationships tab. 4. Click the **Type** field. 5. From the *Values* section, click the **New** button. 6. Enter *Tanker* as a picklist value. 7. Click **Save**. 2. Obtain the **Spring ’26 installation URL and password** from your Revenova representative. Install the upgrade: 1. Select *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. > [!NOTE] > **Upgrade Note**: Several new objects and fields are included in the TMS Spring ’26 release. Set CRUD (Create, Read, Update, Delete) access for the objects and/or fields accordingly. > [!CAUTION] > 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](https://help.salesforce.com/s/articleView?id=experience.networks_overview.htm&type=5) Sites: > > - Carrier Email Loop > - Customer Email Loop > - Fleet Email Loop 1. From **TMS Admin → Configuration**, select the **Reset Reference Data** button ONCE and wait for the email indicating completion. This process completes the following tasks: 1. Deploys the Platform Event subscriber configuration settings for the following events. > [!WARNING] > **Note:** A red error banner displays on TMS Admin → Configuration if any of the configuration settings are not installed. Navigate to **Setup → Deployment Status** to confirm that the Platform Events are installed. If any Event is not installed, the following error is displayed. > > ![Error message indicating Platform Events are not installed and require the Reset Reference Data job.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Release Update Job - Missing PE Configs - 1.png?sv=2026-02-06&spr=https&st=2026-07-28T21%3A20%3A38Z&se=2026-07-28T21%3A35%3A38Z&sr=c&sp=r&sig=VaDHCOOGu7%2F94kZ8E1tBhjb59fkFr1rPI2B5Cv3e46k%3D?sv=2026-02-06&spr=https&st=2026-07-28T21%3A28%3A52Z&se=2026-07-28T21%3A43%3A52Z&sr=c&sp=r&sig=V4JYhec%2F1UUcz1Q2UyuaXHyUXGwo9BhK7oRc9QhNxU4%3D?sv=2026-02-06&spr=https&st=2026-07-29T01%3A12%3A17Z&se=2026-07-29T01%3A27%3A17Z&sr=c&sp=r&sig=hej5PyDtHSLmPsj3EAyk42%2FTxfj2haA%2F%2F24xQXEItpw%3D) 1. EDI Event 2. Fleet Management Event 3. Queued Transaction Event 2. The Commodity, Line Item, and Rate Entry Calculations objects have the following picklist values added to both the **Handling Units** and **Packaging Units** fields. 1. *Accessorials* 2. *Attachments* 3. *Buckets* 4. *Bunches* 5. *Cabinets* 6. *Cages* 7. *Cans* 8. *Carriers* 9. *Casks* 10. *Chests* 11. *Cores* 12. *Dry Bulk* 13. *Each* 14. *Envelopes* 15. *Feet* 16. *Firkins* 17. *Gaylords* 18. *Hampers* 19. *Hogsheads* 20. *Intermediate Bulk Container* 21. *Jars* 22. *Jerrycans* 23. *Kits* 24. *Lifts* 25. *Liquid Bulk* 26. *Loose* 27. *Mixed* 28. *Octabins* 29. *On Hanger or Rack in Boxes* 30. *Packed* 31. *Pails* 32. *Pipe Lines* 33. *Racks* 34. *Slip Sheets* 35. *Super Sacks* 36. *Totes* 37. *Trailers* 38. *Trunks* 39. *Tubs* 40. *Unpackaged* 41. *Van Pack* 42. *Vehicles* 43. *Wrapped* 3. Adds picklist values to the following fields: (Object → **Field** → *Picklist Value*) - Container → **Container Status** → *Arrived at Origin Port Rail Facility* - Container → **Container Status** → *Arrived at Rail Facility* - Container → **Container Status** → *Available at Offdock Facility* - Container → **Container Status** → *Available at Rail Facility* - Container → **Container Status** → *Barge Berthed at Destination* - Container → **Container Status** → *Barge Berthed at Origin Port* - Container → **Container Status** → *Barge Departed from Destination Port* - Container → **Container Status** → *Barge Departed from Origin* - Container → **Container Status** → *Booked* - Container → **Container Status** → *Delivered* - Container → **Container Status** → *Departed on Rail* - Container → **Container Status** → *Departed on Rail at Origin* - Container → **Container Status** → *Discharged at Transshipment Port* - Container → **Container Status** → *Discharged from Barge at Destination* - Container → **Container Status** → *Discharged from Barge at Origin Port* - Container → **Container Status** → *Discovered* - Container → **Container Status** → *Discovering* - Container → **Container Status** → *Empty Dropped Off at Trucker Yard* - Container → **Container Status** → *Empty Picked Up for Return* - Container → **Container Status** → *Empty Picked Up from Trucker Yard* - Container → **Container Status** → *Empty Ready for Pickup* - Container → **Container Status** → *Full Dropped Off at Trucker Yard* - Container → **Container Status** → *Full Ingated at Origin Rail Facility* - Container → **Container Status** → *Full Ingated to Offdock Facility* - Container → **Container Status** → *Full Ingated to Rail Facility* - Container → **Container Status** → *Full Outgated from Offdock Facility* - Container → **Container Status** → *Full Outgated from Rail Facility* - Container → **Container Status** → *Full Picked Up from Trucker Yard* - Container → **Container Status** → *Loaded* - Container → **Container Status** → *Loaded at Transshipment Port* - Container → **Container Status** → *Loaded on Barge at Destination Port* - Container → **Container Status** → *Loaded on Barge at Origin* - Container → **Container Status** → *Loaded on Rail* - Container → **Container Status** → *Loaded on Rail at Origin* - Container → **Container Status** → *Not Found* - Container → **Container Status** → *Unloaded from Rail* - Container → **Container Status** → *Unloaded from Rail at Origin Port* - Container → **Container Status** → *Vessel Arrived* - Container → **Container Status** → *Vessel Arrived at Transshipment Port* - Container → **Container Status** → *Vessel Berthed* - Container → **Container Status** → *Vessel Berthed at Transshipment Port* - Container → **Container Status** → *Vessel Departed* - Container → **Container Status** → *Vessel Departed from Transshipment Port* - Travel Credential → **Type** → *Transportation Worker Identification Credential required for Port Entry* - Travel Credential → **Type** → *Tanker Non dangerous Liquid or Gas* - Travel Credential → **Type** → *Combines HazMat and Tanker Endorsement for transportation of liquids or gases in tankers* - Travel Credential → **Type** → *Endorsement for Towing Double/Triple Trailers* - Travel Credential → **Type** → *Allows access to TSA controlled facilities* - Travel Credential → **Type** → *Government Security Clearance* - Travel Credential → **Type** → *Forklift* - Travel Credential → **Type** → *Learner’s Permit* - Travel Credential → **Type** → *Work Visa* - Travel Credential → **Type** → *Hazardous Material Endorsement* 4. Adds the **Status** picklist value dependency for Fleet Asset → **Type** → *Tanker*: - Available - Damaged - Empty - Hooked - In Shop - Loaded - Loading - Lost - Out of Service - Wrecked > [!WARNING] > **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. 1. Once the Release Update Job is completed, navigate to **Setup → Apex Triggers**. 1. Confirm the following Apex Triggers were deleted. They are replaced with new triggers during package installation. If any of the triggers listed below remain, perform the **delete** action to remove them. 1. **EDIEvent** 2. **FleetManagementEvent** 3. **QueuedTransactionEvent** 2. Navigate to **Setup → Object Manager** and select the *API Quote Log* object. 1. Choose the *Fields & Relationships* tab. 2. Select the **API Provider** field. 1. Find the *Values* section and click the **New** button. 2. Enter *SMC3 EVA* into the box. 3. Click **Save**. #### Optional Brokerage and Fleet Setup Freight Brokerage and Fleet orgs should complete the following optional steps as requested: 1. See documentation for configuring new functionality for the [SMC3 EVA](/previous-releases/docs/smc3-eva) integration. Add the following fields to the appropriate Lightning Record Pages (LRP). 1. Navigate to a Carrier Quote record. 1. Select **Setup → Edit Page**. 2. Drag the following fields onto the LRP. 1. Bill To 2. Bill To Override 3. Carrier Account Number 4. Customer API Access Id 5. External Quote Id 6. Payer 7. Payment Terms 8. Rate Type 2. Navigate to a Carrier Service record. 1. Select **Setup → Edit Page**. 2. Drag the following fields onto the LRP. 1. Broker/3PL 2. Dynamic Pricing 3. Navigate to a Rate Entry record. 1. Select **Setup → Edit Page**. 2. Drag the following fields onto the LRP. 1. Bill To 2. Bill To Override 3. Carrier Account Number 4. Payer 5. Payment Terms 4. Navigate to a Shipper/Consignee Transportation Profile record. 1. Select **Setup → Edit Page**. 2. Drag the following fields onto the Shipper/Consignee LRP. 1. Customer API Access Id 2. Complete the following steps for OpenTrack container tracking feature. Integration setup instructions are available [here](/previous-releases/docs/opentrack-container-tracking). Revenova provides a packaged Lightning Record Page configured for the OpenTrack integration. Complete step **a** below to use the provided LRP or step **b** for any custom Container pages. 1. Assign the Revenova-configured Container Lightning Record Page (LRP) for OpenTrack integration users. 1. Select **Setup → Object Manager**. 2. Find and choose the Container object. 3. Select the Page Layouts tab. 4. Click the **Page Layout Assignment** button. 1. Click the **Edit Assignment** button. 2. Select all of the profiles and from the Page Layout to Use dropdown, choose *Container - Revenova Default*. 3. Click **Save**. 2. Add the following fields to custom Container Lightning Record Page (LRP) or page Layouts: 1. Navigate to a Container record. 1. Select **Setup → Edit Page**. 2. Drag the following fields onto the LRP or page layout. 1. Appointment Date 2. Appointment Time 3. Carrier Release Date 4. Carrier Release Time 5. Current Vessel 6. Current Vessel IMO Number 7. Customer Container Tracking Link 8. Customs Release Date 9. Customs Release Time 10. Demurrage Incurred 11. Demurrage Incurred at Rail 12. Demurrage Owed 13. Demurrage Owed at Rail 14. Destination Timezone 15. Document Cutoff Date 16. Document Cutoff Time 17. Final Rail Station Info 18. Individual Container Tracking 19. Inland Transit Number 20. Is Rail Move 21. Last Free Date - Demurrage (D) 22. Loading Vessel 23. Loading Vessel IMO Number 24. Origin Timezone 25. Port of Discharge Geolocation 26. Port of Load Geolocation 27. Rail Carrier Name 28. Rail Cutoff Date 29. Rail Cutoff Time 30. Rail Earliest Return Date 31. Rail Earliest Return Time 32. Rail Last Free Date - Demurrage (D) 33. Rail Last Free Time - Demurrage (D) 34. Receiving Facility Info 35. Seal Number 36. SL Last Free Date - Demurrage (D) 37. SL Last Free Time - Demurrage (D) 38. Steamship Line 39. Terminal of Discharge Info 40. Terminal of Load Info 41. Trade Type 42. Trucking Carrier Name 43. Vessel IMO Number 44. Voyage Number 45. Yard Location Info 3. Click **Save**. 4. Add the following Related List - Single to the Container LRP on the *Related* tab. 1. Container Events 2. Holds 5. Click **Save**. 3. Complete the following steps to use the [**DAT Contribute API**](/previous-releases/docs/dat#dat-contribute-api): > [!WARNING] > **Caution**: If you’re transitioning from the custom flat file integration to DAT Contribute, contact Revenova Support to turn off that custom integration and email [dataops@dat.com](mailto:dataops@dat.com) to inform DAT of the transition. 1. Navigate to and select the DAT 2 credential card on the TMS Admin → Credentials → Global Services tab. Find and *Check* the **DAT Contribute API** field. 2. Set the **DAT Mode** field on each Mode record that should be sent to the DAT Contribute API in TMS Admin → [Modes](/previous-releases/docs/mode-setup). 3. Ensure that the **USD - U.S. Dollar** currency is active in the org by going to Setup → Manage Currencies. The org must have the USD currency; otherwise, the sent data cannot be processed by DAT. #### Optional Fleet-Only Setup Fleet Management orgs should complete the following additional optional steps as requested. 1. Create [Trip Plan Validations](/previous-releases/docs/trip-plan-validations) and [Fleet Notifications](/previous-releases/docs/fleet-notifications) in the [Carrier Transportation Profile](/previous-releases/docs/carrier-transportation-profile#related-lists1) to warn and prevent users from creating or dispatching Trip Plans with potential issues. 2. Enable the **Show Deadhead Calculator** feature in TMS Admin → Configuration in the Fleet Management Section to use the [Deadhead Calculator](/previous-releases/docs/deadhead-calculator) for deadhead distance in the Fleet Load view. 3. Existing Fleet Management customers using the integration with [Catena](/previous-releases/docs/catena-eld-aggregator) should switch from the obsolete Fleet Management Job 2 to the faster and more efficient Fleet Management Job 4. 1. Navigate to TMS Admin → Configuration and find the Fleet Management section. Set the following field values. 1. Set the **Fleet Management Job** field to *Fleet Management Job 4*. 2. Click **Save**. 2. Assign all available platform cache to rtms. 1. From **Setup**, search for and select *Platform Cache*. 2. Click the *Edit* link for the **rtms** record. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Installation Guide - 3.jpg?sv=2026-02-06&spr=https&st=2026-07-28T21%3A20%3A38Z&se=2026-07-28T21%3A35%3A38Z&sr=c&sp=r&sig=VaDHCOOGu7%2F94kZ8E1tBhjb59fkFr1rPI2B5Cv3e46k%3D?sv=2026-02-06&spr=https&st=2026-07-28T21%3A28%3A52Z&se=2026-07-28T21%3A43%3A52Z&sr=c&sp=r&sig=V4JYhec%2F1UUcz1Q2UyuaXHyUXGwo9BhK7oRc9QhNxU4%3D?sv=2026-02-06&spr=https&st=2026-07-29T01%3A12%3A17Z&se=2026-07-29T01%3A27%3A17Z&sr=c&sp=r&sig=hej5PyDtHSLmPsj3EAyk42%2FTxfj2haA%2F%2F24xQXEItpw%3D) 3. In the *Org Cache Allocation* section find the **Organization** field. 4. Enter *3*. If necessary, enter *0* in **Provider Free**. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Installation Guide - 4.jpg?sv=2026-02-06&spr=https&st=2026-07-28T21%3A20%3A38Z&se=2026-07-28T21%3A35%3A38Z&sr=c&sp=r&sig=VaDHCOOGu7%2F94kZ8E1tBhjb59fkFr1rPI2B5Cv3e46k%3D?sv=2026-02-06&spr=https&st=2026-07-28T21%3A28%3A52Z&se=2026-07-28T21%3A43%3A52Z&sr=c&sp=r&sig=V4JYhec%2F1UUcz1Q2UyuaXHyUXGwo9BhK7oRc9QhNxU4%3D?sv=2026-02-06&spr=https&st=2026-07-29T01%3A12%3A17Z&se=2026-07-29T01%3A27%3A17Z&sr=c&sp=r&sig=hej5PyDtHSLmPsj3EAyk42%2FTxfj2haA%2F%2F24xQXEItpw%3D) 5. Click **Save**. 3. Confirm all available platform cache is assigned to *tms*. The image below shows an org with all available platform cache assigned to *tms*. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Setup - Platform Cache - 1(1).jpg?sv=2026-02-06&spr=https&st=2026-07-28T21%3A20%3A38Z&se=2026-07-28T21%3A35%3A38Z&sr=c&sp=r&sig=VaDHCOOGu7%2F94kZ8E1tBhjb59fkFr1rPI2B5Cv3e46k%3D?sv=2026-02-06&spr=https&st=2026-07-28T21%3A28%3A52Z&se=2026-07-28T21%3A43%3A52Z&sr=c&sp=r&sig=V4JYhec%2F1UUcz1Q2UyuaXHyUXGwo9BhK7oRc9QhNxU4%3D?sv=2026-02-06&spr=https&st=2026-07-29T01%3A12%3A17Z&se=2026-07-29T01%3A27%3A17Z&sr=c&sp=r&sig=hej5PyDtHSLmPsj3EAyk42%2FTxfj2haA%2F%2F24xQXEItpw%3D) 4. Navigate to the Batch Process Monitor and run Fleet Management Job 4. 1. The existing Fleet Management Job 2 is still supported and may be used for troubleshooting purposes. #### Final Steps 1. Revenova has included additional security functionality for many fields in the TMS. 1. See the [Required Field Scanner](/previous-releases/docs/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. 1. Confirm all required TMS batch jobs are running and/or scheduled. See the [Batch Processes](/previous-releases/docs/batch-processes) article for suggested run times. ### Release Spring ’26 Field/Field Set Modification Summary - TMS > [!NOTE] > **Field Set Note**: Review fields added by the installation and set CRUD access as needed. | **Object** | **Field/Field Set** | **Action** | **Notes** | | --- | --- | --- | --- | | API Quote Log | API Provider | Modify | Add *SMC EVA* to picklist values. | | Carrier Quote | Bill To | Add | New field to support SMC3 EVA. | | Carrier Quote | Bill To Override | Add | New field to support SMC3 EVA. | | Carrier Quote | Carrier Account Number | Add | New field to support SMC3 EVA. | | Carrier Quote | Customer API Access Id | Add | New field to support SMC3 EVA. | | Carrier Quote | External Quote Id | Add | New field to support SMC3 EVA. | | Carrier Quote | Payer | Add | New field to support SMC3 EVA. | | Carrier Quote | Payment Terms | Add | New field to support SMC3 EVA. | | Carrier Quote | Rate Type | Add | New field to support SMC3 EVA. | | Carrier Service | Broker/3PL | Add | New field to support SMC3 EVA. | | Carrier Service | Dynamic Pricing | Add | New field to support SMC3 EVA. | | Container | Appointment Date | Add | New field to support OpenTrack container tracking. | | Container | Appointment Time | Add | New field to support OpenTrack container tracking. | | Container | Carrier Release Date | Add | New field to support OpenTrack container tracking. | | Container | Carrier Release Time | Add | New field to support OpenTrack container tracking. | | Container | Container Status | Modify | Added picklist values to support OpenTrack container tracking. | | Container | Current Vessel | Add | New field to support OpenTrack container tracking. | | Container | Current Vessel IMO Number | Add | New field to support OpenTrack container tracking. | | Container | Customer Container Tracking Link | Add | New field to support OpenTrack container tracking. | | Container | Customs Release Date | Add | New field to support OpenTrack container tracking. | | Container | Customs Release Time | Add | New field to support OpenTrack container tracking. | | Container | Demurrage Incurred | Add | New field to support OpenTrack container tracking. | | Container | Demurrage Incurred at Rail | Add | New field to support OpenTrack container tracking. | | Container | Demurrage Owed | Add | New field to support OpenTrack container tracking. | | Container | Demurrage Owed at Rail | Add | New field to support OpenTrack container tracking. | | Container | Destination Timezone | Add | New field to support OpenTrack container tracking. | | Container | Document Cutoff Date | Add | New field to support OpenTrack container tracking. | | Container | Document Cutoff Time | Add | New field to support OpenTrack container tracking. | | Container | Final Rail Station Info | Add | New field to support OpenTrack container tracking. | | Container | Individual Container Tracking | Add | New field to support OpenTrack container tracking. | | Container | Inland Transit Number | Add | New field to support OpenTrack container tracking. | | Container | Is Rail Move | Add | New field to support OpenTrack container tracking. | | Container | Last Free Date - Demurrage (D) | Modify | Updated help text to support OpenTrack container tracking. | | Container | Last Free Time - Demurrage (D) | Modify | Updated help text to support OpenTrack container tracking. | | Container | Last Free Date - Detention (D) | Modify | Updated help text to support OpenTrack container tracking. | | Container | Last Free Time - Detention (D) | Modify | Updated help text to support OpenTrack container tracking. | | Container | Last Handling Facility Info | Add | New field to support OpenTrack container tracking. | | Container | Loading Vessel | Add | New field to support OpenTrack container tracking. | | Container | Loading Vessel IMO Number | Add | New field to support OpenTrack container tracking. | | Container | Origin Timezone | Add | New field to support OpenTrack container tracking. | | Container | Port of Discharge Geolocation | Add | New field to support OpenTrack container tracking. | | Container | Port of Load Geolocation | Add | New field to support OpenTrack container tracking. | | Container | Rail Carrier Name | Add | New field to support OpenTrack container tracking. | | Container | Rail Cutoff Date | Add | New field to support OpenTrack container tracking. | | Container | Rail Cutoff Time | Add | New field to support OpenTrack container tracking. | | Container | Rail Earliest Return Date | Add | New field to support OpenTrack container tracking. | | Container | Rail Earliest Return Time | Add | New field to support OpenTrack container tracking. | | Container | Rail Last Free Date - Demurrage (D) | Add | New field to support OpenTrack container tracking. | | Container | Rail Last Free Time - Demurrage (D) | Add | New field to support OpenTrack container tracking. | | Container | Receiving Facility Info | Add | New field to support OpenTrack container tracking. | | Container | Seal Number | Add | New field to support OpenTrack container tracking. | | Container | SL Last Free Date - Demurrage (D) | Add | New field to support OpenTrack container tracking. | | Container | SL Last Free Time - Demurrage (D) | Add | New field to support OpenTrack container tracking. | | Container | Steamship Line | Add | New field to support OpenTrack container tracking. | | Container | Terminal of Discharge Info | Add | New field to support OpenTrack container tracking. | | Container | Terminal of Load Info | Add | New field to support OpenTrack container tracking. | | Container | Trade Type | Add | New field to support OpenTrack container tracking. | | Container | Trucking Carrier Name | Add | New field to support OpenTrack container tracking. | | Container | Vessel IMO Number | Add | New field to support OpenTrack container tracking. | | Container | Voyage Number | Add | New field to support OpenTrack container tracking. | | Container | Yard Location Info | Add | New field to support OpenTrack container tracking. | | Container Event | | Add | New object to support a timeline event for a container. | | Container Event | Container | Add | New field to support container events. | | Container Event | Container Event Name | Add | New field to support container events. | | Container Event | Event Date | Add | New field to support container events. | | Container Event | Event Time | Add | New field to support container events. | | Container Event | Event Type | Add | New field to support container events. | | Container Event | Geolocation | Add | New field to support container events. | | Container Event | Is Estimate | Add | New field to support container events. | | Container Event | Location Summary | Add | New field to support container events. | | Container Event | Timezone | Add | New field to support container events. | | Document Options | Payer | Add | New field to support SMC3 EVA. | | Document Options | Payment Terms | Add | New field to support SMC3 EVA. | | Fleet Asset | Status | Modify | Add “Tanker” as the controlling field to some existing status options to support Trip Plan Validations. | | Fleet Asset | Type | Modify | Add “Tanker” value to support Trip Plan Validations. | | Fleet Notification | | Add | New object to support the Fleet Notifications feature. | | Fleet Notification | Company/Division | Add | New field to support Fleet Notifications. | | Fleet Notification | Days Out | Add | New field to support Fleet Notifications. | | Fleet Notification | Notification Type | Add | New field to support Fleet Notifications. | | Fleet Notification Log | | Add | New object to support the Fleet Notifications feature. | | Fleet Notification Log | Acknowledged By | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Acknowledged Datetime | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Days Until Expiration | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Driver | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Driver Manager | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Fleet Asset | Add | New field to support Fleet Notifications. | | Fleet Notification Log | Message | Add | New field to support Fleet Notifications. | | Hold | Amount Due | Add | New field to support container fees. | | Hold | Code | Add | New field to support container fees. | | Hold | Comments | Add | New field to support container fees. | | Hold | Container | Add | New field to support container fees. | | Hold | Hold Number | Add | New field to support container fees. | | Hold | Reported Datetime | Add | New field to support container fees. | | Hold | Resolved Datetime | Add | New field to support container fees. | | Hold | Type | Add | New field to support container fees. | | Rate Entry | Bill To | Add | New field to support SMC3 EVA. | | Rate Entry | Bill To Override | Add | New field to support SMC3 EVA. | | Rate Entry | Carrier Account Number | Add | New field to support SMC3 EVA. | | Rate Entry | Payer | Add | New field to support SMC3 EVA. | | Rate Entry | Payment Terms | Add | New field to support SMC3 EVA. | | Transportation Profile | Customer API Access ID | Add | New field to support SMC3 EVA. | | Travel Credential | Type | Modify | Add new picklist options to support the Trip Plan Validations and Fleet Notifications feature. | | Trip Plan Leg | Calculated Fallback Datetime | Add | New field to support Trip Plan Validations. | | Trip Plan Segment | Calculated Fallback Datetime | Add | New field to support Trip Plan Validations. | | Trip Plan Validation | | Add | New object to support the Trip Plan Validations feature. | | Trip Plan Validation | Alert Type | Add | New field to support Trip Plan Validations. | | Trip Plan Validation | Company/Division | Add | New field to support Trip Plan Validations. | | Trip Plan Validation | Validation Type | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | | Add | New object to support the Trip Plan Validations feature. | | Trip Plan Validation Log | Alert Type | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Driver | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Fleet Asset | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Message | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Shown Datetime | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Shown To | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Trip Plan Segment | Add | New field to support Trip Plan Validations. | | Trip Plan Validation Log | Trip Plan Validation | Add | New field to support Trip Plan Validations. |