Progress
This is an important scenario when sending a document through an integrated application, where the application prepares the document or document documents and before sending the signature, the document needs to be checked to make sure it has been prepared correctly.
However, it can also make sense when entering documents through the user interface, where someone prepares the document and another should check it before sending it.
It is possible to automatically insert the signature of the proponent's representative. For now, however, the restriction is that it can be the only one and must be listed first in the signature script.
Signature scenario
Set It depends on the order.
Automatic signature insertion set on workspace or during integration
The first signer in the scenario is the responsible representative of the claimant (their signature inserted automatically), then the checker in the approving role (their signature is not on the document) for the claimant, and then the counterparty signer.
Captain Demo's signature is inserted into the document automatically by setting it up in the workspace or by making the appropriate call via the Signi API. A document approval request is then sent to Employee #4, who can reject the document. If he approves it, it is only sent to the counterparty - Customer 2 for signature
When calling via the Signi API, see 10. Document check before sending - the signature of the authorized person for the proposer is inserted automatically
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article