Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

How to customize the Default calendar

Updated on May 2, 2019


Calendar data instances are used to identify business days, the hours of operation on these days, and non-business days. By default Saturday, Sunday, and holidays are considered non-business days.

You can change the initially supplied calendar data instance and create additional calendars.




Calendars support business day calculations in your Process Commander applications. You can add, delete, and update the calendar to reflect your operation's open business days and local holidays.

In V4.2, V.5.1 and V.5.2, the default Calendar name is named Default. The default time zone is Eastern Standard Time.

Follow the steps below to create a new calendar.

Update: In V5.3, the initially supplied calendar is named USDefault, and the time zone is specified as Americas/New_York.


  1. From the Rules By Type Explorer, select Organization > Calendar. A list of instances appears.
  2. From the Toolbar, click the New icon. The New form appears.
  3. Type Default or another identifier in the Calendar Name field.
  4. Type the calendar starting date in the format YYYYMMDD (such as 20080101) and click Create. The following form appears.

  1. Update the time zone if necessary.
  2. Enter the start and end time in 24-hour format HHMMSS for each business day selected. If you leave the start and end times blank, a 24 hour day is assumed. .
  3. Enter a closed date in YYMMDD format, then click the Append a Row icon () for each additional closed day in the calendar you want to add. When done click Save. Below is a sample of a completed calendar.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us