I have an application that uses unique AnchorTabStrings for locating signature blocks. When we tested the application using the DocuSign Sandbox the signing locations worked flawlessly. However, now in production we are experiencing erroneous behavior. Sometimes the location of the signature is completely off (meaning that it appears in a random location in the document) and other times the signature block is completely omitted (not used). The application is a Windows C# MVVM WPF Desktop application and we are using the DocuSign SOAP API. The number of signature blocks varies depending on how many pages are produced by the user in the application. The names of the AnchorTabStrings I'm using are "AuditorSignatureBlock", "OwnerManagerSignatureBlock", and "TechnicianSignatureBlock". We are not using document templates. Here's a snippet of code where we create a new signing tab within the document.
new Tab
{
DocumentID = this.dataContext._inspReport.DocumentGuid.ToString(),
RecipientID = idRoutingNumber.ToString(),
Type = TabTypeCode.SignHere,
AnchorTabItem = new AnchorTab
{
AnchorTabString = "AuditorSignatureBlock",
XOffset = 0,
YOffset = 0
}
}
Update:
I have narrowed the issue down to the number of pages. Meaning when there is 3 or more pages within the envelope, this is when the feature no longer functions. I produced the same document in the DocuSign sandbox environment and this issue is not apparent. I have submitted a case with DocuSign support.
Since your app is working on the developer sandbox system (demo), but not on the production system, the document may different or anchor string placement may not be enabled on your production account (see below).
First try with the exact same document that worked on the developer sandbox system. If that works but the new document does not, then check carefully that the anchor string in the new document does not include any spaces or other white space, and that it is not being wrapped across two lines.
For example, you can make a test document where the anchor text is not white, then, once it works, change the text color to white.
I've had cases where the transformation from the document creation system to PDF introduced unexpected changes.
For these reasons, one common technique is use strings such as /auditsig1/ for the anchors.
Another diagnostic technique to try is to create an anchor field (tab) by using the DocuSign web tool, and then check that DocuSign can locate the anchor text in your document. In other words, try it on production without your application at all.
Re: anchor strings an optional feature
Yes, anchor strings (also know as Auto-place) may not be enabled for your production account. To check, use the DocuSign web tool as described above. If anchor strings are not enabled there then contact DocuSign to have the feature added to your account.
What happened had nothing to do with AnchorTabStrings. In production there was an additional recipient added for carbon copy and I did not properly handle the recipient IDs (had two recipients with the same ID). Sorry, my fault :(
Related
I have a requirement to first create the Docusign envelope in create status and later attach a list of documents and send it out.For this purpose I am first creating envelope with Envelope Rest API,adding documents using the Documents Rest API and finally sending it out.The anchor tabs that I initially added during create do not get picked up on the attached documents.It seems to ignore those tabs.Is there a way to add anchor tabs to get picked up on all documents.
Thanks
Lakshmi
One thing I would suggest checking is the anchor tabs scope - document or envelope. This is something that many people don't know about.
https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/auto-place/
"anchor population scope"
Also, are you using a composite template by any chance? that may matter
It is hard to say what the issue is without seeing your request. As your use case is complex and there are many variables, I'd advise opening a support case so we can have a look in detail
I am trying to write a DocuSign integration where a customer uploads a PDF file and sends it to a list of signees. The customer should not have to place the right amount of anchors in the document. Instead, a new page (or several pages if necessary) for signatures should be added to the document automatically, with one signature box per signee. I want to avoid modifying the PDF myself. Is there any way DocuSign can do this for me?
The easiest and best way to do this would be to utilize anchor strings, which you've mentioned above that you would rather not do. Normally under these circumstances I'd recommend using a template, however you've indicated that you want the customer to be able to upload the PDF, correct?
The issue there comes down to document dimensions. If you were using a template, the coordinates for a tab would be stored in the template and be applied automatically. If your customer is supplying a PDF, you don't have a guarantee on how small or large the page dimensions will be. IE: An image taken with a Retina display vs. a 6MP camera would be like a Post-It Note vs. a calendar. The remaining option would be to find a standard set of coordinates that would work. For example, when a customer upload a new PDF always have a signature or initial tab applied at x/y: 0,0 so it will always appear at the top left.
Alternatively, what we would normally recommend is that the customer add in a unique identifier like /signer1signature/, then apply the tab via anchor string where it will be applied at every instance, even if it's a single instance hidden on the signature line.
This is thru the Rest Api. Suppose you have a signer and a document with a few signing tabs. I'm using a composite template and the signer has a template role. Suppose the template role does not match up, so the signing tabs aren't created. What you get is the left tools pane and the user can drop/drop signatures. My question: if no tabs can be created, is it possible to stop the left tool pane from showing up, that the person is basically just viewing the document? This situation may never happen, but I'd like to know if there is a way out if it does. I'm sure the answer is to prevent it from happening in the first place.
In DocuSign, recipients who are assigned the "Signer" role will always be given the opportunity to provide input -- either via tabs that you've assigned to them in the document(s) or via tabs that they place on the document(s) themselves (if you assign no tabs to them). If you specify a recipient as a "Signer" but include no tabs for them, they will get the "freeform" signing experience that you describe, where they can drag/drop tabs from the left panel onto the document(s) where ever they choose -- I don't believe there's any way to prevent this.
I am using embeded signing and I have noticed that the checkbox's are in different locations at different stages.
I can either make it look correct while doing embeded signing... the check mark is centered in the box, or I can make it so that the check marks (X's) are properly centered in the summary pdf.
However I do not know how to consistently get the check marks to align in both the embeded interface, or the pdf summary...
anyone solve this?
This is not the answer you're hoping for but -- unfortunately, there are not separate settings to specify the location of a form field during signing versus on the completed document (PDF). You only get one opportunity to specify a field's location (during the Create Envelope process), and DocuSign then automatically determines location of the field in the completed document (PDF) -- presumably using the same coordinates that you specified during the "Create Envelope" process, although not always exact (as you've discovered with the checkbox element).
So, the best advice I can offer is to always verify placement of fields BOTH in the signing view AND in the completed view -- and then use trial and error to specify field location in a way that produces best overall results across both views.
Background: We use the DocuSign SOAP API method CreateEnvelopeFromTemplatesAndForms for a very clear reason (mainly, we don't want to keep track of page numbers and X/Y coordinates) and we do not want to stop using this api method (unless there is another method that doesn't force us to keep track of page numbers and X/Y coordinates). I mention this before someone happily suggests I use another method.
Problem: We've recently been asked to send large envelopes through the DocuSign api (could exceed 100 mb). I know that DocuSign doesn't place a limit on envelope size, but rather on size of payload per api call when the envelope is created. I think what we need to do is the following, but I am having trouble:
Step 1: load up to 50 mb in the templates
Step 2: call CreateEnvelopeFromTemplatesAndForms but set the ActivateEnvelope parameter to False
Step 3: load up to another 50 mb in the a new set of templates
Step 4: call CreateEnvelopeFromTemplatesAndForms again but this time set the ActivateEnvelope parameter to True.
Is what I'm trying to do possible? I keep getting an error that says the "TransactionID has already been used." If what I'm trying to do (in general) is possible, any code samples would be much appreciated.
I believe Anchor Tags is a viable and easy to use feature that should solve your issue here. With anchor tags you can still use the CreateEnvelopeFromTemplateAndForms() API call but you won't have to specify page numbers or (x,y) coordinates for your DocuSign Stick-eTabs. Instead, those tabs will get "anchored" to your documents based on content that it finds in the document itself.
For instance, let's say you have a document that needs to be signed and in the document where the signature should go you have the text "Sign Here". You can have the system place a signature tab close to this "Sign Here" text. You could have it place it X amount of pixels to the right, or Y inches or cms to the right, etc.
You can add these tabs at the account level, which means they will get applied whenever their corresponding text is found in ANY envelope you create in your account, OR you could add them in your API request so that they are only used on that particular envelope.
For more info please see the following links:
Previous Stack Overflow Question
Explanation on Dev Center - look at Tab Positioning section