> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/learn/features/dynamic-validations.md).

# Dynamic Validations

Saral App supports dynamic validation feature. As this application will be used by different educational boards , this feature will avoid maintaining different frontend source code to customise validations. This feature is available from `v1.5.1` release.

The validations can be configured in the ROI Layouts JSON in backend using regular expressions and failure messages.&#x20;

Refer [Layout specification](/learn/specifications/layout-specification.md) and [Layout configuration](/use/layout-configuration.md)for details about ROI Layout configuration.

Dynamic validation will come from backend with regular expression, and dynamic validation is used at cell level if validation is not available at cell level then in that case result validation will be used which is used as global result validation and it will also come from backend.

Result validation(This is global result validation irrespective of cell level)&#x20;

`"resultValidation": { "validate": { "regExp": "[0-1]", "errorMsg": "Omr result should be 1 or 0" } }`

Cell level validation&#x20;

`"validate": { "regExp": "[0-1]", "errorMsg": "Omr result should be 1 or 0" }`

`"validate": { "regExp": "[0-5]", "errorMsg": "Omr result should be 0 to 5" }`


---

# 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://saral.sunbird.org/learn/features/dynamic-validations.md?ask=<question>&goal=<user_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.
