Hi

We'd like to use 'Evaluate schedule' within Architect to check against 'Meeting' schedule and provide appropriate call treatment within call flows.
I've tested the "Schedule Evaluation Settings" and found that the 'DateUTC' is not exactly the UTC time but "Brisbane" time for our AU purecloud instance.

On the other hand, the 'Schedule' in PureCloud Admin page doesn't have a timezone setting, only 'Schedule Group' does.
The client is based in NZ so to work around this odd checking logic along with the mandatory timezone setting in "Schedule Evaluation Settings" we just used expression to offset the DateTime.

DateTime(UTC)
Expression: AddHours(GetCurrentDateTimeUtc(),-10)
Timezone: Pacific/Auckland (+13)

The only concern for this setup is daylight saving. We do not know if the system will adapt to daylight saving with this particular action. If it doesn't that it will be very tedious to update the offset for every single flow. (The next daylight saving is in April and we can't afford to redesign all the flows)

Has anyone come across this type of requirement here? Appreciate any ideas.

Thanks,
MJ
#Implementation
#Routing(ACD/IVR)

------------------------------
Mei Jane Lim
Datacom Connect Limited
------------------------------

HI there

How did you get on with this?  Looking at something similar at the moment related to timezones.

------------------------------
Vaun McCarthy
NTT New Zealand Limited
------------------------------

Original Message:
Sent: 02-20-2020 01:12
From: Mei Jane Lim
Subject: Evaluate Schedule action - timezone

Hi

We'd like to use 'Evaluate schedule' within Architect to check against 'Meeting' schedule and provide appropriate call treatment within call flows.
I've tested the "Schedule Evaluation Settings" and found that the 'DateUTC' is not exactly the UTC time but "Brisbane" time for our AU purecloud instance.

On the other hand, the 'Schedule' in PureCloud Admin page doesn't have a timezone setting, only 'Schedule Group' does.
The client is based in NZ so to work around this odd checking logic along with the mandatory timezone setting in "Schedule Evaluation Settings" we just used expression to offset the DateTime.

DateTime(UTC)
Expression: AddHours(GetCurrentDateTimeUtc(),-10)
Timezone: Pacific/Auckland (+13)

The only concern for this setup is daylight saving. We do not know if the system will adapt to daylight saving with this particular action. If it doesn't that it will be very tedious to update the offset for every single flow. (The next daylight saving is in April and we can't afford to redesign all the flows)

Has anyone come across this type of requirement here? Appreciate any ideas.

Thanks,
MJ
#Implementation
#Routing(ACD/IVR)

------------------------------
Mei Jane Lim
Datacom Connect Limited
------------------------------

The issue only happens on our dev instance. When running on a production instance, selecting 'current' UTC along with the right timezone works as expected. We never got to the bottom of the problem with our dev instance though.

------------------------------
Mei Jane Lim
Datacom Connect Limited
------------------------------

Original Message:
Sent: 07-08-2020 01:52
From: Vaun McCarthy
Subject: Evaluate Schedule action - timezone

HI there

How did you get on with this?  Looking at something similar at the moment related to timezones.

------------------------------
Vaun McCarthy
NTT New Zealand Limited

Original Message:
Sent: 02-20-2020 01:12
From: Mei Jane Lim
Subject: Evaluate Schedule action - timezone

Hi

We'd like to use 'Evaluate schedule' within Architect to check against 'Meeting' schedule and provide appropriate call treatment within call flows.
I've tested the "Schedule Evaluation Settings" and found that the 'DateUTC' is not exactly the UTC time but "Brisbane" time for our AU purecloud instance.

On the other hand, the 'Schedule' in PureCloud Admin page doesn't have a timezone setting, only 'Schedule Group' does.
The client is based in NZ so to work around this odd checking logic along with the mandatory timezone setting in "Schedule Evaluation Settings" we just used expression to offset the DateTime.

DateTime(UTC)
Expression: AddHours(GetCurrentDateTimeUtc(),-10)
Timezone: Pacific/Auckland (+13)

The only concern for this setup is daylight saving. We do not know if the system will adapt to daylight saving with this particular action. If it doesn't that it will be very tedious to update the offset for every single flow. (The next daylight saving is in April and we can't afford to redesign all the flows)

Has anyone come across this type of requirement here? Appreciate any ideas.

Thanks,
MJ
#Implementation
#Routing(ACD/IVR)

------------------------------
Mei Jane Lim
Datacom Connect Limited
------------------------------