Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Pallavi Gurram (Pallavi Gurram)
PEGA
Fellow Cloud Architect
Pegasystems Inc.
IN
Pallavi Gurram Member since 2015 9 posts
PEGA
Posted: Apr 12, 2016
Last activity: Apr 6, 2018
Posted: 12 Apr 2016 22:44 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

Post Pega 7.2 Upgrade encoutered "** ** Multiple timezones not supported for one calendar" error.

Post Pega 7.2 upgrade, java steps using business calendar api in activities throwing "** ** Multiple timezones not supported for one calendar" error.



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 12 Apr 2016 22:47 EDT
Pallavi Gurram (Pallavi Gurram)
PEGA
Fellow Cloud Architect
Pegasystems Inc.
IN

The above issue will be encountered in case of same calendar rule name exists more than one time with different timezones. Hence we have remove the unused calendar rule.

To see attachments, please log in.
Posted: 8 years ago
Posted: 17 Oct 2016 1:08 EDT
Pallavi Gurram (Pallavi Gurram)
PEGA
Fellow Cloud Architect
Pegasystems Inc.
IN

Hi,

We have identified the unused calendar data instances with same name more than one with different timezones in  Records > Organization > Calendar

We have taken a suggestion from the customer in identifying the right calendar data instance based on their operators.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice