> 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/menu-operaciones.md). # "Operations" Menu ## 5.1.2.1. File This menu offers all the tasks that can be performed with files. The submenus described below will be enabled when the element selected in the list of the right panel is a file: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/wFfgV8K3xPCuMQSOBell/image1.png) * **Sign**: triggers the signing process, see **5.2.1**. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/bTkJ19Pj8kovfLWQRwg2/image2.png) offers the same functionality. * **Delete the signature**: from here you can delete the file's signature as long as the file does not have signatures from other users. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/jW5uOeqjbCO7EpOEwAGc/image3.png) offers the same functionality. For more information, see **5.2.2.** * **Comments**: opens a dialog that allows notes to be made about the file so that the rest of the signers can see it, see **5.2.3.** * **Reject/move/delete**: opens a dialog that allows the information needed to remove the file from the signing workflow to be completed, either by moving it to another directory or by deleting it completely. This operation can only be performed by users whose profiles have the corresponding permission. For more information, see **5.2.4.** ## 5.1.2.2. Application This menu offers all the tasks that can be performed with applications. The submenus described below will be enabled when the element selected in the tree or in the list of the right panel is an application: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/1BrpYxhfrSMHbcOU0e18/image4.png) * **Enable (F)/Accept (R)**: triggers the process of enabling the application if the application is for signing, or accepting it if the application is for verifying signatures. This operation can only be performed by users who have the corresponding permission in their profiles and for applications that have “*Yes*” in the “Enablement” section of the profile. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/rMNcuSgfNb6O0uEk0vsf/image5.png) on the taskbar offers the same functionality. * Enablement is the generation of a file, in Editran/FF's own format, that summarizes the current status of each file in the application (with respect to who has signed it, what the resulting signature files are, and whether any signature is missing). The file is placed in the signatures directory with the same name as the application and the .p7b extension. While it remains in that directory, the signing process is paused. * On the side where the signatures are verified and the enablement has been received, acceptance is the generation of a file, in Editran/FF's own format, which constitutes confirmation of the application received; optionally, it can include a remark. The file is placed in the signatures directory with the same name as the application and extension .Rec.Acept.p7b. * **Disable (F)/ Reject (V)**: if the application is for signing, the enablement file will be deleted, and if it is for verifying, a rejection file for the application will be created. The rejection file has Editran/FF's own format; it will remain in the signatures directory with the same name as the application and extension .Rec. Recha.p7b. It records the reason for rejecting the received application. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Z2VhsuabfWxvUwEPVnvR/image6.png) on the taskbar offers the same functionality. * **Validate the Send-Receive**: if the application is for signing and the acceptance file or rejection file has been received from the receiving end, from here a new file can be generated, in Editran/FF's own format, which completes the sending and receiving of the signatures. The file is placed in the signatures directory with the same name as the application followed by the extension .ValEmiRec.p7b. While this file remains in the directory, the application's signing process will be paused. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/SHj66kILa149e1ygGg7B/image7.png) on the taskbar offers the same functionality. * **Initialize**: returns the application to its initial state, deleting all signatures. Only users who have permission to enable/accept the application can perform this operation. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/14oxpv9wjXmUPtfVeRsI/image8.png) on the taskbar offers the same functionality. * **Decrypt/decompress the files**: if the selected application is for verifying signatures and compressed and/or encrypted files have been received, they can be decompressed and decrypted here. ## 5.1.2.3. Display If the element selected in the window is a file, it displays its content in a user-friendly format; if it is an application and it is enabled, accepted, rejected, or send-receive validated, it displays the content of these files in a user-friendly format. ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/BTMlJhMLfCvA38bnYgTr/image9.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/usuario-de-onesait-ecosystems-editran-ff/barras-de-menu-y-herramientas/menu-operaciones.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.