What is the meaning of the DocuSign attribute ApplyAnchorTabs - docusignapi

I'm using DocuSign REST API v.2 and I've seen that for each document to be signed there is the attribute ApplyAnchorTabs, but I haven't found informations about its use; I have set it both 'true' and 'false' but the result is always the same.
What is the meaning of ApplyAnchorTabs ?
Thanks

When you add a new document to an envelope, you can decide if you want your pre-defined anchor-tabs to be applied to it. So You could have an envelope with multiple documents and only some of them use the anchor tabs.
Anchor tabs are strings that are used to determine where tabs (signing elements) are positions. So you can position them either using X/Y coordinates or using strings that you find in the document to help you place them.

Related

How to remove non-matching DocuSign generic template anchor field from signing document c#?

I am sending the document in an envelope to sign along with the template Id to be applied. In this case, I have defined SignHere tabs for 10 signers using AnchorString. Sometimes the signer's count passed to sign the document would 2 sometime it would be 10.
What I am trying to achieve is, when there is only 1 matching signer then the rest of the AnchorString should be removed from documents, and space for those fields should also be managed accordingly.
Like, In below screen, there is only one signer passed for document as Signer2. So, in this case Signer and Signer3 should be removed.
Is that possible to remove those non-matched AnchorString from document and manage the space accordignly using c# DocuSign SDK?
Do I need to set any Envelope property to handle that case or any other configuration need to be done while sending an Envelope?
DocuSign does not remove information from the documents provided so it can not remove the anchor strings that you didn't use in your document. As a workaround you can create your anchor strings with a white font so it matches the background and it will not be noticeable to the user. This will still leave the empty space in the document, to remove the empty space you will need to provide different documents based on the scenario

DocuSign what are the special fields I can add to Word documents to use via the API

I am testing the Docusign API and I can send a document to sign and get it signed in the position I want using the SignHere data structure and setting the AnchorString.
I want to add a field for the signed date but what is the format and field name required. I can't see anywhere that tells me how to type these into a Word document.
I see you can create templates online using Docusign and put in these fields but I don't see how that will work for us. The document will be dynamically created by our document assembly system and then sent via the Docusign API so I need to build in the fields at that point when I add the signature anchor string.
So what is the Word document special field format and list of Docusign available fields please?
Also it would be good to know how to insert a field to ask the signer to enter some text. Any entry box.
Thanks for any help.
If you're using Salesforce to send out these documents, the DocuSign CLM product supports template codes in Word. See docs.
Otherwise, you can only specify locations of fields (tabs) in the Word doc. This is done via anchor strings also known as auto-place fields. Docs.
Placing the anchor strings in your Word doc is the first step. For the second step, I recommend that you create a DocuSign template by using the DocuSign web tool. Then, when you send the document via the API, you combine it with the template. Or better, you can insert the Word document into the template itself.
The advantage of this technique is that your business users, with the right instructions, can update the template by themselves.
An alternative is for the DocuSign API request to specify the document and the various fields (tabs) that should be included in the document for the signers.
Added
Two other options:
Create your source documents as HTML documents. You can include special tags to indicate different types of DocuSign fields. You can also indicate sections of documents that can be expanded/closed by the signer. HTML field documentation.
This is the best approach, IMHO.
Create your source documents as PDF Forms with form fields. DocuSign can then transform the PDF form fields into DocuSign form fields. There are limitations. Docs.

Can we position signers by recipient id through the DocuSign API?

We've set up our template to include signature blocks and we're able to send the recipient's name and email address with the envelope. These recipients appear in the recipient list and when you sign in to DocuSign you're able to select one of the recipients from the list and position it appropriately.
We're looking at removing this manual step so that we can say, for example, the first signature we send across in the envelope corresponds to signature block one in our template and the second to the second as so on.
When we create the signature blocks in our template we can assign roles and the DocuSign documentation suggests that if we send a role across with the envelope we should be able to achieve the automatic positioning that we're after.
What we're wondering is whether we can also do this with the recipient id rather than the role?
There are multiple ways to position tabs (signature blocks) for recipients.
One approach is to specific x/y coordinates where the tab should be located inside the document (also specify page #)
Another approach is to use AnchorTags which is specific text that the tab (or tag) would be located in. This can be used with white-on-white text in the document, that could be invisible to the signer but allows the tag to be placed there. This can also be a real part of the document (like 'Date:') and you can specify an offset to improve your positioning.
Read more how to use AnchorTags in the API here - https://developers.docusign.com/esign-soap-api/reference/sending-group/using-anchor-tags

Docusign API, "Correct Document" or just change fields

Using the Docusign API, I am trying to change the fields that exist on a document. When I first create the document, I am able to change field values using "tabs." I get how to do that.
When I am trying to edit, or in Docusign's terms "correct," a document after it has been sent out, but before being signed, I am having trouble figuring out how to access those fields again to change the values.
I have tried using the API avenue described here ( PUT /v2/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}/fields ), but even after successful calls, the values of the fields aren't changing, and I believe it is because I should be trying to access the tabs, as I did when first changing the tab values as I created the document, instead of targeting the fields, since the two seem to be different. Any thoughts? Thank you in advance for your answers.
To update Tab values you should use the putRecipientTabs api.
Once a signer completes the Signing process, the tab values cannot be updated.
Also not all Tab values can be updated. See this answer for more information.
The putEnvelopeDocumentFields api is for a different purpose. Document fields are different from Tabs. Document fields are an array of name-value custom data strings to be added to a document. Custom document field information is returned in the status, but otherwise is not used by DocuSign.
I figured it out.
The "fields" we are seeing on documents are "tabs," and they are children of the recipients.
The hierarchy goes envelope > recipients > tabs, which tabs we were trying to change. Not envelope > document > fields, which refers to something else--just familiarizing with the language of the api.
Here is a link to the reference for how to change "fields" aka "tabs", and that link includes sample requests.
One thing that helped me target my actual fields, since I kept on getting an error that the field didn't exist for the recipient, is to do a get request of all available tabs and use that response body as the request body for the update call (where we change the field values). Then you know the field information will be accurate, paring the body down to exactly the "fields" aka "tabs" you are interested in targeting.

Setting Alignment of \s1\ on the document - DocuSign for salesforce

I am sending documents for signature from salesforce using DocuSign. I am having an issue with aligning the tag - \s1\, \t1\, \d1\ on the document.
My understanding is Docusign will replace tags automatically for specific signers to sign. But they are off by few pixels and come over the line marked in the document.
could anyone tell me how i could configure sure that the user don't enter details over the line on the document but above the line.
Thanks in advance for the response.
Getting proper tag placement with anchor text usually takes some trial and error -- i.e., testing DocuSign tag placement based upon various positions of the anchor text strings (\s1\,\t1\, \d1\, etc.) that you put in your document(s).
One tip: If you're creating your documents (i.e., adding the anchor text strings) with Word or something similar, putting each anchor text string inside a textbox (with no textbox borders) is a good way to give you more finite control over tag placement -- because you can move the textbox wherever you want to, regardless of where underlying text exists in the document. For example, here's a screenshot from Word where I've added an **\s1** tag inside a textbox, and placed it precisely where I want it over the signature line:
If I sent this document through DocuSign and thought the Signature tag was placed lower than I wanted it to be, I'd just edit the document to move the textbox up a few pixels (without affecting the signature line placement itself), and then re-test.

Resources