Overview
Each form field can optionally have a visibility switch which is a rule that shows or hides the field based on what's been entered in other fields. For example, "Only show the spouse's name field if the candidate selects Married."
*Note* You will need the following permissions to access Forms:
- View Forms
- Create Forms
For more information on permissions, please see the article titled Onboarding - User Groups and Permissions.
Opening the Field's Rule Section
Begin by navigating to the Onboarding Portal > Configurations > Forms and select the intended form within the list:
If the form has been published, create a new "Draft" version by selecting "New Draft":
If the form is currently within a "Draft" status, select "Open Editor":
Within the Form Builder, locate the field you want to show or hide conditionally and select the Gear icon to open the field settings:
Building the Show/Hide Condition
Within the "Visibility" section of the sidebar, select "Add Rule":
Set the effect to either "Show" or "Hide":
- Show means the field appears only when the condition is met.
- Hide means the field disappears when the condition is met.
For our example, we want the "Will you submit to a drug screening" question to appear within the form in the event the employee has answered "Yes" to the previous question of "Will you submit to a background check"
Add a "Condition". For this example, we will select the following:
- Field: employee.custom_attribute.will_submit_background_check
- Operator: is
- Value: yes
Once the Condition has been added, select "Close":
Saving the Rule
Select "Save" within the sidebar to complete the addition of the Show/Hide Rule:
You will also see the condition as a visual on the field within the form builder:
To verify the rule is working as intended, select "Preview" at the top right of the form builder and then change the value on the controlling field. The dependent field should appear or disappear in real time.
*Note* Renaming a field will break the rules that point at it.
A rule references the controlling field by its path (form.existing_certification) stored as plain text. Renaming that field's path will update its PDF mappings and any subfields, but it does not update rules on other fields that point at the old path. Those rules keep referencing a path that no longer exists.
To fix it, open each field whose rule referenced the renamed field, re-pick the controlling field in the condition, and save. When you rename a field, verify the form's other rules before you publish.