A template turns the answers of a response into a document, so staff do not copy answers into a PDF. This page covers generating the document, sending it, and having a rule do the first part for you. How to write a template is covered in Documents.
Why a template does not break
A template points at stable field IDs, not at field labels. Renaming a question or moving it does not break the template. A template version never changes once published: editing creates a new version, and a document or request keeps pointing at the exact version it was made from. Publishing a new version changes nothing about requests that already exist.
A template can also name signer roles, such as "Client" and "Contractor", with {{signer.client}}. When you make a request from it, you give each role a person.
By hand
- Open the response and its Documents and signatures panel.
- Choose a published template and press Generate document. Wait until it is Ready. If it fails, the reason is shown, for example a character the document font cannot draw. Fix the answer or the template and retry.
- Press Send for signature and add the signers, roles and fields as in Create a signing request.
The document is made from the response as it was at that moment, and the request is bound to that revision. If the person edits the response later, the request that is out does not change and is not cancelled. To send the corrected content, make a replacement.
With a rule
An automation on the form can prepare the request for you whenever a response is submitted:
- Add the action Prepare a signing request and name a published template of the form.
- Take the signer's name and email from the response with
{{ submission.<field name> }}, or write them out. - Add Ask a person to review the draft. Staff review is the default: the draft waits, the person who can send is told, and nothing reaches the signer until they approve it.
- Add Send the signing request. It sends only a draft a person approved, for the version they looked at. Changing the draft afterwards makes it unapproved again.
- Use the preview with a sample response. It shows the template version that would be used and any template field the sample leaves empty, and it prepares and sends nothing.
- Save the automation as active.
When you save an active rule, Formspring checks that the template exists on this form, is published, and still has every field it uses, that the signer comes from a field the form really has, and that the rule starts from a response. A rule that fails is not saved, with the reason.
Sending without a review is possible but only as an explicit choice. Set the send action to Automatically, without a review. Then only a member who may send signing requests can save the rule, it must follow a step that prepares the draft in the same automation, and it sends only that draft. Everything else still applies: the allowance, the sender checks and the idempotency. Use it only when the signer expects the request, since nobody reads the document first.
The same response, template and revision is prepared once, however often the event repeats. A later edit to a response prepares a new draft for the new revision and leaves a sent request alone. The form itself must not ask for signing consent: the signer consents when they sign the exact generated package.
