Conditional statements are a type of setting used across FormBuilder where logic is needed to define how certain parts of a form should operate. For an introduction to conditional statements and where they are found, visit ATLAS FormBuilder - Introduction to Conditional Statements.

Each conditional statement entry field provides a dropdown list of condition types to choose from. Selecting a condition type from this list provides at least one additional field, the customization of which allows the user to create one of the conditions that specifies the conditional statement's logic.

Conditional statement entry fields only allow for the input of one condition by default, though three logical operators (And, Or, Not) are also provided as selectable options, and can be used to chain together more complex conditional statements. For more information on these logical operators and their effects, visit ATLAS FormBuilder - Logical Operators in Conditional Statements.

The full list of selectable options when building a conditional statement is 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.
  
  For more information on the text merge fields available in FormBuilder, visit ATLAS FormBuilder - Text merge fields.
  
  

• 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.
  
  

• Response Saved for Later: Activates in relation to the state of a form response being saved using the "Save and Return Later" button in the survey view. Asks whether the condition should check for responses that have or have not used the option.
  
  NOTE: Only available for selection in forms that have enabled the "Allow Save and Return Option" setting under Form Properties.
  
  

• 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.
  
  

• Form Registered State: Activates in relation to a form response's registered state. Asks whether the condition should check for responses that are registered, or for responses that have not been registered.
  
  NOTE: Only available for selection in event registration forms in advanced mode.
  
  

• Latest Reservation Attempt: Activates in relation to a form response's last attempt at reserving a registration slot. Asks whether the condition should check for the latest reservation attempt being successful or unsuccessful.
  
  NOTE: Only available for selection in event registration forms in advanced mode.
  
  

• 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.