How to use Automated anchor tags feature on the Embedded Sending View

Question

I have a question regarding the Embedded Sending View. Through our program, the user selects documents which are sent to the Embedded Sending View where the user then selects recipients and has the option to add fields on the documents. The documents can have automated anchor tags such as \\s1\\, \\s2\\, and so on. What we need is for the tabs, such as Sign Here or Initial, to be displayed in the add fields page of Embedded Sending, which is not happening. Templates are not an option at this time as the documents are defined by our users. I tested this in the DocuSign Console and it didn't work there at all, no tabs came up automatically on the add fields page despite anchor tags existing on the page.

This is the document that I tested

This is a screenshot of the Embedded Sending View. There were two signature anchors in the document and two signers/recipients were created in the Embedded Sending View.

This is a screenshot of the Tagging View - The Sign Here tabs do not come in automatically.

This is a screenshot of the page to actually sign the document through the email is sent. There are no Sign Here tabs displayed.

Answer 1

Automated anchor tags rely on the number in the tag text matching a recipient ID in the signer's definition. In order for \\s1\\ and \\s2\\ to map to your recipients, they'll need to have recipient IDs 1 and 2.

Automated anchor tags do not work if the document is uploaded through the web console - only if the envelope is created through the API with the document and recipients defined.

The 'stock' automatic anchor tags only work through DocuSign for Salesforce. Upon closer inspection, it looks like DFS includes a set of tags in its API traffic to create an envelope.

To approximate this behavior, I created a custom anchor tag that did work. To create these tags yourself:

• Navigate to Go to Admin > Document Custom Fields
• Add Field
• Name: Anchor Signature
• Type: Sign Here (or Initial Here if desired)
• Shared: Checked (makes tag available to all users on the account)
• AutoPlace Text: \\s{r}\\

In practice, the {r} gets replaced with the recipient ID.

This tag definition:

Results in tags being placed in my example draft that I created through the API: