> 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/estados-de-las-aplicaciones.md). # Application statuses An a*pplication* of E*ditran/FF* reaches different states as the associated files are signed and the corresponding operations are carried out. The application state clearly indicates the point at which it is, as well as the possible actions that can be performed on it. Below are all the states that an Editran/FF application can take, along with a brief description: | **Status** | **Description** | | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **0 - All signatures missing** | No file has been signed. | | **1 – Signatures missing** | Not all files have been signed by all required users. | | **2 - There is some incorrect signature** | Some of the signatures were made with an invalid certificate or the signed file and the original do not match. | | **3 – Signed. Sending not enabled** | All files have been signed by all users but sending has not yet been enabled. | | **4 – Sending enabled** | All files in the application have been signed by all users, all signatures are correct, and sending has been enabled. The information collected in the enablement file is satisfied. | | **5 – Reception accepted** | The signatures received in the application are correct and acceptance of the reception has been signed. | | **6 – Reception rejected** | One of the received signatures is not correct and the rejection of the application has been signed. | | **7 – Not received** | In applications to verify, the enablement file of a reception application has not been received or, if the application does not require enablement, no signature file. | | **8 – Issuance-Reception accepted** | Acceptance of the application has been received from the remote end and validation of the entire operation has been signed. | | **9 – Sending enabled without all signatures (forcibly)** | The application has been enabled for sending without all the necessary signatures. | | **10 – Enabled. Encrypted and/or compressed** | The application has been enabled and the data has been encrypted and/or compressed. | | **11 – No Data Files Exist** | There are no files associated with the application (the folder of files to be signed is empty). | | **12 – Sending enabled with invalid certificate** | The application has been enabled with an invalid certificate (not found, revoked, expired...) | | **13 – Application signed. No enablement file required.** | When the application is configured with attached signature, all files are fully signed and no enablement file is required. | | **14 – Sending enabled. Data files missing** | The enablement file contains information about data files which, however, are no longer in the directory. | | **15 – Invalid enablement file** | There is an application enablement file, but it has been manually modified after being generated and Editran/FF cannot interpret it. | | **16 - Invalid issuance-reception acceptance file** | There is an issuance-reception acceptance file for the application, but it has been manually modified after being generated and Editran/FF cannot interpret it. | | **17 - Invalid reception acceptance file** | There is a reception acceptance file for the application, but it has been manually modified after being generated and Editran/FF cannot interpret it.. | | **18 - Invalid reception rejection file** | There is a reception rejection file for the application, but it has been manually modified after being generated and Editran/FF cannot interpret it. | | **Status** | **Description** | | **19 - Issuance-Reception accepted with invalid certificate** | The certificate with which the issuance-reception acceptance was signed is not valid (not found, revoked, expired...). | | **20 - Reception accepted with invalid certificate** | The certificate with which the reception acceptance was signed is not valid (not found, revoked, expired...). | | **21 - Reception rejected with invalid certificate** | The certificate with which the reception rejection was signed is not valid (not found, revoked, expired...). | | **22 - Sending enabled. Some signature is incorrect** | The application is enabled, but by validating some of the signatures mentioned in it, it is found that they were made with an invalid certificate or that the signed file and the original do not match. | | **23 - Sending enabled. Some signature is missing** | Some of the signatures in the directory have been deleted after the enablement was performed. | | **24 - Sending enabled. Some data/signature file is new** | In the data and/or signature directories there is some file that has been added after the enablement was performed. | From the User dialog you can view the states of all applications associated with a user by expanding the branch *Applications*. This could be a costly task if there were many applications because the number of calculations to be performed is high. If you only want to see the states of the applications to sign or to verify, it is recommended to open the tree using the +/- and then click on the corresponding branch. If what you want is to consult the state of a specific application, the most convenient thing is to use the “*Summary of the* *Application*” (see **5.1.3.2).** The state of the application can be requested from an external application using the command “EstadoApl.exe” which returns the number associated with each state (see section **7.3).** --- # 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/estados-de-las-aplicaciones.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.