> 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/visualizadores.md).

# Viewers

The viewers first perform a validation of the file's format and content, ensuring that both are consistent and comply with the Spanish Banking Association standard, or the corresponding body in each case, for each type of file. If these validations do not finish successfully, the file will not be displayed and the program will inform the signing user of the cause of the error with a message such as:

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

If the file is valid, the dialog will display it. For easier viewing, all data that is content of the file has been written in black, and the description or title of it in blue.

From the same dialog, you can print the complete file (with the same dialog format) or only the summary (the most relevant data from the content).

This is what the dialog looks like if the file follows the SEPA 34-14 standard:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/d7hsUftV7VDoZr33F43V/image2.png)


---

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