Form Setup (Attendee/Registration Form)

Introduction

A registration form is an online form that enables attendees to register for an event, submitting their information into the registration and profile database tables.

Each form must belong to one event, but an event can have any number of forms.

Examples: Attendee Registration form, Exhibitor Registration form, Appointment Preferences selection form, etc.

Note: By default, all Certain forms and websites are “private” (invisible to search engines). For information about changing this for all or some events, see the PDF guide, .

Security Note: If the event has an Access Token (generated on ), then anyone going to any forms or websites in the event would have to enter the token before proceeding.

The Sections of a Registration Form

A form consists of one or more sections, which you can group into one or more pages.

You can select the sections, their order, and the number of sections per page, as needed.

The following is the list of Sections available: (These links open the detailed topics for those pages)

That custom name is what you see on this Form Setup page.

Note: Every form must include a section.

Recommended: Accommodation and Travel sections should be on separate form pages.

Suggested order: Accommodation Entry > Accommodation > Travel Entry > Travel, across four consecutive form pages.

Last page: The last section should be the (from which a confirmation email can also be sent).

Setup Information

> Note: If this is selected, and the Event Start or End Dates are changed later, the relevant form dates will change accordingly.

Prior to this, attendees will see the “Not open” message you can configure in the section of this page.

> Note: If the event has a status of “Cancelled”, then the form will not be available to attendees at all.

This avoids the potential risk of registrations being entered after the event has ended.

But if you want to override this, for a post-event survey form, for example, you can select the Allow form open beyond event end date setting described below.

If you don’t specify a URL for the form, the system creates one for you automatically.

For example, “ Click here to register as a speaker ”.

This is useful if you are creating multiple events (containing multiple forms) using an event template.

Using these data-driven hyperlinks eliminates the need to update hard-coded links to registration forms in your new events.

This is generally used in the case of a “series” event, where each registration form is actually a separate event.

You can change this if you select Enable page-specific, page-level URL .

This is particularly useful when you want to view the primary form from an external website, such as an online calendar.

A report will show the Primary Form Name and Primary Form URL values (if those columns are included in the report).

> Note: To change which form is the primary, select this check box for the new one, which automatically clears it for the original.

If you are not viewing inactive forms on the , you may not be aware that a primary form is still set for an event.

(The getEventForms method in API 1 can provide the form’s URL.)

This makes a post-event survey form possible, for example.

So if, for example, you’ve selected that option and set the Form Close Date to any point after the Event End Date then you must also select this option.

(Ordinarily, all forms in the event are closed at that point.)

When you are logged into the Certain admin interface and viewing the attendee registration form, you see a ‘gear’ icon on the left of each form section header.

Click that to show a split screen view: one frame with the attendee view of the form, and the other with the admin-side configuration screen for that form section.

Select (Do not change) in order to leave the registration status unaffected by entry into the form.

Select (Do not change) in order to leave the registration status unaffected by exit from the form.

• Custom statuses added on .

• The 11 default registration statuses ( New, Requested Invitation, Waitlist Hold, Invited, Request Denied, Invitation Sent, Pre-Registered, Declined Invitation, Cancelled, No-show, Attended ) unless the account has the Show Default Statuses option cleared on ; in which case none of those are available.

But it is very rare for an account administrator to clear this setting.

Page Layout

Select the sections that you want to include in the form from the Available Sections list on the left, and move them to the Online Form Sequence list on the right.

Video: (2 min.)

(To save scrolling through a long list of sections, you can type any part of a section name in the Filter text box. That’s a predictive search that limits the list to matching sections.) (If there are any sections in the Online Form Sequence box that you don’t want to include, move them back to the Available Sections box.)

Insert a {Secure Page} break before any section that collects credit card information (such as the Payment or Accommodation sections) or before a section to build a multi-page form. Either causes the page before it to end with a Continue button.

Three Rules for Building a Registration Form

1. Every form must include the section.

2. The Accommodation Entry section is optional.

If it is not used, then attendees will only be able to request one room.

If it is used, then it must be on the page immediately before the section.

The Accommodation Entry section serves no purpose other than as an introduction to the section.

3. The last section of the form must be a section.

You do not need to add a {New Page} at the end.

Page & URL Titles

You can choose to display a step-by-step navigation bar in this section.

The navigation bar helps attendees to see where they are in the registration process as they proceed through the form.

Each number corresponds directly to a section in the Page Layout section (above).

Boxes left blank will not display on the final navigation bar.

The registrant’s browser will also include this label after the registration site name, confirming the current step.

(The forms are by default 508 compliant, this enables screen readers to identify the page a registrant is currently on. Keeping in mind that any custom HTML added in the events should follow 508 compliance to ensure everything in the page stays accessible. One example would be adding a banner HTML, to keep things 508 compliant double-check that any custom HTML includes aria-labels which helps screen readers relay information correctly.)

The character used to separate the titles.

Default = » – the HTML code for the double right-angle quote character, ».

Click the color picker to the right of the text entry field to select a color, or enter a hex-code directly, e.g. #003385.

Font styles can be configured on the page.

Can be plain text or HTML.

Default = » – the HTML code for the double right-angle quote character, ».

Many planners do not wish to show registration form navigation on the entry page if one is used, especially where the attendees may be forced to authenticate with a username or password.

A list of text fields numbered from 1 to n, where n is the number of pages you have included in the Online Form Sequence (above).

Each one is preceded by a #.

In each field, you can enter an optional text label to be added (preceded by #) to the URL for that page.

(Caution: The examples you see are just placeholders, with suggested text. To use this feature you must enter your own text.)

This enables each page of your form to have a unique URL, so that form progress can be tracked via embedded web tracking codes.

For example, if this was “ENTRY”, then the URL for the first page would be something like: example.com/profile/form/index.cfm#PKformID=0x12345678a

// #ENTRY

You could then use that page-unique URL in your web analytics.

That title is available as a Dynamic Data Field (DDF) in the Advanced Display and can be included in your display shell.

Registrants see it as the name in their browser tab.

Web analytics programs can pick it up for reporting,

Global Display Settings

Global Display Settings determine the default display behavior for the entire form.

The labels may be displayed to the left of the input fields or above them.

The default is Left / Right.

You would usually change this to Top / Bottom if you use the Insert Row button on to create a multi-column profile section layout, making the online form look more like a paper registration form.

Note: Does not apply to quite all sections at the moment.

Does apply to Registration Details, and to these sections of the Verify and Confirm pages: Accommodation, Appointment, Attendee Type, Questions, Registration Details, and Travel (V.1).

Default = Text.

Default = Text.

Default = Subheader.

This is a subtle layout tool that inserts slightly more space around form sections.

These are configured on .

Required Fields Settings

Certain optionally displays an image next to each field on a form page which is required.

If this field is set to blank no image will be displayed.

Default is an asterisk = <span class="error"> * </span>

Default = “ Please correct the following errors: ”

This is only required to make forms 508-compliant.

A screen-reader user can click the hyperlinked error message to focus the cursor on the associated field.

Required Fields Messages

You can customize the error messages displayed to the attendee when what they have entered fails validation.

The should be enough to explain each one.

Agenda Item Error Messages

You can customize error messages related to agenda items.

The should explain their use.

Labels for Registration Assistance Link

You can customize the message shown to an attendee if they click the link for registration assistance.

You can include HTML tags in the text.

The should be enough to explain each one.

Labels for Buttons and Links

Here you set the messages that appear on standard links and buttons that can be automatically displayed on the form.

If no text is entered in a field, the button will not be displayed (except that the Continue button is Required).

Default = “ Continue ”.

Default = “ Add Another Registrant ”.

Default = “ New Registration ”.

Default: “ <br /><br />Email Registration Assistance ”.

This is to avoid fake form submissions and subsequent spam emails generated by web ‘bots.

Caution: If you clear this option, the form will not include a CAPTCHA check box.

Creating and Editing Registration Forms (ADVANCED SETTINGS)

Click the Advanced button on this Form > Setup page to edit messages that are displayed automatically when triggered by circumstances.

Each message contains default text which you can change or delete.

Each one of these settings includes the following fields: 1. Append – If required, select a dynamic data field (DDF) to append to the Header of the Message. 2. Header Text – The text to be displayed in the header bar. Example: “Important Notice”. 3. Message HTML – The text of the message displayed when triggered. 1. For each one, you can accept the default or customize it as necessary. 4. Enable Editor? – If selected, you edit the Message HTML in a WYSIWYG editor, with the usual controls for formatting it. 1. If left clear, you enter the message in plain twext (which can still include HTML tags). 5. Show the Registration Assistance Link – If selected, a link opens a pop-up window that enables potential attendees to contact the primary Registration Contact for the event.

Customize Entry Page Message (Before Form Open Date)

Customize Entry Page Message (After Form Close Date)

Customize Entry Page Message (After Event End Date)

Customize "Closed Form" Message

Customize "Event Registration Capacity" Message

> Note: This message is not displayed in either of these situations:

1. If Registration Capacity is blank, meaning there is no limit.

2. If the option is selected to Allow form to remain open when event capacity is reached. (See under , above.)

3. That includes when Automatic Event Waitlisting is enabled, since that requires the latter option to be selected.)

Customize "Maximum Concurrent Registrations" Message (Based on active sessions)

If you are anticipating an event will be in high demand and will have a spike of registrations upon going live, we recommend that you contact Certain Product Support with the name of your event, your go-live date and time, and the anticipated number of registrations within the first hour.

Product Support can then make a recommendation on the maximum number of concurrent sessions (registrations) that can be reached before a custom message is displayed.

This feature works in conjunction with the ‘Incomplete registrations count against capacity/inventory for ‘X’ minutes after their last modification ’ value that is defined under > Global Settings section. This value defines the number of minutes that a registrant has to complete their registration before their session is timed out.

When the maximum number of registrants is reached, the custom error message will appear and the page will refresh every 15 seconds, allowing in new registrants as other registrants complete the form. An image will appear below the custom message, indicating the page will automatically refresh in ‘X’ seconds.

If you would like to extend the length of the refresh interval, this value can be modified by Certain Support.