Information About Custom User Fields
What are User Custom Fields? - This feature is used if you need to collect and store additional user information. Adding a custom field lets you expand the user database to contain additional user data. Examples include membership numbers, identification codes, addresses, or special dates.
There is no technical limit to the number of additional fields you can add in your test.com site. However from a practical perspective if you have more than twenty fields, contact your GAUGE/test.com representative; there might be better ways to capture the information you may need. One alternative is using no score survey like questions you can add to your tests.
Adding Custom User Fields
To add a custom user field, navigate to Custom User Field section by going to Manage > Settings > Configuration Settings > Custom User Fields.
Next click on the button that says "Add Custom User Field". Then give your user field a name and enter a description. When you are done make sure you click the checkbox that says "Is Activated" and click the "Save New User Field" button at the bottom of the page.
Optional Custom User Field Settings
Authenticate Behavior Option
As a security measure, prior to starting a specific test or program, you can require users to validate against a previously entered value in a custom field. For example, if a custom user field is added to contain users' driver's license numbers before a user is allowed to start a test, they would need to enter in their correct driver's license number. Selecting one of the authentication types below activates this custom user field for this purpose.
Once a custom user field is set up here or authentication purposes, you then need to edit the specific test (or program) on the Options tab and indicate you want this feature turned on for that specific test/program.
More than one custom user field can be set up for authentication. When the feature is turned on for a test, then all the custom user fields set up for authentication will be displayed to your test takers. If you are using the feature that hides custom user fields from users based on user group membership, then those fields will not be included in any authentication.
Two types of authentication are available. 'Challenge' authentication is used to prevent a user from starting content unless they know the value of the field they are being challenged to provide. 'Verification' authentication is used to capture (and save) the information you are asking a user to provide. From a security perspective, 'Challenge' authentication is stronger because the application is actually comparing what a user has entered against information already entered in the application, while 'Verification' authentication only collects data. For 'Challenge' authentication if no value was previously entered to compare against, then the application will collect (and save) whatever value is entered and then will then let the user proceed with starting their content.