Time Picker
Time Picker selects a time-of-day value. It participates in the state, validation, and submission boundary of its Form.
1. When to use it
Typical uses:
- Working hours
- Appointment times
- Hour/minute/second values without a date
2. Add and configure
- Add Time Picker 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 |
|---|---|
| Control Type | Sets the initial value, content, or format used by the field. |
| Show Time | Enables or disables this behavior. |
| Time Format | Sets the initial value, content, or format used by the field. |
| Hint | Controls how the field is displayed in Design Preview and Runtime. |
| Required | 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 Time Picker.
4. Form value and backend contract
Submitted value: A string.
"14:30:00"
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: Supports onChange so a selection change can continue a Page Interaction.
6. Recommendations
Recommendations: Agree on one format and time-zone policy with the backend; do not mix dates, local times, and instants.
Return to the Form overview for layout, validation, submission, drafts, and backend protocol guidance.