You are here: Reference > Data classes > Calendar data instances > Calendar form - Completing the Schedule tab

  Calendar form
Completing the Schedule tab
  1. About 
  2. New 
  3. Schedule 
  4. History 
  5. More... 

Use the Schedule tab to define the schedule of your organization's business days and normal hours.

Caution: Keep the Closed Days complete and up-to-date. Computations for service levels, escalation, urgency, timeliness, due dates, and other properties often depend on correct holiday schedules.

By default, information on this tab supports date and time computations only. Calendar data instances do not affect when users can log in or what they can do when logged in, unless your application implements such constraints.

Field

Description
Standard Time Zone

Select a time zone for this calendar. The system uses this value when comparing the current date and time with scheduled absences for the operator. This value does not affect other standard processing, though you can access it in your application processing.

For example, select America/New York for the United States Eastern Time zone.

These time zone codes follow the Olson TZ database, used in the ICU4J 3.4.4 library and most UNIX systems. Details on the Olson TZ database are available from ftp://elsie.nci.nih.gov/pub.

If another calendar data instance has the same first key part as this calendar name, this field must match the Standard Time Zone value of the other calendar.

Schedule

add row Record the regular weekly work schedule that applies to this calendar.
Business

Select or clear these seven check boxes to indicate the weekdays that are normal business days.
Start

Optional. For each selected weekday, enter the local time that work begins on that weekday. Use the format HHMMSS, with no punctuation. For example, enter 201515 for 15 minutes, 15 seconds after 8 P.M.

These time values are available for the isBusinessTime() and AddTime() standard functions in the Pega-RULES:BusinessCalendar library. They are used in service-level agreement calculations (when based on business days). For example, if an assignment created at 3:15 P.M. has an associated goal of three hours, but the workday is from 9:00 A.M. to 5:00 P.M., the goal time becomes 10:15 on the next workday.
End

Optional. Enter for each weekday that is selected, the local time that work ends on that weekday. Use the format HHMMSS, with no punctuation. Enter a time that is later than the start time.

If you leave both the Start and End fields blank, functions in the BusinessDate library (and service-level agreement calculations based on business days) assume the work day is 24 hours long.
Closed Days

add rowOptional. Enter in this array all dates when your business is closed for holidays or any other reason, other than weekdays not selected.

Use the date format YYYYMMDD. Order is not significant. The system converts your input to a display format (MM DD YYYY).

Up About Calendar data instances

Open topic with navigation