Is there a way I can control which timezone to use when a signer signs the Document and the DateSignTab is auto-populated? I'm running tests signing from my computer, and the first signature is using EST while the second is using PST.
Thanks!
This can only be controlled by the recipient, if they have a DocuSign account, in their preferences they can select their timezone option. If the recipient does not yet have a DocuSign account - this will default to the account's timezone.
Related
I am a signer and sender of a document. The time zone configured under Regional Settings in Admin and My Preferences is Mountain Time but the time zone from the event notification is Pacific Time with an offset of -7 (Mountain Time).
The documentation states:
Date Signed field: The time zone and date/time format information shown in >Date fields and form data in the signing user interface and PDF documents >depends on the signer:
If the signer has a DocuSign account, then the signer's time zone and the >sender's date/time format settings are used for the information. If the >sender’s account does not allow users to set their own date/time format, then >the date/time format setting for the account is used. Note: By Default, all >signer accounts are set to a default of PST for the time zone.
There is no 'time zone' under Signing Settings.
Expecting <TimeZone>Mountain Standard Time</TimeZone> but receiving <TimeZone>Pacific Standard Time</TimeZone>
EDIT: As a separate but related question: Is the time zone shown in the event notification the time zone specified in the account settings? This post says it is Completed event notification - date time zone but that is 2 years old now so just wanted to be sure.
The DocuSign Connect timezone passed is a legacy setting and in order to change it you'll need to contact the DocuSign Developer Support. Thanks.
createSender creates a URL, which I would like to use to let the sender preview the document before it's send out. Hence the documents are created using templates and and the API.
The link which is created would lead me out of my UI. Does the user need to sign in? Future plan is to have many user's, which have no DocuSign account.
For embedded sending Your app will have to authenticate the user. If you are doing a Service Integration then your Api account will be used as the sender.
Once the sending url is generated using the createSenderView api, there is no authentication required to access the URL.
You also have an option to build a User Application using the docusign Api where your App can support sending from multiple accounts.
The createSenderView requires that the person is a DocuSign user (with their own account and password).
Only DocuSign users can send. We charge for sending, not for signing or receiving.
What exactly do you want to preview? (And why?)
the documents themselves? Use the EnvelopeDocuments resource. You can also preview the thumbnails of the documents.
the documents with the "fields" ("tabs") that indicate where people will sign? I'm not sure that is do-able.
or the recipients and their routing order? Use EnvelopeRecipients: list method.
Added
Another solution is to use a dummy certified delivery "recipient". Add this recipient as the first recipient. This will block the envelope from proceeding on the recipient routing.
Then get the envelope's documents to show as a preview.
Then, if ok, alter the envelope's recipients to remove the certified delivery recipient. The envelope will then continue on with the first "real" recipient.
For webhook event notifications, the completed event in particular, will the delivered and signed dates always be in PST or will they vary based on the server the user's base url points at or their account? I don't see that mentioned anywhere in documentation and it's impossible to tell from a demo account.
Of note:
1) We are not using Connect, just redirect url(s) on our integrator key that are added to envelope definition's envelope notification properties.
2) We are supporting multiple clients, each with their own DocuSign account.
The dates in the event notification will be in the Timezone that is set in your account settings. This will be applicable to all the envelopes sent from your account.
You can go to the Docusign Admin page and manage your account settings.
See this answer for more information.
EDIT:
You can set the property includeTimeZone in your eventNotification. The envelope’s time zone information will then be included in the webhook messages.
I am using the DocuSign REST API via the DocuSign.eSign library on Nuget.
I am able to create and send an envelope via the rest API sandbox, and it all works except the SignedDate tab which is always in US date format.
I have set the Admin account I use to send the requests to UK format dates, but when the envelope is opened on DocuSign by a recipient the date is always in US format.
I also tried setting the language of the recipient to en_GB to see if that would work. Anyone else had this issue?
The only way to set the format of the DocuSign dateSigned tab is through the admin console. Please ensure that you are creating an envelope for the same account in which you are also updating the format in the admin console.
Further to Luis' answer, it's worth noting that the format for 'dateSigned' tab is stored separately to the sender's date preference, and from the account's Regional Settings.
The dateSigned formatting settings can be found in Admin > Signing and Sending > Signing Settings.
I'm using the DocuSign REST API (from a developer demo account) to send a document to an e-mail address that already has a DocuSign account (free account). The user gets the DocuSign notification in their e-mail but not in their DocuSign web interface .........Am I doing something wrong ? Is there a specific API that I have to use so that the documents go into the users' DocuSign web interface ( if the user has an account associated with the e-mail address ).
Cheers !
My request is the following:
--b2cb90e7^M
Content-Type: application/json^M
Content-Disposition: form-data^M
^M
{"status":"sent","emailBlurb":"Please review and sign this report.","emailSubject":"Patient Report","documents":[{"documentId":"1","name":"TEST006.pdf"}],"recipients":{"signers":[{"recipientId":1,"name":"Some Name","email":"somename#company.com","tabs":{"signHereTabs":[{"xPosition":42,"yPosition":42,"documentId":1,"pageNumber":1}]}},{"recipientId":2,"name":"Some Name","email":"some.name#gmail.com","tabs":{"signHereTabs":[{"xPosition":42,"yPosition":42,"documentId":1,"pageNumber":1}]}}]}}^M
--b2cb90e7^M
Content-Type: application/pdf^M
Content-Disposition: file; filename="TEST006.pdf"; documentId=1^M
^M
etc.
Do I understand correctly that your scenario is as follows?
The Envelope is being created/sent via API in the DocuSign Demo environment (http://demo.docusign.net).
The DocuSign account owned by the recipient of the Envelope is a "Free Trial" account. (It's a "Free Trial" account if it's accessed via either http://www.docusign.net or http://na2.docusign.net -- this is the DocuSign Production environment.)
If that's your scenario, then the reason that the Envelope's never showing up in the recipient's DocuSign Inbox (within their "Free Trial" account) is because an Envelope that's sent from the DocuSign Demo environment will never be delivered to a DocuSign user's Inbox in the DocuSign Production environment -- and "Free Trial" accounts technically reside in the DocuSign Production environment.
If you want to test the scenario of sending an Envelope via API in the Demo environment and have it arrive in a user's DocuSign Inbox, then that user account will need to exist in the DocuSign Demo environment as well. You can either add that user as a new user within the same account that you're API calls are using, or create that user under an altogether separate DocuSign account by simply creating another "DocuSign Developer account" via the DocuSign Dev Center.