Once a request is sent, the document, the fields, the recipients, their roles and the signing settings cannot change. This is what makes each signature mean one specific thing. A mistake is corrected with a replacement: a new request linked to the old one.
When to replace
- The document or its terms need to change.
- A signer's name or email address is wrong, or the signer asks to hand the request on.
- The deadline needs to change.
- The response was corrected and the document should reflect it. Editing the response does not touch a request that is already out.
You do not need a replacement for a message that did not arrive, a link that expired, or a signer who needs a reminder. Those are fixed on the request: see Failed delivery.
Steps
- Open the request and choose Create replacement. Formspring creates a draft with the same document, recipients and settings, no signatures, and a link to the original.
- Change what has to change. If the document itself is wrong, generate a corrected document from the response first and start from it.
- Open the original and choose Void request. Voiding stops the outstanding request: the signers' links stop working, and the people who were waiting are told. Signatures already made stay in the history of the original.
- Review and Send for signature on the replacement. It will not send while its predecessor is still open.
Everyone signs the replacement again, from the start, with a new email code. A signature on the original is never copied. The replacement is a new request and uses one request from your allowance when you send it. The review step says so before you confirm.
What you cannot do
- Void a request that is completed or is finishing up. A completed document is never made unsigned. If the agreement changes, make an amendment as a new request and note it. The original stays as it is, within its retention rules.
- Reopen a declined or expired request. Make a new one.
- Edit a recipient on a sent request, or approve a hand-over request by changing the address in place. Approving a hand-over creates a replacement draft for you to review and send.
For developers
POST /api/v1/signing-requests/{id}/replace creates the replacement draft and POST /api/v1/signing-requests/{id}/void voids the original. A send that carries an old expected_version fails with revision_conflict, so two people cannot overwrite each other.
