Skip Logic for fields in Form (v11)

1 Introduction
2 Examples:

Introduction

You need to know how to edit XMLs to define skip logic.
Skip logic can be configured only via XML import.
Skip logic is retained even if the form is edited and saved via UI (enhanced in v6.2).

The syntax for skip logic in custom forms has been updated in version 11. To provide better clarity and to allow the use of additional object fields such as participant and visit, the new syntax is now similar to a JSON-based dictionary.

Below are the example of code to display fields when specimen belongs to Class “Cell“.

Old syntax:

$extendedObj.specimenClass = "Cell

New syntax:

specimen.specimenClass == "Cell"

Examples:

If the field is marked as ‘Required,’ meaning it is mandatory for data entry, adding the showWhen condition will override this 'Required’ setting.

Use Case 1: Show Form field based on the Specimen Class.

Added the ShowWhen condition in form XML to show field based on Specimen Class.

Show form field “Media“ only when specimen class == “Cell“:

When Specimen Class is not “Cell” then form field “Media“ is not shown:

Use Case 2: Show the Form field based on the value of another form field.

<showWhen><![CDATA[field_name == "value"]]></showWhen>

Show a field ‘Legal Guardian', if the participant is ‘Age Below 18' is selected as 'Yes’

Data-Entry page when ‘Age Below 18' is selected as 'No’

Use Case 3: Show a Custom field based on the value of another custom field.

For participant custom field use = cpr.participant.extensionDetail.attrsMap.variableName
For Visit custom field use = visit.extensionDetail.attrsMap.variableName

For Specimen custom field use = specimen.extensionDetail.attrsMap.variableName

Added the ShowWhen condition in form XML to show field based on another custom field value.

Show custom field “Branch Form field1“ only when custom field “Show visit Form“ value = y.

When custom field “Show visit Form“ value = n then custom field “Branch Form field1“ is not shown: