Using Anchors (AnchorText ancillary output)

Overview

Note: The AnchorText does not currently support EmbeddedPDF documents.

This section provides guidelines for using the AnchorText ancillary output. Through this functionality, when the AnchorText ancillary output is passed in with the transaction request, third party eSiging applications can add initial, signature, and date fields to a document.

When generating the document package, Engine will also generate a supplemental PDF document (<x>-AnchorText.pdf) containing all anchors assigned with the corresponding SignerName.
Note: In <x>-AnchorText.pdf, <x> will signify the "Packet" name. If the “Packet” name is not specified, then the default packet name is “Default”, which will be used for <x>.
This <x>-AnchorText.pdf document is included in the document package when the AnchorText ancillary output is selected and lists each document that contains anchors by providing the InstanceDisplayName, the SignerRole, and SignerName values; for example:
Application Disclosure-WI | Borrower | John Doe
Note: The SignerRoleOtherDescription value is used when SignerRole = Other

Other considerations

Consider the following when using the AnchorText ancillary output:

  • The <x>-AnchorText.pdf document cannot be merged with other documents.
  • <x>-AnchorText.pdf document will exist for each packet