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.
Related
We're using the DocuSign SDK (version 3.5.0) We are developing an integration with DocuSign using JWT authentication.
In regional settings of the account, I have set the value of time zone to Canberra, Melbourne, Sydney.
But, whatever the time zone is, in webhooks, the datetime fields are always in UTC. Also, I have noticed that the other APIs such as (audit trail endpoint) also returns the datetime field in UTC.
Will this be constant or this can be changed by any other methods?
DocuSign's developer support group can update your account's API Timezone to a timezone other than UTC. But:
The API Timezone may not work with the newest JSON Connect webhook notification messages.
If your application is later connected to any additional accounts, then you'd need to have those accounts updated too.
My recommendation is that your software change the timezone for the incoming UTC datetime values. There are library methods for doing this for all languages. (Don't try to write the code by hand, there are some weird corner cases.)
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.
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 am using DocuSign Connect/DocuSign Event Notifications to update DocuSign envelope/recipient statuses. I have written a .net application that parses an XML posted by Connect/Event notifications to update the statuses. Since each of my client's DocuSign account lies in a different time zone, I retrieve time zone of each of my client's DocuSign account from Connect update and my .net application adds offset based upon the time zone to update the statuses.
I need to know all possible values of DocuSign account time zone that I can retrieve from XML posted by Connect/Event notifications as the time zone values in DocuSign account are different than the time zone values that I get from Connect updates.
For example, if the time zone set in the DocuSign account is "Pacific Time(US & Canada)",the time zone that I get from Connect/Event notifications is "Pacific Standard Time".
Is there is a list of all possible values of Time zone that DocuSign Connect process posts?
Connect will use your Time Zone used for API for almost all of the timestamps.
In Features, Set Time Zone used for API:
The correct Time Zone will be used in your Connect XML:
There are very few time entries in Connect that do use UTC and they are identified with a Z.
Example: 2014-07-24T18:09:14.9430000Z
This should be manually converted by your listener to the approperiate time zone.