Joget DX 8 Beta Released
The beta release for Joget DX 8 is now available, with a focus on UX and Governance.
If you have thousands of selections to choose from, Popup Select Box is an ideal form element to use as you will be choosing from listing with pagination and search filter, improving loading speed and user experience.
Figure 1: Screenshot showing Popup Select Box in Form Builder
Figure 2: Screenshot showing Popup Select Box in actual Form
Figure 3: Screenshot showing Popup Select Box in actual Form - Performing selection
Figure 4: Popup Select Box Properties
|ID||Element ID (By declaring as "appeal_claim", a corresponding database table column "c_appeal_claim" will be created)|
|Label||Element Label to be displayed to end user.|
|Data List||Data List to display for selection.|
|Display Field||Field ID from the target Data List for eventual selected option label.|
Figure 5: Popup 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.
Target Data List's column ID value to be saved as option value.
Toggle Multiple Selection.
|URL Request Parameters for Datalist|
Refine the target Data List selections by defining the filter criteria here.
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".
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".
|Select Button Label||Select Button Label|
|Popup Dialog Height|
Height in character
|Popup Dialog Width|
Width in character
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