Time zone changes in delegated accounts in Verse

Hi all,

Faced with time zone change in Settings -> Availability in delegated accounts:
1. Harry Lick user with time zone GMT-6:00
2. User Antonio Rossi with time zone GMT+2:00.

User Harry Lick opens user Antonio Rossi's calendar via delegation and just looks at his appointments.
After some time, the user Antonio Rossi updates his mail and sees that in Settings -> Availability his time zone has changed and it is now Harry Lick GMT-6:00.

Why did the time zone change? How to fix it?

Thanks

Hello Moises,

Sorry for the delayed response. May I know which version of Verse you are using with build number.

Please confirm the exact steps to reproduce the issue.

1) Antonio granted delegation access to Harry.

2) Current time zone setting for both users at Verse are as below. Please provide the screenshot if possible.
Harry Lick user with time zone GMT-6:00 (Central)
Antonio Rossi with time zone GMT+2:00 (?)
3) Now Harry opens Antonio's calendar and just looks at his appointment and no changes.

4) After some time, Antonio on his own workstation opens his email via HCL Verse and the go to Verse settings >> Availability time zone, he sees it got changed to GMT-6:00 (Central).

Please confirm if users are using new calendar event form (this is default starting with verse 2.0), but just confirm the value set for "VOP_GK_FEATURE_168" ini on Verse server.

For your awareness, we have launched a new Digital Solutions Community site (https://developer.ds.hcl-software.com/) which includes our new product forums. The content for our legacy product forums will soon be migrated to this new site. If you haven’t yet done so, we encourage you to sign up on the site and engage with the community of experts for our products!

Regards

Aniket

Hi. I have the same problem. I have VOP_GK_FEATURE_168=1 and Verse 3.2.4 .

Hello Aleksandr,
Thank you for your update. I am checking on this. Meantime, please confirm the steps I have mentioned.
Regards
Aniket

Hello Aleksandr and Moises,
I am able to reproduce the issue. I am checking internally on this and update you.
Regards
Aniket

2 Likes

Hello Aleksandr and Moises,
Dev team acknowledged the bug and team is working on this via defect number VERSE-68459.
Regards
Aniket

1 Like