Additional Information (Shift Building Block)
Keep in mind the following information while working with the shift building block.
For repeating calendar days (PTC.Shift.CalendarDayRepeating Data Shape), note the following:
• The day index (dayIndex) values must start at 0 and increment.
• No gaps are allowed in the day index:
◦ Valid: 0,1,2,3,4,5,6
◦ Invalid: 0,1,2,5,6,7,8
◦ Invalid: 1,2,3,4,5,6,7
• Non-working days for a calendar must specifically be indicated using the nonWorkDay field.
• Within a shift schedule, there can be no repeating day indexes. Each day index value must be unique within a given shift schedule.
Understanding Calendar Exceptions
A calendar exception represents a specified period of time which is an exception to a shift schedule. For example, a calendar exception can be created for a span of hours on a certain day for a company meeting, or for the duration of a holiday.
The DPM solution does not create any shift instances are created for the period of time included in the calendar exception. For more information, see Understanding Shift Instances in the DPM Help Center.
 |
Because shift instances are generated in advance (for "today" and "tomorrow"), calendar exceptions should be created at least 2 days before they are needed.
|
Calendar exceptions can be created by executing the AddCalendarExceptions service from the PTC.ShiftImpl.Manager Thing.