Joget DX Preview Release Available for Download
Check out Joget DX, the next generation successor to Joget Workflow for faster, simpler digital transformation.
Multi Select Box allows you to select multiple items with auto-complete behaviour. Multi Select Box is a useful replacement for the ordinary SelectBox, particularly when there is a very long list of options to choose from. Options are displayed based on the user's input.
Figure 1: Screenshot of Multi Select Box in Form Builder
Figure 2: Screenshot of Multi Select Box in actual Form
Figure 3: Multi Select Box Properties
|ID||Element ID (By declaring as "country", a corresponding database table column "c_country" will be created)|
|Label||Element Label to be displayed to end user.|
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.|
Figure 4: Multi Select Box Properties - Advanced Options
Default Value when there's no existing value found/selected.
Hash variable is accepted here. For example, you may key the following
to pre-populate the field with current logged in user's name.
You may define multiple default options by separating them using semicolons.
Toggle Multiple Selection.
|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 to the current value of the element ID defined.
Column width in characters.
Determines if the element is editable.
|Display field as Label when readonly?|
Displays the value of the element as plain text when element is set to "Readonly".
Attach a Validator plugin to validate the input value.
When will validation takes place?
Validation will takes place whenever form is submitted except when it is submitted as "Save as Draft".
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.