Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Radio is one of the generic HTML Form input elements. In the Form Builder, one is able to define the options available to the Select Box via various means, including the use of Options Binder.
The easiest way to see how the Radio button works are to use the existing built-in App Expenses Claims. Here are the steps:
Fill up the following fields as follows and click on Apply Change (see Figure 3):
|Label||Element Label to be displayed to the end-user.|
Element ID (By declaring as "type", a corresponding database table column "c_type" will be created)
Please see Form Element for more information about defining the ID and list of reserved IDs.
Select Box options
Options defined here will not be put into use if Options Binder is defined below.
|Or Load Data From|
Radio options to be populated using the Options Binder plugin.
Default Value when there's no existing value found/selected.
A hash variable is accepted here. For example, you may key the following
to pre-populate the field with currently logged in user's name.
You may define multiple default options by separating them using semicolons.
Attach a Validator plugin to validate the input value. Please see Form Validator.
When will validation takes place?
Validation will take place whenever a form is submitted except when it is submitted as "Save as Draft".
|Field ID to Control Available Options Based on Grouping|
Dynamically change the available options based on the "grouping" attribute defined in the options by matching the current value of the element ID defined.
Determines if the element is editable.
|Display Field as Label When Readonly?|
Displays the value of the element as plain text when an element is set to "Readonly".
If the form is part of a workflow process, upon saving of the form (by clicking on "Save as Draft" or "Complete" button). The value in this input field will be saved into the corresponding workflow variable named here.
Using a non-existent Workflow Variable name
You will get the following warning with the name printed out (e.g. status) in the server log if you attempt to map to a non-existent Workflow Variable.
context attribute status does not exist in process context - adding new attributes to the process context is not allowed