Logic Rules (Attendee Form)

Source:

Published:

Keywords: Logic Rules (Attendee Form), Form Logic, Conditions, Operators, 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.

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 basis includes a "condition" that can be to "always apply".

The basis includes at least one IF clause in most cases.

The basis includes one or more clauses joined by AND / OR conjunctions in many cases.

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 in order to accurately collect the event's registration data online.

Certain "undoes" any logic-based actions that resulted from the original answer when an attendee modifies their information. Certain "undoes" logic-based actions on the verify/edit, payment, and confirmation pages of the registration form. For example, if the registrant selects "Manufacturer" as their business type, and that answer results in a $30 registration fee, then if the registrant changes their business type to "Retail", the $30 fee will be removed.

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

The selected option displays the Logic Rule Details page. The Logic Rule Details page includes the Conditions section. The Logic Rule Details page includes the Actions section. The setup of Conditions and Actions is described under List Rule Details.

Labels for Form Sequence

Each logic rule must be assigned to a form Section on which it will be processed in the online form sequence.

The online form sequence is defined on Form > Setup > Sections.

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

Default section labels include "Logic 1", "Logic 2", etc. A custom Label and Description can be defined for each logic section instead. The custom Label and Description are what the user sees when adding logic sections to the form. The custom Label and Description are what the user sees when setting the online sequence on Form > Setup > Sections.

For example, "Logic 1" can be renamed to "Assign Attendee Type & Display Error". Renaming can make the purpose obvious. Renaming can eliminate the 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

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

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

Example section names include Logic 1, Logic 2, etc.

A form may include up to 20 logic sections.

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

Example processing order values include 1, 2, 3, etc.

Conditions

Choose one of the two radio buttons for Conditions.

No further "Conditions" detail is required.

Complete the details for the Actions.

The condition(s) begin with an IF.

The user selects a question/data field.

The user selects a comparison operator.

The user enters an answer value.

Question / Data Field

Select a question or field from the list.

The list of available question/data fields may include items based on enabled modules for the event.

Possible Question / Data Field options include:

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

The sessions instance statuses are the possible statuses of the selected published session instance.

If the user selects Display Questions as the inline action under Select Action, then the Question / Data Field list is restricted to:

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

Comparison Operator

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

The comparison operator is part of the condition.

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 |

Answer Value

Enter the value to be compared in the unlabeled field to the right of the comparison operator.

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

Conjunction

If the rule needs more than one condition, the rule uses AND or OR from an unlabeled drop-down list after the Answer Value.

After selecting AND or OR, another set of fields displays to select a question / data field, select an operator, and specify an answer value.

The user can repeat this process as many times as necessary.

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

> Identical rules would cancel each other out.

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

Example 1 (= conflict):

Neither rule would be applied.

The cancellation occurs because the conditions are identical ("If attendee type = Attendee").

Example 2 (= success):

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. This requirement includes cases where one or both 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:

| Action | Use for | | --- | --- | | Inline Actions | |

Inline Actions

Display Questions

Use this action to "nest" questions.

Display Questions shows 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 selecting this action are restricted to selecting a Question / Data Field. The Conditions available for selection must be enumerable. Enumerable types include Radio, Checkbox, Select, S elect Multiple, or numeric.

> Note: If your 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 you to select from. > This enables the Display Questions action 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 potential occurrence will be displayed.

For example:

> Caution: If Agenda Item Quantity is used in a condition for this action, then the agenda 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 ", select:

The list of available questions includes which ones are optional or required. An administrator configures optional or required settings on Account Settings > Registration > Profile Data.

Select also:

Display Agenda Sections

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

Display Attendee Types

Use this action to display a customized list of attendee types in the attendee type section.

Display Promo Code

If using the "Registration Groups As Promo Codes" sub-module, Display Promo Code can display a customized list of promo codes.

The promo codes come from those set up on Plan > Promo Codes.

Registrants select promo codes from the displayed list.

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

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

Display Groups

If using the "Registration Groups" sub-module, Display Groups can display a customized list of groups.

The groups come from those set up on Plan > Groups.

Allowing attendees to select their own group is part of the scenario.

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

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 action is useful for changing the selections for specific attendee types.

This action can allow different attendee types to share the same form.

Display Custom HTML Sections

Use this action to display Custom HTML sections.

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

Hide Actions

Do Not Display Attendee Types

Use this action to hide the attendee type section for some registrants based on a condition.

Example conditions include whether or not a particular passcode or promotional code was entered.

Assign Actions

Assign Agenda Items

Use this option if automatically assigning an agenda item based on criteria is needed.

Criteria examples include custom question answers.

Criteria examples include attendee type membership.

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

Assign Attendee Type

Use this option if automatically assigning an attendee type based on criteria is needed.

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

Set Custom Registration Properties

Use this action to assign Custom Registration Properties to an attendee.

"Custom Reg" properties are set up for the event on Plan > Configure > Options > Custom Registration Properties.

Assign Approval Status

If using the Qualification and Approvals module, this option automatically sets the final approval status of a registration.

The setting is based on criteria such as answers to particular custom questions.

The setup can be without requiring the external review process.

Assign Promo Code

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

The promo code comes from those set up on Plan > Promo Codes.

Assign Group

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

The group comes from those set up on Plan > Groups > Group List.

Assign Question Response

Use this action to assign responses to custom questions.

This action can set a value for a custom registration question.

The set value can depend on the registrant's answer to another question.

Assign Sessions

If using the Variable: UCModule is not defined in the project. module, assign sessions to a registrant based on criteria.

Sessions come from those set up on Manage > Speakers and Sessions > Sessions.

Sessions assignment selects one or more published, scheduled session instances. 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, then the session is not assigned.

The sessions section in a form 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: Do not use logic to assign sessions that include inventory. > If the session were full, then the session would not 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 when the registrant makes a modification. The modification causes the logic rule that assigned the session to now evaluate as false.

Note about copying:

Sessions may not be copied.

Assign Reg Status

Use this option if automatically assigning a registration status to a registrant based on a condition is needed.

Only standard registration statuses can be selected.

Custom registration statuses cannot be selected.

If the account has the Show Default Statuses check box cleared in Account Settings > Implementation > Security, then this action cannot be used. Clearing this setting is rare for an account administrator.

Other Actions

Return Error Message

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.

Use this action to prevent a registrant from completing the registration process for some reason.

Hide Addtl Reg Add

Used to restrict the number of additional registrants.

Clear Questions or Agenda Items

Clear action is performed if certain conditions are met.

Clear action deletes data from a field.

Clear action replaces the data with its default value.

The default value is typically zero.

Send Email to Third Party

This action updates travel agents, tour operators, hotel reservation staff, and other third parties associated with an event.

Certain can automatically:

The user must select an email template from the drop-down list to the right of the Action menu. Because the logic rule can send email when fields in the email template have been modified, the logic rule should include those fields in the email template.

Send Email to Registrant

Send Email to Registrant sends email to a registrant if the condition is met.

The user must select an email template from the drop-down list to the right of the Action menu.

The user selects at least one of the following options:

If the user selects "Send email to Registrant Email", then two more options are added:

The email is sent to the selected recipient(s) if the email addresses exist on the registrant's profile record. Each selected address is checked and processed separately.

For example:

The sent email is sent to the Assistant Email address.

There is no registrant email address to send copies of.

> Note 1: If both "Send email to Assistant Email" and "CC Assistant Email" are selected, then the Assistant address receives two emails. > One email is sent as an original email to just the assistant. > Another email is sent as a copy of the one sent to the registrant.

> Note 2: The logic rule may send email to additional registrants. > The user may have selected the Assistant and/or Additional Email addresses. > The user should 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 results in a multi-select list. The multi-select list is where the user selects Attendee Type(s) to 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 where they are placed. > The "assign" actions are processed after the page where the logic is 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 returns 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 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 earlier assignment uses separate form sections. The sort order can 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 restricting attendees from selecting more items from Group A of agenda items than the attendees selected in Group B of agenda items.

For example:

The error message occurs because the sum total of Convention Registration items is 10 (1+9=10). The error message occurs because the sum total of Opening Session Tickets is 11 (2+3+6 = 11).

Note that package logic requires previously defined packages in the event. See Plan > Event Setup > Create and Edit Packages.

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

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

Package Total Quantity 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.

Agenda Item Quantity 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.”