Page Comparison

Initial Considerations

This tool 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 of to instrument(s) within . This feature affects the Record Status Dashboard, Record Home Page, and Record Instrument List on the left-hand menu when in a participant record. .

• When the condition is not met, said instrumeinstrument(s) appear greyed-out .When a condition is NOT met for a given record, the instrument and cannot be accessed within the user interface by default: (click on the image(s) images below to expand)

Important notes:

• Form Display Logic does not impact data imports as this feature only operates in the data entry user interface to enable/disable the display of instruments.You may define as many conditions as you want. A form may an instrument. It is possible to adjust the default display settings using the ‘optional settings’ found in the Form Display Logic interface:

  • Image Added

• An instrument may be selected in multiple conditions, but if so, please note that

  • 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'

• Record 5 has all forms available, as this record has not been assigned to a group, thus no conditions are able to be applied.

Image Removed

Image Added

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:

The Process (expand below)

Image Removed

Image Removed

Additional Considerations

• If

  your Survey Queue is setup in a way which contradicts your Form display logic, Survey Queue functionality takes precedence over Form Display Logic, as Form Display logic is only a display function for project users.

  • Example) The below example uses the ‘simple example’ use case listed above

    • Although record 13 indicates they are in group 1, the survey queue indicates that all records should complete the pre & post survey, so when the first survey is sent to a participant, they will be provided both surveys for completion, even though your user interface has this greyed out:

• 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 :

    Image Modified

    • Keep forms enabled if they contain data: this selection

    will ensure internal project user can access instruments that have already collected data, that

    • 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)

      Image Added

    • 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:

    this does the opposite of the above

    • Image Added

    • 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.

      Image Added

      • (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.

        Image Added

      • 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.