Select Form Input

The Select form input provides a single and mult-select user dropdown list.

Pre-v7 Layout (legacy)

Configuration Options

Configuration options are specified by one of the following input control types:

• Constant (free) text
• Selected (single) values from a dropdown list
• Checkboxes
• Rules expressions (identifiable by inputs appearing with a (?) to the right of the input box) - in general this indicates that when specifying a value the expression should be encapsulated in square brackets [...]

Configuration items are specified according to the form requirements as follows:

• To enable multi-select select the Multiple checkbox.
• The Chips option (obsoleted in v7) is a preferred styling when using multi-select with larger numbers of entries, as it switches from a comma separated display, to show values as lozenge chips.
• The selection choices derive from the Data Source, which may be defined in the Service Form or a shared Data Source.
• Choose Validate Required to make selection mandatory. For multi-select validate required enforces selection of at least one value.  Selection validation for Select and Autocomplete will also validate that values are present within the Data Source. This is server-side validation and is useful when forms are exposed via API.
• Placeholder text is displayed within the selection box until a choice is made.
• Specify a Label (text to appear above the input in bold font) and a Hint (text to appear below the input in small font) to reduce ambiguity on the form UI.
• When updating an existing value (not applicable when creating new data), a Default Attribute can be selected from a list of attributes from the bound form identity.
  • Alternatively, specify a Default Value with a rule expression
  • Important Note: when working with a shared Data Source the Default Attribute cannot be used, and instead a rule expression referencing the Projected silo is required, e.g.

 [Identity.Graph.Projected.<name of attribute(s) specifying current selection>]

• If you do not wish to target an attribute in the underlying schema, you can redirect the value on form submission to Update Auxiliary Attribute instead
• Use Prepend Icon or Append Icon to specify (or derive) string values corresponding to Lucide Icons names
• To encrypt text value(s) at rest, select the Encrypt checkbox.
• Use a Rule Validation expression to validate the input with a rule, such that any non-null result returned.  Common examples of rule expressions to use here include:
  • you require a mandatory value but only under certain conditions (e.g. a value must first be specified on another input control on the current form page)
  • you require more than one value to be selected