Setting up Word-based document templates in  Agiloft with the appropriate DocuSign tags is a key part of the integration, as this makes it easy for users to generate documents that already have DocuSign tags in the proper locations. By automating document creation with document templates, the user sending the documents doesn't have to manually place signature tags in the DocuSign interface.

DocuSign Tags in Agiloft document templates use the following syntax:

$docusign:TagType:FieldName:RoleName(Label){property1:value1,property2:value2}

• $docusign: begins each tag for DocuSign functionality.
• TagType: uses one of the available types to indicate what information will be stored there. For example, SignHere, FullName, or Title.
• FieldName: optionally designates a name for the field. The FieldName portion of the tag is optional and usually left out, except in cases where there are multiple tags using the same tag type and the same signer. The FieldName text appears in a tooltip in DocuSign if a user hovers over the tag.
• RoleName: assigned to a specific signer according to their role in the envelope. The options come from the entries in the DocuSign Roles table.
• Label: used to differentiate lines that use the same tag type and role name. Labels can be reused in the document to indicate identical fields, but different labels must be used for different fields to distinguish them for DocuSign and prevent overlapping.
• property and value: used to apply additional properties to the tag, such as making the tag optional, setting a specific font, or adding tooltip text.

Tips

Keep the following tips in mind when creating print templates with DocuSign tags:

• Microsoft Word can be inconsistent in the way it formats document templates, variables, and API tags from  Agiloft. Often, Word can insert extra formatting that is not visible in the document but that can interfere with DocuSign Tags. Be careful when formatting DocuSign tags in Word document templates, and be sure to test the results.

• As a rule, do not use HTML-enabled text fields in  Agiloft to insert DocuSign Tags into document templates. The resulting Word document will separate any sections containing HTML code away from the main document's XML file, which will result in an incorrect translation by the DocuSign API.
• Turn off spelling and grammar checks for document templates, as Word may insert formatting that will interfere with the DocuSign Tags.

DocuSign Tag Types

For each DocuSign tag, you need to specify the tag type to determine how the field behaves. Some fields automatically populate with the signer's information, while others require the signer to enter information or make a choice.

The following tag types can be used in a DocuSign tag:

• Approve
• Checkbox
• Company
• DateSigned
• Decline
• Email
• EmailAddress
• FullName
• InitialHere
• SignHere
• Text
• Title

For more information about these tags, see the DocuSign documentation here. Note that the DocuSign page lists field types by name, not by the syntax you need to use to insert them in document templates. Inside a tag, the field type should not have spaces.

Using Tag Types

In most cases, simply combine a tag type with the appropriate role name to create a DocuSign tag. For example:

• A DocuSign tag to indicate the signature for a signer whose role name is "InternalSigner1" would appear as: $docusign:SignHere::InternalSigner1
• Add a DocuSign "Decline" button with: $docusign:Decline::Signer1

Other commonly used tag types include DateSigned and InitialHere. A signature block that includes the DocuSign tags for the signer's signature, full name, title, and date signed is a common configuration.

Any DocuSign tags should be formatted with white text so that the tag text does not appear in the final document. Here's an example with dark red highlighting applied to show the text:

Example DocuSign tags in white text, shown with red highlighting to make them visible

Remember to use DocuSign tags for all signature block items. This way, signer information does not need to be known at the time the template is generated.

Using Field Names

When there are multiple tags containing the same tag type and signer, they will cause overlapping signatures and other problems on the final document. For example, a signature field that appears multiple times in a document will create overlapping signatures if their syntax is identical. To distinguish between tags in this situation, use the FieldName part of the tag syntax to give each tag a unique value.

To prevent the problem of duplicated tags, use different field names for each tag that will be used in the template. Likewise make sure to use different field names if the same tag needs to be used more than once within the same envelope.

$docusign:SignHere:unique1:Customer1(unique1)
$docusign:SignHere:unique2:Customer1(unique2)

Tag Properties

You can optionally include additional properties in your tags. Note that any property that conflicts with the body of the tag is discarded.

The following properties are supported:

Common DocuSign Tags

Here are some example DocuSign tag constructions.

Example Repeat Tags

If the same tag needs to be used more than once within the same envelope, make the FieldName unique: