I'm trying to dynamically populate a non-signer CC role upon creating an envelope from a template using the REST API. Is this possible? Currently, when I add the "receive a copy" recipient role to a template and then set the email for that roleName in the code and send the document off for signing, it automatically "completes" the document which seems like a bug or it may be that I'm doing something that isn't supported? Can anyone help?
Thanks,
Janea
Ergin was correct. Using the API call to add the CC role as the envelope is created from the template works as expected. It did not seem to work initially but, not sure why.
Carbon copy recipients are unique in that that is the only recipient type that does not take any actions on the envelope. They simply receive a copy of the envelope when it's their turn in the routing order, they never see the "tagging" workflow (unless they are added as another signing recipient on the envelope at the same or a different routing order).
When you have a CC recipient and it is their turn in the routing order, nothing happens except that they receive the notification email. If they have the highest routing order out of all recipients (i.e. if they are the last recipient) then the envelope status will already be completed by the time it reaches them and it won't change status and will remain as complete.
Are there other recipients? If there's only a single recipient and they are marked as "receive a copy" or "CarbonCopy", and not marked as a "Signer" type, it will probably see the envelope as complete.
Related
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
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.
I'm trying to build a POC for our internal application using DocuSign, but I have some issues.
The flow is:
create a template in docuSign with a set of dynamic fields to be populated from the client app
the template has 2 recipients that have to sign the document - client and buyer with empty emails. The emails should be populated dynamically based on the order, so they're not fixed
from the client app, create an envelope that will use the template, will populate automatically the fields from the template and will open an embedded page where the first user(client) can sign the document immediately(without going to mail)
immediately after the client finished signing the document, an email should be sent to the second recipient(buyer) to finish the signing
For now, I succeed to implement all the steps, except the last one - the document is not sent automatically to the second recipient for signing.
How can I do that?
I know that I can use a recipients lists for sending email to receipts, but this is not possible when using a template - I get an error.
Thanks in advance!
Check that your template definition has the two recipient roles defined with different Signing order values.
The first recipient will have signing order 1, second signing order 2.
When you create the envelope from the template, you set the clientUserId for just the first signer. That way the second signer is a regular ("remote") email recipient.
If you'd like more help, please EDIT your question to show the code you use for creating the envelope from the template.
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.
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