How to show docusign ID in the document - docusignapi

I am using embedded sign flow. I am able to show signHereTabs in the document, but I also want to show docusign id of the owner. I am not able to find any option in the api on how to show account owner's docusign id (name, sign & company) in the document. Is there any specific anchor for that ?

In order to get that information on the envelope then the sender (or owner) will need to also be a recipient on the envelope and have those tags added.
Another option would be to add data fields for the signer that are locked and populate it with the senders information.

I think there are a few possible solutions here:
Add the sender as a recipient to the envelope (i.e. a Carbon Copy recipient or a Signer).
Use envelope custom fields to pass the data you need.
For #1 if the sender is already a recipient you can add corresponding name, company, email, and other tags to the envelope. If you don't want them to be a signer of the envelope you can probably get away with adding them as a CC recipient (so that they simply get a copy of the doc) and give them the same routingOrder as the one signer.
Alternatively, for #2 you can use envelope customFields which are traditionally used to pass meta data about the envelope around but you can use to store the sender data instead. See the DocuSign Dev Center and API Guides for more info.

Related

Embedded signing error when envelope signing order is set

I am integrating a WebApp with DocuSign and use Embedded Signing to allow users sign the envelopes I am creating (and updating recipients) on the fly out of some predefined templates.
Everything works ok in the simple cases but for the templates with the signing order set (Second recipient should sign the envelope only when the first one has done) I've got {"errorCode":"UNKNOWN_ENVELOPE_RECIPIENT","message":"The recipient you have identified is not a valid recipient of the specified envelope."} error message when creating Recipient View.
Could you advise is there a way to show the envelope for such recipient (second) if now is not her turn to sign? Or this is how Embedded Signing works and you are not able to create Recipient View for the recipient whose recipient order is not the current?
Thank you!
You can only show the embedded view for the current signer or recipient. You can have more than one current person at a time by setting their routing orders to the same number.
Eg, two signers can have routing order of 1.
Either change the template, or you may be able to update the routing order via a composite template when you send the envelope

Reading email ID from the form and update the recipients list in envelope programmatically

I have a DocuSign with multiple signature field (one primary and others secondary), I need to send a form to primary signer where there are few additional email fields which the primary signer will fill and the document needs to go to those email ids (which primary signer has provided in the form). Primary recipient has to sign first signature field and then send the same form to another recipient and he has to sign other signature field keeping the previous recipient signature and so on and I have to set the recipients programmatically in envelop. Is it possible? and how can I implement that?
The answer to this is 'sort of.' We do have a feature that can take care of this for you, or you can programmatically add in additional recipients based on formdata.
The recipient role is an agent managed envelope, specifically Address Recipients. What this role does is allows that person to set the name / email address of any future recipients in the signing order. You would essentially create a placeholder role with the tab information for the additional recipients. Once your Address Recipients role fills in the names / emails, they're automatically processed per your template / envelope.
The other option would be to either update existing envelope roles from dummy information to the intended recipients programmatically. The reference guide for creating a new recipient on an envelope can be found here: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/create/ -- you should be able to add in additional signers as long as the envelope has not reached a 'Completed' status. I would advise adding a sort of placeholder / approver role after the initial signer fills in the email information so the envelope doesn't automatically complete.
The reference page for updating an existing recipient can be found here: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/enveloperecipients/update/
Regards,
Matt
The way it worked for me is -
Created a template envelop with a recipient role (Update Recipients) and few dummy signers.
In the code just pick the first recipient and send the document to that recipient.
When the recipient with role "Update Recipients" receives the document he can further modify the dummy recipients and the email goes to them for their signature.
When all the recipients signs the document the workflow completes.
But I have one problem: When all the recipients complete their signature and workflow completes, I want to further do some processing in my code so how I can specify a "return url" which will be called when workflow is completed.

Creating envelopes where first signer specifies next recipient(s)

I need to send out a document / envelope. I'm using the C# SDK, since we'll be sending from a service. We know who the recipients of the document COULD be, but it's up to the first recipient to either sign or choose a recipient.
The first recipient of the document can do one of two things-
Sign the document
select a different recipient from a drop-down list of Roles, and then have the document go to that user for their signature.
these future roles are "Dealer" and "Lawyer". We'll know, at the time of
selection who these user's are (names & emails).
Right now, I have a template (from Word), with tabs that will be populated when sending the initial envelope, so that all users can see the data.
My question(s) are:
Is using the Template the best option? Should I attempt to update the text within the Word document, by not having it configured as a template?
How should I add the users / roles / signers to the envelope, since they can be chosen ? I saw something about Intermediaries - is this what I should be using to specify the next recipient in the document? Currently, I have three "Roles" defined in my template- one for "Provider" - the first recipient, then "Dealer" and "Lawyer".
IF not using a Template, how should I specify / add the follow-up users, "Dealer" and "Lawyer"?
Any assistance is greatly appreciated!
Using a template is probably what you need. You can update the document inside a template before sending an envelope that is created from the template. (you can also use"correct" to update an envelope that was sent, but only by the original sender and there are some other limitations)
see comment from Drew, you cannot do a conditional recipient yet, but there are other options, including a special type of recipient that can add other recipients (if that's what you want).
You can create a more complex workflow that have the first envelope trigger a second envelope with the recipients you want. That could work for you. Not sure yet about all your requirements, but the first signer can trigger this using our web-hook from connect.

Document Templates - Roles Set to In person or email signing

I have successfully created a system to use a document template to create a new envelope.
The system has a tabbed UI and iframe that fetches new URLs from the Docusign API every time a tab is changed, and when a URL expires.
My problem is that now, some clients will either be sign in-person or sign via email. After reading the docs, I don't see a way to change from an in-person to an email signer after the envelope has been created. Is that correct?
Is it possible to set whether a role will be in-person or email sign at the time of envelope creation, without affecting the original template?
If that is not possible, Is my best option to create a template with duplicate fields for both in-person and email signing, and only use the appropriate ones based on my case?
If you need to change an in-person signer to a remote signer, or vice-versa, or any other recipient type into another recipient type you have two options:
Perform an Envelope Correction
Remove then Add the Recipient back to the in-process envelope as a different type.
For option #1, using an envelope correction you can edit things like recipients, tabs, and even documents if they have not been signed yet. Make the following API call to request the correction URL of an envelope:
POST /v2/accounts/{accountId}/envelopes/{envelopeId}/views/correct
API Docs: https://docs.docusign.com/esign/restapi/Envelopes/EnvelopeViews/createCorrect/
For option #2, the system does not let you convert a recipient into another recipient type - HOWEVER - you can delete a recipient from an envelope then add them back in as a different type. For instance, delete an in-person signer and then add them back in as a signer.
You can see the needed calls through the EnvelopeRecipients Resource.

Change from Remote to Embedded Signing

I have a remote envelope that's out for signature. I know how to create an embedded envelope, but I'm not sure how I can change a remote envelope to an embedded envelope.
Any help?
Note that Embedding vs. Remote does not apply to the "envelope" per say but rather it applies to your recipients.
For instance, you can have an envelope with 2 recipients where the first has been added as a Remote recipient (and thus will receive an email to initiate the signing) and the second has been added as an Embedded recipient meaning you will handle creating the signing URL and navigating them there, etc.
Therefore, if you added someone as Remote and want to change them to Embedded (or vice-versa) you can do a Correction of that envelope. Take a look at the following REST API call:
Modify or Correct and Resend Recipient Information
Note that to configure the recipient as embedded you will need to set their clientUserId property to a non-null value.
UPDATE
Note: If the system does not let you add the clientUserId property of a recipient then you might have to
Delete the recipient from the envelope
Add them back in with the clientUserId assigned
To delete the recipient from the envelope you can make this call:
Delete Recipient
Then to add them back in with the new info:
Add Recipient

Resources