Comment on page
This determines how the control looks. For example, this may include colors, text, or the visibility of certain aspects of the control.
This determines if the Block can be seen or if it is hidden.
This specifies the style of the control, including if it is underlined, highlighted, or outlined.
This will show a temporary hint or description inside the field to help the user know what information is required. It disappears when the user enters a value.
This displays extra information about the field when the user hovers their mouse over it.
This determines if a clear button shows next to the value that the user entered. The clear button will clear the entered value if it is clicked.
The mode of the icon refers to the different ways the icon can be uploaded or added onto the control. This includes adding a pre-built icon from the library, uploading your own icon, or using the URL of an icon that exists on the web.
The format refers to the type or way that data is presented. Options for these include currency, decimal, exponential, fixed point, large number, percent, thousands, millions, billions, trillions, milliseconds, seconds, minutes, or hours.
This describes the behavior of a control. For example, read-only or disabled prevents the user from modifying the control.
The value is the value that is taken from the control such as the user input, or the default value of the control that you predefine.
Data Sources can be created for a page in the application and can be used to display contextual or real-time data to the user. Data sources can include databases or data streams and can be bound to controls on the page.
This allows you to filter the records to only display certain results that meet a condition. For example, displaying all records last modified in 2021.
This allows you to sort records in increasing or decreasing order.
Shows a limited number of results.
This will skip a number of records in the list.
This will determine if the default row is always shown, only shown when empty, or never shown.
Validation involves making sure the user enters the correct information on controls such as a form. Fields or Fieldsets (a group of fields) can be added to the page with a corresponding confirm button for the form. If the button and fields are configured to have validation and the user clicks on the confirm button, the fields in the form will be validated.
The validation group is able to group multiple forms on a page, each with its own action button. For example, if the user clicks on the confirm button for validation group 1, only the fields under that validation group will be validated.
If the field is blank, the form will not be submitted and an error will show.
If the user enters a value that does not match a specific pattern (for example, the input must contain at least two words), the form will not be submitted and an error will show.
Validation patterns use Regular Expressions (regex) to pattern search the value and determine validity.
This is the text that displays to the user when the user did not enter the value correctly.
This is an option for buttons that allows you to choose the validation group the button should validate.
The action refers to any event that may be triggered when the user clicks on a Block or part of a Block. For example, the page may redirect to another page or website, a data source may be updated, or a confirmation dialog may appear.
This configures the page or website that the webpage will navigate to when the user clicks on a control. The options are:
- Landing Page takes you to the current App's landing page
- Page takes you to the specified page of the current App
- Previous Page takes you to the previous page of the browser
- URL takes you to the specified URL (any website), optionally in a new tab/window
You can use parameters if you want to send particular values to another page. For example, you may want to send the value of a control to another page as the user is navigating to it, in order to change the data on that page dynamically.
Operations include inserting records, updating, deleting, or refreshing a data source. For example, if the user clicks on a button, the details they entered can then be inserted as a record in the database. If multiple operations are required, the order that these actions are executed can be changed. For example, you may want to update the database first before deleting a record.
If the execution condition option is set to true, you will then be able to add a condition that will be checked before operations are executed. You also have the option to override the fields that are in the data source.
If the confirmation dialog option is enabled, a confirmation message dialog box will appear when the user clicks on the button.
The title and message of the dialog box can be configured as well as the text on the continue and cancel buttons.