Skip to main content
The Single Select form field allows users to choose from a dropdown list of predefined options. Each option consists of a label (displayed to users) and a corresponding value (stored in the process data). This component supports static data, enumerations, and dynamic process data sources with advanced features like search filtering and conditional option enabling.
Single Select demonstration
Example: Consider a dropdown with “Sports” (value: “S”) and “Music” (value: “M”). When a user selects “Sports”, the value “S” is stored in the process instance under the Select element’s data key.

Configuration overview

Configure your single select component using these main sections:

Basic Settings

Process data binding, labels, and properties

Data Source

Static options, enumerations, or dynamic data

Behavior

Hide/disable conditions and event handlers

Styling

Visual appearance and platform overrides

Basic configuration

Process data key

The process data key establishes the binding between the select element and process data, enabling its later use in:

Core Properties

Label: The visible text displayed above the select element
  • Rendered as plain text, without Markdown formatting
Placeholder: Text shown when no option is selected
  • Provides guidance on what to select
  • Should be clear and actionable
  • Example: “Choose your preferred option…”
Empty message: Custom text for no results scenarios
  • Displayed when search yields no matches
  • Helpful for dynamic data sources
  • Example: “No matching options found”
Search for options: Enable filtering functionality
  • Improves usability for long option lists
  • Real-time filtering as users type
  • Case-insensitive search capabilities
  • Particularly useful for large datasets
Has clear: Add option to clear selection
  • Provides users with reset functionality
  • Useful for optional fields
  • Improves user control and flexibility
Has helpertext: Turn on to add additional context or instructions in the Helpertext field
  • Can be displayed as regular text
  • Can be hidden within an expandable info point

Data source configuration

Default value setup

Configure the initial selected option: Default value: Specify which option should be pre-selected
  • Must match a value from your data source
  • Improves user experience by reducing required interactions
  • Consider user context and common selections
Default value configuration

Source types

Choose the appropriate data source for your select options:
Purpose: Fixed list of options defined at design timeConfiguration:
  • Options → Add new (+): Define label/value pairs manually
  • Label: User-friendly display text
  • Value: Internal identifier stored in process data
Best For:
  • Fixed categories (Yes/No, Active/Inactive)
  • Configuration options
  • Simple selection lists

Enhanced option control

Individual option enabling/disabling is available for Process data source types only.
When using Process data, you can control which options are selectable using the enabled property: How It Works:
  • enabled: true or missing: Option is selectable (default)
  • enabled: false: Option appears but is disabled
Example:
Common Use Cases: Conditional availability based on permissions, progressive disclosure, status indication (e.g., “Out of Stock”), or guided selection flows.
Disabled options support theming for both disabled unselected and disabled selected states. An option can be both selected and disabled simultaneously.

Validation

Apply validators to ensure data quality and completeness: Available Validators:
  • Required: Ensures a selection is made
  • Custom: Complex business logic validation
  • Custom expression: Validation based on an expression you write
For comprehensive validation options, refer to our Validators Guide.

Behavior configuration

Hide/disable expressions

Control the select element’s visibility and interaction using JavaScript expressions: In the Expressions section of the Settings tab, select + and add a Hide or Disable condition. The element is hidden or disabled while the expression evaluates to true. For how conditions are evaluated, see Hide and disabled conditions.

Event handlers

Configure interactive behaviors for your select element:
For detailed event handler configuration, see the Event Handlers guide.

Platform customization

Settings overrides

Customize your select element differently across platforms:
Override Options:
  • Label: Desktop-optimized terminology
  • Helper: Extended descriptions with more context
  • Placeholder: Detailed guidance text
Web-Specific Features:
  • Keyboard navigation: arrow keys move through the options, Enter selects, Escape closes the list
  • Larger option lists with scrolling
The ⋮ menu next to Web overrides, listing Copy from Android, Copy from iOS, Copy to Android and Copy to iOS
Use Copy from <platform> or Copy to <platform> to reuse override settings across platforms.

Visual styling

Layout options

Left Icon: Visual cue for the select purpose
  • Category icons (📂, 🏢, 👤)
  • Functional indicators (🔍, ⚙️, 📊)
  • Status symbols (✓, ⚠️, 🔒)
Icon Configuration:
  • Icon Key: Select from Media Library
  • Platform-specific optimization
  • Consistent with design system
Icon configuration example

Theme customization

Override default styling for complete visual control:
Theme override interface
Layout & Structure:
  • Border radius for rounded corners
  • Border width for outline definition
  • Font for typography consistency
Common properties styling
Default State:
  • Text color customization
  • Font family and size options
Disabled State:
  • Dimmed appearance
  • Consistent with disabled styling
Label styling options
Standard Helper:
  • Text color and font options
Tooltip Helper:
  • Background color customization
  • Icon color options
  • Typography controls
Helper text styling
When no option is selected:
  • Border and background colors
  • Icon color customization
  • Placeholder text styling
Empty state styling
Time-Saving Tip: Use Copy from <platform> or Copy to <platform> in the style overrides to reuse styling across platforms without manual reconfiguration.
The ⋮ menu next to Theme overrides, listing Copy from Android, Copy from iOS, Copy to Android and Copy to iOS

Advanced example: Dynamic dropdowns

Create sophisticated dropdown interactions with dependent selections using process data and business rules.

Scenario overview

Build a customer contract selection system where available contracts depend on the selected customer:
Dynamic dropdowns demonstration

Process structure

Required Elements:
  1. Task Node: Populates dropdown data using business rules
  2. User Task Node: Contains the select elements and form interface

Implementation steps

  1. Open FlowX.AI Designer → Processes → Definitions
  2. Click New Process to open Process Designer
  3. Add the required nodes:
    • Task node (for data preparation)
    • User task node (for user interface)
Process structure
Task Node Configuration:
  • Action Type: Business Rule
  • Execution: Automatic, Mandatory
  • Language: MVEL (or your preferred scripting language)
Sample MVEL Script:
Business rule configuration
User Task Node Configuration:
  • Action Type: Save Data
  • Execution: Manual, Mandatory
  • Data to Send: application
UI Structure:
  1. Card Element (root component):
    • Custom UI payload: {"application": ${application}}
    • Title: “Customer Contract”
  2. Form Element (container for selects)
  3. First Select (Customer Name):
    • Process data key: application.client.selectedClient
    • Label: Customer Name
    • Source type: Process data
    • Name: application.client.identity
  4. Second Select (Contract ID):
    • Process data key: application.client.selectedContract
    • Label: Contract ID
    • Source type: Process data
    • Name: application.contracts
    • Parent: SELECT (first dropdown)
Select configuration
Test Process:
  1. Click Start Process in the designer
  2. Select a customer from the first dropdown
  3. Verify that the second dropdown populates with relevant contracts
  4. Submit the form to validate data storage
Expected Behavior:
  • Customer selection triggers contract list update
  • Only contracts associated with selected customer appear
  • Form submission stores both selected values
Dynamic example in action

Enhanced dynamic example with disabled options

Extend the previous example to include conditional option disabling:

Best practices

Accessibility

  • Provide clear, descriptive labels and helper text
  • Ensure sufficient color contrast for all states
  • Set an accessibility label when the select has no visible label
See the Accessibility guide for keyboard navigation, ARIA auto-binding, and screen reader details.

User Experience

  • Keep option lists manageable (under 10 items when possible)
  • Use search functionality for longer lists
  • Provide clear visual feedback for disabled options
  • Consider default selections for common use cases
  • Group related options logically
  • Show loading states for dynamic data

Data Management

  • Use meaningful keys for integration purposes
  • Plan for data validation and error handling
  • Consider performance impact of large option sets
  • Document business rules for option availability
  • Test with realistic data volumes
  • Implement proper error handling for external data sources

Performance

  • Optimize search algorithms for responsiveness
  • Consider pagination for very large lists
  • Monitor performance with real-world data
  • Test on various devices and network conditions

Common use cases

Last modified on November 13, 2026