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

<figure><img src="https://3958097797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHNwbN62wHJkXHE6QwYrR%2Fuploads%2FeDzW5PY3KcJWDH0UvZwz%2FScreenshot%202025-12-02%20at%2015.38.28.png?alt=media&#x26;token=e5a4b116-e2f5-448f-9c0a-66dd8b160784" alt=""><figcaption><p>Field Definition Screen Example</p></figcaption></figure>

<table><thead><tr><th width="194">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>This should correspond to the policy field names in the Webapp</td></tr><tr><td><strong>Path</strong></td><td>This is usually <code>data</code> unless you have other data structures in your webapp.</td></tr><tr><td><strong>Validation</strong></td><td><p>This usually include a few things:</p><ol><li>data format - for example, <code>string</code> , <code>integer</code> , <code>iso_date</code></li><li>required/not required - if the data is always required, you should put <code>required</code> , otherwise, left empty</li><li>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</li></ol></td></tr></tbody></table>