Widgets have both individual and system settings. System settings are the same for all the widgets. They are used to configure a widget’s visibility and access to its data, define what happens, when the user moves or hovers the pointer over the widget, etc.
- On mouse enter handler. Create an event that happens on mouse enter, for example, a pop-up window with a tip. To do this, you need to add a corresponding script. Click the Create button, enter the script name and click Open. The Scripts tab opens where you can write the script;
- On mouse leave handler. — Create an event that happens on mouse leave. For example, make it close the tip window we created in the previous step. Add a corresponding script the same way as in the previous step. We recommend configuring these events together.
- Hide. Specify when a widget is shown on the form:
- Always show. The widget is always visible the users;
- Show on condition, Hide on condition. Specify a condition for hiding or showing the widget. To do that, bind a context variable to this field. For example, select Hide on condition and bind it to a Yes/No switch variable. The widget will be shown to the user if the user selects No when filling out the form. If the user selects Yes, the widget will be hidden. Below you will find an example of how this option is used;
- Show for groups. Select user groups that will be able to see the widget. Users who are not included in these groups will no see the widget;
- Always hide. The widget will remain hidden all the time;
- Read only. Configure access to the widget:
- It is best to use Inherit from parent option when you combine several widgets in one. For example, you place the Associated items widget into the Column widget that has the Read only setting. If you select the Inherit from parent option for Associated items, users won't be able to edit the list of items.
- If you select Yes, the user won’t be able to edit the widget's data.
- Select No to allow users to edit the widget's data.
- HTML styles. Here you can specify the CSS styles for the widget. For example, to enter its width.
- HTML classes. You can create an HTML style using the Code widget and apply it to the current widget. To apply a style, enter its name specified in the script in this field. You can use the same style in several widgets. For example, you can quickly apply one background color to all widgets on a form.
You can enable additional options for widgets that contain data, such as a tasks list, page header, added information, and so on. This will make the app form or custom page load faster.
- Load content when the tab is active. The option is used in the Tabs widget. Enable it to load the contents of the tab only when switching to it.
- Load the contents asynchronously. This option is available for widgets that contain data, such as Columns, My Tasks, Panel with header. Enable it to display the content only after the custom page or app form has fully loaded.
You can bind the widget settings fields to context variables. This is convenient if you need to dynamically change widget settings on a page or during a business process. To bind a field:
- Click the icon next to the field name. In the Hide field, select Show on condition or Hide on condition.
- Click <Not defined>.
- Select a context variable from the drop-down list. The list only displays variables with the same data type as the bound field.
- Save and publish the widget.
The setting is now defined by the selected context variable.
Let's say we have the Orders app to handle customers’ requests. For orders without prepayment, it is required to determine the payment schedule. In this case the sales rep fills out a table with the schedule information on a separate tab. The tab can be hidden or displayed depending on whether the sales rep checks the Full Prepayment box or not.
This can be done with the following settings:
- Go to the Orders app menu and click Form Settings.
- In the window that opens, add the following properties on the Context tab: Payments of the Table type and Full Prepayment of the Yes/No switch type.
- Go to the Create tab and click +Create form (if the form has already been created, click Edit form). The interface designer with the creation form will open.
- Drag the Tabs widget to the top panel and add the Order and Payment schedule tabs. Add the Full Prepayment property to the first tab and the Payments table to the second one.
- Go to the Payment schedule tab’s system settings. In the Hide field, select the Hide on condition option and bind it with the Full Prepayment property.
- Click Save and Publish on the designer top panel.
Now if the sales rep doesn’t check the Full Prepayment box, the Payment schedule tab appears on the app form. Here, the sales rep can specify the payment details for the current order.
Found a typo? Highlight the text, press ctrl + enter and notify us