Creating S-Sign-enabled S-Docs templates can be done in almost no time. Similarly, if you've just installed S-Sign into an org that's had S-Docs for a while, you can quickly enable S-Sign in any pre-existing S-Docs template. To learn how to create S-Docs templates, click here.

Note: If you are using a version of S-Sign before 1.900, please Click here to view legacy instructions on creating S-Sign-enabled templates.

Sign requests consist of two types of S-Docs templates: PDF and HTML. The HTML template will be used as the body of the sign request email. The PDF template will be used to generate the documents that you would like to be signed.

Configuring the HTML Template

The HTML template is like any other S-Docs HTML email template, with two extra steps.

First, you need to enable S-Sign on the HTML template. To do this, click on your template and go into the Template Editor. Click Advanced Options and select SSIGN from the "E-Sign Vendor" dropdown. After that, your HTML template is S-Sign enabled.

Next, you need to place a link in the "Source" page of the Template Editor that looks like the following:

<a href="[[[SIGNLINK]]]" target="_blank">Click Here to Sign</a>

[[[SIGNLINK]]] is an S-Sign merge field that will be replaced with a link in the email that takes the recipient to a page where they can sign the document. You can also use the S-Sign merge field [[[DOCUMENTNAME]]] to display the name of the PDF document in the outbound email. Once out of the "Source" page of the template editor, it should look like this:

 

Configuring the PDF Template

Similar to the HTML template, the PDF template is like any other S-Docs PDF template with the exception that you need to enable S-Sign. Just as you did with the HTML template, go into the template editor, click Advanced Options and select SSIGN from the "E-Sign Vendor" dropdown. Since it's a PDF template, an S-Sign menu will appear on the left of the template editor.

From there, you can select your S-Sign field type from the dropdown menu (signature, initials, text, or checkbox), and then paste the field tag into your template where you want the field to appear in the finished document. For example, if you want the signature box to appear after the words "Please Sign Here," you would paste the field tag like this:

That's it! Once you have modified the HTML template to include the [[[SIGNLINK]]] code and enabled S-Sign on both templates, you are ready to send out an E-Signature request using these two documents.

Legacy Instructions

Just like the current version, legacy S-Sign requests consist of two types of S-Docs templates: PDF and HTML. The HTML template will be used as the body of the sign request email. The PDF template will be used to generate the documents that you would like to be signed.

To enable the HTML template for E-Signature, you'll need to go to the "Advanced Options" tab of the Template Editor and select "SSIGN" for the "E-Sign Vendor" dropdown (just like with the current version). However, you do not need to do this for the PDF template.

Once you've made this change, you need to place a link in the "Source" page of the template editor that looks like the following:

<a href="[[[SIGNLINK]]]" target="_blank">Click Here to Sign</a>

[[[SIGNLINK]]] is an S-Sign merge field that will be replaced with a link that takes the recipient to a page where they can sign the document. You can also use the S-Sign merge field [[[DOCUMENTNAME]]] to display the name of the PDF document in the outbound email.

Similarly, the PDF template is like any other S-Docs PDF template, with the exception that you need to place the S-Sign merge field [[[SIGNATURE]]] wherever you'd like the recipient's signature to be placed. When you generate a document using this PDF template, [[[SIGNATURE]]] is replaced with a large image that says "Sign Here" until the recipient signs the document. Once the recipient signs the document, all instances of [[[SIGNATURE]]] will be replaced with the recipient's signature image. Hence, [[[SIGNATURE]]] can be placed in multiple locations of the document, but the recipient only signs once, and all instances of [[[SIGNATURE]]] will be replaced by the same image.

That's it! Once you have set the HTML template's "E-Sign Vendor" value to "SSIGN," modifed the HTML template to include [[[SIGNLINK]]], and modified the PDF template to include [[[SIGNATURE]]], you are ready to send out an E-Signature request using these two documents.