How to set up a Form's Entry Page

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

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. Page HTML can include any information desired.

The text entered into the page HTML field will be converted into HTML. Carriage returns will be replaced with HTML <br> (break) tags. The page can also restrict access to the registration form through a variety of permissions.

Form Entry Permissions

Open Enrollment or Profile Login is the least secure method of access to a Form. Open Enrollment or Profile Login is the default entry permission.

Open Enrollment allows anyone who has access to the Form URL to view the Form. An emailed invitation link from a colleague can provide access to the Form URL. A link to the Form on a webpage can provide access to the Form URL.

Profile is for situations where a Username and Password are set as Required. Profile is for situations where the person does not have an existing Registration ID in the Event. The Import Registrations process typically creates the existing Registration ID.

Reg ID in URL or Integrations Only is an advanced option. This advanced option is typically used if an ID value is passed 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 listed as: Reg_ID, Reg Code, Profile External ID, Username and Password, or email.

Restrict to Registrations in this event (Existing or Imported) is an access-restriction option. Restrict to Registrations in this event restricts access to the Form to only those people who have an existing Registration in the Event. Registrations can be created through the Import Registration process. Registrations 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. Registration Statuses can include Custom Statuses. For example, a Form designed for accepted applicants could be restricted to enable Registrations with an “Invited” Status. For example, a Form designed for accepted applicants could be restricted to not enable Registrations with a “Denied” Status. If no Statuses are selected, or if 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.

Registrants must read the waiver.

Registrants must check the box before viewing the Registration page.

The waiver text will be highlighted in the error font color.

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. Each Registrant must be pre-assigned a password prior to invitation. A Personal Identification Number can be used as the unique username.

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. Usernames can be re-used from event to event.

Passcodes

If Optional or Required is selected, several options are displayed.

Selecting Hide Text? collects the passcode as a hidden text field.

A hidden text field prevents the Registrant from seeing what they are typing.

Three types of passcodes are used on the Entry page.

The passcodes can be 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.

The Registrant will be shown Questions, Agenda Items, and options accordingly.

A single (unique) password may be provided for each Attendee Type.

The passcode is compared to pre-assigned Registration Codes for this Event.

Registration Codes can be set up for one-time use.

One person uses the code to access the Form and completes a Registration.

No other person will be allowed to use that same code to access the Form online.

To enable one-time use, ensure that the Prevent reg edits? check box is selected in the form setup. 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 access the Form online using that code.

SSO Login

If any SSOs (“Single Sign Ons”) such as social logins for LinkedIn or Facebook have been configured for the Event, then SSOs are available for selection. SSOs are configured in Plan > Configure > Single Sign On. Selection of those SSOs makes them available on the Form.

Attendees will have the option to click the relevant button to pre-populate the Form with their details. Which fields are pre-populated is determined by the SSO configuration in Account Settings. The pre-populated fields 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. The message display depends on whether the Registrant has an existing Incomplete or Completed Registration.

The messages for Incomplete and Completed Registrations can use the HTML editor. The messages for Incomplete and Completed Registrations can use Event fields inserted into the message. The messages for Incomplete and Completed Registrations can use Registration fields inserted into the message.

For example, <{First Name}> and <{Last Name}> and other registration fields can be displayed in the message body.

Default messages are available by clicking Default Value below each message entry box.

The options for defining messages are listed as:

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. > The Event Registration Capacity Message is customized on Plan > Forms > Setup > Advanced.

Other Options

A Registration button is the label on the button to submit the Entry section. If the Registration button label is blank, then the default text provided in the Event Setup will be shown on the Submit button. The default text is ' Continue '.

A Disclaimer is text shown immediately below the Registration button. A Disclaimer is shown above the general Submit button.

The Default disclaimer text is:

Since only one button is shown on the Form, the disclaimer text can be positioned above or below the Entry Submit button. The position is controlled by using the optional button or the general button.