Multiple calendar instance in Pega

General
1

We have a requirement where UI-selected dates should be moved to the next business day if they fall on a weekend or non-business day.

We are using the OOTB functions @isBusinessDay() and @nextBusinessDay() in Pega Platform for this logic.

However, we are facing an issue where our calendar data instance is only available for 2026, and dates from 2027 onwards are not evaluated correctly, leading to failures.

As a workaround, we are considering creating multiple calendar instances for different years (2026, 2027, 2028, etc.).

Is this a recommended approach in Pega?

Also, will maintaining multiple calendars have any impact on SLA processing, batch jobs, or other system functionalities?

What is the best practice for handling future business day calculations in this scenario?

Thanks in advance.

2

Hello @Debanjan_Seth

Yes, for date related operations and/or calculations Pega relies on the Calendar instances. This is clearly evident if you look at parameters list on the functions related to date/day calculations/operations.

Not just functions, other rules and data instances are also tightly coupled with Calendar instances.

You have to maintain one calendar instance per year with a starting date. Ensure that you have an associated ruleset for your calendar instances so that it will be easy for you to deploy them to higher environments.

Hope this helps

Regards

JC

3

Thanks Much appreciated your response.