Figure 1: Screenshot with Select Box highlighted in sample CRM app
Screenshots taken from http://localhost:8080/jw/web/console/app/crm/1/form/builder/crm_account
Figure 2: Select Box Properties
| Name | Description |
| 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. |
| Options (Hardcoded) | Select Box options |
| Or Choose Options Binder | Select Box options to be populated using Options Binder plugin. |
| Name | Description |
|---|---|
| Value | Default Value when there's no existing value found. Hash variable is accepted here. For example, you may key the following #currentUser.firstName# #currentUser.lastName# to pre-populate the field with current logged in user's name. |
| Multiple Selection |
|
| Validator | 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". |
| Field ID to control available options based on Grouping |
|
| Size (Rows) |
|
| Readonly | 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". |
| 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 |