Using eSignatures

eSigning sends a document or a whole booklet to the people who have to sign it and attaches the signed file back to the case.

Signing runs through Certifaction, so the integration has to be set up before any of this works. Per ontology you can point at the information holding a signatory's name, email address and phone number, which prefills them when a request is sent, and a user can still correct them there. Each process sets the legal weight its signatures carry. A proof or file information can also be sent for signing (new in Atfinity 17).

Choosing the signatories

For a document and a proof, you choose the signatories among the identifiers of its condition, since those are the instances it is generated for. For a file information the signatory is the instance it belongs to, or for one inside a structure the instance holding the structure.

Sending

In a case you send either a single item or a whole booklet. Before it goes out you see one entry per signatory, with the items that person has to sign and their contact details to correct if needed. The eSignatures tab then follows every request until it is signed or declined, lets you revoke one, and holds the signed files once they arrive.

A proof or file information with no upload yet, or whose file is not a PDF, PNG, JPEG, TIFF, SVG or WEBP, is not part of what goes out, so check a booklet before sending it.