Use this data class to define the business days and holidays for an organization. Calendar data instances can be referenced in organization, work queue, and Operator ID data instances, and in service-level agreements.
If your application and business operations depend on business day calculations, be sure to create calendar instances in advance for each future year (and every district, country, or jurisdiction) needed by your application. Business calendar functions such as isBusinessDay() fail with a Java exception when a date more than one year in the future is referenced and no calendar instance is found.
You can associate a calendar with operators (in the Operator ID data instances), organizations, and work queues.
References to calendars identify only the first key part. The system uses a context-determined date as the (starting) second key part.
Administrators maintain calendar data instances. To access calendar instances on your system, select Designer Studio> Org & Security >Tools > Calendars.
The Data-Admin-Calendar class contains calendar data instances. They are part of the Organization category.
When you save a Calendar data instance, if the Associated RuleSet is [none], the system completes this field with a RuleSet from the current application. This association assists with application packaging. You can update the associated RuleSet using the field in the upper right corner of the form. See Identifying parts of rule and data forms.
If there is no RuleSet associated with the data instance (for example, for existing instances not previously associated with a RuleSet), the Associated RuleSet displays [none].