Visibility

What is it?

Visibility settings are available to all widgets. The settings are able to control when to display or hide that widget and whether it is editable or read-only

How to configure it?

1. In the Page Builder, click on the widget then click the settings button = on the quick control panel.

2. Click the ‘Visibility’ tab.

You will discover two sections: Default Value and What if 

Below are the meaning of the terms under the ‘visibility’ tab:

How to Use Conditional Visibility

Click the “+ New Conditional Visibility”.

Specify your condition. (Know More: Filter and Condition)

Click Edit Button again if you need additional conditions. 

Data Input of Invisible widgets

Due to different sequences of steps, some invisible widgets may store data input, some may not. Simply speaking, we can use the following general rule to conclude the behavior of the system to store data input of invisible widgets.

Default-Visible Widget Example

Consider a form of selecting Department, Category of the issue reported and Screenshot or Files to upload files as shown below:

The widget Screenshot or Files has the following visibility settings:

1. It is defaulted to be visible.

2. If the Department selected is IT Dept, the widget Screenshot or Files will be invisible. All changes made on this widget before the selection of the department will not have any effects on the form record. 

3. If the Category selected is Username & Password, the widget is visible. This condition is higher than that of Department, meaning that it overrides the condition of Department if both conditions are satisfied.

Consider the following 2 situations to see the priority and data input behavior.

Situation 1

Department: IT Dept

Category: Others

At first Screenshot or Files is default to be visible. The user uploads a file to it. Then, the user selects the department as IT Dept. Screenshot or Files become invisible. Since the category selected is Others, no condition is set for this option, Screenshot or Files is still invisible. In the end, the uploaded file will not be passed to the database after saving the record.

Situation 2

Department: IT Dept

Category: Username & Password

At first Screenshot or Files is default to be visible. The user uploads a file to it. Then, the user selects the department as IT Dept. Screenshot or Files become invisible. The user selects the category as Username & Password. Screenshot or Files should be visible again. Since the higher priority condition about Category is satisfied, the lower priority condition rule for Department will be skipped. Finally, Screenshot or Files is visible when saving the record. So the uploaded file will be passed to the database.

Default-Invisible Widget Example

A common reason for having default-invisible widgets in a form is to input and store data for internal purposes. Consider the following example:

This is a leave application form. The upper widgets are defaulted to be visible and the lower widgets are defaulted to be invisible.

Suppose the staff is applying for maternity leave, he is only required to fill in the upper part. The lower part is not shown to the staff  while its values are automatically filled in by the system through some data sources and calculation. This information is generated to be used in internal validation settings. Considering the end user of this form, whose goal is just to apply leave, these information are useless and are therefore set to be invisible.

This example shows that the values of widgets defaulted to be invisible are still stored into the system. And the common situation to use this feature, is when the information is not important to end users but essential for the system's internal processing purpose.