Setup in ENSPACE

How to Configure

1. Access the desired workspace.
2. In the side menu, click on Settings.
3. In the submenu, select Integrations.
4. Find the CertiSign integration and click on "Install Integration".
5. In the CertiSign tab, click again on "Install Integration".
6. Select the environment (production or staging) and fill in the following fields with the information from your CertiSign account:
   • Api Token
7. Click Save to complete the integration installation.

Preparing the Flow for Signature

8. Create a task of type Confirmation.
   • Enable the "Generate PDF" button.
   • Then enable the "Generate Document from Field" button.
   • In the "Document Field", select the field where the document is stored.
   • Optionally, you can:
     • Attach a default PDF to the generated documents.
     • Insert a seal.
9. In your flow, add a Task of type "Use Integration" and select the "CertiSign" integration.
10. After selecting the integration, the following fields will be available:

• CertiSign Actions: select the "Send for Signature" option.
• Signature Standard: here you select the signature standard.
  ⚠️ In ENSPACE, you must select CAdES

  Standard	Simple Explanation	Document Type
  CAdES	Digital signature for general files (like .docx, .xml, .zip).	Generic files
  XAdES	Digital signature focused on XML files.	XML files (integrations, systems)
  PAdES	Digital signature for PDF files.	PDF documents

• Document Source: define whether the document to be signed will come from a specific field or from an item document.
  • If you select "Item Document", you will need to fill in:
    • Document Title
    • Signers Field
  • If you select "Field", you are saying you will get the document from an onlyoffice-type field, and you will need to fill in:
    • Document Field: select a field of the type "File Editor" that contains the document to be sent.
    • Document Title: define the file name. You can use dynamic expressions.
    • Signers Field: use a repeater-type field, which must be previously created in the flow.
      Structure of the Signers Field:
      ⚠️ The repeater field must contain the following subfields:
      • Action (select type): defines the participant’s role in the signing process. The values must exactly match the ones below (labels are free, but values must be identical):

      Value	Description
      signers	Signers who manually or digitally sign the document
      electronicSigners	Electronic signers (no digital certificate, like click or OTP)
      serverSigners	Automatic signers (signature done by the system/server)
      approvers	Approvers (participate by approving, without legal signing)
      observers	Observers (view the document and process, without interaction)
      globalObservers	Global observers (follow the entire flow, not linked to a specific doc)

      • Name (text type): signer’s name.
      • Email (text type with email mask): signer’s email address.
      • Identification (text type): unique identifier of the signer (CPF).
      
      ⚠️ The following subfields are optional:
      • Title (text type): define the name of the document.
      • One Click (radio type): one-click signing, does not require handwritten or image signature.
      • Step (number type): defines the step (order) in which the signer will sign the document.

Finalizing

11. With your tasks created, just add the signers field and the document field to a form. Be sure that this form is filled in before generating the PDF and proceeding to signature.
12. You can now test it.