> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/time-input.md).
# Time Input
## Description
This part allows your application users to enter time values in an application.
## Use
With this party you can provide your users a field where they can enter a time value in the format HH:MM. The system converts the value to a number that the amount of minutes between 00:00 and the provided time. This makes it possible for the application to use time entries in a calculation, for example. The time input should always use the 24-hour format: HH:MM.
## Editor Fields
### Basic Tab Options
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| ----------- | ----------------------------------------------------------------------------------- | ------------ | ------------------ |
| Data object | This is the name of the data object that stores the time value the end-user enters. | Data Object | Mandatory |
| Caption | This is the text that appears in front of the time input field. | Text | Optional |
### Validate Tab Options
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Type | This allows the user to have the system trigger the display of an error message based on user-defined parameters:
- mandatory: This means the end-user must provide a value or the system will display an error message.
- numeric, percentage, currency: These mean that the value the end-user enters must be a number and may contain a comma or dot as decimal character. This validation rule can be used when the data-object-type is set to text. This combination allows the user to enter decimal number and allows users to enter a different decimal point (e.g. comma).
- time: This means the input must be a time string--hh:mm (12:14, for example) or hhmm (1214) are both allowed
- custom: This allows the user to set a custom validation parameter.
- email: This means the value the end-user enters must contain an '@' symbol.
- date: This means the input must be a date string; mm/dd/yy, for example.
| Options | Optional |
| Condition | This is only required when type=custom--when the user has set a custom validation parameter. It tells the system under which condition to display a validation message. | | Conditional |
| Message | This is the message the system displays to the end-user if a validation rule is not met. The system displays the message associated with the first violated rule. | Text | Optional |
### Advanced Tab Options
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------ |
| Captions | This allows you to specify different captions based on rules. The system only displays one caption, the last caption in the table the rule determines to be true. If there is no rule the system determines to be true, the system uses the 'standard' caption. For an example, see [Multi-Caption Example Project](/release-9/example-gallery/example-projects-for-parts/multi-caption-example-project.md). | Text | Optional |
| Events | These are the JavaScript events that should be attached to the date picker. | Text | Optional |
| Disabled | This parameter indicates whether the input field is disabled or not. If the field is disabled, the end-user cannot change the displayed value. | Yes \| No | Optional |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/time-input.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.