How to set up a Form's Entry Page

Overview

• The Entry page of the Form is the first page of the Form that a Registrant sees.
• It can be used as the Event's entire Website (for simple events), or simply as an instructional entry to the online registration process.
• It can also be used to limit access to the Form - by requiring Attendees to log in using a username and password, for example.

Entry Section

• The instructions will appear above the header bar, at the top of the section.
• Text Above Header will appear above the Header Text in the header bar (in a contrast color).
• Page HTML will appear directly below the header, and can include any information desired.
• The text entered into the page HTML field will be converted into HTML, i.e., carriage returns will be replaced with HTML BR (break) tags.
• This page can also restrict access to the registration form through a variety of permissions.

Form Entry Permissions

• Open Enrollment or Profile Login: This is the least secure method of access to a Form, and is the default entry permission.
• Open Enrollment allows anyone who has access to the Form URL (such as an emailed invitation link from a colleague, or a link to the Form on a webpage) to view the Form.
• Profile Login is for situations where a Username and Password (described below) are set as Required, but the person does not have an existing Registration ID in the Event (typically created through the Import Registrations process).
• Reg ID in URL or Integrations Only: This is an advanced option, typically used if you pass an ID value to the Form via GET or POST methods. Customers who integrate Certain with back-office systems or internal portals will adopt this approach to expedite access to the Form. Forms accessed via a registration link that includes the Dynamic Data Field “Reg ID for URL” appended to the URL string should also use this option. This option will deny access to the Form unless a valid ID passed by either GET or POST is found. Valid IDs are: Reg_ID, Reg Code, Profile External ID, Username and Password, or email.
• Restrict to Registrations in this event (Existing or Imported): Use this option to restrict access to the Form to only those people who have an existing Registration in the Event. Registrations can be created either through the Import Registration process, or may already exist as a result of a past Registration.
• This option can be used to allow existing Registrants the ability to return and make modifications.
• Entry into the Form can be restricted to specific Registration Statuses, including Custom Statuses. For example, a Form designed for accepted applicants could be restricted to enable Registrations with an "Invited" Status, but not enable Registrants with a "Denied" Status. If no Statuses (or all Statuses) are selected, then Registrations will not be restricted based upon their Registration Status.

Waiver Checkbox

• To include a waiver checkbox on the Entry page, select Require from the Collect? menu.
• If Require is selected, these options are displayed:
• Waiver Message: Text that will be shown in the Entry section with a checkbox next to it. Registrants must read the waiver, and check the box, before viewing the Registration page.
• Box not checked: Text of message shown to a Registrant who does not check the box and tries to register.
• Default: "Please check the box below to certify that you have read this message." The waiver text will be highlighted in the error font color.
• Leave the waiver text field blank if you do not require a waiver check box.

Username and Password

• The highest level of security is offered by the Username and Password fields.
• Each Registrant must be pre-assigned a unique username (or Personal Identification Number) and a password prior to invitation.
• Alternately, Registrants may be asked to select a Username and Password the first time they register.
• Usernames are attached to the Registrant's Profile record, so that they can be re-used from event to event.

Passcodes

• If you select Optional or Required, several options are displayed.
• Instructions: Text displayed above the Passcode text box.
• Display: Text displayed to the immediate left of the passcode text field. Check 'Hide Text?' in order to collect the passcode as a hidden text field (so that the Registrant cannot see what they are typing).
• Three types of passcodes are used on the Entry page:
• Global passcode: Registrants enter a single password in the Passcode field to gain access to the Form.
• Compare to attendee type: Passcodes can be collected from Registrants and compared to the Attendee Types for an Event. If the passcode provided matches one for that Event, then the Registrant will be assigned to the corresponding Attendee Type, and shown Questions, Agenda Items, and options accordingly. A single (unique) password may be provided for each Attendee Type.
• Compare to reg code: The Registrant may be asked to enter a passcode which is compared to pre-assigned Registration Codes for this Event. These codes can be set up for one-time use; that is, once one person uses the code to access the Form and completes a Registration, no one else will be allowed to use that same code to register online. To do this, make sure that the Prevent reg edits? check box is selected in the form setup. In addition, if the Form is set so that the Registrant's name is read-only, then the Registration Code is non-transferable. Therefore, only the intended recipient may register online using that code.
• SSO: If any SSOs ("Single Sign Ons"), such as social logins for LinkedIn or Facebook, have been configured for the Event in Plan > Configure > Single Sign On, select those to be used on the Form.
• Attendees will have the option to click the relevant button to pre-populate the Form with their details. (Which fields are prepopulated is determined by the SSO configuration in Account Settings. They always include at least First Name and Last Name.)
• Message for Existing Registrations: This option gives the planner the ability to script messages to display to existing Registrants on the Entry page, depending on whether the Registrant has an existing Incomplete or Completed Registration.
• The messages for Incomplete and Completed Registrations can use the HTML editor, as well as Event and Registration fields inserted into the message. For example, <First Name>, <Last Name>, and other registration fields can be displayed in the message body. Default messages are also available by clicking Default Value below each message entry box. These options are defined as:
• Incomplete: Some information has already been collected on the Registrant.
• Complete: All necessary information has been collected, and the Registrant is confirmed.
• Note: If a Registrant with a Cancelled Status tries to log back in using their Username & Password, Passcode, or Single Sign On, they will see the Event Registration Capacity Message (customized on Plan > Forms > Setup > Advanced).

Other Options

• Registration button: The label on the button to submit the Entry section. If blank, the default text provided in the Event Setup will be shown on the Submit button. (Default: 'Continue')
• Disclaimer: Text shown immediately below the Registration button, but above the general Submit button.
• Default: "<BR>NOTE: Your registration is not valid until you have successfully completed the entire process and received a printable confirmation page and an email confirmation."
• Since only one button is shown on the Form, you can decide if you want the disclaimer text to appear above or below the Entry Submit button by using the optional button or general button.

Was this article helpful?

• 0 out of 2 found this helpful
• Have more questions? Submit a request
• Return to top

Related articles

• Web Integration Links
• Form Entry & Security
• Troubleshooting Data Fields in Emails
• Accommodation Guide (PDF)
• How can I receive an email when someone registers for my Event?

Comments

• 0 comments
• Please sign in to leave a comment.