Loading...
Wisenet

      How To Create an Automation

       

      This is an EARLY ACCESS feature.

      Required LRM Access: Owner

      Automation Triggers

      1

      What is an Automation Trigger?

      A trigger is the event that starts your automation. A trigger can have conditions that must be true for the automation to run.

      A trigger entity is the type of record that the automation is based on. Currently supported entities are:

      1. Course Enrolment
      2. Unit Enrolment
      3. Quote
      4. Course Offer

      A trigger type is the kind of change to the entity that will fire the automation. Currently supported types are:

      1. Entity Created (when a new record is added)
      2. Entity Updated (when an existing record is changed)

      Each automation can have only one trigger, but you can attach multiple action groups to it.

      2

      Add an Automation Trigger

      1. Navigate to LRM > Settings > Automation (under Automation)
      2. Click Create Automation
      3. Enter a Trigger Code (unique identifier)
      4. Enter a Trigger Name (something meaningful to you and your team)
      5. Select a Trigger Entity (e.g. Course Enrolment)
      6. Decide if you want to set the trigger on a custom field
        • If yes, select the custom field
      7. Select a Trigger Type (Entity Created or Entity Updated)
        • If you are setting the trigger on a custom field, the trigger type must be Entity Updated.
      8. Click Save.

      Once saved, you cannot change the trigger entity or the trigger type.

      The automation will save as inactive. You must add at least one action group with one action before activating the automation.

      (Optional) Add Trigger Conditions

      3

      What are Trigger Conditions?

      Conditions refine when your automation will run. They prevent the automation from firing every single time a trigger event occurs.

      You can apply conditions to:

      • The trigger entity itself
      • Custom fields on the trigger entity
      • The parent entity of the trigger entity

      A condition includes:

      1. Entity (e.g. Course Enrolment)
      2. Field (e.g. Status)
      3. Condition type
        • Value is
        • Value changed from
        • Value changed to
      4. Evaluator (e.g. equals, does not equal, greater than, contains)
      5. Value (depends on field + evaluator)

      Notes:

      • If the trigger is Entity Created,  you can only use Value Is.
      • If your evaluator is has a value or has no value, you do not need to enter a value.

      4

      What is a Condition Group?

      Conditions support both AND and OR logic.

      • Condition group = a set of conditions joined by AND.

      • Multiple groups can be joined by OR.

      Example:

      [Condition 1 AND Condition 2] OR [Condition 3 AND Condition 4]

      This means:

      • All conditions in a single group must be true for that group to pass.

      • If any group passes, the automation will trigger.

      5

      Add Trigger Conditions

      1. Navigate to LRM > Settings > Automation
      2. Click on the automation name to open the Automation Detail page.
      3. Click Add Condition Group
      4. In the group, click Add Condition
      5. Choose:
        • Entity (options depend on your trigger entity)
        • Field
        • Condition type (Value Is, Value Changed From, Value Changed To)
        • Evaluator (e.g., equals, does not equal, contains, is greater than)
        • Value (if required)
      6. (Optional) repeat to add more conditions inside the same group.
      7. (Optional) add more condition groups if needed.
      8. Click Save.

      Notes:

      • If the trigger type is Entity Created, you can only choose Value Is as a condition type.
      • If your evaluator is has a value or has no value, you do not need to enter a value.

      What is the difference between Value Is and Value Changed To?

       

      If your trigger type is Entity Updated, you can add a condition where the value is something, or the value changes to something. These have a subtle but important difference.

      For example, if your trigger is Course Enrolment Updated:

      • No conditions → fires whenever any Course Enrolment field (except a custom field) changes.
      • Condition: Status Value Is “Active” → fires whenever any field (except a custom field) changes, as long as Status = Active.
      • Condition: Status Value Changed To “Active” → fires only when Status specifically changes to Active.

      Next Step

      Add and Edit an Automation Action Group