# Field Definition Similarly to the `Validation Rules` in `Pricing Logic`, which defines the validation rules for quote data, Field Definition defines all the validation rules for the policy data. If you use the Webapp Builder to configure the customer journey, you should be able to get the Field Definition from the App export and you can simply copy and paste it for setup.

Field Definition Screen Example

FieldDescription
NameThis should correspond to the policy field names in the Webapp
PathThis is usually data unless you have other data structures in your webapp.
Validation

This usually include a few things:

  1. data format - for example, string , integer , iso_date
  2. required/not required - if the data is always required, you should put required , otherwise, left empty
  3. other validation rules - this can be (1) limiting the input to a list of allowed value; (2) checking the input value to be within certain range; any other validations
--- # 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/product-builder-manual/fundamentals/create-your-first-product/field-definition.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.