Special events apply to weekly schedules only, and are considered any exception to the (normal) weekly schedule. Special events can be “one-time” only event changes or recurring event changes, such as holidays. Configuration includes both day(s) of occurrence and related time-of-day events.
In the time-of-day event definitions of special events, you can have them “intermingle” with regular weekly events, or completely override the weekly schedule. In addition, you visually prioritize special events, via list order. This allows any overlapping special events to occur in an ordered fashion.
Each weekly schedule component has its own special events, configured on a Special Events tab in its scheduler view. Event times (and values) entered for any special event apply to that schedule only.
If the special event is a “reference” type, days of its occurrence are specified in the CalendarSchedule component that is referenced. This allows you to globally change
the days that special events occur in weekly schedules, by editing one or more referenced CalendarSchedules. For more details,
see CalendarSchedule Usage.
If needed, you can provide different permissions for the special events of a weekly schedule (BooleanSchedule, NumericSchedule, etc.) than for the rest of the schedule’s configuration, using advanced techniques. In early NiagaraAX releases, operator Write access for the schedule was required to have write ability on any of the four tabs in its Weekly Scheduler view (including Special Events).
There is also now automatic “read-only” access to all tabs of the Weekly Scheduler view for a user with only “operator Read” permissions on a schedule. Previously, such a user could
only see the Summary tab.
To configure a schedule to allow special events access separately, you must “unhide” its “CompositeSchedule” slot (named Schedule) working from the schedule component’s slot sheet (Figure 311).
Once the child CompositeSchedule is unhidden, you can expand it in the schedule’s property sheet (Figure 312).
As shown, this “Schedule” slot contains child slots, including a “specialEvents” schedule and a “week” schedule. Now, you can assign the child “specialEvents” CompositeSchedule to a different category that the top-level schedule (right-click the “specialEvents” slot, then choose ).
In this case, you would deselect the “Inherit” option and clear that category, assigning a different category—one that a user could have “operator Write” permissions on, versus only “operator Read” as on the parent schedule component. This would allow such a user to have read access to all the tabs on this schedule’s Weekly Scheduler view, but write access only for managing special events—and not the regular weekly schedule (or other properties).
For related details on security, including permissions and categories, see About Security.