Fully adopt local time zone support across all Domains/Applications
While building operations utilizes time zones in the city table to insert the relative time instead of absolute (typically GMT), this support is limited to only Operations. Customers often complain that their times are off by a few hours, or sometimes off by a day, because the times are stored based on server time, and not on the user's location time.
So for example, a move request entered today might show in the system as being entered tomorrow if the server time is sufficiently ahead of local time.
As more and more clients are global and utilizing a single instance across multiple time zones, this can become very confusing to sort out.
Mike Garabedian
shared this idea
-
Jim L.
commented
Greetings Eptura - we have a customer that is asking if this User Voice update for local timezones is included in 2022.02 for Correct and Preventive Maintenance?
They are seeing all their work requests come through in database server time, not the timezone that the work is to be performed in. I have looked for updates in the Help portal, but I have not been able to identify how this update was rolled out back in 2021. Thanks for your help with this matter. -
Priti
commented
Hi Fred, Has this issue been resolved for the workplace services catalog? A client is using Workplace Service Catalog / Workplace Booking in version V25.3 and we are seeing this issue as it pertains to the email notifications that are sent to the user for the booking confirmation.
-
Steven.Post@am.jll.com
commented
The fully adopt local time zone support across all Domains/Application request includes Hoteling and Reservations, the morning and afternoon booking times should respect the user's local time, also respectful of the city table time zone. This should also be invoked as it relates to the check-in reminder e-mail notifications and cancellations.