> For the complete documentation index, see [llms.txt](https://docs.kasko.io/webapp-builder-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasko.io/webapp-builder-manual/basic-concepts/fields.md).

# 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.

<figure><img src="/files/zHSbgDmkVMQ7U9mRp36d" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/vWqkkCI64BRB0DNlTNqu" alt=""><figcaption></figcaption></figure>

#### 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.

<table><thead><tr><th width="230.33333333333331">Type</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>Text (string)</td><td>Plain text value can be anything</td><td><img src="/files/d78AVE8MMGxnVrEKXujw" alt="" data-size="original"></td></tr><tr><td>Number (integer)</td><td>Only digits (e.g. count, size, monetary value etc.)</td><td><img src="/files/YzrtGjKEgsMaT0RSl3Nk" alt=""></td></tr><tr><td>True / False (boolean)</td><td>Yes or No question, usually used for optin checkboxes</td><td><img src="/files/6zmv9zF9SmGrVIjakcmn" alt=""></td></tr><tr><td>Phone number</td><td>Validates validity of phone number as well as provides component to enter it</td><td><img src="/files/4tETolnJOqexEZYwoUh1" alt=""></td></tr><tr><td>Date</td><td>Displays datepicker input (usually used for entering date of birth, policy start date etc.)</td><td><img src="/files/plo6QnOeFebBlccXGcTD" alt=""></td></tr><tr><td>Date + Time</td><td>Same as Date except user can also select exact time of day</td><td><img src="/files/jIAzOCNsHtjc7IuheAnU" alt=""></td></tr></tbody></table>

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

<figure><img src="/files/t8bxWCF5QpwfFhcw0ez8" alt=""><figcaption></figcaption></figure>

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.