eSign ready template
This is is a Word template with merge fields that can be used to generate a document to send via eSigning.
The setup of this template is different than a template for the classic workflow.
The parties
Generally the first section of a contract defines the parties. An eSign template looks like this:
The mergefields will be merging data from the signatories.
A generated document:
Place a signature
In an eSign template there are no "Sign here" or "Place your initials" elements available.
Instead the signatories will sign in the System One interface, outside the PDF document.
When all signatories have signed the document, a page with all the signatures is automatically added to the begin of the document.
Footer
When an eSign document is sent out, a footer is automatically added to each page of the PDF.
The footer contains information to identity the document. Make sure that your documents have no footers.
Unavailable merge fields
Some of the merge fields that are available in the classic workflow cannot be used in eSign templates.
When you try to use them anyway, the text NOT AVAILABLE FOR ESIGN is shown.
| «DocInternalId» | The document number is automatically assigned and added to the footer when the document is sent out for signature. |
|
«DocSendDate» |
The send date is automatically set to today and added to the footer when the document is sent out for signature. |
|
«DocDueDate» |
Use «DocDueInDays» instead. |
| «DocRel… | Any fields that start with DocRel don't work. Use «SignerRel… instead. |
|
«DocCon… |
Any fields that start with DocCon don't work. Use «SignerCon… instead. |
| «DocSubject» | This field doesn't exist for eSign |
|
«DocOverDue» |
This field doesn't exist for eSign |
|
«TextAddOn» |
You cannot merge in artist riders. Add the artist rider as a PDF from storage instead. |