Using the Dashboard Rule Block

The Dashboard Rule Block is used to set user permissions and manage filters on a dashboard. This block supports both static and dynamic values. Within the Dashboard Rule Block, select the app and the dashboard. For each dashboard widget, you can set the user permission to view, export, add, or edit the selected widget. You have a dropdown list for View, Export, Add, and Edit actions from which you can choose the action as True or False, or get the appropriate value (either True or False) dynamically from a previous block.

 

 

You can set where, group by, sort by, and limit conditions for each widget.

 

 

You can display or hide action buttons in a datalist using the Dashboard Rule Block.

Note: Action buttons in a datalist are not only used to manage data but also to open a chat or display a pop up. You can choose to display or hide an action button within a datalist using the init rule.

In the Dashboard Rule Block, select the app, select the dashboard, and select the datalist. Click Action Buttons from the left panel and select the buttons to show from the dropdown list.

 

 

Note: All action buttons in a newly created datalist will be displayed in the Dashboard Rule Block. However, to view and select action buttons from an existing datalist, you must first go to Dashboard Edit and update the datalist to the dashboard.

Click the tab Set Filters to manage dashboard filters. Select the field and filter value from the dropdown list.

 

 

Click the tab Advanced Rules for more options. Choose the action as

  • Set static variable – to display specific data on an HTML card. Enter the inputs in the fields Variable and Value.
  • Redirect to url – to redirect a user to a specific page. The path to be redirected to can also be given as dynamic.
  • Hide tab – to hide a specific tab on the dashboard.

 

For the action Set static variable, you can set the variable name as dynamic also.

 

You have a Show JSON button within the block to show how the configuration has been saved in the backend.