CalendarSchedule slots and other notes

The CalendarSchedule has a StatusBoolean input and output (slots “In” and “Out”). In most applications they are left unlinked.

Output is true during any configured calendar day(s), otherwise it is false.
Input overrides the calendar schedule calculation (if linked). Any non-null input (true or false) is immediately passed to the output.

By default, for any CalendarSchedule copied from the schedule palette, the following additional slots are pinned on the component’s glyph (shape on wire sheet):

Next Time

Time of next scheduled output change for the CalendarSchedule. If more than a year away, this value is null.
Next Value

The next scheduled output value, at “Next Time”. Value is meaningless if Next Time is null.

From the CalendarSchedule’s property sheet, you can access and change the following additional slots:

Cleanup Expired Events

Either true (default) or false.
- If true, calendar events of type “Date” and “Date Range” that have already occurred, and cannot occur again (as configured), are automatically deleted after they occur. This is recorded in the schedule log, and you no longer see them in the Calendar Scheduler view.
- If false, all calendar events are retained, even if they cannot occur again (as configured).
Scan Limit

Specifies a limit on how far ahead the schedule searches to find the next event output change, where the default is 90 days, and range is from 1 day (minimum) up. This can prevent excessive CPU usage. If changed, a value less than the default is typically recommended—for example, 14 days.
Facets

Facets applied to the input and output, which by default are simply “true” and “false.”