Templates / Document processing / document-signature
Document E-Signature
Generates an agreement, sends it for e-signature and waits for the provider's callback, correlated on the envelope id. A signed agreement is archived; a declined one goes back to its owner; and if nothing comes back in 14 days an interrupting timer voids the envelope so it cannot be signed late.
Scenarios · 2
- The counterparty signs and the agreement is archived send-envelope → await-signature → archive-document → agreement-signed
- The counterparty declines and the owner is told await-signature → notify-owner → agreement-declined
Job types · 5
-
dms-archiveArchive signed agreement -
document-generateGenerate agreement -
esign-envelope-sendSend for signature -
esign-envelope-voidVoid envelope -
owner-notifyNotify owner: declined
Files · 2
- document-signature.bpmn Process model
- document-signature.bpmn.tests.json Test scenarios (runScenario format)
Every scenario passes on @bpmnkit/engine's runScenario in the
package's tests. casen template use document-signature [dir] writes the files above
into your project — see the templates guide for running
the scenarios and deploying.