Skip logic rules allow you to determine whether a field/page should be shown or skipped based on the value of a previous field.
Skip logic rules can be set for fields, groups or pages, and are useful when you would like to skip a field, group or page that should not be answered by a participant based on a previous response they gave. For example, if a participant indicates that they are male, all fields relating to pregnancy should be skipped for this participant.
You can add, remove or edit skip logic rules at any time.
An icon on the right of the field name indicates whether skip logic has been added to this field (green) or not (grey). Clicking on this icon takes you to the relevant tab so that you can add, view or edit your skip logic rules.
Setting up skip rules:
Click on the field, group or page you want to add skip logic to. In the 'Skip logic' tab, click on 'Configure skip logic' (only if you haven't specified any skip logic rules yet).
Note: Skip logic cannot be applied to the first page as there are no previous responses to configure the skip logic conditions.
Choose whether the field/page should be 'skipped if' or 'shown only if' certain conditions are met (3). Indicate whether this skip rule should apply only when all the prerequisites are met, or if any one of the prerequisites is met (4).
Next, select the source field (5) - the response to the source field will determine whether the current field/page should be shown/skipped. Different comparison operators (6) will be available to choose from, depending on the type of the selected source field. Finally, enter a value (7) for the condition. Depending on the source field type, this can be a static value, field reference or a function.
In the example above, the field 'first_name' will be skipped if the field 'consent' is equal to 'No' or if the value of the 'age' field is less than '18'.
Skip logic can also be configured to show or skip a field based on whether the source field has received a response or not. For example, I want to collect demographic information only if the participant's signature has been captured. If the signature has not been captured, the demographics page will be skipped.
Below is a summary of field types that can be used as source fields and the comparison operators and value of the condition that can be selected/chosen in each case.
|Source field type||Comparison operator||Value of condition|
|Text||Equal to, not equal to, has a value, has no value||static value, field reference or function|
|Number||Equal to, not equal to, greater than, less than, less than or equal to, greater than or equal to, has a value, has no value||static value, field reference or function|
|Single select||Equal to, not equal to, has a value, has no value||one of the source field's options|
|Multiple select||Includes, excludes, has a value, has no value||one of the source field's options|
|Cascade select||Equal to, not equal to, has a value, has no value||static value, field reference or function|
|Calculated value||Equal to, not equal to, greater than, less than, less than or equal to, greater than or equal to, has a value, has no value||static value, field reference or function|
(Image, Audio, Video, Signature)
|Has a value, has no value||-|
|Date/Time fields||Has a value, has no value||-|
|Advanced fields (Location, Barcode)||Has a value, has no value||-|
You can add as many skip logic rules to a field as required. You can also easily remove a skip logic rule by selecting the bin icon to the right of it, or remove all skip logic rules by clicking 'Remove all'.
Hint: Test your skip logic rules by using the 'Preview' button on the far right in your top toolbar.
Note: It is not currently possible to branch from one field to another. You can either add a skip rule to each individual field or page, or you can group fields together and then add a skip rule to the group.
Using the legacy form designer? Have a look at our article on using Skip logic in the legacy form designer.