> 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/ibm-editran-v5.3-cics-en/electronic-signature/graphical-interface/applications-presentation-sessions/application-signing-rules.md). # Application signing rules This screen is accessed with option 7.2.3.2 of the Editran FF administrator menu. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/FF ADMINISTRATOR | | 19:00:36 SIGNATURE RULES | ----------------------------------------------------------------------------- | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFICATION | | | | | | OPTION ...........: C | | EMI-REC ..........: E | | APPLICATION .......: *EDTRFF | | STANDARD ............: | | COMPANY ..........: | | | | | | | | QUERY PERFORMED. | ------------------------------------------------------------------------------- ``` * We must enter: * OPTION * EMI-REC: E for issuance R for reception * APPLICATION: local code, remote code and the application * STANDARD * COMPANY * In all options, EMI-REC (E/R) is mandatory * In all add, delete, modification or query options, search by session is allowed using \* to perform generic searches. * If neither standard nor company is entered, it is understood to be a generic rule. * For issuance, we cannot enter standard or company * If a standard is entered, the rule will apply to files belonging to that standard. Standards 19 and 34 are accepted. * The company is made up of NIF (9 positions) and suffix (3 positions). These NIF and suffix values are obtained from the File Presenter Identification and, failing that, from the Identification of the first debtor (standard 34) or the Identification of the first creditor (standard 19). To define a company that can be applied to a NIF and all suffixes, we can enter the NIF and suffix "???". If we enter company, standard is mandatory. * For a reception application, multiple rules can be defined, without standard, with standard and without company, and with standard and company. * Rule validations are performed from the most restrictive to the least restrictive. * If the file has a standard, only the rules for that standard are validated. * First, the rule with matching NIF and suffixes from the file will be applied. * If there is none, the one that matches the NIF and has no suffix defined ("???") will be applied. * If none matches, the rule without NIF or suffix will be applied. * If the file has no standard, the generic rule is applied. * In any of the options (query, modification or delete), if none of them (session, standard and company) is entered, the generic rule will be queried. To query, modify or delete specifically, enter application and optionally standard and company. ## Specific operation ### Rule screen If the option, EMI-REC and the application are filled in on the initial screen, and optionally standard and company, the rule management screen will appear. ``` ----------------------------------------------------------------------------- | 24/06/2026 SIGNATURE MANAGEMENT | | 19:01:17 ADD RULES | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM48 STANDARD: 34 COMPANY: 475687960001 EMI-REC: R | | | | | | TOTAL NUMBER OF SIGNATURES....: 000 | | NUMBER OF MANDATORY GROUPS...: 000 | | | | | | U - USERS | | G - GROUPS | | | | | | OPTION: U | | NAME: | | | | | | | | | | | | EXIT, ADD | ------------------------------------------------------------------------------- ``` The selection fields appear in the header. * **APPLICATION** (header): Local code, remote code and application. * **STANDARD** (header): Banking standard. * **COMPANY** (header): Company made up of NIF plus suffix. * **EMI-REC** (header): (Issuance/Reception) * **TOTAL NUMBER OF SIGNATURES**: Number of signatures expected in the rule. This parameter only applies to reception. * **NUMBER OF MANDATORY GROUPS:** Number of user groups expected in the rule. This parameter only applies to reception rules. * **OPTION**: U (user) or G (group). In issuance, groups are not allowed * **NAME**: Name of the user or group. ### Reception user screen. If a user is entered, for a reception standard, the following screen will appear if the public certificate is indicated as a path. ``` ----------------------------------------------------------------------------- | 24/06/2026 SIGNATURE MANAGEMENT | | 19:01:36 ADD USERS | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM48 STANDARD: 00 COMPANY: EMI-REC: R | | | | USER: ANAALVAREZ1 | | | | GROUP: SIGN FILES (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): N COUNTERSIGNING USER: | | | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | | | PATH OF THE PUBLIC REMOTE CERTIFICATE: | | AnaAlvarezAntunez_Cert_1.cer | | | | | | | | | | | | | | EXIT, ADD | ------------------------------------------------------------------------------- ``` and in the case of a DN, as follows: ``` ----------------------------------------------------------------------------- | 24/06/2026 SIGNATURE MANAGEMENT | | 19:01:36 ADD USERS | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM48 STANDARD: 00 COMPANY: EMI-REC: R | | | | USER: PABLOPEREZ1 | | | | GROUP: SIGN FILES (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): N COUNTERSIGNING USER: | | | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | | | REMOTE CERTIFICATE IDENTIFICATION: | | EMAILADDRESS=pperez@dominio.com, CN=Pablo Pérez Puente - Certificate1, | | OU=Onesait, O=Indra, L=Madrid, ST=Madrid, C=ES | | | | | | | | | | | | EXIT, ADD | ------------------------------------------------------------------------------- ``` * **GROUP:** If we leave this field blank, the user will not belong to any group. We can include them in a group by entering the group name. * **SIGN FILES (Y/N)**: The user can sign files. The signing user cannot countersign. * **COUNTERSIGN REQUIRED (Y/N):** The user's signature must be countersigned. * **COUNTERSIGNING USER:** It is the name of the user associated with the rule who must countersign. The countersigning user must have countersign permission. * **TOTAL FILE AMOUNT:** Maximum amount authorized for the user by the total of the file's transactions. This parameter only applies to reception standards. A single amount, total or partial, or none can be entered. In standards without a rule, amounts cannot be entered. * **LARGEST TRANSACTION AMOUNT:** Maximum amount authorized for the user per transaction. This parameter only applies to reception standards. A single amount, total or partial, or none can be entered. In standards without a rule, amounts cannot be entered. * **REMOTE CERTIFICATE IDENTIFICATION:** It is the DN of the user record that was provided in option 2.2 and is shown here for information. * **PATH OF THE PUBLIC REMOTE CERTIFICATE:** It is the PATH of the user record that was provided in option 2.2 and is shown here for information. ### Issuance user screen If a user is entered, for an issuance standard, the following screen will appear: ``` ----------------------------------------------------------------------------- | 24/06/2026 SIGNATURE MANAGEMENT | | 19:01:36 ADD USERS | ----------------------------------------------------------------------------- | APP.: 000099940A00099940NORM50 STANDARD: 00 COMPANY: EMI-REC: E | | | | USER: ANAALVAREZ1 SIGN (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): N COUNTERSIGNING USER: | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | SIGNER ROLE: | | ACTION ON THE DOCUMENT: | | CITY: PROV: ZIP: COUNTRY: | | CERTIFICATE ALIAS: | | te-5eb3b3d0-aa9d-4d07-9d4d-22b9069caa6d | | KEYSTORE PATH: | | rsc/keystore/AnaAlvarezAntunez_Cert_1.pfx | | | | RACF USER: | | KEY RING: | | | | | | EXIT, ADD | ------------------------------------------------------------------------------- ``` ℹ️Amounts will not be entered in issuance rules * **SIGN (Y/N):** The user can sign files. The signing user cannot countersign. * **COUNTERSIGN (Y/N):** The user is a countersigner and does not sign. * **COUNTERSIGN REQUIRED (Y/N):** The user's signature must be countersigned. * **COUNTERSIGNING USER:** It is the user who performs the countersignature. ℹ️Additional fields can be filled in: * **SIGNER ROLE:** Defines the role of the person in the electronic signature. * **ACTION ON THE DOCUMENT:** Defines the signer’s action on the signed document. * **SIGNING LOCATION:** If desired, the CITY, PROVINCE, POSTAL CODE AND COUNTRY where the signature is made will be entered The following fields are selected from the AGE policy provided with the installation (plt-firma-AGE-v1-8.xml). * **LOCAL CERTIFICATE ALIAS, RACF USER KEYSTORE PATH and KEY RING:** They are the user record data that were provided in option 2.2 and are shown here for information. ### Group screen (reception only) If a group is entered, in a reception standard, the following screen will appear. In issuance, groups are not allowed. ``` ----------------------------------------------------------------------------- | 24/06/2026 SIGNATURE MANAGEMENT | | 19:02:21 GROUP MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940EDTRF2 STANDARD: 19 COMPANY: EMI-REC: R | | | | GROUP: GROUP | | | | | | MANDATORY SIGNATURES: 001 TOTAL FILE AMOUNT : 000000000 | | | | MANDATORY GROUP : Y LARGEST TRANSACTION AMOUNT: 000000000 | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------- ``` * **MANDATORY SIGNATURES IN THE GROUP**: Indicates the minimum number of users that must sign in order to satisfy the group. * **MANDATORY GROUP (Y/N)**: Indicates whether it is mandatory for the group to be satisfied. The group is satisfied when the mandatory signatures are reached. * **TOTAL FILE AMOUNT and LARGEST TRANSACTION AMOUNT**, for information purposes, indicate the highest amount value by total file or by transaction that the users in the group have. ## Generic rule query. If query, EMI-REC, the application (the asterisk wildcard can be used) is filled in on the initial screen and neither standard nor company is entered, the rule query screen will appear. ``` ----------------------------------------------------------------------------- | 21/06/2024 EDITRAN/FF ADMINISTRATOR | | 08:50:16 SIGNATURE RULES | ----------------------------------------------------------------------------- | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFICATION | | | | | | OPTION ...........: C | | EMI-REC ..........: R | | APPLICATION .......: A00099940000099940NORM* | | STANDARD ............: | | COMPANY ..........: | | | | | | | | QUERY PERFORMED. | ------------------------------------------------------------------------------- ``` Press ENTER ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 08:51:03 RULE QUERY | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM* STANDARD: 00 COMPANY: EMI-REC: R | | | | S APPLICATION STANDARD COMPANY SIGNATURES GROUPS | | - ------------------------ ----- ------------ ------ ------ | | A00099940000099940NORMA1 34 000 000 | | A00099940000099940NORMA2 34 002 000 | | A00099940000099940NORMA3 34 003 001 | | A00099940000099940NORMA4 34 003 000 | | A00099940000099940NORMA5 34 002 001 | | A00099940000099940NORM20 34 76000056Y??? 001 000 | | A00099940000099940NORM21 34 76000056Y??? 000 000 | | A00099940000099940NORM22 34 76000056Y??? 001 000 | | A00099940000099940NORM23 34 76000056Y??? 001 000 | | A00099940000099940NORM24 34 76000056Y??? 002 000 | | A00099940000099940NORM25 34 76000056Y??? 000 000 | | A00099940000099940NORM26 34 76000056Y??? 000 000 | | A00099940000099940NORM27 34 76000056Y??? 002 001 | | | | EXIT, ADVANCE, SELECT | ------------------------------------------------------------------------------- ``` The selection fields appear in the header. * APPLICATION (header): Local code, remote code and application. * STANDARD (header): Banking standard. * COMPANY (header): Company made up of NIF plus suffix. * EMI-REC (header): Issuance/Reception) In the query lines, the following will be displayed * S: Field to select the rule. * APPLICATION: Local code, remote code and application. * STANDARD: Banking standard. * COMPANY: Company made up of NIF plus suffix. * SIGNATURES: Number of mandatory signatures in the rule. * GROUPS: Number of mandatory groups in the rule. If a rule is selected, the associated users will appear. ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 08:51:55 USER QUERY | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM25 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | SIGNATURES: 000 GROUPS: 000 | | S GROUP USER COUNTERSIGNER SIG CSG AMOUNT(T/P) | | - --------------- --------------- --------------- --- --- ------------ | | HECTORHOMERO1 RICARDO Y N 000000000 | | OSCAROSORIO1 Y N 000000000 | | RICARDO N Y 000000000 | | | | | | | | | | | | | | | | | | | | | | | | EXIT, SELECT | ------------------------------------------------------------------------------- ``` The rule fields appear in the header. * APPLICATION (header): Local code, remote code and application. * STANDARD: Banking standard. * COMPANY: Company made up of NIF plus suffix. * ISSUANCE/RECEPTION (header). * SIGNATURES (header): Number of mandatory signatures in the rule. * GROUPS (header): Number of mandatory groups in the rule. In the query lines, the following will be displayed * S: Field to select the user. * GROUP: Group to which the user belongs within the rule. * STANDARD: Banking standard. * USER: User name. * COUNTERSIGNER: Countersigner name * SIG: The user signs files. * CSG: The user countersigns. * AMOUNT (T/P): Maximum amount authorized for the user per transaction (partial) or by total file. If a user is selected, the user screen whose content was described in the previous point will appear. ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 08:54:34 USER QUERY | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM25 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | USER: HECTORHOMERO1 | | | | GROUP: SIGN FILES (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): Y COUNTERSIGNING USER: RICARDO | | | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | | | REMOTE CERTIFICATE IDENTIFICATION: | | EMAILADDRESS=alias@dominio.com, CN=Héctor Homero Helguera - Certificat | | o 1, OU=Onesait, O=Indra, L=Madrid, ST=Madrid, C=ES | | | | | | | | | | | | EXIT | ------------------------------------------------------------------------------- ``` ## Modification of rules and associated users. If modification, EMI-REC, the application (the asterisk wildcard can be used) and optionally standard or company are filled in on the initial screen, the rule modification screen will appear. If a specific rule is selected by indicating the specific EMI-REC, application, standard and company, the rule selection screen will be skipped. ``` ----------------------------------------------------------------------------- | 21/06/2024 EDITRAN/FF ADMINISTRATOR | | 09:00:58 SIGNATURE RULES | ----------------------------------------------------------------------------- | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFICATION | | | | | | OPTION ...........: M | | EMI-REC ..........: R | | APPLICATION .......: A00099940000099940NORM* | | STANDARD ............: 34 | | COMPANY ..........: 76000056Y??? | | | | | | | | | ------------------------------------------------------------------------------- ``` Press ENTER ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 09:02:46 RULE MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM* STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | S APPLICATION STANDARD COMPANY SIGNATURES GROUPS | | - ------------------------ ----- ------------ ------ ------ | | A00099940000099940NORM20 34 76000056Y??? 001 000 | | A00099940000099940NORM21 34 76000056Y??? 000 000 | | A00099940000099940NORM22 34 76000056Y??? 001 000 | | A00099940000099940NORM23 34 76000056Y??? 001 000 | | A00099940000099940NORM24 34 76000056Y??? 002 000 | | A00099940000099940NORM25 34 76000056Y??? 000 000 | | A00099940000099940NORM26 34 76000056Y??? 000 000 | | A00099940000099940NORM27 34 76000056Y??? 002 001 | | A00099940000099940NORM28 34 76000056Y??? 003 001 | | A00099940000099940NORM29 34 76000056Y??? 003 001 | | A00099940000099940NORM30 34 76000056Y??? 002 001 | | A00099940000099940NORM31 34 76000056Y??? 002 001 | | A00099940000099940NORM32 34 76000056Y??? 001 000 | | | | EXIT, ADVANCE, SELECT | ------------------------------------------------------------------------------- ``` If we select one of the rules, the following screen appears: ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 09:04:14 RULE MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | | | TOTAL NUMBER OF SIGNATURES....: 002 | | NUMBER OF MANDATORY GROUPS: 001 | | | | | | U - USERS | | G - GROUPS | | | | | | OPTION: | | NAME: | | | | | | | | | | | | EXIT, MODIFY | ------------------------------------------------------------------------------- ``` Where the total number of signatures and the number of mandatory groups can be modified if nothing is entered in the OPTION field. If the user option is entered, the list of users associated with the rule will appear (the \* can be used to perform pattern-based searches). ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:10:54 USER MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | SIGNATURES: 002 GROUPS: 001 | | S GROUP USER COUNTERSIGNER SIG CSG AMOUNT(T/P) | | - --------------- --------------- --------------- --- --- ------------ | | GROUP1 HECTORHOMERO1 Y N 000000000 | | GROUP1 RICARDO Y N 000000000 | | | | | | | | | | | | | | | | | | | | | | | | | | EXIT, SELECT | ------------------------------------------------------------------------------- ``` If we select one of the users, we can change the data belonging to the user: ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:11:32 USER MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | USER: HECTORHOMERO1 | | | | GROUP: GROUP1 SIGN FILES (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): N COUNTERSIGNING USER: | | | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | | | REMOTE CERTIFICATE IDENTIFICATION: | | EMAILADDRESS=alias@dominio.com, CN=Héctor Homero Helguera - Certificat | | o 1, OU=Onesait, O=Indra, L=Madrid, ST=Madrid, C=ES | | | | | | | | | | | | EXIT, MODIFY | ------------------------------------------------------------------------------- ``` And if we select group modification, the following group list screen will appear: ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:14:37 GROUP MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | SIGNATURES: 002 GROUPS: 001 | | S STANDARD COMPANY GROUP MAND. SIGS MAND. GROUP | | - ----- ------------ --------------- ------------ ----------- | | 34 76000056Y??? GROUP1 002 Y | | | | | | | | | | | | | | | | | | | | | | | | | | | | EXIT, SELECT | ------------------------------------------------------------------------------- ``` In it, we can select the group we want to modify and proceed to change the corresponding data: ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:16:03 GROUP MODIFICATION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | GROUP: GROUP1 | | | | | | MANDATORY SIGNATURES: 002 TOTAL FILE AMOUNT : 000000000 | | | | MANDATORY GROUP : Y LARGEST TRANSACTION AMOUNT: 000000000 | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------- ``` ## Deletion of rules and associated users. If deletion, EMI-REC, the application (the asterisk wildcard can be used) and optionally standard or company are filled in on the initial screen, the rule and user deletion screen will appear. If a specific rule is selected by indicating the specific EMI-REC, application, standard and company, the rule selection screen will be skipped. ``` ----------------------------------------------------------------------------- | 21/06/2024 EDITRAN/FF ADMINISTRATOR | | 12:18:08 SIGNATURE RULES | ----------------------------------------------------------------------------- | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFICATION | | | | | | OPTION ...........: B | | EMI-REC ..........: R | | APPLICATION .......: A00099940000099940NORM* | | STANDARD ............: | | COMPANY ..........: | | | | | | | | | ------------------------------------------------------------------------------- ``` ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:18:47 RULE DELETION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM* STANDARD: 00 COMPANY: EMI-REC: R | | | | S APPLICATION STANDARD COMPANY SIGNATURES GROUPS | | - ------------------------ ----- ------------ ------ ------ | | A00099940000099940NORMA1 34 000 000 | | A00099940000099940NORMA2 34 002 000 | | A00099940000099940NORMA3 34 003 001 | | A00099940000099940NORMA4 34 003 000 | | A00099940000099940NORMA5 34 002 001 | | A00099940000099940NORM20 34 76000056Y??? 001 000 | | A00099940000099940NORM21 34 76000056Y??? 000 000 | | A00099940000099940NORM22 34 76000056Y??? 001 000 | | A00099940000099940NORM23 34 76000056Y??? 001 000 | | A00099940000099940NORM24 34 76000056Y??? 002 000 | | A00099940000099940NORM25 34 76000056Y??? 000 000 | | A00099940000099940NORM26 34 76000056Y??? 000 000 | | A00099940000099940NORM27 34 76000056Y??? 002 001 | | | | EXIT, ADVANCE, SELECT | ------------------------------------------------------------------------------- ``` If we select one of the rules, the following screen appears: ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:21:24 RULE DELETION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM20 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | | | TOTAL NUMBER OF SIGNATURES....: 001 | | NUMBER OF MANDATORY GROUPS...: 000 | | | | | | U - USERS | | G - GROUPS | | | | | | OPTION: | | NAME: | | | | | | | | | | | | EXIT, DELETE RULE AND USERS | ------------------------------------------------------------------------------- ``` If F2 is pressed, the system will delete the rule and all associated users after confirmation. ``` ----------------------------------------------------------------------------- | 18/06/2025 SIGNATURE MANAGEMENT | | 11:43:18 RULE DELETION | ----------------------------------------------------------------------------- | APP.: 000099940A00099940NORM20 STANDARD: 00 COMPANY: EMI-REC: E | | | | | | TOTAL NUMBER OF SIGNATURES....: 000 | | NUMBER OF MANDATORY GROUPS...: 000 | | | | | | U - USERS | | G - GROUPS | | | | | | OPTION: | | NAME: | | | | | | DO YOU WANT TO DELETE THE RULE AND THE USERS?(Y/N).: N | | | | | | EXIT, CONFIRM | ------------------------------------------------------------------------------- ``` If, on the other hand, U is entered in the option field, the system will delete the users associated with the rule. ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:23:49 USER DELETION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | SIGNATURES: 002 GROUPS: 001 | | S GROUP USER COUNTERSIGNER SIG CSG AMOUNT(T/P) | | - --------------- --------------- --------------- --- --- ------------ | | GROUP1 HECTORHOMERO1 Y N 000000000 | | GROUP1 RICARDO Y N 000000000 | | | | | | | | | | | | | | | | | | | | | | | | | | EXIT, SELECT | ------------------------------------------------------------------------------- ``` ``` ----------------------------------------------------------------------------- | 21/06/2024 SIGNATURE MANAGEMENT | | 12:24:07 USER DELETION | ----------------------------------------------------------------------------- | APP.: A00099940000099940NORM27 STANDARD: 34 COMPANY: 76000056Y??? EMI-REC: R | | | | USER: HECTORHOMERO1 | | | | GROUP: GROUP1 SIGN FILES (Y/N): Y COUNTERSIGN (Y/N): N | | COUNTERSIGN REQUIRED (Y/N): N COUNTERSIGNING USER: | | | | TOTAL FILE AMOUNT : 000000000 | | LARGEST TRANSACTION AMOUNT: 000000000 | | | | REMOTE CERTIFICATE IDENTIFICATION: | | EMAILADDRESS=alias@dominio.com, CN=Héctor Homero Helguera - Certificat | | o 1, OU=Onesait, O=Indra, L=Madrid, ST=Madrid, C=ES | | | | | | | | | | | | EXIT, CONFIRM DELETION | ------------------------------------------------------------------------------- ``` When F2 is pressed, the system will delete the user associated with the rule after confirmation, and if the user is the last user associated with the rule, it will also delete the rule. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/electronic-signature/graphical-interface/applications-presentation-sessions/application-signing-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.