Data Consistency Checking - Metasys - LIT-1201793 - Software Application - Site Management Portal - 12.0.50

Metasys Site Management Portal Help

Brand
Metasys
Product name
Site Management Portal
Document type
User Guide
Document number
LIT-1201793
Version
12.0.50
Revision date
2023-06-02
Language
English

The exception schedule or calendar verifies the existence of exception and calendar dates and that the start date of a date range occurs earlier than the end date for schedules and calendars when:

  • Exception and calendar dates have all four fields defined and do not use wildcards (Month, Day of Month, Year, and Day of Week). For example, if you entered Monday, January 10, 2010, in the Exception Detail or Calendar Entry Detail dialog box, a warning message appears because January 10, 2010, is not a Monday.
  • Exception and calendar dates have Month, Day of Month, and Year defined and use a wildcard for the Day of Week field. For example, if you entered February 29, 2010, and any in the Day of Week field of the Exception Detail or Calendar Entry Detail dialog box, a warning message appears because there is no 29th day in February, 2010.
  • Exception and calendar date ranges have all fields of both the start and end dates defined. For example, if you entered a start date of Tuesday, July 2, 2010, and an end date of Monday, July 6, 2010, in the Exception Detail or Calendar Entry Detail dialog box, a warning message appears because July 2, 2010, is not a Tuesday.
  • Exception and calendar date ranges have Month, Day of Month, and Year defined and use a wildcard for the Day of Week field for both the start and end dates. For example, if you entered a start date of August 27, 2010, and any in the Day of Week field, and an end date of August 6, 2010, and any in the Day of Week field in the Exception Detail or Calendar Entry Detail dialog box, a warning message appears because the end date occurs before the start date.

Because the Schedule can reference Calendars residing in another device, the scheduling feature performs the following calendar reference verification:

If a schedule references a calendar in another device and that device goes offline, the schedule assumes that while the device is offline, the calendar’s Present Value does not change. For example, a schedule residing on NAE1 refers to a calendar residing on NAE2 and the Calendar Object’s Present Value attribute is True; however, if NAE2 is offline at midnight, the schedule assumes the calendar’s Present Value changes to False at midnight. This means that the exception schedule is not active.

If a schedule refers to a calendar and that calendar is deleted, the schedule assumes the Calendar object Present Value is False and the exception schedule is not active.

When the date changes, the daily schedule ends and the Schedule object executes the next day’s regular schedule, exception schedule, or Default Schedule Command.