Address
Address records a freely editable address string. It participates in the state, validation, and submission boundary of its Form.
1. When to use it
Typical uses:
- Mailing addresses
- Office locations
- Addresses that do not need separate region fields
2. Add and configure
- Add Address to the Fields slot of a Form Section.
- Set a stable, unique Field Key / Name that matches the backend DTO property.
- Configure the component properties below, then add Required, Help Text, Full row, or conditions as needed.
- Check the initial value and layout in Design Preview, then use Form Validate / Submit to test the full data path.
3. Main properties
| Property | Purpose |
|---|---|
| Required | Enables or disables this behavior. |
| Help Text | Controls how the field is displayed in Design Preview and Runtime. |
| Full row | Controls how the field is displayed in Design Preview and Runtime. |
| Visible When | Defines the data shape used for binding, submission, or responses. |
| Disabled When | Defines the data shape used for binding, submission, or responses. |
| Clear When Hidden | Enables or disables this behavior. |
Common properties such as Field Key, Required, Help Text, Full row, and Visible When come from the Form field contract. The table highlights the settings most relevant to Address.
4. Form value and backend contract
Submitted value: A string.
"123 Market Street, Toronto"
The example shows the data shape only. The API must still validate type, range, and authorization against its business DTO.
5. Validation, conditions, and interactions
Every field can use Form properties such as Required, Visible When, Disabled When, Required When, Dependencies, and Clear When Hidden. Conditions improve interaction but never replace backend validation or authorization.
Component capabilities: The value participates in Form state; only events exposed in the property panel are available to Interaction.
6. Recommendations
Recommendations: Set explicit length limits for business fields. Never place passwords in defaults, logs, or Page Context.
Return to the Form overview for layout, validation, submission, drafts, and backend protocol guidance.