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 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 appear above the header bar, at the top of the section. Text Above Header appears above the Header Text in the header bar (in a contrast color). Page HTML appears directly below the header, and it can include any information desired. The text entered into the page HTML field is converted into HTML. Carriage returns are 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 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.

Access examples include an emailed invitation link from a colleague.

Access examples also include a link to the Form on a webpage.

Open Enrollment allows the person to view the Form.

Profile Login is for situations where a Username and Password are set as Required.

Profile Login applies when the person does not have an existing Registration ID in the Event.

Registration IDs are typically created through the Import Registrations process.

Reg ID in URL or Integrations Only is an advanced option.

Reg ID in URL or Integrations Only 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 use this approach.

This approach expedites 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 use this option.

This option denies 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) restricts access to the Form.

Restrict to Registrations in this event limits access to only those people who have an existing Registration in the Event.

Registrations can be created through the Import Registration process.

Registrations may also already exist as a result of a past Registration.

This option can be used to allow existing Registrants the ability to return.

This option can be used to allow existing Registrants the ability to make modifications.

Entry into the Form can be restricted to specific Registration Statuses.

Entry into the Form can include Custom Statuses.

Example: A Form designed for accepted applicants could be restricted to enable Registrations with an "Invited" Status.

Example: The same Form could prevent Registrations 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.

Registrants must read the waiver.

Registrants must check the box.

Registrants must check the box before viewing the Registration page.

Text shown to a Registrant who does not check the box appears when the Registrant tries to register.

The waiver text is 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 (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. Usernames can be re-used from event to event.

Passcodes

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

Check ' Hide Text? ' to collect the passcode as a hidden text field.

Hidden passcodes prevent the Registrant from seeing what the Registrant is typing.

Three types of passcodes are used on the Entry page.

Passcodes are compared to the Attendee Types for an Event.

If the passcode matches one for that Event, then the Registrant is assigned to the corresponding Attendee Type.

The assigned Attendee Type determines what Questions are shown.

The assigned Attendee Type determines what Agenda Items are shown.

The assigned Attendee Type determines what options are shown.

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-time use means that once one person uses the code to access the Form and completes a Registration, no one else can use the same code to register online.

To enable this, make sure 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.

Only the intended recipient may register 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 in Plan > Configure > Single Sign On, select those to be used on the Form.

Attendees can 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. The fields always include at least First Name and Last Name.

Message for Existing Registrations

This option gives the planner the ability to script messages. The messages display to existing Registrants on the Entry page. The messages display depending 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 also include Event and Registration fields inserted into the message. Example message fields include <{First Name}>, <{Last Name}>, and other registration fields displayed in the message body.

Default messages are also available by clicking Default Value below each message entry box. The options are defined 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 (customized on Plan > Forms > Setup > Advanced ).

Other Options

If blank, the default text provided in the Event Setup appears on the Submit button.

Default: ' Continue '

Disclaimer text appears but is shown above the general Submit button.

Since only one button is shown on the Form, the disclaimer text can appear above or below the Entry Submit button by using the optional button or general button.

Source: https://platform-support.certain.com/hc/en-us/articles/200210580-How-to-set-up-a-Form-s-Entry-Page

Published:

Keywords: Form Entry Permissions, Entry Section, Waiver Checkbox, Username and Password, Passcodes, SSO Login