User Guide
The system is very straightforward to use. You can start using it for your own purpose by following three logical steps:
System behavior and User interaction
Upon submission of the registration form, the fields are checked whether they are blank or complete.
If there are required fields that are not filled, the system generates an error page identifying them and prompts
the user to complete the omitted fields. The next step in the data validation process checks whether the email address
is valid by sending an email confirmation message to that address. The user who receives this email must click on
the confirmation link in the message if s/he wishes to complete the registration process. Upon confirmation, the user receives a final
confirmation message that his/her registration is complete.
The registration form closes automatically based on the
expiration date specified during the event registration step.
Finally, you can view the
registration records and statistics of your event or export the data in CSV format for additional processing or integration into a different system.
Connect to the event registration page.
On this page you can (1) define the name of the event; (2) choose which fields are required and which are optional;
(3) give a description to the fields that you want to use in the registration form;
(4) set a closing date for the registration.
The description gives meaning to the generic fields, which helps
you make sense of the registration data eventually.
For user convenience there are predefined fields,
which are semantically meaningful to the system, such as email, first name, and last name.
You can't change the descriptions of those fields.
The only required field is Email. All other fields are optional.
An unchecked field is regarded as an optional field, which can be left blank in the registration form.
Your registration form should reference the fields using the field names displayed in abbreviation
on the event registration page.
The system assigns a unique ID to each registered event. You need this ID for your registration form,
to customize the response messages and access the registration database.
If the event registration is successful, you will get an
EventID as shown below:
There are four places in the registration workflow that the person registering for an event gets a response message from
the system: (1) upon submission of the registration form, (2) registration confirmation request email,
(3) registration completion, and (4) registration complete confirmation email.
Each message has two parts: (1) customized message and (2) registration details.
The text file containing the customized message can contain HTML code and must be saved as Unicode or UTF-16LE
if encodings other than ASCII are used.
Note: it is not advisable to use HTML tags in the email response message.
The customized message files are named according to the following convention, where #eventID# is the ID of the event
you get when you register an upcoming event:
Submission Web response: "submit_message_#eventID#_UTF16_LE.txt"
Confirmation request email: "email_message_#eventID#_UTF16_LE.txt"
Registration completion Web response: "registration_completion_message_#eventID#_UTF16_LE.txt"
You can also reference three system variables in your customized messages. The table below describes the availability of this feature for the different message types.
|
|
#event_name# |
#registration_info# |
#confirm_link# |
|
Web submission message |
OK |
OK |
|
|
Confirmation request email |
OK |
OK |
OK |
|
Web registration completion message |
|
OK |
|
|
Registration completion email |
OK |
OK |
|
There are only two simple requirements to observe when creating your own registration form: (1) field references and (2) action parameters.
You can also user the form generator utility to create a simple template, which you can
use as a basis to develop your own registration form.
