Routing triggers allow FormBuilder users to fine-tune the specific times or circumstances in which they activate, using settings called trigger conditions. There are numerous types of trigger conditions available, and they can be combined using simple logical operations.

To edit a routing trigger's conditions, first navigate to the desired routing trigger's settings page, or create a new routing trigger. For more information on how to accomplish this, visit ATLAS FormBuilder - Adding and Editing Routing Triggers.

Once on your trigger's settings page, locate the Trigger Condition section.

Inside this section is a dropdown list that contains several different types of trigger conditions or logical operations to choose from. They are as follows:

• Answer Value: Activates in relation to an answer value of one of the form's questions. Asks for the question whose value will be checked, and for a "match type," meaning the type of check performed against this answer value. The available options for match types are:
  
  
  • Defined Choice Match: Provides a list of the question's defined choices. The answer value must match whichever choice you select from this list. This option is only available for question types with multiple defined options, such as a radio button or dropdown list question.
    
    
  • Exact Value Match: The question's answer value must match the exact value that you type into the provided field.
    
    
  • Regular Expression Match: The question's answer value must match the value of a regular expression that you type into the provided field.
    
    
  • Has Value: Provides a choice of whether the question must have an answer value, or must have NO answer value.
    
    
• Text Merge Field: Activates in relation to the value of one of the form's text merge fields (including the answer values of questions). Asks for the text merge field to be checked, and the "match type." The available options for match types are the same as for the Answer Value condition, EXCEPT for Defined Choice Match.
  
  
• Form Submit Date: Activates in relation to the date and time at which form response is submitted. Asks whether the condition should look for responses submitted between two separate dates, or for responses submitted within a certain number of days, weeks, or months of the current date.
  
  
• Form Submit State: Activates in relation to a form response's submission state. Asks whether the condition should check for responses that have currently been submitted at least once, or for responses that have not yet been submitted.
  
  
• Form Cancelled State: Activates in relation to a form response's cancellation state. Asks whether the condition should check for responses that have been canceled, or for responses that have not been canceled.
  
  
• Form Waitlisted State: Activates in relation to a form response's waitlisted state. Asks whether the condition should check for responses that are on a waiting list, or for responses that are not on a waiting list.
  
  
• Payment Promised: Activates in relation to the promised state of a form response's payment. Asks whether the condition should check for responses whose payments are promised (such as a check payment not yet received), or for responses whose payments are confirmed (a payment that has been successfully received).
  
  
• Payment Status: Activates in relation to a form response's payment status. Asks whether the condition should check for responses whose have made payments, partially paid for something, refunded a payment, or have not paid for something yet.
  
  
• Payment Method: Activates in relation to the payment method used on a form response. Asks if the condition should check for responses that made payments with IPay, check payment, or manual adjustment.
  
  
• Group Membership: Activates if a user associated with a form response is a member of a specific security group. Asks if the user in question should be the response submitter, the response's last modifying user, or the user entered into one of the form response's Campus Person questions. Also asks which of the security groups in the form's form group should be checked for membership.
  
  
• Current Date: Activates in relation to the current date, and provides two date fields. If both are filled out, the condition will activate when the current date is between the two entered dates. If only the first field is filled out, the condition will activate when the current date is after or equal to the entered date. If only the second field is filled out, the condition will activated when the current date is before or equal to the entered date.
  
  
• Current Phase: Activates if the form response's current phase matches the selected phase.
  
  
• Associated Period: Activated if the form response's associated period matches the selected period.
  
  
• And: Logical operator that allows for multiple child conditions. Activates if all child conditions are met.
  
  
• Or: Logical operator that supports multiple child conditions. Activates if any of its child conditions are met.
  
  
• Not: Logical operator that supports one child condition. Activates if its child condition is NOT met.

Only one "base" trigger condition can be selected, but through the use of logical operators, multiple conditions can be strung together to create complex logic for your condition.

Make sure to save your changes once you are finished editing your routing trigger's conditions.