Time event rules, Time event specification requirements – Visara Master Console Center Administration Guide User Manual
Page 158
Visara Master Console Center
158
© Visara International 2007
Time Event Rules
Time event rules are modified or created from the Time Event rule window.
From this window, it is possible to:
Modify time events.
Modify time event actions.
Time Event Specification Requirements
To specify time events properly, follow these rules:
The start time and end time, if entered, must be in a valid format according
to a 24 hour clock. Midnight is entered as “00:00”, not “24:00”. If both start time
and end time are entered, the end time must be later than the start time.
Events that are run by a certain number of seconds, minutes, or hours cannot
continue past midnight. This is because the start time on the next day might not
match the next time the event is to be run, and the MCC system cannot resolve
this ambiguity. For example, if an event is repeated every 5 hours starting at
3:00
A
.
M
., it runs at 3:00
A
.
M
., 8:00
A
.
M
., 1:00
P
.
M
., 6:00
P
.
M
., and 11:00
P
.
M
. The
next time to run the event would either be at 3:00
A
.
M
., because of the start time
specified for the rule, or 4:00
A
.
M
., which is five hours after the last run time.
Therefore, the latest possible end time for an event is 11:59
P
.
M
.
The start date and end date, if entered, must be valid according to the locale’s
date format.
At least one day of the week must be selected to run an event. In addition, if
an event is specified to run on a weekly basis, that particular day of the week
must be selected. For example, if the start date is 7 February 2007 (a
Wednesday) and the event will be run every two weeks, the checkbox for
Wednesday must be selected.
If an event is run every n days (where n is not a multiple of 7) or by any
number of months, all days of the week must be selected. For example, if an
event is started on a Monday and run every two days, it runs on Monday,
Wednesday, Friday, then Sunday, Tuesday, Thursday, and Saturday of next
week. All these days must be checked.
If an event is being run on the 29
th
, 30
th
, or 31
st
of the month, that event will
be run on the 1
st
of the next month in months that do not have those days. For
example, if a start date of January 31 is specified along with a repeat interval of
1 month, the task runs on January 31, March 1, March 31, May 1, May 31, and
so on.