Skip to main content

Overview

Automations let you define rules that are evaluated when a trigger event occurs. If the rule evaluates to true, the specified action will be performed. As an example, whenever a case is ingested from a scanner, based on a rule like if Item Name is "Crown" you can automatically add a crown product to the case.

An advanced example is to chain several automations together:

  • When the IOS Case Create event fires, first assign a doctor-office pair.

  • In another IOS Case Create event, automatically add products to the case.

  • As those products are added, run additional product/model rules on the Product Added event.

  • Finally, based on the complete set of products, run another automation that selects the case type on the Product Added/Removed event.

All of these steps occur during the initial IOS Case Create trigger, before the case even appears in the case list.

Creating an Automation​

  1. Navigate to Admin -> Settings -> Automations
  2. Select the event that will trigger the automation
  3. Click on "Create Automation"
  4. Add a name, rules, and actions
  5. Click on "Save"

1. Triggers​

  • IOS Case Create
  • Product Added/Removed
  • Additional Step Added
  • Case Tag selected (upcoming)
  • Doctor-office pair selected (upcoming)

2. Rules​

Rules are evaluted during a trigger event, and if the rules are met, the actions will be performed. The fields available for the rules depend on the trigger event. As an example, for the IOS Case Create trigger, the fields that are available pertain to fields we ingest from the scanner.

3. Actions​

Actions perform once an event is triggered and the rules are met. For the IOS Case Create trigger, the actions available are adding products, and assigning a doctor-office pair.

Available Actions​

  • Add productss
  • Assign doctor-office pair
  • add tag
  • select case type
  • create an additional step
  • send a case message
  • put a case on hold

4. Putting it all together​

IOS Case Create trigger​

For the IOS Case create trigger, you can either specify one or more products or doctor-office pair to assign to the case.

The IOS Case Create trigger gets triggered on both

  1. When a case is ingested from an external scanner automatically. We first assign the doctor-office pair, then if there are products we can assign, we'll assign them to that case.
  2. If no doctor-office pair was automatically assigned to the case, then after a user manually assigns a doctor-office pair, we'll trigger the automation to assign the products to the case.

Product Added/Removed trigger​

The Product Added/Removed trigger gets triggered when a product is added to or removed from a case. For the case type selection, the rules available are based on the product restoration types dropdown value, which after evaluation will use an action of selecting a case type on a Case.

This trigger is also used for product automations, but only when a product is added to a case, never when a product is removed from a case. This happens in 2 places:

  1. When a case is ingested, and products are added to the case via the IOS Case Create automations that add products, we will run these automations to add the products to the case.
  2. When addding a product to a case on the case page, when clicking "Add X Products" we will first see if there are any automations that would add products to the case, if there are, we will show you the newly added products from the automations in the Dialog/staging area, and ask you to confirm the products to be added to the case, otherwise, the products will just be added to the case and no confirmation is needed.

Additional Step Added trigger​

The Additional Step Added trigger gets triggered when an additional step is added to a case. You can match based on the additional step's template additional step name or description. The actions available when an additional step is added to a case are:

  • add another additional step
  • send a case message
  • put a case on hold