Form Display Logic

NOTE: Form Display Logic is an advanced feature

Initial Considerations

This feature is useful for projects who have participants that follow different workflows, as it allows you to grant access to instrument(s) at the record level when/if condition(s) are met. The logic is very similar to branching logic, except rather than applying logic at the field level, the logic is applied at a records instrument level.

NOTE: Form Display logic impacts project user’s view of and accessibility to instrument(s). This feature affects the Record Status Dashboard, Record Home Page, and Record Instrument List.
When the condition is not met, said instrument(s) appear greyed-out and cannot be accessed within the user interface by default: (click on the images below to expand)

Record Status Dashboard

Record Home Page

Record Instrument List

Important notes:

Form Display Logic is merely a ‘display’ function, which means this feature does NOT block end-users from taking survey(s) that are greyed out from selection in the user interface.

If you are using the Form Display Logic feature and the ‘Survey Queue’ function, be sure to read the additional considerations provided at the end of this page!

Form Display Logic does not impact data imports as this feature only operates in the user interface to enable/disable the display of an instrument. It is possible to adjust the default display settings using the ‘optional settings’ found in the Form Display Logic interface:
An instrument may be selected in multiple conditions
- Form display logic is not able to enforce that all conditions be met, instead the form will be enabled if at least one of the conditions is met.

Simple example:

Let’s say you wish for a specific instrument to be accesible to 1 user group, and a second unique instrument to be accesible to user group 2. In this example, the project has 3 instruments:

'Study Intro' where the participant is assigned to a group field (1 or 2)
- ‘Treatment Survey’ should only be accessible to participants assigned to group 1
- ‘Control Survey’ should only be accessible to participants assigned group 2

To accomplish this you would…

a) Select the form(s) for user group 1 > insert logic, (see condition 1 below)

b)Select the form(s) for user group 2 > insert logic specific for group 2, (see condition 2 below)

c) Save

Now when reviewing the Record Status Dashboard you’ll see…

Records 1 & 2 which are assigned to group 1, have access to ‘Treatment Survey’, but do NOT have access to ‘Control Survey'
Records 3 & 4 which are assigned to group 2, have access to ‘Control Survey’, but NOT ‘Treatment Survey'

Now, let’s take it a step further to cover a special use case of using ‘form display logic’ with ‘survey queue' functionality…

If your Survey Queue is setup in a way which contradicts your Form display logic, Survey Queue functionality takes precedence over Form Display Logic.
- Although record 13 indicates they are in group 1, the survey queue setup directs all user to complete boths surveys after completing the ‘study intro’ survey, thus when the first survey is sent to a participant, they will be provided both surveys for completion, even though the internal user interface has the control survey inaccessibile:

Survey Queue Setup which contradicts the setup Form Display Logic conditions:

Participant’s View of Survey Queue after completing ‘Study Intro’ Survey:

Internal, Project user view / Result:

The Process (expand below)

Navigate to your 'Online Designer' page
Click ‘Form Display Logic’
Create your condition(s)
1. Select one or more instrument(s) you wish to apply access logic to. The logic you create controls when said instrument is accessible.
  1. If working with a longitudinal project:
    - Ensure your conditional logic includes the fields [event name] within the logic
    - Ensure you select the specific event(s) instruments you wish to apply logic to.
    - You will have the option to select unique event(s) or [all events]. Typically, [all events] is not used as form display logic is utilized to create unique conditions at specific timepoints, rather than across all timepoints.
      - Whether you use ‘all events’ or a unique event, will depend on your project workflow
Click ‘Save’
Understand the optional Form Display Logic settings available for use, this is very important if you are also using ‘Survey Queue’ functionality:
Review, Test, and Update Form Display Logic as needed

Additional Considerations

If implementing ‘Form Display Logic’ in a Production project which has already collected data, be sure to review the ‘Optional Settings' and enable as needed for your projects specific needs.
- Examples below :
  - Keep forms enabled if they contain data: this selection ensures instruments which would normally be greyed out and restricted from display/access due to the condition not being met, are accessible to internal users if data has already been collected in said instrument: (notice the 3rd instrument is available to view)
  - Hide forms that are disabled: If data has been collected and this setting is selected, then users cannot access the collected data from the user interface: (notice the 3rd instrument is greyed out:
  - Enable support for Surve Auto-Continue: When a participant is taking surveys that are showcased as ‘hidden’ (inaccessible) in the user interface, if that instrument which is ‘hidden’ also has the ‘auto-continue’ feature enabled, that survey will be skipped over.
    - (example) Auto-continue is enabled for the first 3 instruments, however because the additional support for auto-continue is enabled, when the participants takes their survey(s), they are not showcased nor provided the ‘treatment’ survey for completion.
    - If this setting had not been enabled, the user would have been given the ability to complete all surveys, including treatment, even though they were assigned to the control group condition.