Docusign placeholders

Kyloe AwesomeDocs offers the functionality to send generated AwesomeDocs documents out for signing and/or updating included forms via Docusign.

The Docusign placeholders are entered in exactly the same way as a merge field in word but are of a different syntax, and uses two underscore characters before and after the placeholder tag:

__DOCUSIGN.RECIPIENT1__

All Docusign placeholders should be entered with their text colour matching the background colour (white on white, for example). This is because when Docusign adds the signatures it does not replace the tag in the document. This can result in ugly signed documents with the tags from AwesomeDocs showing through the signatures.

Tip: For visibility, you can highlight the merge fields in a Word document.

Standard Docusign signing placeholders

In order for documents to be signed by recipients you will need to provide a location for fields such as signature, name and signature date in your document.

The list of available Docusign signing placeholders is as follows:

DocuSign placeholder type	Syntax
Recipient signature	__DOCUSIGN.RECIPIENT1__
Recipient name	__DOCUSIGN.NAME1__
Recipient title	__DOCUSIGN.TITLE1__
Recipient initials	__DOCUSIGN.INITIAL1__
Date of signature	__DOCUSIGN.DATE1__

The number at the end of each tag represents the order of the recipient to sign. The number should match the order of the current recipient list under Config.

If, for example, you wished recipients one and three to sign you would add two tags in your document: __DOCUSIGN.RECIPIENT1__ and __DOCUSIGN.RECIPIENT3__.

Other Docusign placeholders

It is possible to add some custom Docusign fields to an AwesomeDocs template. These fields can then be completed in the document by the recipient in Docusign.

Using the form fields option under Config, you have the option to update Bullhorn information on return.

DocuSign placeholder type	Syntax
Free type text box	__DS.text1-XXXX__
A checkbox	__DS.checkbox1-XXXX__
Date Entry	__DS.DateEntry1-XXXX__
Date Entry - forces signer to enter a date in a specific format	__DS.DateEntryDDMMYYYY1-XXXX__
Add an Approve button (the stage before signing)	__DS.approve1__
Add a file attachment (same for all attachments)	__DS.attachment1__

The XXXX in the placeholders above should be replaced by a sensible name. The name is used to identify the field to both the recipient and yourself.

Names cannot end with numerical values, use one, two etc. instead. This text appears as a tooltip when the recipient is completing the information.

To easily know by name what the Docusign placeholder is used for helps when used as a form field under the template's config, as the Docusign field needs to be mapped to the appropriate Bullhorn field to work.

Radio buttons

It is also possible to add a group of radio buttons. These are slightly more complicated than the other fields as they require a group name as well as individual names. These are entered in the following format:

DS.radio1-#XXXX-XXXX

The first XXXX is to identify the group, the second each option. This is best shown with an example:

Radio button group A
__DS.radio1-#groupA-optionA__
__DS.radio1-#groupA-optionB__
__DS.radio1-#groupA-optionC__
__DS.radio1-#groupA-optionD__

Radio button group B
__DS.radio1-#groupB-optionA__
__DS.radio1-#groupB-optionB__
__DS.radio1-#groupB-optionC__

These tags would show two groups of radio buttons, the first with four options and the second with three.

Optional fields

All of the above fields can be set to optional (with the exception of checkboxes and radio buttons). All you need to do is add _o to the tag. For example, to make one of the signature locations optional:

__DOCUSIGN.RECIPIENT1_o__

This can be useful for some contracts which have both a mandatory signature and one or more opt-in sections.