# Fields ### What are fields? Fields represent data that will be sent (or not) to our back-end. Adding new field you can choose if a field should be sent to `quote` or `policy` or both. And it is required to create a name for that field.

After creation these fields can be placed into currently opened page via drag & drop mechanism.

#### Quote Quote is data that is relevant for creating price. This data is used in pricing calculator. #### Policy Policy is data that is only needed for other information related to policy (for example displayed in dashboard, documents, emails etc.) #### Payment Payment is data that is related to payment data (e.g. iban number and others) ### Data types We can handle multiple different data types for different use cases. Each field can have one data type that determines what type of component is displayed on page.

Type	Description	Example
Text (string)	Plain text value can be anything
Number (integer)	Only digits (e.g. count, size, monetary value etc.)
True / False (boolean)	Yes or No question, usually used for optin checkboxes
Phone number	Validates validity of phone number as well as provides component to enter it
Date	Displays datepicker input (usually used for entering date of birth, policy start date etc.)
Date + Time	Same as Date except user can also select exact time of day

Each field can have different validation rules for what values can be entered.

We can also set field to have `Default value` that is starting value for field. User would be able to change that value in page where this field is placed. Field can be required or optional. If `Field is required` is checked user won't be able to continue to next page before entering value to this field. `Allowed values` is comma separated list of values that user can enter (e.g. "yearly,quarterly,monthly"). User wouldn't be able to continue the flow if entered or selected value doesn't match one of these allowed ones. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.kasko.io/webapp-builder-manual/basic-concepts/fields.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.