Follow

Notes on field value dependent regions in surveys

  1. Date and time logged data types need to be added with the same options as are available for date and time user defined fields.
  2. Checkbox and radio button logged data types need to be added as enhancements to the dropdown list types. The same types of display options (checkbox, radio button, number of columns) as are available for dropdown list fields in Recruiter volunteer profiles should also be available in surveys. These parameters should be defined on the page which defines the dropdown logged data types. (Basically it is all one data type with three display options.)

It should be possible to override the logged data definition options such as the number of columns with a parameter manually included with the field when the field is inserted into a survey. This will permit things such as one number of columns on one survey and a different number of columns on a different survey.

    1. Example 1: 

 [t-shirt color::columns=3]

  1. It should be possible to insert field value dependent regions for the following types of fields:
    1. Drop Down List
    2. Checkboxes
    3. Radio Buttons
    4. Yes/No
    5. Number
    6. Dates
    7. Times
  2. For all field types it should be possible to insert field full and field empty dependent regions.
    1. Example 1 – Full: 

 [DREGION::FULL::age][/DREGION]

    1. Example 2 – Empty: 

[DREGION::EMPTY::age][/DREGION]

  1. For number, date, time, dropdown list, checkbox, radio button, and yes/no fields it should be possible to insert survey option value dependent regions for which the comparison value is any one of the available values of the field:
    1. Example – survey option value dependent region: 

[DREGION::option::value=“red”::t-shirt color][/DREGION]

  1. For number, date, and time fields it should be possible to insert field value dependent regions for which the value in the field is compared against any one of the standard numeric comparison operators (<, <=, =, >=, >) value is any one of the available values of the field:
    1. Example 1 – number field: 

[DREGION::option::value>“12”::Hours][/DREGION]

    1. Example 2 – date field: 

[DREGION::option::value>=“03 Feb 2008”::Start Date][/DREGION]

    1. Example 3 – time field: 

[DREGION::option::value>=“13:00”::Start Time][/DREGION]

  1. For number, date, and time fields it should be possible to insert field validation value dependent regions for which the comparison value is any one of the available values of the field:
    1. Example – survey option value dependent region: 

[DREGION::validation_error::value<“18”::age][/DREGION]

  1. For date fields “today” should be available as a comparison value
    1. Example – Date field: 

[DREGION::validation_error::value>“today”::Start Date][/DREGION]

  1. For time fields “now” should be available as a comparison value:
    1. Example 1 – Time field: 

[DREGION::validation_error::value>“now”::Start Time][/DREGION]

    1. Example 2 – date and time fields used together: 

[DREGION::validation_error::value=“today”::Start Date][DREGION::validation_error::value>“now”::Start Time]
Warning! You may not enter a date or time in the future.[/DREGION][/DREGION]

 

  1. For time fields it should be possible to enter the comparison value in either 12 hour or 24 hour format:
    1. Example 1 – Time field: 

[DREGION::option::value>=“13:00”::Start Time][/DREGION]

    1. Example 2 – date and time fields used together: 

[DREGION::option::value>=“1:00am”::Start Time][/DREGION]

    1. Example 3 – date and time fields used together: 

[DREGION::option::value>=“1:00pm”::Start Time][/DREGION]

  1. It should be possible to specify whether or not a logged data field is required in the survey. Whether or not the field is required is a characteristic of each instance of usage of the field itself in the survey and not a characteristic of the logged data itself. The default for all fields is “not required”.

Whenever a required field is inserted a value required dependent field is automatically inserted on a line by itself immediately after the field. The default text for number, date, time, short text, and long text fields is “!!! Please make an entry in the <logged data name> field.” Text in this field is red by default.

    1. Example 1: 

[Hours]<br />[DREGION::value=“required”::Hours]<font color=“red”>!!! Please make an entry in the Hours field.”</font>[/DREGION]*

*  It would be best to achieve the font color using the currently supported techniques instead of using the deprecated <font> tag.

Each time the OK button or link is clicked by the user all of the required fields are checked to see if a value has been entered. For each required field that is missing a value, the value required dependent region for that field is then displayed allowing the user to see all at once which required fields are missing values.

If any field validation value dependent regions (including field value required regions) are displayed when the OK button is displayed then form is not submitted and the user is not permitted to leave the form until all such warnings have been resolved.

Future enhancements: Add save a button and links that allow users to save uncompleted surveys without exiting. The OK button or link could be renamed “Finish” then to allow a user the capability to save and the Cancel button and link could be renamed “Close” to allow a user to close a incomplete survey. This would also require the addition of grid columns in the eCoordinator and Recruiter volunteer log books that would indicate the status of a survey as either “In progress” or “Complete”. It would also be necessary to keep a record of which survey is used to make each log book entry so that same survey could be used by a volunteer via Recruiter when editing or completing a log book entry or by an eC use when creating, editing, or completing log book entries. If an old log book entry did not have a survey attached to it or if all the logged data in the log book entry are not currently available as part of the survey currently attached to the log book entry then the currently eCoordinator method of editing the log book entry should be used.

  1. Nesting field dependent regions is permitted.
    1. Example – date and time fields used together: 

[DREGION::validation_error::value=“today”::Start Date][DREGION::validation_error::value>“now”::Start Time]<font color=“red”>
Warning! You may not enter a date or time in the future.</font>[/DREGION][/DREGION]

  1. Multiple regions dependent on the same logged data are permitted.
    1. Example: 

[DREGION::validation_error::value<=“0”::Hours]<font color=“red”>Please enter a value greater than zero and less than or equal to 12.[/DREGION]

[DREGION::validation_error::value>“12”::Hours]<font color=“red”>Please enter a value greater than zero and less than or equal to 12.</font>[/DREGION]

  1. Multiple instances of logged data are permitted.
    1. Example: 

[DREGION::option::age<“12”::Hours]Please enter your reasons for being considered for a special age exception:[Age exception explanation][/DREGION]
[DREGION::option::age>=“18”::Hours]Please enter your reasons for being considered for a special age exception:[Age exception explanation][/DREGION]

Note: (Future enhancement) It might be nice to permit an “or” syntax to avoid the need for repetition of the fields, tags, and text shown above in the examples for items 14 and 15.

Example: 

[DREGION::option::age<“12” or age>=“18”::Hours]Please enter your reasons for being considered for a special age exception:[Age exception explanation][/DREGION]

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk