> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/modulos-visualizadores-y-validadores/validadores.md).

# Validators

Validation consists of comparing the application's “Validation Criterion” parameter, **which must be an integer**, with the value of the “Sum of Amounts” field (from the totals record) in the file. This parameter, and the validation described, will apply to all users associated with the application. If the figure is less than the total of the file, a message of the following type will appear:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/KuYE3SeTVGhNYj0TmllN/image1.png)

This means that the user will only be able to sign files whose “Sum of Amounts” value is less than that amount.

If this validation is positive, the system will still check the same thing with the “Validation Parameter” field of the Application – User relationship (if completed), this restriction applying only to the specific user in the relationship.

Only if the user passes the validations contained in the profiles will they be able to sign the file, which, in any case, can always be viewed.


---

# 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.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/modulos-visualizadores-y-validadores/validadores.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.