I'm using the DocuSign SOAP API to create and send envelopes (insurance application forms) with one or two signers.
I want the first signer to land on a specific url when signing is complete and the second signer to land on a different url when their signing (and therefore the entire envelope) is complete.
I can set a Destination URL in my brand for "Signing Completed" but that's at the signer level for all signers.
Is there a way to specify a landing page/url which the user can be redirected to when all signers have completed signing?
You can use specify a routingOrder for each recipient and set the appropriate URL for the recipient in the final routing order.
Once the final recipient sign, the user will be redirected to the URL.
Related API RequestSenderToken
Related
I have an envelope I've created through the API and I set the status of it to sent during creation time so it was never sent to the customer. Then using receipientViewRequest I grabbed the link for it and sent that to the customer in an email so they can sign it. However, the link only works once. After the first click/visit, the link expires. Is there anyway to get a link to the envelope that doesn't expire?
The signing flow which you are using is called as Embedded Signing. In embedded Signing, you need to invite or ask your signer to visit your App, and when signer is ready to sign the document then at that time you should generate the signing URL (on-demand) and ask user to complete the signing. This link is one time use and by default, it expires in 300 seconds if not used. If you want DocuSign to send an email to the signer with your App URL so that signer is redirected to your App when he/she clicks the email link, then you can put your App URL in the embeddedRecipientStartURL property of the signer in the API call. By adding this property DocuSign will send an email to DocuSign and on click on Review Documents button, browser will be redirected to your App, once it reaches your App then you can generate embedded Signing URL so that you can host the Signing ceremony.
You should never send this embedded Signing URL link in an email or via any medium. If you want DocuSign to send an email to the signer so that signer can sign the document at any time then you should do Remote Signing, this can be achieved by removing the clientUserId for the recipient in your API call.
In docusign is it possible to create a signing request via the web interface and then retrieve the sigining URL via the API
at the moment, I update the Envelope using the API to attach a clientUserID as this is lacking when created via the web interface.
Then I retrieve the signing view url however, there is no signing tab when navigating to that url. The only action I have is to close.
I have tested using the API and the envelope contains signing tabs so I'm not sure what the issue would be.
Any help would be much appreciated!
When you send a DocuSign envelope if you assign one or more tabs to your recipient it becomes what's known as a Free Form signing experience, where the recipient decides where to sign the document.
On the other hand if you specify one or more tabs for the recipient then it's a Guided Signing experience. In guided signing the recipient can only sign and take actions at the tabs the sender has specified.
It sounds like you are successfully creating the envelope and signing URL but that there are no tabs configured for the signer. If that's the case you should confirm your code is identifying the recipient correctly by specifying the name, email, recipientId, and clientUserId values.
I would also check that the tabs are being set in your request body correctly for the given recipient. First get the recipient information for the envelope using the EnvelopeRecipients: list API to ensure the data is what you expect, then generate the signing URL using the corresponding data.
With reference to the below question -
Docusign API Multiple Embedded in Person Signers
InPerson Signer: Since the earlier question doesn't have an answer ticked.
From my webpage (C#, Asp.Net MVC), Once the documents are uploaded to Docusign, I want the whole document to be opened in a separate tab and with multiple signers. I am able to achieve this for a single inperson signer by mentioning the ClientUserId. If there are more than one inperson signer then how will the docusign works? On every Sign, does it give my web app a response and then do I need to call the next recipient View URL.
Help much appreciated.
The recipient View URL will provide you the URL to open the docusign document for the first signer. Once the recipient signs and clicks on FINISH, the response URL should contain the envelope ID as the query string parameter. Add a new Action method to accept the envelope id as query string parameter. Fetch the recipient list by using EnvelopesApi.ListRecipients method. Check the recepientList.CurrentOrder property which states the next person in the line to sign. Fetch the recipient view url of the next person and redirect to the new url again. Repeat this process until the CurrentOrder is null.
DocuSign: when using an embedded signer, how do you send email to the signer if they select "Finish Later?"
I have tried to deselect the "Suppress Emails to Embedded Signers". But that did not seem to change anything.
If it is not possible to send a signer an email, how does they get back to the document, since the url that is generated is only good for 5 minutes?
DocuSign offers two main methods for initiating workflows with your recipients: Remote Recipients or Embedded Recipients.
Remote Recipients, which is the default, receive an email from the DocuSign platform which has a link that they use to open the signature request through a browser and sign through the DocuSign Web App (i.e. website). In this scenario recipients are guided through the DocuSign website and have full access to all features and settings.
On the other hand, Embedded Recipients do not context-switch, wait for an email, and then sign through the website. Instead, when you embed a given recipient you are telling the DocuSign platform that YOU are taking care of everything, such as preparing the signing URL, delivering to the user (recipient), and handling the callback once they are done signing.
In this case, whether they sign the document, decline to sign, close the window, or do something else like hit the "Finish Later" button, there will be a query parameter appended to the return URL you configure so that you can determine what action they took. For instance if they declined to sign the document and your returnUrl was set to https://www.docusign.com/developer-center the callback would look like:
https://www.docusign.com/developer-center?event=decline
Therefore, when you Embed a recipient and they either do not sign in time (due to the 5 min expiration of the URL) or they try to access it more than once (they are one-time use only) your app will need to parse the returnUrl to determine what action they took and simply generate a new signing URL when needed.
Create an envelope using Server Template and then get the return URL for Embedded signing and also send the Envelope to the recipient via email to sign the document. So that , User can sign the document either using Email Link (Remote) or Embedded link in Web. Please let me know there is any option to achieve this in DocuSign API ?
A solution is to specify both a clientUserId and an embeddedRecipientStartURL when creating a Recipient.
Specifying a clientUserId causes the recipient to be an "embedded" signer.
Specifying an embeddedRecipientStartURL causes the recipient to also receive an official DocuSign email inviting them to sign the documents.
The embeddedRecipientStartURL parameter is intended to be a URL that DocuSign can redirect the signer to within your app, and the idea is that you take care of any necessary authentication. However, rather than supply a URL to your own app, you can instead supply a magic value of "SIGN_AT_DOCUSIGN". In effect, this causes the recipient to be both embedded and receive an official "please sign" email from DocuSign."
A single recipient in an envelope workflow must be specified as EITHER a Remote recipient (so that DocuSign will send them an email when it's their turn in the routing order) OR an Embedded recipient (so that DocuSign will not send them an email) -- it's not possible to specify a recipient as both Remote and Embedded. However, in the scenario you describe, you might consider the following approach:
Specify the recipient as an Embedded recipient when you create the envelope.
Immediately after creating the envelope (or when it's that recipient's turn to view/sign the envelope), your application creates and sends an email to the recipient and includes a link to a page within your application (website) -- you can include querystring parameters on the link URL to contain recipient name and email address.
Develop the page in your application (the one that the email links to) such that it identifies the recipient (perhaps by reading the recipient name and email address from the querystring parameters in the URL), and then uses that information to make a "POST Recipient View" call to retrieve the URL from DocuSign that can be used to launch the recipient's signing session.
Using this approach, the recipient will still receive an email when it's their turn to sign -- but the email will be sent by your application -- and the link in the email will lead the recipient to your application where your application will then request (from DocuSign) and present (to the recipient/user) the URL to view/sign the envelope.