Multi-Registration Setup

Step 04: After setting up the layout, configuring the webcast list, and arranging the standard form fields, now you can setup the custom form fields. In this step you will be able to add 6 custom field types, update the labels and change the display order of the custom fields. The custom field types that can be added to the template are:

  • Textarea (line 365)
  • Textfield (line 377)
  • Select Dropdown (line 390)
  • Radio Button Options (line 409)
  • Multi-Select Checkbox (line 429)
  • Single Checkbox (line 452)

If you are adding a dropdown, radio button or checkbox UDF, the "value" must match exactly to the value that was added in the system otherwise the data will not be recorded. If you need multiple UDFs of the same type, be sure to follow the structure in the code. You can also copy the first curly brace "{" to the last curly brace with comma "}," of that specific UDF and paste in the code.

The sections below are samples of the JavaScript that will need to be updated in the template. Each section below is separated by UDF type. When adding UDFs to the form, the main areas in the code you need to focus on are:

  • "labelText" - appears above the field
  • "name" - in this case you will be replacing the X's in "UDFXXXX" which is the UDFNo
  • "required" - determines if the field is required or not
  • "order" - allows you to adjust the order the fields display in
Textarea UDF 
  1. // TEXTAREA
  2. {
  3. labelText: "Textarea Label", // Change label above input field
  4. fieldType: {
  5. inputElem: "textarea" 
  6. },
  7. id: "",
  8. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  9. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  10. order: 35,
  11. },
Input Textfield UDF 
  1. // INPUT TEXTFIELD
  2. {
  3. labelText: "Input Label", // Change label above input field
  4. fieldType: {
  5. inputElem: "input",
  6. type: "text" //ADD "text" AS TYPE TO CREATE TEXT FIELD
  7. },
  8. id: "",
  9. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  10. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  11. order: 40,
  12. },
Select Dropdown UDF 
  1. // SELECT DROPDOWN
  2. {
  3. labelText: "Select Option Label", // Change label above input field
  4. fieldType: {
  5. inputElem: "select"
  6. },
  7. list: [{
  8. value: "Option 1" // UPDATE VALUE OF SELECT OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  9. }, {
  10. value: "Option 2" // UPDATE VALUE OF SELECT OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  11. }, {
  12. value: "Option 3" // UPDATE VALUE OF SELECT OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  13. }, ],
  14. id: "",
  15. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  16. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  17. order: 45,
  18. },
Radio Button UDF 
  1. // RADIO BUTTON OPTIONS
  2. {
  3. labelText: "Radio Label", // Change label above input field
  4. fieldType: {
  5. inputElem: "input",
  6. type: "radio"
  7. },
  8. list: [{
  9. value: "Yes", // UPDATE VALUE OF RADIO OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  10. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  11. }, {
  12. value: "No", // UPDATE VALUE OF RADIO OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  13. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  14. }, ],
  15. id: "",
  16. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  17. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  18. order: 50,
  19. }
Multi-Select Checkbox UDF 
  1. // MULTI-SELECT CHECKBOX
  2. {
  3. labelText: "MultiSelect Checkbox Label", // Change label above input field
  4. fieldType: {
  5. inputElem: "input",
  6. type: "checkbox"
  7. },
  8. list: [{
  9. value: "Option 1", // UPDATE VALUE OF CHECKBOX OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  10. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  11. }, {
  12. value: "Option 2", // UPDATE VALUE OF CHECKBOX OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  13. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  14. }, {
  15. value: "Option 3", // UPDATE VALUE OF CHECKBOX OPTION (MUST MATCH VALUE THAT IS IN THE SYSTEM)
  16. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  17. }, ],
  18. id: "",
  19. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  20. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  21. order: 55,
  22. },
Single Checkbox UDF 
  1. // SINGLE CHECKBOX
  2. {
  3. labelText: "", // For a single checkbox, it is recommended to add your text to the value in the list below. If you want a label you can add it between the quotes.
  4. fieldType: {
  5. inputElem: "input",
  6. type: "checkbox"
  7. },
  8. list: [{
  9. value: "Sinlge checkbox text displays here", // Change the text that displays next to the checkbox here
  10. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  11. }, ],
  12. id: "",
  13. name: "UDFXXXX", // Replace XXXX with the UDFNo found in PB, i.e UDFXXXX to UDF1000
  14. required: "1", // 1 = REQUIRED, 0 = NOT REQUIRED
  15. order: 60,
  16. },

*Please note: All numbers displayed on the left side of the code are based on the line numbers displayed in the text editor when editing the HTML in the template. The code above is just a visual reference of the templated HTML that should be used as a guide. It is HIGHLY RECOMMENDED to update the code that is within the template.

If there are any questions on configuration of the Multi-Registration Template, send an email to: streaminghelp@notified.com.

To download the latest Multi-Registration Template, click here.

© Copyright 2019. All rights reserved.