User Manual

Operating Reference
Alarms
3
A6V10415471_en_a_40 225 | 352
No ACK, No Reset ● Event handling started (and at least
one event-handling command sent)
or not started yet (and no command
sent yet)
● Event source back to Quiet
Waiting for
condition
Ready to be closed
Closed
Optional ACK, No Reset ● Event handling started (and at least
one event-handling command sent)
● Event source back to Quiet
Unprocessed
Waiting for
condition
Ready to be closed
Closed
● Event handling not started yet (and
no event-handling command sent
yet)
● Event source back to Quiet
Unprocessed
Ready to be closed
Closed
3.3.10 Event Sorting
● If there are no arrows in any of the column headers, it means the default Event
List sorting is applied.
● In some Client Profiles:
– A small up or down arrow in one of the column headers in Event List
indicates that a non-default sorting order was applied. For instructions, see
Changing the Sorting of Events [➙ 62].
– In the case of recurring events [➙ 225], the sorting only applies to the
parent event. Any individual recurrences of an event are always sorted by
date and time in ascending order, under the parent, and you cannot change
this order.
3.3.11 Recurring Events
A recurring event occurs when the same event source repeatedly generates the
same condition. More specifically, this happens when the same property of a field
point continuously switches between the active and quiet states. For instructions,
see Handling Recurrences of an Event [➙ 56].
If allowed by the Client Profile, in Event List, recurring events are grouped together
under a parent event, which acts as a container for them. The parent event has a
Counter field in its event descriptor that indicates the total number of occurrences.
This counter automatically increments whenever the same event recurs.
Information Contained in the Parent Recurrent Event
The parent event descriptor always displays the most recent recurrence of the
event, (which also corresponds with the topmost recurrence of the set), along with
the following summary information:
● Event Status of the most important recurrence (priority order is Unprocessed,
Waiting for condition, then Ready to be closed)
● Source Status of the most recent recurrence
● ID of the event identified by [...] indicating the range between the first and the
last recurrence (for example, 3201…3245)
● Counter indicating the total number of times this event has recurred.
Children of a Recurring Event
You can expand a recurring event by clicking its Counter field. The children of a
recurring event display under the parent event. The children are always sorted by
date and time in ascending order, irrespective of what sorting [➙ 225] is applied to
Event List.