Autopilot: Understanding rule creation logic

Turvo’s automation features provide the ability to create rules for your Turvo tenant to automate certain functions based on the circumstances of the action. Turvo’s most robust automation feature is Autopilot, where Admin-level users and above can create logic statements to configure rules for automations that should occur in specific circumstances. This kind of logic statement is also found in other automation features, such as notification rules and customer account thresholds. 

In this article, we’ll introduce you to rule creation logic and spotlight features of your Turvo tenant where these rules are created and managed.

Rule creation logic

Autopilot and other automation features in Turvo use When/If/And/Then statements to dictate the action that takes place. Try thinking of the scenario you need to create rules for by putting the criteria in sentence form.

  • When: The scenario that the rule is being created to address.
    • Most When statements create exception rules, but others create accessorial acceptance/rejection rules or payable discrepancy rules, or billable rate application rules.

When [X] occurs

  • If: The main criteria that must be true during the scenario that defines the rule.
    • In some scenarios, you are able to use a drop-down to choose which If statement is needed for the rule. In others, a particular If (Required) field appears that must be configured.
    • The If statement usually comes with additional fields, such as text fields, drop-downs, and Is/Is Not toggles where you define the statement.

When [X] occurs, if [Y] is true

  • And: Additional criteria that narrow the circumstances defining the rule.
    • Most scenarios allow for multiple And statements to be added on using the +Add Criteria button.
    • In some scenarios, an And (Required) field is added automatically.

When [X] occurs, if [Y] and [Z] are true…

  • Then: The action taken by Turvo based on the criteria in the previous statements. This appears within the Action section of the modal, and is not explicitly marked as “Then” within the user interface.
    • In some scenarios, the Action section has a drop-down that allows you to change the action taken by Turvo.

When [X] occurs, if [Y] and [Z] are true, then take Action [A].

Protip: Check out our video, Automate workflows with Autopilot rules to see the logic behind setting up rules for your tenant in action. 

Where Autopilot rules are made:

Autopilot rules can be made by Admin-level users and above in the following two sections of the Admin Console > Rules page.

To create an Autopilot rule for shipments or orders:

  1. Navigate to the Admin console by clicking on your profile icon in the top right corner of your dashboard.
  2. Select Admin console from the drop-down menu.

image1.png

  1. Click the Rules card.

image8.png

  1. On the Rules page:
    1. Click the Shipment header or the Order header in the column to the left to create rules for each respective entity.
    2. In the Shipment or Order rules view, click the Autopilot header to expand the section.

image6.gif

  1. Click + Create rule to open the Create shipment rule or Create order rule modals.

From here, you can create rules to automate functions on your tenant. Check out the articles below to learn more about leveraging Autopilot for different types of automation:

Note: Some of these features may not be available on all tenants by default.

Other automation features that use the same rule logic

The following features use the same When/If/And/Then rule logic found in Autopilot to configure other automations on your Turvo tenant:

  • User notification rules: All users can create their own notification rules, allowing Turvo to notify them when certain actions occur on the tenant, such as shipment updates or exception creation. 
  • Tenant-level notification rules: Admin-level users and above can configure notification rules that can apply to all users on your tenant with a specific user role via Admin Console > Rules > User > Tenant notifications.
  • Customer Threshold rules: In Admin Console > Rules > Customer > Thresholds and Accounts > Customers > [Profile] > Details > Thresholds, Admin-level users can configure time thresholds for when a shipment is considered approaching late or running late to its next destination, which Turvo uses to apply the #ApproachingLate and/or #RunningLate tags to the shipment.
  • Order optimization: The Optimization feature found in Admin console > Settings > Order > Optimization allows you to create rules to determine the minimum and maximum weight, volume, and units for equipment types. This will help prevent undersized or oversized shipments in the automatic order to shipment planning process.
    • See our Understanding and updating tenant settings article to learn more about using optimization rules.
    • Note: The rules creation modal found in this section is not an exact match for the other rule creation features detailed above, but it still uses a When/If/Then structure.

Note: Some of these features may not be available on all tenants by default.

Was this article helpful?

0 out of 0 found this helpful