> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-developer/object-editors/theme-editor/validations-properties.md). # Validations Properties Reference documentation for Servoy Theme Validations Properties ## Overview

The **Validations Properties** section defines settings related to form validation within the application. Proper validation ensures that user inputs meet specific criteria before submission, enhancing data integrity and user experience. ## Properties Here's an in-depth look at each property: ### Form required label suffix Sets the suffix text or symbol that indicates a form field is required. This is typically an asterisk (\*) or similar symbol placed next to the field label to visually indicate to users that the field must be filled out.\ Value: Text or symbol (e.g., `*`). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.servoy.com/reference/servoy-developer/object-editors/theme-editor/validations-properties.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.