Introduction
Logic Rules are simple or complex rules that control the display and processing of registration forms.
Logic Rules are often referred to as "Form Logic."
Planners can use Logic Rules to create highly customized online registration forms based on the specific needs of their event registration process.
A logic rule always belongs to only one form.
A form may have many logic rules.
Videos: All Logic Rules videos
- Using Logic Rules to: Assign Attendee Types (2:54)
- Display a Custom Question (3:06)
- Send Email to a Third Party (4:22)
- Hide the Additional Reg Button (4:32)
An Overview of Logic Rules
The basis of a Logic Rule is an action that will occur on a form IF a set of conditions is met.
The condition can be "always apply," but it is usually at least one IF clause.
IF one or more clauses are joined by AND / OR conjunctions, THEN the action occurs after the conditions are met.
For example: IF {the attendee type} {equals} {Exhibitor} THEN {Display Questions} {Exhibitor-only Questions}.
A Logic Rule can include many levels of conditional clauses, such as: IF {email address} {does not end with} {"@certain.com"} AND {company} {contains} {"certain"} OR {position} {contains} {"certain"} THEN {Assign Attendee Type} {Certain Inc. Employee}.
An infinite variety of combinations can be used to create forms as complex as needed in order to accurately collect the event's registration data online.
When an attendee modifies their information, Certain "undoes" any logic-based actions that resulted from the original answer. For example, if the registrant selects "Manufacturer" as their business type, and that answer results in a $30 registration fee, then if they change their business type to "Retail," the $30 fee will be removed. This "undo" action occurs on the verify/edit, payment, and confirmation pages of the registration form.
Note: Logic Rules are created here, but a logic section must be included in the online form setup in order for the logic to be processed in the form.
List and Labels
List of Logic Rules
The Logic Rules set up for the current form are listed here. This may be a multi-page list.
Click edit in the Actions column to view or modify a rule.
Click copy in the Actions column to make an exact copy of a rule.
Click Add New to add a new logic rule.
Whichever you click, the Logic Rule Details page is displayed, with the Conditions and Actions sections in which you set up the logic rule, as described under List Rule Details below.
Labels for Form Sequence Each logic rule, as described under List Rule Details below, must be assigned to a form Section on which it will be processed in the online form sequence (defined on Form > Setup). A form may include up to 20 logic sections, and any number of rules may be processed on a single section. Rather than use the default section labels of "Logic 1," "Logic 2," etc., you can define a custom Label and Description for each one. For example, you could rename "Logic 1" to "Assign Attendee Type & Display Error," making its purpose obvious. This eliminates any need to toggle back from Form Setup to this Logic Rules section to remember what action the rules in a Logic section are performing.
Logic Rule Details (Attendee Form)
Details and Conditions
List Rule Details
- Name – (Required.) A descriptive name for the rule. This should describe the condition and the action that will follow; for example, "Display exhibitor questions to exhibitors (attendee type)."
- Section – Select the section on the form on which the rule will be processed. (Logic 1, Logic 2, etc.) A form may include up to 20 logic sections, and any number of rules may be processed on a single section.
- Processing Order – The order in which the rule is processed displayed relative to other rules in the same Section. (1, 2, 3, etc.)
Conditions
- The two radio buttons are: Always apply; Apply ONLY if these conditions are met.
- Condition details begin with IF. The user selects a Question / Data Field, a Comparison Operator, and an Answer Value.
- Question / Data Field – Choose a question or field from the list. Depending on enabled modules, this list may include: Standard Profile Fields; Custom Profile Fields; Standard Registration Fields; Registration Payment Fields; Custom Registration Fields; Custom Travel Fields; Other items such as Group, Promo Code, or Today; Room Reservation Fields; Agenda Item Quantity; Agenda Item Status; Travel fields; Qualification and Approval Fields; Custom Event Fields; Appointment Fields; Sessions Instance Status.
- Operator – The operator compares the data field contents with the option entered as the Answer Value. Operators include: =, <>, >, <, >=, <=, begins with, ends with, contains, does not begin with, does not end with, does not contain, is one of, is not one of, is blank, is not blank.
- Answer Value – Value used for comparison (not shown if operator is is blank or is not blank).
- Conjunction – If more than one condition is required, use AND or OR.
- Note – To combine AND and OR in the same rule, use the ")AND(" and ")OR(" conjunctions.
Rules with Identical Conditions
- Warning: Do not include two logic rules with identical conditions (using the same operator) on the same page. They would cancel each other out.
- If two rules are the same apart from the operator, they would work as expected.
Examples (conflict and success)
- Logic Rule 1A: Display questions/agenda; If attendee type = Attendee.
- Logic Rule 1B: Assign Reg status; If attendee type = Attendee.
- Result: The two rules would cancel each other out if used on the same page because the conditions are identical ("If attendee type = Attendee").
- Logic Rule 2A: Display questions/agenda; If attendee type = Attendee.
- Logic Rule 2B: Assign Reg status; If attendee type Contains Attendee.
- Result: The two rules would work as expected if used on the same page, because the conditions are different; the operator is = in one, and Contains in the other.
Tip: Using a different operator is usually the simplest way around the restriction. Just be sure that two rules on the same page never include identical conditions, even when one or both of the conditions include AND/OR conjunctions.
Actions
- Select Action – Select the action to be applied if all the Conditions are met during the registration process. Actions include:
Inline Actions
- Display Questions – Use this action to "nest" questions, displaying questions based on the registrant's answers to earlier questions on the same page.
- The "questions" available for selection include question headers for display purposes.
- In most cases, the Conditions available when you have selected this action are restricted to selecting a Question / Data Field, and the ones available for selection are those that are enumerable (Radio, Checkbox, Select, Select Multiple, or numeric).
- Note: If the Question/Data Field is a Standard Profile field with a set of known answers, the Answer Value displays that list for you to select from. This enables you to display a particular custom question only to registrants from a particular country or list of countries.
- Best Practice Warning: Only use a Display Question action for any given question once on a page. If logic includes such an action for the same question more than once on the same page, only the last occurrence will be displayed.
- For example: You could set the rule to display questions about golf only if the attendee has selected a golf agenda item.
- Caution: If you use Agenda Item Quantity in a condition for this action, the agenda item must be configured on the Agenda Section to be selected via "Quantity Input Type." The "Summary Group Input Type" option is not supported for Display Questions.
- The Operators available for the selected Question / Data Field are restricted to = and <>.
- Under 'Select Question(s) to Display', you can select: Questions, including Registration Custom Questions; Standard Profile Fields; Question Headers.
- Display Actions
- Display Agenda Sections – Use this action to conditionally display a particular section of agenda items to a select set of attendees.
- Display Attendee Types – You may display a customized list of attendee types in the attendee type section by using this action.
- Display Promo Code – If using the "Registration Groups As Promo Codes" sub-module, you may display a customized list of promo codes (from Plan > Promo Codes) to registrants. The promo codes displayed will be restricted to those for the registrant's attendee type, so the logic action needs to occur after the attendee type has been selected or assigned.
- Display Groups – If using the "Registration Groups" sub-module, you may display a customized list of groups (from Plan > Groups) for registrants to select. The groups displayed will be restricted to those for the registrant's attendee type, so the logic action needs to occur after the attendee type has been selected or assigned.
- Display Questions or Agenda Items – Use this action to conditionally display particular questions to the registrant. This is useful if you wish to change the selections for specific attendee types but you want all attendee types to share the same form.
- Display Custom HTML Sections – Use this action to display Custom HTML sections to provide information to certain attendees.
Hide Actions
- Do Not Display Attendee Types – Hide the attendee type section for some registrants based on a condition.
- Assign Actions
- Assign Agenda Items – Automatically assign an agenda item to a registrant based on criteria.
- Auto-Cancellations – Agenda items assigned via logic are automatically canceled before completion if the registrant makes a modification that makes the logic rule now evaluate as false.
- Assign Attendee Type – Automatically assign an attendee type based on criteria.
- Set Custom Registration Properties – Assign Custom Registration Properties to an attendee.
- Assign Approval Status – Automatically set the final approval status based on criteria (without external review).
- Assign Promo Code – Assign a promo code to a registration.
- Assign Group – Assign a group to a registration.
- Assign Question Response – Assign responses to custom questions based on other answers.
- Assign Sessions – Assign sessions to a registrant from published, scheduled session instances.
- Assign Reg Status – Assign a registration status based on a condition.
Other Actions
- Return Error Message – Display an error message at the top of the current page and continue to display while the condition remains true.
- Hide Addtl Reg Add – Restrict the number of additional registrants.
- Clear Questions or Agenda Items – Clear action deletes data from a field and replaces it with its default value.
- Send Email to Third Party – Send an email to a selected third party if a condition is met; requires selecting an email template.
- Send Email to Registrant – Send email to a registrant if the condition is met; requires selecting at least one recipient option and an email template.
- Best Practices: The action typically adds an extra field to add an item; Display Attendee Types displays a multi-select list; the order of processing matters.
Note: The action selected usually results in an extra field to add an action item. Best Practice: Ensure the correct section position for form setup. The "display" actions are processed on the same page as the logic section. The "assign" actions are processed after the page is submitted. The "return error" action is processed after its page is submitted; however, if the logic evaluates to true, the form is returned to the current page.
Best Practices When Working with Agenda Item and Session Fees, Discounts, and Tax
- Percentage Fee and Discount calculations must be in separate logic rules from Tax calculations.
- Charges may not be calculated correctly if both percentage calculations and tax are combined in the same logic rule.
- Assign any Percentage Fee or Discount in a form via logic earlier in the form sequence than the Tax, using separate form sections (although using the sort order will also work within a section).
- The general rule is to add tax to a registration via form logic at the end of the last page before Verify.
Section Header (Display Action Only)
- The instructions, header text, and page HTML are displayed at the top of the section containing any questions that result from the Display Questions or Agenda Items action option.
Using Package Logic Package logic enables you to restrict attendees from selecting more items from Group A of agenda items than were selected in Group B of agenda items. For example, if an online Registrant selects 1 Advisor Registration (RA) and 9 Member Registrations (RM), and then selects 3 tickets for Opening Session 1A (OS1), 2 for Opening Session 1B (OS2), and 6 for Opening Session 1C (OS3), the registration form should return an error message and not enable the registration to continue, because the sum total of Convention Registration items is 10 (1+9=10) and the sum total of Opening Session Tickets is 11 (2+3+6 = 11). Note that in order to use package logic, you must have previously defined packages in the event. See Plan > Event Setup > Create and Edit Packages. Once packages exist, logic can compare the sum of Package A to Package B. The logic can compare selected quantities of two agenda items. The following items appear in the logic condition drop-down list: Package Total Quantity (lists all defined packages); Agenda Item Quantity (lists each agenda item). The Quantity Sum Total returns the sum of the Quantity values for that registration for all agenda items in the package. The following is an example logic rule: IF “Sum of Opening Session Tickets” “Data: >” “Sum of convention registrations” THEN “Return Error” “You have entered more Opening Session Tickets than Convention Registrations. Please review the quantities that you have entered. You must purchase the same number or more Convention Registration tickets than Opening Session Tickets.”
Was this article helpful? 0 out of 0 found this helpful
Have more questions? Submit a request
Related articles
- Form Setup (Attendee/Registration Form)
- Logic Rules: Overview of Display Options (Display, Hide, Assign)
- Using Inline vs. Display Logic
- Partial Refunds
- How to Delete Images and Files in an Event or an Account