> For the complete documentation index, see [llms.txt](https://rpa-connect.gitbook.io/rpa-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rpa-connect.gitbook.io/rpa-connect/en-us/form-design/property-assignment/validations.md). # Validations In the ***Validations*** section, you can set various conditions that the entered data must meet to be considered valid. By configuring these parameters, you can anticipate different response options and minimize the risk of potential errors, such as a code exceeding the allowed character limit. In general, the basic validations you can set are:

Property	Characteristics
Min	Refers to the minimum acceptable value for that field and is entered as a number. The type of value varies depending on the field; for example, in text fields, it refers to the minimum number of characters the input can contain, while in numeric fields, it refers to the lowest accepted number.
Max	Works the same way as Min, but instead defines the maximum allowed value.
Whitelist	Allows you to create a list of the only values that will be accepted in that field. To input them, type each value and press enter, which will save and display them as tags in the configuration. Unlike fields with options, the user will not see this list but will receive an error message clarifying the accepted values when entering an unapproved one.
Blacklist	Configured in the same way as Whitelist, but unlike this property, it allows you to define a list of values that will not be accepted in that field. The user can enter any data except those listed here.

Next, we will look at another type of more complex validations that allow for the analysis of specific data and, if certain conditions are met, prevent the form from being submitted and display a custom error message: ***Validation Expressions***. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rpa-connect.gitbook.io/rpa-connect/en-us/form-design/property-assignment/validations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.