You can configure visibility rules on web form fields to dynamically present additional fields and options based on data subject selection. This ability is limited to advanced user roles with enabled permissions to edit and configure web forms.
To configure dynamic web form fields
Many web form template fields come preconfigured with visibility rules. They will appear in the drop-down list and live preview with the Visibility Rule icon. Follow the below steps to add visibility rules to active fields added on the web form.
On the menu, select . The Web Form Templates screen appears.
Click the View button on web form template you want to configure. The Web Form Customization screen appears.
-
On the Web Form tab above the configuration options, click the Branch 
icon.
-
Select an active field from the list you want to dynamically configure. The field must be enabled on the web form in order to appear in this list.
Note
After you've configured rules for a field, the Branch icon will appear next to the field name in the drop-down list.
Click the Add Rule button.
-
Give the new rule a name, then proceed with the rule setup. For more information, see Visibility Rule Configuration Screen Reference.
Configure the visibility rule with ALL/ANY requirements, Conditions (e.g. is, is not), and the Action, then click the Save button. For more information see, Sample Configurations.
Note
You must organize the fields in the Web Form Customization screen for the rule to use conditional logic correctly.
For example, if you want a particular field to appear after the data subject picks a request type, you will need to place that field immediately after the Request Type field.
-
Once a rule has been configured, the Visibility Rule icon will appear in the live preview next to the dynamic field.
Visibility Rule Configuration Screen Reference
The specific configuration of your visibility rules will depend on your data collection obligations, which may include niche data subject types, internal versus external request types, state and/or country of residency, jurisdiction, or even the available products or services of your company. The following use cases are example configurations to provide insight into the capabilities of dynamic web form fields.
Request Types
You can configure dynamic fields to populate Request Type options based on data subject's subject type and state or country of residency. For example, you can leverage this configuration to show or hide different request types based on their jurisdiction's data rights (e.g. EU citizen rights versus those of California residents).
You can also use conditional visibility rules to provide guidance for data subjects when selecting a request type. For example, you can create a form field with informative guidance text in the Label and Description fields and provide button options or display content to inform them how their selection affects their web form submission.
Employee IDs
You can configure dynamic fields to populate Employee ID fields when data subjects select employee as their subject type. For example, you can use this configuration to service internal data subject requests from employees or to service specific account numbers from consumers.
Account Numbers
You can configure dynamic fields to populate Account Number fields when data subjects select customer as their subject type. For example, you can use this configuration to service specific accounts owned by consumers who submit requests.
Submit Button
Note
Visibility rules for this field are currently available as preview. To enable this feature, contact OneTrust Support or your account representative.
You can configure dynamic fields to disable the Submit button on a web form when data subjects select a specific country as their location. For example, you can use this configuration to disable request submission originating from a specific country.
