> 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/usuario-de-onesait-ecosystems-editran-ff/barras-de-menu-y-herramientas/consultas.md).

# Queries

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

## 5.1.3.1. File hash

It displays a dialog that makes it easy to query the hash of each application's data files. In the dialog it is possible to configure both the hash algorithm with which you want to calculate it and the format in which you want to display it. Through the “Copy all” button, the hash of all the files of the application selected in the combo box is copied to the clipboard, using the algorithm and format that are selected. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/xrWJ9e4SXM5OcTr4vnuw/image2.png) on the taskbar offers the same functionality.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/se4zfSFXVsZo8albugrd/image3.png)

## 5.1.3.2. Application summary

It displays a dialog with all the information the user may need for each application. It is a faster alternative to querying branch by branch, application by application, in the tree.

You can consult:

* The static characteristics of the application, whether it is encrypted, compressed, whether it requires an enablement file, the format, etc. (the parameters that were specified in *AdminFF).*
* The dynamic characteristics, for example, the current state of the application (which will depend on the signatures existing at that moment), the particular state of each file with respect to each user of the application, and information on whether the groups are met or not (number of mandatory and permitted signatures) or the joint conditions, as appropriate.
* The enablement and acceptance/rejection files, when they exist.

From this dialog, you can also go to sign files when one is still awaiting signature.

By changing the combo box selection, you can consult the status of any of the applications in which the logged-in user is a signer.

The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/E36oXDTKAxgHz85cx54p/image4.png) offers the same functionality.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/N9AfVe7lQicB9Ao9W4iN/image5.png)

## 5.1.3.3. View log

It displays a dialog with all the log records logged by the system. The query can be filtered by application name and by date, the details of each record can be viewed, and the integrity of the log can be checked to determine whether it may have been tampered with. The log file has a proprietary Editran/FF format and is secured: any tampering with the file would be detected by Editran/FF. The integrity of the file can be checked through the “*Check*” button in the “*File integrity” section.*

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/hg5KUNAzeK4fzn1d36Ww/image6.png)

The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/JLnoW5Bb518gxxciPW2v/image7.png) on the taskbar offers the same functionality.

## 5.1.3.4. Check integrity

Checks the integrity of the log file as to whether it has been externally tampered with outside Editran/FF. It offers the same functionality as the “*Check*” button in the Log dialog.

## 5.1.3.5. Refresh the information

Refreshes the content of the tree and the list. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/SwiXogGq0v7S6t0M7XLJ/image8.png) on the toolbar offers the same functionality.


---

# 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/usuario-de-onesait-ecosystems-editran-ff/barras-de-menu-y-herramientas/consultas.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.