--- title: "Get Started with Revenova" slug: "getting-started-with-revenova" tags: ["Admin", "End User", "Expanded Content", "Getting Started"] updated: 2026-07-31T21:21:10Z published: 2026-07-31T21:21:10Z canonical: "documents.revenova.com/getting-started-with-revenova" --- > ## 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. # Get Started with Revenova Revenova TMS (TMS) is the leading multi-modal Transportation Management System on the Salesforce AppExchange. As a fully-native force.com managed package, it seamlessly connects to your CRM environment and takes advantage of all the capabilities inherent in the Salesforce platform. These include mobile support, point-and-click reports and dashboards, anytime/anywhere access, and industry-leading reliability, scalability, and security. ## **Document Purpose** The purpose of this document is: 1. To direct everyday TMS users to resources that aid in the performance of their tasks. 2. To provide managers/team leaders with links to important configuration documentation. 3. To provide Salesforce administrators with resources for supporting the TMS. ## **Managed Package Installation** Please see the Revenova [TMS Installation Guide](/v1/docs/revenova-tms-installation-guide) for instructions to install the TMS into a Salesforce environment. ## **Salesforce Platform Help and Environment Configuration** Salesforce provides an extensive library of online text and video describing the capabilities of the Force.com platform and the CRM (and other) products it provides. As a native Salesforce application, the TMS is completely seamless within your Salesforce environment. Please click on the Help links and icons present on every page of the application to access these resources. Most configuration activities that are Salesforce platform-related are described with online help and training videos. Contact [Salesforce Help](https://help.salesforce.com/s/) with CRM and platform questions. Get the most out of Salesforce by completing [Trailheads](https://trailhead.salesforce.com/). Access the links on every page for the following platform-related activities. 1. [Adding](https://help.salesforce.com/s/articleView?id=sf.adding_new_users.htm&type=5) or modifying a user. 2. [Deactivating](https://help.salesforce.com/s/articleView?id=sf.how_to_deactivate_users.htm&type=5) a user. 3. [Adding, modifying, or deleting](https://help.salesforce.com/s/articleView?id=sf.admin_userprofiles.htm&type=5) a security profile. 4. [Changing a page layout](https://help.salesforce.com/s/articleView?id=sf.customize_layout.htm&type=5) for a specific record type or object. 5. [Adding, modifying, or deleting](https://help.salesforce.com/s/articleView?id=sf.basics_understanding_list_views_lex.htm&type=5) a tab-based list view. 6. [Creating dashboards and reports](https://help.salesforce.com/s/articleView?id=sf.analytics_overview.htm&type=5). 7. [Validation rules](https://help.salesforce.com/s/articleView?id=sf.fields_about_field_validation.htm&type=5) to ensure data integrity and TMS functionality. 8. Enable [Lightning Web Security](https://help.salesforce.com/s/articleView?id=000392327&type=1) for custom components. 9. Create [groups](https://help.salesforce.com/s/articleView?id=platform.user_groups.htm&type=5) and add users to apply permissions as necessary. ## **Explore TMS Documentation** Learn more about how the TMS functions. 1. Much of the TMS functionality is conducted on custom Salesforce [Lightning Web Components](/v1/docs/lightning-web-components-lwcs). 2. For security purposes, certain TMS fields may require adding to User Permission Sets. See the [Required Field Scanner](/v1/docs/required-field-scanner) to search by User for field permissions. 3. Connect to [3rd party integrations](/v1/docs/integrations) to send and receive data, track loads, and much more. 4. Customize and use the most important data with [Field Sets](/v1/docs/field-set-summary). 5. System administrators configure how the TMS operates with [TMS Admin](/v1/docs/tms-admin-components) and [TMS Accounting Admin](/v1/docs/tms-accounting-admin). 6. Learn how to set up, configure, and customize TMS Features. 7. Manage assets with the [Fleet Management](/v1/docs/fleet-management-2) module. 8. Track invoices, payables, and payments with [Accounting](/v1/docs/accounting-seed-1) packages. 9. Conduct TMS tasks with either an [API](/v1/docs/revenova-tms-web-services-guide) or [EDI](/v1/docs/edi-management-1) service. 10. For How-To, Troubleshooting, Customer Requests, Webinars, and many other resources, see the [Revenova Learning Center](https://revenova.my.site.com/learningcenter/s/login/). ## Critical Customer Responsibilities 1. Make sure you **maintain your security profiles and sharing settings** so that the appropriate capabilities and data are exposed to your various user groups. 1. See Salesforce documentation regarding [Profiles](https://help.salesforce.com/s/articleView?id=sf.admin_userprofiles.htm&type=5) and [Permission Sets](https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm&type=5). 2. See the [Required Field Scanner](/v1/docs/required-field-scanner) to search by User for required field permissions. 2. If you are using the [**Sales Tax**](/v1/docs/sales-taxes-1) object, ensure that the rates defined there are current and correct. 3. Salesforce requires that user email addresses are verified to enhance accountability and security when sending emails. Prior to the Salesforce Spring ‘25 release, a verification email was sent to each user once per release. When an org is updated to the Spring ‘25 release, a reminder email is no longer sent. See additional Salesforce information [here](https://help.salesforce.com/s/articleView?id=002183046&type=1). 1. *Unverified email addresses are not able to deliver email messages.* 2. Confirm an email address is verified by completing the following steps. 1. From the *View Profile* icon, select *Settings*. 2. Choose the Email section and select **My Email Settings**. 3. If a **Resend Verification Email** link is present next to the *What email address would you like to use as your return address?* setting, the email address is not verified. 1. If the **Resend Verification Email** link is not available, the user's email is verified. 3. This process is separate from the *Verified* setting next to the **Email field** on the User record. 4. All TMS users - including API Users, Email Loop Users, Carrier Portal Users, and Customer Portal Users require a Revenova TMS license to access TMS records. 1. Any Revenova add-on packages (PayIQ, TMS Analytics) require additional Revenova licenses to access package functionality. ## **Load Lifecycle** **Salesforce Path** The **Load Status** field value changes automatically as a load moves through its lifecycle as follows: 1. New load: **Unassigned** 2. Load with outstanding Carrier Quote Request(s): **Quotes Requested** 3. Load with carrier quote(s): **Quotes Received** 4. Load tendered to carrier: **Tendered** 5. Load with tender accepted by the carrier: **Assigned** 6. Load with tender declined by the carrier: **Declined** 7. Load with **First Stop Carrier ETA Date** populated: **Dispatched** 8. Load with **First Stop Arrival (or) Departure Date** populated: **In Transit** 9. Load with **Last Stop Arrival (or) Departure Date** populated: **Delivered** *This field can be set manually by the user if process automation is not used for a process step or steps.* > [!WARNING] > Picklist values *cannot* be added or changed on the **Load Status** field. *Do not change the field label or API name of the packaged picklist values.* This packaged field is used throughout the Revenova application and should not be changed. As a workaround, create a separate picklist field to denote additional load status and updates. In order to install ***any*** TMS upgrade, the **Load Status** picklist field must not be added to or adjusted. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Load Status - 1.jpeg) ## **Multi-Currency Considerations** The TMS can be used in both single- and multi-currency environments. > [!NOTE] > When **manually** creating a record, the user is responsible for selecting the appropriate currency. In multi-currency environments, the following currency code assignments occur for TMS **auto-created** records: | New Record Type | Scenario | **Currency Source** | | --- | --- | --- | | Account | Online Carrier Application | Default | | Account | New Load Customer/Shipper/Consignee | Default | | Account | Customer Portal New Load Customer/Shipper/Consignee | Default | | Fuel Index History | EIA API Integration | Parent Index | | Load | New Load Widget | Default Load Currency Setting | | Load | Load Clone | Cloned Load | | Load | Customer Portal | Default Load Currency Setting | | Load | Carrier Load for Freight Plan | Default Load Currency Setting | | Load Accessorial | Accessorial addition | Parent Load | | Line Item | New Load Creation/Modification | Parent Load | | Freight Plan | Freight Plan Creation | First Customer Load Added | | Freight Plan Load | Freight Plan Creation/Modification | Parent Load | | Customer Quote | DB Stored Rate Quote Auto-Creation | Rate Entry | | Customer Quote | Quote auto-creation on Customer Portal | Customer Account | | Customer Quote Accessorial | Quote auto-creation on Customer Portal | Parent Quote | | Customer Quote Tax | Tax Calculation | Parent Quote | | Customer Invoice | Invoice auto-creation | Customer Quote | | Customer Invoice Accessorial | Invoice auto-creation | Parent Invoice | | Customer Invoice Tax | Tax Calculation | Parent Invoice | | Carrier Quote | DB Stored Rate Quote Auto-Creation | Rate Entry | | Carrier Quote | Email Loop RFQ | Carrier Entered | | Carrier Quote | New quote record in Freight Quote Assistant | Carrier (Service) | | Carrier Quote Accessorial | Quote auto-creation or accessorial add | Parent Quote | | Rate Entry | Stored Rate creation for Customer Transportation Profile | Transportation Profile | | Stop | New Load Creation/Modification | Parent Load | | Transportation Profile | Batch Transportation Profile Creation | “Parent” Account | | Vendor Invoice | Auto-creation based on Carrier Quote | Carrier Quote | | Vendor Invoice Accessorial | Auto-creation based on Carrier Quote | Parent Invoice | See the Salesforce documentation to edit dated exchange rates in the organization. The **Load** object financial fields represent currency rollups from the child quote, invoice, and payment records. They are automatically converted to the load record’s currency based on the effective exchange rate for the **load’s expected ship date**. The Load Financial Summary is shown below as an example. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Load%20Financial%20Summary%202%20-%20with%20date-time(1).png) ## **Geolocation Support** The TMS supports geolocation services based on the following: 1. The platform geolocation support for account shipping addresses auto-populates the **ShippingLatitude** and **ShippingLongitude** account fields. 1. Make sure to turn on this feature from **Setup → Data Management → Data Integration Rules**. 2. Populating the Stop object **Geolocation** field when a load is created with no-account stops. 3. Using account and stop geolocations when **searching load/quote history** on the [Freight Quote Assistant](/v1/docs/freight-quote-assistant-1). 4. Populating **Miles Away** and **Kilometers Away** on stops for an in-transit load. 5. Populating **stop** and **driver locations** on route maps. 6. Geolocation-based truck posting search. 7. Geolocation-based delivering load search. # State and Country Picklist Support The TMS supports Salesforce environment with or without State and Country Picklists enabled. State and Country Picklists provide an error-proof mechanism for entering world-wide address information. Please see the [Salesforce online help](https://help.salesforce.com/s/articleView?id=sf.admin_state_country_picklists_configure.htm&type=5) for more information on this capability. > [!WARNING] > It is strongly recommended to add a **Default Country/Territory** for the org. Selecting a default country/territory helps to prevent state/province mismatches when receiving information from 3rd party vendors. > > ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/image-1708717828927.png) > > > > The state/province and countries added to the fields above may be made available across the TMS. To add them as selections, add the countries and/or states/provinces to the two global picklists: > > - Countries > - States This capability extends only to “native” Salesforce lead, account, and contact address fields. The following objects/fields do not inherit the Salesforce State and Country picklists. It is possible to add state/province and country picklist values directly to the following TMS fields, as desired: | Object | Field | Purpose | | --- | --- | --- | | Carrier Liability Limit | Country | Defines country where limit applies. | | Customs Broker | Origin Country | Define load origin countries handled by customs broker. | | Customs Broker | Destination Country | Define load destination countries handled by customs broker. | | Lane | Origin Country | Lane definition origin country. | | Lane | Origin State/Province | Lane definition origin state/province. | | Lane | Destination Country | Lane definition destination country. | | Lane | Destination State/Province | Lane definition destination state/province. | | Sales Tax | Origin Country | Origin country for taxation purposes. | | Sales Tax | Origin State/Province | Origin state/province for taxation purposes. | | Sales Tax | Destination Country | Destination country for taxation purposes. | | Sales Tax | Destination State/Province | Destination state/province for taxation purposes. | | Stop | State/Province | No-account stop location information. | | Stop | Country | No-account stop location information. | | Zone | State/Province | Zone definition location information. | | Zone | Country | Zone definition location information. | ## **Verifying Email Domains** Salesforce requires that user-authored and system-generated emails must have an authorized domain. [Org-wide email addresses](/v1/docs/organization-wide-email-address) do not appear in the “From” line without this authorization. Configure and verify DKIM keys or authorized within Salesforce before attempting to send emails. See Salesforce information for [DKIM setup](https://help.salesforce.com/s/articleView?id=sales.emailadmin_setup_dkim_key.htm&type=5) and [authorized email domains](https://help.salesforce.com/s/articleView?id=xcloud.security_user_email_verification_domain_auth.htm&type=5). ## **C****reate a Revenova Support Case** In the Revenova Learning Center, open a support case, check it’s status, and respond to cases. Check the current status of Salesforce [here](https://status.salesforce.com/). Any instances impacting the performance of the Salesforce platform are recorded here. 1. Sign in to the Revenova Learning Center. > [!NOTE] > Only Revenova customers with Admin login credentials to the Revenova Learning Center may create and manage cases. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Create%20Support%20-%201.jpeg) 2. Click the **Open a Case** tab. 3. Choose the Case Type. 4. For Subject, enter a title for the issue. 5. In the Description section, follow the prompts to describe the case: 1. Details about the issue or question. 2. Error messages that were received. 3. Troubleshooting steps that were followed. 6. Choose a Category and Integrations/Services (optional). 7. Choose the Instance Type where the issue was experienced or request an upgrade (optional). 1. When selecting Sandbox, please provide the Org Id. 8. Choose a Severity level (see below). 9. Attach files to add any relevant files to the case, such as error logs or screenshots. 10. Review the case details and click **Submit**. The Case Number and summary appear. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Create%20Support%20-%202.jpeg) ### **Describe the Case** Provide as much description as possible. Include relevant resource information, along with any other context that might help us understand the issue. For example, to troubleshoot an error message, include the error message in text format, a screenshot, user(s) experiencing the error, and the Load number where the error is encountered. When as much detail as possible is provided, the chances that the case can be resolved quickly is increased. ### **Choose a Severity** It is highly recommended to choose the highest severities *only* for cases that can't be worked around or that directly impact production applications. The following table lists the severity levels and example problems. | **Severity** | **Description and example** | | --- | --- | | Severity 4 | A general inquiry, how-to, routine technical issue, or to request an upgrade or feature. | | Severity 3 | Non-critical functions of Revenova or the Salesforce platform are behaving abnormally, but the issue is not time-sensitive. | | Severity 2 | Important functions of Revenova or the Salesforce platform are impaired or degraded. | | Severity 1 | Business is significantly impacted. Critical functions of Revenova or the Salesforce platform aren't available. | ## **C****reate a Customer Request (CR)** **Create a new CR** 1. Sign in to the [Revenova Learning Center](https://revenova.my.site.com/learningcenter/s/login/). 2. Click the **My Current Customer Requests** tab. 3. Click the **New Request** button at the top of the list. Enter the CR information into the modal. **Review Existing CRs and Reprioritize** 1. Sign in to the [Revenova Learning Center](https://revenova.my.site.com/learningcenter/s/login/). 2. Click the **My Current Customer Requests** tab. 3. Drag and drop the CR/row in the list to reprioritize as desired. 4. Make edits and click the CR hyperlink. The CR detail record page is where edits may be made. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/CR - 1.jpeg) ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/CR - 2.jpeg)