We are using the REST API v2.
Consider this scenario:
Our system creates an envelope with two signers. The second signer
doesn’t have any kind of authentication via Docusign. In terms of the
API that means setting signer.requireIdLookup = false (no RSAID verification).
The first signer signs ok.
BEFORE the second signer signs the system
determines that authentication via RSAID is required after all. I
tried updating signer 2 to enable RSAID, but it doesn’t work. By
reading the documentation here it looks like changing the
requireIdLookup on a sent envelope is not supported.
Any ideas on how to do this? Voiding the envelope and starting again is not a good option because we don't want signer 1 to sign again.
As mentioned in the above comments, this is currently not supported. You need to determine if you will be using RSA ID check - which is controlled through the requireIDLookup property - at the time you are adding your recipients to the envelope, which might not necessarily be at the time of envelope creation. It's possible to create the envelope and save it as a draft envelope, then add recipients at a later time.
Related
I am embedding the signature request with DocuSign in my application. Is there any way that I can allow customers to change embedded signature responsibility(forward the document to someone else)?
I have already checked the setting to enable recipients to Assign to Someone Else according to this link: https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=yca1573855023892&topicId=uin1573855010064.html&_LANG=enus
enter image description here
Another question, if it is impossible then is there any way that customers can save all the changes that they have made so far?
Embedded Signing doesn't directly support signers changing signing responsibility. This is because out-of-the-box if a captive signer did so, the recipient they changed it to would not have a way to access the envelope.
The most straightforward way to resolve this would be to change the signer to a Remote signer so that the Signer Reassign function you've linked would work.
If it's necessary for a signer to remain embedded/captive, but still have the ability to reassign, you would need to build out functionality in your application that would (outside of DocuSign)
prompt the recipient for the new signer's info
make an UpdateRecipient call on the envelope to change the name/email/clientUserId as needed
Notify the new recipient that they have an envelope to sign
Grant the new recipient access to the envelope.
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.
We are using REST API to create envelopes and the Template is set up in DocuSign, with signer roles etc. Our customer wants to be able to decide in every separate occasion whether to use InPerson signing or send the signing link via email to the recipient.
Currently/originally we implemented Embedded signing, but our customer wants the "security question" (e.g. ask for driver's license number) to be there before the signing. So that they can prove that the buyer has actually been there to sign.
Is there a way to do this? I have the DocuSign Template set up with "needs to sign" option, but when sending the request to create a new envelope, somehow change a signer to be InPerson and trigger a workflow for that?
I managed to find information about Embedded signing and clientUserId, but is there a way to deliver information for example to the Certificate of Completion, like with the InPerson case with the input showing there?
In order to switch from In-Person (embedded) to remote signing and vice-versa, you will need to use the property ClientUserId. It is well described in the DocuSign article Embedded Signing.
If you're willing to switch after the envelope is created, see my recent question here that deals with the same issue.
To implement the "security questions", DocuSign offers multiple authentication option. It seems to me that you are looking to use the "ID Check" authentication here
In C#, it would look like this when you try to implement ID Check for a given signer :
signer.RequireIdLookup = bool.TrueString;
signer.IdCheckConfigurationName = "ID Check $";
Lastly, for your question regarding the authentication method and the certificate of completion, the Embedded signing article I mentioned above explains well what happens for the authentication method in the certificate completion below :
The authenticationMethod is an enumerated value that indicates the convention used to authenticate the signer. Since, with Embedding, you are telling Docusign that you are handling authentication this is your way of telling the platform how you authenticated the recipient. This information will also be included in the Certificate of Completion, a PDF that is automatically generated for every completed envelope.
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 am using the DocuSign API in an embedded manner. I create an envelope and add signers, the first signer always being set as embedded. This allows me to retrieve a URL that is then embedded in an iframe.
However, I also wish, to trigger an email (as soon as the envelope has been created, NOT upon completion) that gets sent to the primary recipient/signer as if they were a nonembedded signer.
I tried adding the signer twice, with the same role, to the recipients, but that didn't work. No email was sent.
Is there a way to accomplish this?
I believe there is a setting to enable this but that it needs to be enabled by someone on DocuSign's side, like your account manager. If you do not have an account manager yet please respond to the auto-generated emails that were sent out to you once you created your account, you should have 3 of them.
The account settings available are only for Completion emails. However, the REST API also supports an embeddedRecipientStartURL parameter on the signer object that triggers a normal DocuSign email. The value of this parameter is the URL that should be included in the email. This means you can link back to your own application and request the recipient view as normal.
Check here for more detail: Signer embeddedRecipientStartURL. Note: if you set this to a value of "SIGN_AT_DOCUSIGN" then DocuSign will provide its own URL and take care of signing. The trade-off is that you won't be able to initiate any bespoke authentication you are doing in your own application.