We need to validate a date field(Data Field) is greater than today's date in DocuSign Template. How can we validate a Date greater than today's date in DocuSign Data Field?
I assume enabling Connect is just a configuration and will be available in specific accout typesI was trying to check what this means, which i found in the connect service guide.
"Request your account be configured to publish transaction updates. Your DocuSign Account
Manager can help you with this step
1. Is there any way to uncheck the "Expire/Void Envelope" checkbox? We do not want any envelopes to expire.
2. When an envelope is voided, is there any way of preventing recipients from receiving the void email? When cleaning up outstanding envelopes, instead of deleting them, we'd like to void them, but do not want to email notifications to go out to our clients.
Is there a way to turn off email authentication and not have any authentication at all? This would be for a less important internal process.
I am experiencing delays in recieving access code emails on the demo site. Most of the time it will take only a few seconds to get an email but other times it may take 4 hours. Is this delay something that will occur in the productin environment as well?
I am working on a project for a limited roll out of DocuSign. Currently I am trying to satisfy a user case that sends the document back to the creator to "hold" until the right time to pass onto a VP. I can make this happen via adding the sender into the flow with the action of "Acknowledge."
However, opening the file once it's come back at that stage is enough to trigger it to move on. That's not a positive enough action -- there is a concern the document might be sent on by mistake. Is there a way to require my creator to do something aside from JUST opening it (although they have no place to sign), so that they can perhaps peek at the document to make sure it's what they think it is, without triggering it on to the next step?
My other solution is to break it down into separate workflows; they can always take a document that was reviewed by legal ops and signed off on and forward in a new envelope to the next recipient, but that's not as slick as just setting the whole workflow up at once and building in the hold.
One of my users has an envelope with a wrong email address for one of the signers. Is there a way to remove the signer so that it shows Complete status instead of In Process without it resending to the other parties? She tried the Correct option last time this happened but it resent the request out to the others and confused them as they had already signed even though the resend box was no checked.
We're a legal company in the UK and our contract needs a set expiry - 6 hours after being sent due to regulations.
Can someone please offer some information on how this can be done? We've looked into preferences and the only expiry is 1 day minimum..
We're a legal company in the UK and our contract is 8 pages long. We've only recently started using DocuSign and our clients have complained about not being able to locate the signature field.
Is there any way to optimise this so the client can find the signature field easily instead of having to scroll down 8 pages?
Perhaps adding the document as an attachment and signature field in the body of the email or something similar?
Any answers will be appreciated! Thank you.
I see the radio Button Tag descriobed in the documentaiton, but it is not liste din our list of tags we can add. Is it still available? Is it only available at a higher level plan that the basic one? If so, where can i see a complete list of all tags and which level planyou must be on to use each tag?
Has anyone else experienced Docusign emails looking terrible in Gmail? This happens for all emails - what the signer receives to sign, viewed/signed notifications, etc. They are all text (even if you accept images) and the spacing is huge. The emails look very unprofessional. In Apple Mail they look great. Why do they look so bad in Gmail??
We require some attachments to complete our envelop. We are running into an issue when a signer tries to use the Fax option to complete the envelope, but then uses an eFax system. Typically this happens when the signer is not the person sending in the compliance documents (CEO signs, an assistant will be sending in the attachments). While the DocuSign fax cover sheet is being included as part of the send, it is typical with an eFax that is sent through Outlook (and other systems I am sure) that the first page of the 'fax' is a standard cover sheet that Outlook creates for the fax. Meaning the DocuSign fax cover sheet is actually the second page of the 'fax' instead of the first page (as it would be if sent from a regular fax). I do not believe that is a function that can be overridden through Outlook. And of course the DocuSign system needs that bar code to be the first page in order to accept the attachments and attach to the envelope. I am stumped on anyway to get around that general cover page created by default from the eFax. Any work arounds that people have used? Educating the signer to attach the documents during the signing process is the only method that comes to my mind.
I am trying to bulk send and I am getting an error with my CSV file. The error is displayed below.
What is the retry frequency for an account that has Connect enabled and the "Require Acknowledgement" setting turned on, assuming that the endpoint on our side does not reply with a successful acknowledgement each time it is hit?
We've recently begun using Docusign and have seen a rather high number of customers fail authentication using the RSA method, 12%. Is this typical for other users, if not what are your experiences using the ID Check option?
We have enterprise account and we are using it to send envelope signing requests via email to our users. Currently it shows "From" in email as "XYZ Ltd via DocuSign". As we have multiple brand profiles, I want this "From" to be displayed as per brand(like "LineOfBusiness1 via DocuSign") - Using same integrator key though. Is it possible to do so? If yes, how?
I am a realtor & on some of our forms, there is a field that we need to complete that states where the location was that the document was signed. I have clients that are mobile (long haul truckers) who complete the documents on the road & I do not see a way to create a custom tag to insert so this would indicate the location signed. I have the date & time figured out but having this field would be great. Thank You!
Is there any way for a CarbonCopy person to see the document before it's signed? We have sales people we're sending orders to besides the customer and we're trying to see if they're viewing the docs before the customer signs them.
I was having issues with the validation of signatures on the signed pdf downloaded via the DocuSign API, which led me to the following post:
I haven't tried this yet. But I noticed that the pdf downloaded from the DocuSign Viewer does not have this issue. So, I checked into the certificates in the two pdfs. And I found this:
Certificate in the PDF downloaded via DocuSignAPI:
VeriSign Class 3 Public Primary Certification Authority - G5
VeriSign Class 3 Extended Validation SSL
Certificate in the PDF that is downloaded from DocuSign Viewer:
Adobe Root CA
Entrust CA for Adobe
DocuSign, Inc. <email@example.com>
These pdfs belong to the same Envelope. Any explanations on why these are different would be highly appreciated.
Thank you in advance.
Please see the below code snippet, I am trying to send acknowledge receipt to some recipients, but not getting succeeded. Also looked in your community & guide for REST API, but did not find anything related to this tag “acknowledge receipt”. Can you please help me out with suitable format for this tag & how to use it. I already have DocuSign Dev account.
string envDef = "<envelopeDefinition xmlns=\'" + strEnvDefUrl + "'>" +
"<emailBlurb>This comes from C#</emailBlurb>" +
"<emailSubject>From Code Behind - API Call for adding signature request to document and sending</emailSubject>" +
// add document(s)
"<name>" + strfileName + "</name>" +
// add recipient(s)