A navigation list can be used to attach an action to an entire row. Such a row is called a navigation list item.
A navigation list with three empty rows.
The class property allows you to specify one or more cascading style sheet (CSS) classes for the widget. The classes should be separated by a space. The classes will be applied to the widget in the browser and the widget will get the corresponding styling. The classes should be classes in the theme that is used in the project. It overrules the default styling of the widget.
1) the default styling defined by the theme the project uses
2) the `Class` property of the widget
3) the `Style` property of the widget.
You can see which widgets in a page have styling applied via the class or style property by clicking the Show styles button.
The style property allows you to specify additional CSS styling. If a class is also specified, this styling is applied after the class.
will result in red text on a blue background.
You can see which widgets in a page have styling applied via the style or class property by clicking the Show styles button.
Navigation list item
Each row in the navigation list is a navigation list item. A navigation list item can be associated with an action. Conditional visibility is available for list items.
Action defines what action is performed when a navigation list item is ‘clicked’. This can either be opening a page or calling a microflow. For opening a page see Opening Pages and for calling a microflow see Starting Microflows. Microflows attached to a navigation list item have no Confirmation or Advanced microflow settings.
By default, whether or not an element is displayed in the browser is determined by how the page is designed and the user’s roles within the application. However, the page can be configured to hide the element unless a certain condition is met.
The widget can be made visible only if the object of the data view that contains the widget satisfies the specificied criteria.
A practical example would be a web shop in which the user must submit both billing and delivery information. In this case, you might not wish to bother the user with a second set of address input fields unless they indicate that the billing address and delivery address are not the same. You can accomplish this by making the delivery address fields conditionally visible based on the Boolean attribute
Based on Attribute Value
When selected, this shows the widget while a particular attribute has a certain value. Only boolean and enumeration attributes can be used for this purpose.
Based on Expression
When selected, this shows the widget while a provided expression evaluates to true. The object of the containing data view is available inside an expression as a
Note that the expression is evaluated in the browser, and hence, we advise against using “secret” values (like access keys) in it. In particular, we disallow usages of constants. Also, client-side expressions currently do not support all the functions that are available in the microflows. Please refer to an autocomplete list to know what functions are supported in your version.
The widget can be made visible to a subset of the user roles available in your application. When activated, this setting will render the widget invisible to all users that are not linked to one of the selected user roles.