Logic Rules (Attendee Form)

Source:

Published:

Keywords: Logic Rules, Form Logic, registration forms, conditions, actions, package logic

Document ID: https://platform-support.certain.com/hc/en-us/articles/30759298174103#split1

Introduction

Logic Rules (often referred to as “Form Logic** ™”) are simple or complex rules that control the display and processing of registration forms.

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: Using Logic Rules to:

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.

Although the “condition” can be to “always apply”, it is usually at least one IF clause.

The IF clause is often one or more clauses joined by AND / OR conjunctions.

The action can be thought of as a THEN clause after the conditions. The THEN clause describes what happens 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. For example: 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. The combinations collect the event’s registration data online.

Certain “undoes” logic-based actions when an attendee modifies information. Certain “undoes” any logic-based actions that resulted from the original answer. For example, if a registrant selects “Manufacturer” as their business type and that answer results in a $30 registration fee, then the registrant changes the business type to “Retail”, the $30 fee is removed. The “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 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 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 item is clicked, the Logic Rule Details page is displayed. The Logic Rule Details page contains the and sections. The Logic Rule Details sections describe how to set up the logic rule. The Logic Rule Details sections are described under below.

Labels for Form Sequence

Each logic rule must be assigned to a form Section.

The form Section determines where the logic rule will be processed in the online form sequence.

The online sequence is defined on .

A form may include up to 20 logic sections. Any number of rules may be processed on a single section.

Instead of using default section labels like “Logic 1”, “Logic 2”, etc., custom labels and descriptions can be defined for each logic section. Custom labels and descriptions are what planners see when adding logic sections to the form. Custom labels and descriptions are also what planners see when setting the online sequence on .

For example, “Logic 1” can be renamed to “Assign Attendee Type & Display Error”. The rename makes the purpose obvious. The rename eliminates the need to toggle back from Form Setup to remember what action rules in a Logic section are performing.

Logic Rule Details (Attendee Form)

Details and Conditions

List Rule Details

A descriptive name for the rule is required.

The rule name should describe the condition and the action that will follow.

For example, “Display exhibitor questions to exhibitors (attendee type)”.

The section on the form on which the rule will be processed must be selected.

“Logic 1, Logic 2, etc.” are supported.

A form may include up to 20 logic sections.

Any number of rules may be processed on a single section.

The order in which the rule is processed must be selected.

The processing order displays relative to other rules in the same Section.

The processing order uses values like (1, 2, 3, etc.).

Conditions

The specified action will always be applied.

No further “Conditions” detail is required.

Complete the details for the .

The specified action will only be applied if the condition(s) evaluate to “True”.

The condition(s) begin with an IF.

The condition setup requires a question/data field.

The condition setup also requires a comparison operator.

The condition setup also requires an answer value.

Select a question or field from the list.

The available options depend on which modules are enabled for the event.

The available options may include:

Travel fields also include Trip information Fields such as Has Travel Reservations, etc.

If Display Questions is selected as the inline action under , then the Question / Data Field list is restricted to:

For example, a rule can display questions about golf only if the attendee has selected a golf agenda item.

The operator compares the contents of the data field with the option entered into the answer field to the right.

Operators are restricted as described in the relevant action documentation.

Operators include:

| Operator | Use for | |---|---| | = | Equals | | <> | Does not equal | | > | Greater than (numeric values only) | | < | Less than (numeric values only) | | >= | Greater than or equal to (numeric values only) | | <= | Less than or equal to (numeric values only) | | begins with | String of characters at the beginning of the value | | ends with | String of characters at the end of the value | | contains | String of characters that appears anywhere within the value | | does not begin with | String of characters that should not be found at the beginning of the value | | does not end with | String of characters that should not be found at the end of the value | | does not contain | String of characters that should not be found anywhere within the value | | is one of | A list of items against which the value will be evaluated. The value must be found in the list for the condition to be met. Each item must be separated by a comma from the next, with no intervening space, as in: value 1,value 2,value 3. Note: This operator is meant to be taken literally; the answer is one of the selected options—multiple answers will not work. (For instance, if you select "If question A is one of answers X, then...", and the attendee chooses X AND Y, the rule is evaluated as false, and the action is not triggered.) | | is not one of | A list of items against which the value will be evaluated. The value cannot be in the list for the condition to be met. Each item must be separated by a comma from the next, with no intervening space, as in: "value 1,value 2,value 3". | | is blank | No value has been entered | | is not blank | Any value has been entered |

The unlabeled field to the right of the comparison operator is used to enter the value to be compared.

This field is not displayed if the operator is “ is blank ” or “ is not bla nk”.

If more than one condition is needed, a conjunction value is selected from the unlabeled drop-down list after the Answer Value.

The selected conjunction value is AND or OR.

Another set of fields is then displayed for selecting an additional question / data field.

The next set of fields also includes selecting an operator.

The next set of fields also includes specifying an answer value.

This process can be repeated as many times as needed.

> Note: To combine AND and OR conjunctions in the same rule, use the “ )AND( ” and “ )OR( ” conjunctions. > For example: IF ( Workshop A = Registered OR Workshop B = Registered )AND( Include Conference Proceedings Booklet= Yes ) THEN...

Rules with Identical Conditions

> Warning: Do not include two logic rules with identical conditions (using the same operator) on the same page.

> The identical conditions would cancel each other out.

If the two rules were the same apart from the operator, then the rules would work as expected.

Example 1 (= conflict):

Result: The two rules would cancel each other out if used on the same page. Neither rule would be applied. The conditions are identical. Example condition is “If attendee type = Attendee”.

Example 2 (= success):

Result: The two rules would work as expected if used on the same page. The conditions are different. The operator is = in one rule. The operator is Contains in the other rule.

Tip: Using a different operator is usually the simplest way around the restriction. Two rules on the same page must never include identical conditions. Two rules must not include identical conditions, even when one or both conditions include AND/OR conjunctions.

Actions

Select the action to be applied if all the are met during the registration process.

Actions include:

Inline Actions

Use this action to “nest” questions.

Nesting displays 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 available when the Display Questions action is selected are restricted to selecting a Question / Data Field.

In most cases, the available Question / Data Field options are enumerable.

Enumerable types include Radio, Checkbox, Select, S elect Multiple, or numeric.

Note: If the Question/Data Field is a Standard Profile field such as Country with a set of known answers, then the Answer value displays that list for selection. This enables displaying 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 the logic includes such an action for the same question more than once on the same page, only the last potential occurrence will be displayed.

For example:

A data field can have a value of 1 or 2.

Two Display Questions actions use that field in their conditions.

Result: Only the second action is processed. If value is 2 then Question 5 and Question 6 are displayed. If value is 1 then neither question is displayed.

> Caution: If Agenda Item Quantity is used in a condition for this action, then that agenda must be configured on the to be selected via “Quantity Input Type”. > The “Summary Group Input Type” option is not supported for Display Questions.

The available for the selected Question / Data Field are restricted to = and <>.

Under “Select Question(s) to Display”, you can select:

The list of those available and whether they are optional or required is configured for the account by an administrator on .

Use this action to conditionally display a particular section of agenda items to a select set of attendees.

Display a customized list of attendee types in the attendee type section by using this action.

If using the “Registration Groups As Promo Codes” sub-module, choose to display a customized list of promo codes.

Promo codes come from those set up on .

Registrants select from the displayed promo codes.

The displayed promo codes for the registrant are restricted to promo codes for the registrant’s attendee type.

The logic action needs to occur after the attendee type has been selected or assigned.

If using the “Registration Groups” sub-module and allowing attendees to select their own group, choose to display a customized list of groups.

Groups come from those set up on .

The groups displayed on the form are restricted to groups for the registrant’s attendee type.

The logic action needs to occur after the attendee type has been selected or assigned.

Use this action to conditionally display particular questions to the registrant.

This action is useful for changing the selections for specific attendee types while sharing the same form for all attendee types.

Use this action to display Custom HTML sections.

Custom HTML sections are useful for providing information to certain attendees.

Hide Actions

Hide the attendee type section for some registrants based on a condition.

A condition example is whether or not a particular passcode or promotional code was entered.

Assign Actions

Automatically assign an agenda item.

An agenda item example is a session breakout, meal, activity, or other option.

The assignment is based on criteria.

Criteria examples include how a particular custom question is answered or which attendee type the registrant belongs to.

Auto-Cancellations: Agenda items assigned via logic are automatically canceled before completion of the registration. Auto-cancellations occur if the registrant modifies information. The modification makes the logic rule that assigned the agenda item now evaluate as false.

Automatically assign an attendee type to a registrant.

The assignment is based on criteria.

Criteria examples include how the registrant has answered a particular custom question.

Assign Custom Registration Properties to an attendee.

Custom Reg properties are set up for the event on .

If using the Qualification and Approvals module, automatically set the final approval status of a registration based on criteria.

Criteria examples include answers to particular custom questions.

The approver status can be set without requiring the registrant to go through the external review process.

If using the Registration Groups As Promo Codes sub-module, assign a promo code to a registration.

Promo codes come from those set up on .

If using the Registration Groups sub-module, assign a group to a registration.

Groups come from those set up on .

Assign responses to .

For example, set a value for a custom registration question depending on the registrant’s answer to another question.

If using the “Variable: UCModule is not defined in the project” module, assign sessions to a registrant.

Sessions come from those set up on .

Select one or more from a list of all published, scheduled session instances.

> Warning: Sessions are always published for specific attendee types. > If a logic rule tries to assign a session to an attendee of any other attendee type, the session will not be assigned. > The same principle applies to sessions in a form’s . > That Sessions section lists only the sessions published for the registrant’s attendee type. > Therefore the attendee type must be assigned on the same or previous page of the form.

> Best Practice Note: Don’t use logic to assign sessions that include inventory. > If the session were full, it wouldn’t be assigned. > The registrant would not see a warning.

Auto-Cancellations: Sessions assigned via logic are automatically canceled before completion of the registration. Auto-cancellations occur if the registrant makes a modification. The modification makes the logic rule that assigned the session now evaluate as false.

Note: When a form is copied, this action is copied with the form. When an event is copied, this action is not copied with the form. Sessions may not be copied.

Assign a registration status to a registrant based on a condition.

Only standard registration statuses can be selected.

Custom ones cannot be selected.

If an account administrator clears the Show Default Statuses check box in , then custom registrations statuses are not supported for this action. However, clearing that setting is very rare.

Displays an error message at the top of the current page.

The error message continues as long as the condition for the rule is true.

This action prevents a registrant from completing the registration process for some reason.

Restricts the number of additional registrants.

The Clear action is performed if certain conditions are met.

The Clear action deletes data from a field.

The Clear action replaces the field with its default value.

The default value is typically zero.

To keep travel agents, tour operators, hotel reservation staff, and other third parties associated with an event updated, Certain can be set to automatically send email.

Certain can automatically:

An email template must be selected from the drop-down list to the right of the Action menu. Since a logic rule can send email to a third party when fields in the email template have been modified, those fields should be included in the email template.

Sends email to a registrant if the condition is met.

An email template must be selected from the drop-down list to the right of the Action menu.

At least one of these options must be selected:

If “Send email to Registrant Email” is selected, two more options are added:

The email is sent to the selected recipient(s) if those email addresses exist on the registrant’s profile record. Each email address is checked and processed separately. If only one of the selected fields has a value on the registrant’s record, only that one email is sent.

The logic rule also supports CC copies. CC copies are only sent if the email address exists.

> Note 1: If both “Send email to Assistant Email” and “CC Assistant Email” are selected, then that address receives two emails. > One original email is sent to the assistant. > One CC copy is sent to the assistant.

> Note 2: Since a logic rule will likely send email to additional registrants, personalize the email template with appended data fields such as first name and last name.

The action selected usually results in an extra field for adding an action item. For example, selecting the Display Attendee Types action shows a multi-select list. In that multi-select list, you select Attendee Type(s) Display.

> Note: The action helps determine the correct position of a section in the online form setup. > The “display” actions are processed on the same page of the form as the logic section in which they are placed. > The “assign” actions are processed after the page in which they are placed is submitted. > The “return error” action is processed after its page is submitted. > If the logic rule evaluates to be true, then the form is returned to the current page instead of proceeding to the next page.

Best Practices When Working with Agenda Item and Session Fees, Discounts, and Tax

Percentage Fee and Discount calculations need to 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. The assignment uses separate form sections. Using sort order within a section also works.

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. The registration form should not enable the registration to continue. The error occurs because the sum total of Convention Registration items is 10 (1+9=10). The sum total of Opening Session Tickets is 11 (2+3+6 = 11).

Note: In order to use package logic, packages must have been previously defined in the event. Packages are defined in .

Once packages are created, use logic to compare the sum of Package A to that of Package B. Logic can also compare the selected quantities of two agenda items.

The following are listed in the logic condition drop-down list:

Lists all packages (groups of agenda items) defined in the event.

Returns the Quantity Sum Total for the current registration.

The Quantity Sum Total is the sum of the Quantity values for that registration for all of the agenda items in the package.

Lists each agenda item in the event.

Returns the total number of this agenda item selected for the current registration.

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