[hfe_template id='1680'] Dynamic Field/Value Visibility | HALO

Dynamic Field/Value Visibility

In this lesson we will cover:

– What Dynamic Visibility Is

– Configure Dynamic Field Visibility 

What Dynamic Visibility Is

Dynamic field visibility is the process of making a field dependant on the value of another field. When one condition is selected, the field will be made visible. 

For example, we can configure fields within a form on the end user portal to only appear if the below checkbox is selected. This guide: here, includes a use case of dynamic field visibility (Topic 2: Adding dynamic visibility to a service status field).

Fig 1. New Starter Form

Upon the end user selecting the checkbox, the following fields will appear requesting additional details.

Fig 2. Dynamically Visible Fields Appearing

Configure Dynamic Field Visibility 

To configure a field's Dynamic Field Visibility, we will need to navigate to Configuration > Ticket Type > Select the Ticket Type >  Edit the field list. We will then need to edit the field or the field list group by selecting the pencil icon.

Fig 3. Editing Visibility of a Field

A popup will appear where you are able to able to configure its visibility and make the field mandatory if needed.

Under the Dynamic Field Visibility heading, click add.

Fig 4. Adding Dynamic Field Visibility to a Field

Now that the dynamic visibility is set for this field shown in Fig 4, the only way that the field will become visible is that the "Do you require hardware…" checkbox is checked on (Value=True).

When the add button is clicked (Shown in Fig 4), an additional popup will appear where you will have to specify which field you would like to make the current field dependant on upon selection.

Fig 5. Adding The Visibility Restriction

Once you have selected the field that will be dependant on the other, you will have to select the value. In this case as it is a checkbox, select that the checkbox is enabled.

Fig 6. Dynamic Field Example

Once this has been selected, click save and now the field visibility will take effect. Fields such as single select and multi select custom fields, that contain a set list of values (not SQL lookup custom fields) will have the additional table of Dynamic Field Value Visibility when editing the fields on a ticket type:

Fig 7. Dynamic Field Value Visibility

This values table will populate on i.e. the "Ticket Tags" field or single select fields that you create in the custom field area of Halo.

[hfe_template id='2416']