> 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/operaciones-principales-sobre-las-aplicaciones/habilitar-envio-aceptar-la-aplicacion.md). # Enable sending/Accept the application This can be done, with an application selected in the tree (left panel) or in the list (right panel), in one of the following three ways: 1. From the menu “*Operations –> Application -> Enable (F)/Accept (V)”* 2. The button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/8A4vAkdi5pXAKZ9XjTXG/image1.png) on the taskbar. 3. The context menu (right mouse button). Triggers the process of **enable the application** if the **application is for signing** or to **accept it** if the **application** is **for verifying signatures**. This operation may only be performed by users who, in the application-user relationship profile, have the corresponding permission and on the applications that have configured “*Yes*” in the “Enablement” section of the profile. * **Enable an application (in applications for signing)** 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, which are the resulting signature files, and whether any signature is missing). The file is left in the signatures directory with the same name as the application and the extension *.p7b.* While it remains in that directory, the signing process is stopped. When “Automatic enablement” has been selected in the application profiles, all signature files associated with each of the files in the data directory exist and are all correct, the system will automatically ask: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Fp6jQm0Gi5qrkb0DyDFU/image2.png) On the other hand, if enablement is triggered manually by the user: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Y6Pnb84FLHgAKddQpi4J/image3.png) Then, in both cases, the user will be prompted for the certificate PIN if more than 5 minutes of inactivity have elapsed. If the application is also going to be encrypted, the PIN of the encryption certificate will also be requested. When files are missing to be signed, and the user has permission to enable even if signatures are missing, the following message informs them: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/HMLMpHkL2ZQGJ3YXleEO/image4.png) The next step will be to decide whether to move the signed files, and their signatures, to another folder: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/82JGu8FhDb6nsTFpUKXN/image5.png) If yes, these files will disappear from their source folders and will be moved to the “No Signature” folder, which is created, if it does not exist, under the directory where the data files are stored. This process prevents unsigned files from being sent when there is a process that does so automatically when the application enablement file exists. In addition, if compression was configured in the application profile, an informational dialog similar to the following will be displayed: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/FnJndYRehJp55xqm35It/image6.png) Finally, a signed enablement file is automatically generated by this user and the application will reach one of the following states: “Sending enabled”, "Sending enabled without all signatures (forced)" or "Sending enabled. Encrypted and/or compressed". If an output directory was configured in the application, the data files and/or signature files will be moved to it at this point, depending on what was indicated in the configuration. From that moment on, application validation is done on that directory and the signing flow remains stopped while files exist in it. * **Accept an application (in applications for verifying signatures)** At the end where the signatures are verified and the enablement has been received, acceptance is the generation of a new signature file, in Editran/FF's own format, which represents the confirmation of the received application; optionally, it may include a note. The file is left in the signatures directory with the same name as the application and extension .Rec.Acept.p7b. If applicable, before acceptance, it will have been decrypted and/or decompressed (see **5.3.5**). By performing this operation, the application will reach the state “Reception accepted”. --- # 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/operaciones-principales-sobre-las-aplicaciones/habilitar-envio-aceptar-la-aplicacion.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.