I am using the most current DocuSign.eSign.dll NuGet package for C#/.NET.
I have a single Signer, who needs to sign two different documents (PDFs). I want the signer to sign both the documents together, in the same session.
So, I created a new envelope that has TWO documents (base 64 encoded) and EACH of those documents has the same SINGLE signer, but get back an error saying that the envelope has DUPLICATE RECIPIENTS.
How else am I supposed to construct this API call/envelope, in order for the signer to sign both the documents together, in the same session on the DocuSign website?
Your envelope should have one recipient (signer) and two documents.
The documents field in the envelopeDefinition object takes an array of document objects.
Create one document object for each of your documents and you should be all set.
As stated by, Lary K, it needs to be an array. I just posted an example here: How to send multiple documents for signature DocuSign for Salesforce
Related
I have a working application where a generic document is defined in the DocuSign template with auto-place anchor strings. In creating the envelope I replace the generic document with a document generated by my application.
A new requirement is to have multiple documents in the template with document visibility turned on so as to control recipients only seeing certain documents.
I have successfully created envelopes replacing the multiple documents with my generated documents using composite templates.
The problem I'm having is with using auto-place anchors. I either receive a response from the API that anchors must be specifically placed on the document or when the recipient receives the document, the process repeatedly loops thru the anchors and never allows the recipient to finish the signing of the document.
The question is can I use auto-place anchors with document visibility?
The documents I am generating are the same as in the template, but now have been populated with customer information that may change the location of where a signature is needed
I suggest you try with multiple composite template, each with 1 document.
See my article for more template ideas.
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
I'm evaluating DocuSign esignature API (c# SDK) for an e-signature solution.
Our scenario is easy:
single PDF
multiple signers
each signer has its own signature form field defined in the PDF
Is there a way to map specific signature form field inside PDF to specific signer?
What we already tried:
Anchor text is working but it is cumbersome for our clients to position anchor text, changed its color so it is invisible. Also it is error-prone
TransformPdfFields somewhat working but as I understand it is all or nothing it transforms all form fields and all signature fields are mapped to single signer (am I wrong here?)
Thanks.
With DocuSign, each field (SignHere fields, text input fields, etc) is owned by a specific signer or other recipient type. Fields are called tabs in the API.
At a schematic level, the object hierarchy is:
There are multiple ways to map signHere tabs to different signers and locations in your documents:
Use a template. You or your business person can create a template using the DocuSign web tool. Then your app can use the template id to create and send an envelope.
The different signers are referred to as roles in the template. Eg customer signer 1, internal signer etc. Your app assigns specific names / emails to the roles when it creates the envelope.
Assign the tabs (fields) to signers using the API. The tabs can be positioned using absolute locations or via anchor strings.
Use an HTML document as your source documents. You can specify the tab locations in the HTML. See docs.
Use a PDF Form as your source document. If you name the form's fields consistently then you can use the DocuSign composite templates feature to have the form's fields belong to different recipients/signers. I do not recommend this approach if you have control over the source documents. But if you are give PDF Forms as your source documents, you can make use of them.
Tell me if this is correct: suppose I have an envelope with a couple of documents that need signing and a couple that just can be viewed. The template is set up to place signing tabs at specific anchor text spots in the document. I use the same template for all the documents. Can I create just a signer for all these documents and they will not be asked to sign anything on the view only documents because there are no anchor tags to match up? There is no way that they would be made to perform some action on the documents to be only viewed?
If the Recipient is of type Signer and have tabs assigned on an envelope then the recipient will not be able to add any additional tabs. This applies to the entire envelope, individual documents does not matter.
However if the Recipient has no tabs assigned then the recipient will have the option of Free form signing.
Free-form signing occurs when no tags are placed on a document submitted via DocuSign. This means that the signer will be presented with a palette of signature options (Signature, Initial, Full Name, etc.) which can be applied to the document at will.
So for your case, if you assign the Signer a Tab on the first document then the Signer will not be able to add new tabs on any document.
While I was poking around the DocuSign API getting it set up for an application, I noticed recipients have two separate ID's, one being a recipientId and the other recipientIdGuid.
The first value recipientId appears to be plain numbers, whereas the other value looks to be a UUID or hash of some kind.
I'm assuming the recipientId fields are unique to the envelope, whereas the recipientIdGuid version is unique across the service? I'm trying to get the Docusign Connect service set up currently, so I'm wondering what I should be storing locally in our own DB.
RecipientGUID is the GUID for a particular recipient on a particular envelope. No two recipients will ever have the same recipientGUID.
RecipientId is a local reference integer, used for mapping recipient to other objects, such as mapping the recipient in the envelope to tabs assigned to them in that envelope. The Sender sets these values. No two recipients in the same envelope will have the same ID, but across envelopes there is no uniqueness requirement.