Data Settings
Data settings control how component data is stored, processed, and managed. These settings determine the behavior of the data beyond its visual presentation in the form.
Common Data Settings
- Data Source: Where selection options come from (static, URL, resource)
- Storage Type: How the data is stored (e.g., as string, number, boolean)
- Persistent: Whether the data persists between form loads
- Protected: Prevents the field from being changed after submission
Data Source
For components that present options to users (like Select, Radio, and Checkbox), the Data Source setting determines where these options come from:
Static Values
Static values are defined directly in the component settings. You can specify:
- Label: The text displayed to users
- Value: The data stored when the option is selected
URL
Options can be loaded dynamically from an external URL. You can configure:
- URL: The endpoint that provides the data
- Value Property: The property in the response that contains the value
- Label Property: The property in the response that contains the label
- Headers: Custom HTTP headers for the request
Resource
Options can be loaded from a resource defined in the system. You can select:
- Resource: The data resource to use
- Value Property: The property to use as the value
- Label Property: The property to display to users
Storage Type
The Storage Type setting determines how the data is stored and processed:
- String: Text data (default for most fields)
- Number: Numeric data (integers or decimals)
- Boolean: True/false values
- Object: Complex data structures
- Array: Lists of values
Choosing the appropriate storage type ensures that data is processed correctly in workflows and integrations.
Persistent
The Persistent setting determines whether the field's value is saved between form sessions. When enabled:
- The value is stored in the browser's local storage
- The field is pre-filled with the saved value when the form is loaded again
- The value persists until explicitly cleared
This is useful for forms that users may need to complete over multiple sessions.
Protected
The Protected setting prevents the field from being changed after the form is submitted. Protected fields:
- Cannot be edited in form revisions
- Maintain their original value throughout the workflow
- Are displayed as read-only in form views
This is useful for maintaining the integrity of critical data points throughout a workflow.