Editing HTML Based Express Registration Templates

Sample Template

The xregsample.htm template can be downloaded from the Custom Templates folder on the ACEweb Resources site (you will need the user name and password to download this file. Contact your ACEware technician if you don't have them):
https://www.aceware.com/aw/templates/Custom/
Place the template in the wconnect/ace/custom folder.
Open the sample template and save another copy with a relevant name. Naming options:

Give the template a generic name such as MasterSM.htm. You can place a link to the page on your web site, or send the URL to the specific customers (e.g. a specific firm taking a contract course).

<a href="/wconnect/ace/custom/MasterSM.htm>Mastering Student Manager</a>

Name the template the course number, e.g. 16SACE010A.htm. The express registration page will open in place of the regular course status page.

Give the template a generic name then enter the name into the Information Page field on the course ACEweb Info tab. The express registration page will open in place of the regular course status page.

Setting the Course Code on the Template

You must associate the template with the appropriate course record. To do this, replace coursecode in the action attribute of the Form tag with the course code. E.g.

ACEweb Publish Properties

If you are using options #3b or #3c in the Sample Template section above, the ACEweb Publish Property setting will determine if the course is in the course listings AND if express registration opens when the user selects the course from the list.

Publish/Register Options - the course will display in listings and when the user clicks the link to the course status page, the express registration page will open.

No Publish Options - the course is not in the listing and users will not be able to open the page unless they have a direct link to the course status page.

Publish Only/NO Register - the course will display in listings but will NOT display the express registration page when the user clicks the course status page link. Users will see the regular course status page with the Online Registration not allowed message.

Do Not Publish - the course is not in the listings. If a user has a direct link to the course status page, the user will get the Online Registration Not Allowed message:

Adding Name and Name UDF Data Fields

Edit the template to include the appropriate Name and Name UDF Data fields. Field names (in the <input> tags) must conform to the following naming conventions:

Example: name="txtnmname1"

Characters 1-3 - HTML field type:
txt – open box for entry of text, numbers or dates*
lst (letter L, not number 1) – drop down selection list
chk – check box or radio button
Remaining Characters- the full field name.
Commonly used fields include: nmid (Name ID)**, nmName1 (First name), nmName2 (Middle), nmName3 (Last name), nmAddr1 (First address line), nmCity (City), nmState (State), nmZip (Zip code), nmDPhone (Day Phone), nmEmail, and any Name UDF (e.g. nudfc1, nudfl1, nudfd1, nudfn1).

For organizations who have the AddOwnAccount INI setting set to ON: if you want the system to check for duplicate registrations, you MUST include the Name ID field (i.e. nmid), and the Password field if you are using a password logon option. If you don't, each time a user enrolls through the Express Registration page, a new Name record is created.

If adding Name UDFs, you must also add the following hidden field inside the form tag:

<input type="hidden" name="NameUDFlag" value="">

If adding Name and/or Name UDF Logical type fields, you must add the following hidden fields inside the form tag, with the logical fields you are using entered in the Value attribute. If using multiple fields, separate names with a comma. E.g.

Name Logical Fields: <input type="hidden" name="NAMECHECKS" value="nmelist">

Name UDF Logical Fields: <input type="hidden" name="NUDFCHECKS" value="nudfl1,nudfl2">

*Date fields: ACEweb expects dates entered in the mm/dd/yyyy or mm-dd-yyyy formats. If the user only enters the numbers (e.g. 01012010), ACEweb will not recognize it as a date and will not enter a value in the specified date field.

Appending Data to the Name Comments Field

You can append several values to the Name Comments field on the Comments tab. For example, you can save several essay answers to the field.

To do so,

Name the first field txtnmcomm. E.g.:

Question 1: <textarea name="txtnmcomm" rows="2" cols="60" value="" tabindex="161"></textarea>

Name each subsequent field appendnmcomm. E.g.

Question 2: <textarea name="appendnmcomm" rows="2" cols="60" value="" tabindex="162"></textarea>

Question 3: <textarea name="appendnmcomm" rows="2" cols="60" value="" tabindex="163"></textarea>

The information entered in the fields will be appended to the Name Comments field--with line breaks between the field entries, in the order in which they appear on your template:

Adding Registration and Registration UDF Data Fields

You can also use the Express Registration option to submit data to Registration and Registration UDF fields. The field names (in the <input> tags) must follow the standard naming technique:

Example: name=" txtrgstatus"

Characters 1-3 - HTML field type:

txt – open box for entry of text, numbers or dates*
lst (letter L, not number 1) – drop down selection list
chk – check box or radio button
Field Name - the full field name. Available fields are: rgcode, rgmisc, rgregnote, rgstatus, rgcnfirm, rgptcert; and any Register UDF (i.e. rudfc1, rudfd1, rudfn1, rudfl1)

You must also add the following hidden field inside the form tag:

<input type="hidden" name="RegUDFlag" value="ON">

*Date fields: ACEweb expects dates entered in the mm/dd/yyyy or mm-dd-yyyy formats. If the user only enters the numbers (e.g. 01012010), ACEweb will not recognize it as a date and will not enter the date in the specified field.

Tracking Code

If you want to use the registration Tracking Code on your html based template, the field name must be lstTrackCode. E.g. :

...

Adding Unlimited UDFs

You can use Unlimited UDFs on the Express Registration page.

Add the ECDCFlag hidden field inside the form on your Express Registration page.

Add your Unlimited UDFs fields to the template. The Name attribute must use the "txt" prefix, followed by "nudfu_" if a Name Unlimited UDF, or "rudfu_" if a Registration Unlimited UDF, followed by the UU field name.

Example:

Requiring Fields

Requiring a field means the user must select a valid, non-blank, option. Here are specific rules when creating required fields:

You CANNOT require a checkbox or radio button type field with Yes/No options. The No option is the logical equivalent of a blank value.
Selection Drop Down Lists - there are 2 rules that apply to select tags:
- You must add a "Select [something]" option to your select tag with a blank value. This "Select.." option must be the first one in your list. The blank option will be displayed in the drop down and the system will not allow the user to continue until they select a valid option from the list. E.g.:
  <select size="1" name="lstc1RgCode" value="">
  <option value="">Select T-shirt Size</option>
  <option value="Small">Small</option>
  <option value="Medium">Medium</option>
  <option value="Large">Large</option>
  </select>
  produces this selection drop down box. The user cannot continue until they select a size from the drop down because the value of the Select -T-shirt size option is blank.
- If using a numeric field, all options must be valid values that are greater than 0.00 because 0.00 is the numeric equivalent of a blank value.

Express Registration pages do NOT support the regular options to require fields (i.e. RequiredFields INI setting or Supplemental Data Capture naming conventions).

You will need to use javascript to require fields on any express registration template. We recommend using the Jquery Validate plug-in to require fields.

SQL Database Users

If you are using an SQL database, all the open fields must have a maxlength value set to the length of the field. E.g. first name has a length of 30 characters so you need to have maxlength="30" set on the field.

Note: you do not need to set a maxlength on drop down fields, checkboxes, radio buttons, textarea fields, or date fields.

Adding Course Information

The Express Registration routine cannot access information from the course record. Therefore all pertinent course information must be placed directly on the page (e.g. replace Enter Course Title here with the course title).

Suppressing the System Generated Table

If you are using option 3b (see Sample Template section above), the standard course table will be displayed on your Express Registration page. You can suppress the display of this table by adding an If and Config sections to the bottom of the template--AFTER the closing </html> tag--with the CourseTable tag set to OFF.

</html>

##-If-##

##-/EndIf-##

##-Config-##

<CourseTable>OFF</CourseTable>

##-EndConfig-##

If you also want to suppress the default Payment Prompt (e.g. "A valid credit card ...", "There is no Registration Fee", etc.), add the PayPrompt tag to the Config section (after the <CourseTable> entry in above expression):

<PayPrompt>OFF</PayPrompt>

Course Fee Information

The Main Fees section is set up as a drop down list, with the name "lstRegFee" (letter L, not number 1). You will need to edit the options in the drop down list to reflect the main fees in the course.

The value attribute for each fee must match the Fee Order set in your Main Fees list.

<option value="1">Registration Fee  $595.00</option>

<option value="2">Senior Citizen Fee  $555.00</option>

In the above example, the Registration Fee is the first in the Main Fees list on the Course Fees tab. So the value attribute for the option is set to 1. The Senior Citizen Fee is second in the list, so the value attribute is set to 2.

The Optional Fees are set up as checkboxes, with each having the name "lstAddFee" (letter L, not number 1). The value attribute must match the fee order in the course.

<input type="checkbox" name="lstAddFee"value="1"> Banquet Ticket  $35.00<br>

<input type="checkbox" name="lstAddFee" value="2"> Extra Manual  $15.00<br>

In the above examples, the Banquet Ticket is the first fee in the Other Fees list on the Course Fees tab. So the value attribute for the option is set to 1. The Extra Manual is second in the list, so the value attribute is set to 2.

Free Courses

If the course is free, you must do the following:

Set up a "No Charge" fee on the course with the amount set to 0.00.
Add the following hidden fields to the form:

Note: the value for the ValidateCard field is case-sensitive and must be entered as OFF.

Remove the Fee Rate and Optional Fees sections from the express registration template.
Remove the Payment section from the express registration template.

Workshops

IMPORTANT: the express registration submission looks at the WksCodeMatch INI setting when determining workshop groups. Before adding workshops to your express registration template, please review the WksCodeMatch INI documentation.

If your course has workshops, you must:

Add fields for each workshop group. Note: workshops are considered part of a group even if there is only 1 workshop in the group.
Each field should be called lstWorkshop (letter L, not number 1) then the number of the group, e.g. lstWorkshop1, lstWorkshop2, etc.
You must use the individual workshop code in the value attribute.
Add the hidden WksGroup field to the template with the workshop groups listed in the value attribute. E.g. this example has 3 workshop groups. You need to add the hidden field even if there is only 1 workshop group for the course.

<input type="hidden" name="WksGroup" value="lstWorkshop1,lstWorkshop2,lstWorkshop3">

Examples

This is an example of a selection drop down list. The name goes into the <select> tag and the individual options have the workshop code in the value attribute (the first option has a blank value because it is merely the selection prompt). Users can only select 1 workshop from this group.

<select size="1" name="lstWorkshop1">
<option value="">Select a Workshop </option>
<option value ="AA01">21st Century Marketing Tips</option>
<option value="AA02">Economics of the New Millennium</option>
</select>

This is an example of using radio buttons for a workshop group. Users can only select 1 from this group.

<input type="radio" name="lstWorkshop1" value="AA01" id="WkShopList1" /><label for="WkShopList1"> 21st Century Marketing Tips</label>

<input type="radio" name="lstWorkshop1" value="AA02" id="WkShopList2" /><label for="WkShopList2"> Economics of the New Millennium</label>

These are examples of checkboxes. You can use checkboxes when there is only 1 workshop per group. Users can check as many as they want.

<input type="checkbox" name="lstWorkshop1" value ="AA01" /> 21st Century Marketing Tips

<input type="checkbox" name="lstWorkshop2" value ="AB01" /> Make a Molehill out of a Mountain

Custom WksCodeMatch INI Setting

In some situations, you may need to use a custom WksCodeMatch setting. To set a custom WksCodeMatch behavior, you must add the hidden WksCodeMatch field with the value attribute set. E.g. if you don't want to apply any time slot matching, set the value to 0:

Workshops with Fees

If your workshop has an associated fee, you must add the fee amount into the option value without the $ sign, e.g.

<option value="AA01 25.00">Workshop Option A</option>

When the user selects the workshop, the fee will be added to the total amount due for the registration.

If the course has no registration fees and users are only charged for the workshops they select, you must add the hidden lstRegFee to the form tag:

Payment Information

The sample express registration template contains the standard payment information fields (i.e. payment type, card number, exp date, etc.). However, you may need to edit the Payment Type list to remove any credit cards you don't accept.

Redirect Payment Services

If your organization is using a redirect payment service (e.g. tLink, PayPal), you will need to complete these steps:

Remove the following card info fields: credit card number, expire date, and CVV. The cardholder name can be left in place since its value will be read from the form and passed on to the payment service – this could help the user avoid double data entry.
If you are only accepting credit cards, remove the Payment type field as well.
Remove any javascript references to the above fields.
Add the following hidden fields (before the closing </form>):

Tabindexes

If you are adding or moving fields, you may need to reset the tabindex values.