Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
The easiest way to see how the Select Box works is to create a new app. Here are the steps:
Fill up the following fields as follows and click on OK (see Figure 3):
Options (Hardcoded):
Default Value | Label |
---|---|
Local | Local |
International | International |
Figure 3
Name | Description |
ID | Element ID (By declaring as "country", a corresponding database table column "c_country" will be created) Please see Form Element for more information about defining the ID and list of reserved IDs. |
Label | Element Label to be displayed to the end-user. |
Options (Hardcoded) | Select Box options Options defined here will not be put into use if Options Binder is defined below. |
Or Choose Options Binder | Options to be populated dynamically using Options Binder plugin. Performance Warning If you have thousands of select options or sourcing them from Options Binder, this may cause a significant increase in page load time. Consider using Popup Select Box instead. |
Name | Description |
---|---|
Value | Default Value when there's no existing value found/selected. A hash variable is accepted here. For example, you may key the following #currentUser.firstName# #currentUser.lastName# to pre-populate the field with currently logged in user's name. You may define multiple default options by separating them using semicolons. Sample option1;option2;option3 |
Multiple Selection | Toggle Multiple Selection. |
Validator | Attach a Validator plugin to validate the input value. When will validation takes place? Validation will take place whenever a form is submitted except when it is submitted as "Save as Draft". |
Workflow Variable | 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 |
Name | Description |
---|---|
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. Also knowns as a cascade select box where the first select box choice determines the second select box list of options. You can download the demonstration app ISIC List from the Joget Marketplace. If you are using Database SQL Query to populate the Select Box, Joget will use the field ID/IDs in the "Field ID to control available options based on Grouping" property in the SQL WHERE condition. If you need to pass more than one parameter, use the semicolon character to separate the parameters, for example "location;username". An example of the SQL query is as follows: SELECT * FROM tableName WHERE c_location = (?) AND c_username = (?) When Joget runs the above SQL in the Select Box, it will "plug" in the current Form location value and the username into the respective SQL conditional fields and retrieve the records accordingly. |
Name | Description |
---|---|
Size (Rows) | Determines the number of rows of selection to be shown. This option is useful when multiple selections are expected. An integer value is expected here. |
Readonly | 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". |
Name | Description |
---|---|
Workflow Variable | 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 |