GMT in Evidence Summary

Hi Kim,

May I have the package ID of this transaction?

In general, the time zone displayed in the Evidence Summary follows your PACKAGE LEVEL time zone setting. (Versus signer level time zone, because the Evidence Summary is per transaction basis) So you can have a quck self check by hitting GET /api/packages/{packageId} endpoint, and find the "timezoneId" directly under the root JSON, which represents your package time zone.

Duo

Hi Duo, 

The below is the code to set the time zone when we create the package. If we apply this, the time zone of the package is changed, but the evidence summary continues to be GMT. Is there something wrong with our setup? We are using .NET SDK.

result = PackageBuilder.NewPackageNamed(_PackageName)

                     .WithSettings(DocumentPackageSettingsBuilder.NewDocumentPackageSettings()

                          .WithoutInPerson()

                          .WithOptOutReason("Information in the package is inaccurate.")

                          .WithOptOutReason("I don't want to receive eSignature Packages.")

                          .WithoutDocumentToolbarDownloadButton()

                          .WithCeremonyLayoutSettings(CeremonyLayoutSettingsBuilder.NewCeremonyLayoutSettings()

                                .WithoutSessionBar()

                                .WithoutGlobalNavigation()

                                .WithoutBreadCrumbs()

                                .WithTitle()

                                .WithProgressBar()

                                .WithNavigator()

                                .WithGlobalDownloadButton()

                                .WithGlobalConfirmButton()

                                )

                          )

                    .WithAttributes(new DocumentPackageAttributesBuilder().WithAttribute("Calyx ID", _LoanGuid).Build())

                    .WithTimezoneId("PST")

                     .ExpiresOn(DateTime.Now.AddDays(_ExpireDay))

                     .DescribedAs("package")

                     .Build();

Hi Kim,

Can you share an example package ID so that I can help you check in the backoffice?

Duo

Thank you for your help, but we found out the cause of the problem. The time zone ID we have did not match the OneSpan time zone ID.

The highlighted item does not match. Can you let me know the time zone ID of OneSpan? I couldn't find those IDs at the OneSpan Site. 

Thanks,

Melissa. 

Hi Melissa,

I see. I've attached two files, one matches the timezone abbreviation to its UI label in OneSpan Sign system, the other one matches the UI label to its OneSpan Sign timezone ID.

In your specific case, I believe MST and AST are supported, AKDT while not AKST is supported (I believe AKDT would automatically be printed as AKST after the daylight saving time ends), HDT and CHST are not yet supported. You could consider to use similar timezone or the one with the same offset, and if it doesn't fit your requirement, please report it to support team ([email protected]) for further clarification.

Duo