{ "emailSubject": "Please sign the document", "documents": [ { "documentBase64": "BASE64_PDF_STRING", "name": "Agreement.pdf", "fileExtension": "pdf", "documentId": "1" } ], "recipients": { "signers": [ { "email": "user1@example.com", "name": "User 1", "recipientId": "1", "routingOrder": "1", "tabs": { "signHereTabs": [ { "anchorString": "/sign1/", "anchorYOffset": "10", "anchorXOffset": "20", "anchorUnits": "pixels" } ] } }, { "email": "user2@example.com", "name": "User 2", "recipientId": "2", "routingOrder": "2", "tabs": { "signHereTabs": [ { "anchorString": "/sign2/", "anchorYOffset": "10", "anchorXOffset": "20", "anchorUnits": "pixels" } ] } } ] }, "status": "sent" }
Answer to Problem Statement :
Sequential signing is supported in DocuSign using the routingOrder
field for recipients.
If any signer declines (rejects) the envelope, DocuSign stops the workflow and sets envelope status to declined
.
DocuSign does not automatically route the envelope back to the previous signer.
To implement "return to previous signer":
Monitor the envelope status using DocuSign Connect or periodic polling.
On rejection, create a new envelope starting from the previous signer.
Use the previous document (flattened PDF or prefilled tabs) to retain signed sections.
In Mendix, extend the existing DocuSign module or call DocuSign REST APIs via custom microflows or Java actions.
Reference Links
Create Envelope (DocuSign API Reference)https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/
Sequential Signing with routingOrderhttps://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-in-order/
Envelope Status Change Notifications (Connect Webhook)https://developers.docusign.com/docs/connect-api/connect-event-notification/
Composite Templates and Tabs for Prefillhttps://developers.docusign.com/docs/esign-rest-api/how-to/using-composite-templates/
Sample Payload for Sequential Signing (2 users shown) for Your Reference