You are viewing limited content. For full access, please sign in.

Question

Question

How does Laserfiche Cloud know what time zone you are in?

asked on November 11, 2022

Is it looking at your computer clock settings through the browser somehow?

0 0

Replies

replied on November 15, 2022 Show version history

For this specific case, we can file a bug to Forms about an action showing different times to users with the same regional settings.

But since you asked "how", the answer is longer. First, it's important to note that there isn't a single method, so it's good that you clarified where you were seeing the inconsistencies. Modern browsers now have an API where they make that information available. But you can see that many of the applications in Laserfiche Cloud began their lives before that API existed, and so may have used other strategies, such as making inferences based on `Date.getTimezoneOffset()`. That's even assuming that the application needs to "know" the timezone. If the Javascript environment provides a way to format Dates as Strings - which it does - then you could argue that an application that uses that API can convert times without really "knowing" or "detecting" the timezone.

That begins to get to whether datetimes are being formatted on the client side or the server side. Of course the user shouldn't care, and the results should always be correct. But sometimes one way is preferable to the other, and so one part of the application suite can appear correct and another part appear incorrect.

Currently, the situation in Laserfiche Cloud is a little fragmented. We have work underway for a unified account settings page, where users and administrators can set their preferred timezone and language. This will help the situation where a user would prefer time values to be presented in a timezone other than the one they are in; for instance a remote worker might choose to use the company's official timezone so that they see the same values as their coworkers.

2 0
replied on January 6, 2023

Hi Brian,

Thanks for the detailed response. We have a similar issue which I'm assuming is related to the above but just wanted to confirm.

When signing in as a "standard" user (i.e. that doesn't have access to process automation admin) we're seeing that in the repository all times are showing in the correct time zone (UTC+0). However in the forms tasks, all times are showing as UTC-8 (e.g. in the task inbox, action history).

When signing in as a user who has access to process automation admin you're asked to choose your time zone the first time you open process automation. When you've done this it appears that the times appear in the correct time zone across both process automation admin and the standard forms task area (and the repository which was already correct).

The default work schedule and work schedule set on the process in question are both set to use the UTC+0 time zone.

Obviously most users won't have access to the process automation area to set this, but I assume this is why you're looking to implement a time zone option on the user accounts? If that's the case do you have any estimates on when this is likely to be implemented please?

Cheers!

Dan

1 0
replied on January 6, 2023

I see Kawana (below) mentioned they're seeing PST - we're seeing UTC-8 (PST).

0 0
replied on January 10, 2023

Yes, this is the bug Brian mentioned above. The inbox for business processes gets its timezone from the user's Process Automation settings instead of the browser. But a "standard" user does not have access to the user interface where Process Automation time zone settings are.

2 0
replied on January 10, 2023

Thanks Miruna, Mark (above) is interested in testing the pre-release when it is available please. We're his Solution Provider - is there something we need to do to sign them up?

1 0
replied on January 10, 2023

We'll contact you and him when when this feature is ready for external testing.

1 0
replied on January 10, 2023

Thank you yes

0 0
replied on May 12, 2023

Hi Miruna,

 

Do you have a release date for this yet?

 

Thanks, Mark.

0 0
replied on November 11, 2022

For end users, I'm 95% sure we're getting it through the browser either by using the native JavaScript Date object (or similarly related objects/properties) or through the Moment.js wrapper.

For Process Automation, you can Specify the Time Zone.

Why do you ask?

0 0
replied on November 12, 2022

When users compare tasks in the Action Pane of forms, it is not matching up, it is exactly whole hours difference, like they are looking at a different time zone. Yet all the users live in the same state and in the same time zone. I have a support ticket open for it but they are asking for screenshot demonstrating the issue, I am not sure what to compare the screenshot with, should it be with the computer clock along side the action pane to show it is not reading it correctly?

If the script fails to access the clock, does it default to a specific time zone?

0 0
replied on November 14, 2022

Forms task time zone is set by Process Automation, you can Specify the Time Zone. (as Samuel Carson mentioned above.)

0 0
replied on November 14, 2022

But the problem is that 2 users who look at the same event, in the same process, see it happening at different times.

 

Same process, logged in under another account

 

 

So did the process complete at 5:53 or 7:53? Their work schedule can only have 1 time zone, how can 2 users see that something took place at a different time.

1 0
replied on November 14, 2022

How fast, relative to each other, were they moving when they saw the time?

0 0
replied on November 14, 2022

This website makes the same browser calls that Laserfiche likely does. My understanding is that (unless overridden), the browser gets the time from the computer clock, and web applications get the time from the browser via JavaScript.

I'd take a screenshot of that site side-by-side with Forms with the local system clock also showing. The browser time site should match the local system clock. If it doesn't (and matches what Forms shows instead), that's likely where the issue lies.

I'm not sure how the script could "fail to access" the browser clock unless the organization's IT is running their own browser scripts that categorically block access to the JavaScript Date object. 

0 0
replied on December 22, 2022

We are experiencing the same issue because our time is showing in PST and we are EST.  Will there be a global setting added where admins can set the time in a particular time zone, so the setting can apply to all submissions?

1 0
replied on January 6, 2023

Yes, we are working on adding account-level language, locale and time zone settings. An administrator will be able to set up an account-level default, users will be able to customize their own settings.

Initially, the settings will apply to "user"-level functionality like the repository, settings pages or the business process inbox. Process designers will be covered in a later phase.

We're looking at a release at some point in the next 3 months or so and we'll be offering early access opportunities for users interested in testing the feature ahead of its release. Post here or message me if you're interested in participating.

1 0
replied on January 9, 2023

Yes please.

0 0
replied on February 22, 2023

i would like to test this as well please we have the same issue.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.