Description
In this example, we will expand the options for setting up the signature Request service and use the send info service. The send info service is used for backed to backend communication between the OKdokument API and Portal to exchange document state
information. This service can be used alone or in conjunction with the result url as described below.
The prerequisite is the implementation of the send info service on the Portal side.
How it works
In this example, the input is a PDF document that already contains signature field tags, so Create signature Request is extended by:
- State: tags, OKdokument API searches through the PDF document and inserts a signature field where it finds a unique text string (tag)
- signAnywhere = disabled, as the document contains a signature field and the functionality of the “anywhere” signature should be disabled
In the Create signature Request configuration, we also added a value for sendInfoUrl, which is called by the OKdokument API after signing (or canceling) the document.
At the moment when OKdokument API scans the tags and inserts the necessary signature acrofields, it returns to the Portal: document ID and a unique url for opening the document for signature
After signing and confirming the document (or cancelling the signing) OKdokument API:
- Redirects the user to the result url with the given result (success, close)
- Addresses the info service of the portal and with the given state of the document (signed, canceled)
The signed document can be downloaded and saved in the Portal using the Download document service.
After downloading the signed document, the document is deleted by calling the Delete document service.
