topic Re: Time Zone Settings in Fusion Manage Forum

Time Zone Settings

Anonymous — Thu, 25 Jun 2015 14:28:37 GMT

Hello

I think it would be good if the time zone settings moved with Brisith Summer Time changes.

The settings for the users on my tennat are all set to GMT, however it's now BST.

This means that the audit trail (change log) is now out of sync.

I thought I could get around it, by manually changing from GMT to BST, however when I tested this with one user, it back-flushed the previous time stamps to make them all BST.

I hope this makes sense.

Thank you

Claire

Re: Time Zone Settings

gasevsm — Fri, 26 Jun 2015 04:19:11 GMT

Greetings, The underlying datetime values didn't change - it is an absolute instance in time. Your timezone setting simply drives how the product represents the date in the product. Eg. If I see that same item in EST we would be looking at the exact same point in time, but from our respective time zones. Hope this helps,

Re: Time Zone Settings

Anonymous — Fri, 26 Jun 2015 07:40:51 GMT

Hi there

Thanks for your speedy response.

I understand what you're saying, unfortunately it is confusing when our
processes are audited.

For example, if a member of staff starts work at 9am, and works on their
item at 9.15 BST (pre the clock changes), and we later review the changes
at a point in time when it's GMT, it will show that they worked on the item
at 8.15am which isn't possible as they wouldn't have been in the workplace.

The change log changes all records to match the user's time zone, even if
they were stamped already.

I hope this makes sense, although I'm not sure there's anything you can do?

Claire Tomlinson
Quality Systems Manager
01482 713864
07770 695456

--

www.willerby.com
Please consider the environment before printing this e-mail.
Confidentiality: This message contains information which may be privileged
or confidential and is intended for the individual(s) or named entity
above. If you are not the intended recipient you must not use, disclose,
copy or distribute the message. If you have receive the message in
error please notify the sender immediately and delete this email from your
system. Any views or opinions presented are solely those of the author and
do not necessarily represent those of the company. Please note that e-mail
is neither secure nor authenticated. Willerby Holiday Homes Ltd does not
accept any responsibility for loss or damage arising in any way from its
receipt, opening or use. Terms and Conditions: This e-mail and any other
arrangements are subject to our terms and conditions of business, a copy is
available upon request.
*Willerby Holiday Homes Ltd, Registered in England No. 387583. Registered
Office: Willerby Holiday Homes, Imperial House, 1251 Hedon Road, HULL, HU9
5NA.*

Re: Time Zone Settings

gasevsm — Sat, 27 Jun 2015 04:10:20 GMT

What you saymakes sense, but the use case seems incorrect. Eg. Based on your request, when the user makes a change just prior the time reverts from GMT back to BST and someone reviews that change after the time shifts, wouldn't they see time as if user made a change in the future time that hasn't happened yet. How would you account for this in your Audit process? Current behavior can be accommodated in audits. Yes it will remain in effect - it would not say 'change made 9:15'; rather it would say 8:15 per your current time zone setting. Please note that the reviewer's is also shifted back by an hour; from that POV, same time elapsed from when change was made when the check was performed, regardless of timezone setting or daylight change. For example, Outlook (and many many other systems) would auto-convert time to match user's timezone setting. Eg. a user sends an email at 9:15a and someone reviews it after entering GMT; they will see email received 8:15a. Vice versa would be equally covered. Another example is when two users are collaborating real-time sitting in different timezones eg EST and GMT. They expect to see that change by one user made a minute ago in one timezone is reflected as such with the viewer in the other timezone. Hope this is clear why the system will continue to behave as it does,

Status changed to: Solution Provided

nguyentru — Mon, 29 Jun 2015 21:51:56 GMT