Grass Valley iControl V.6.02 - Manual (Page 171)

iControl
User Guide
161
Selecting the Faults only contribution causes a sub-alarm to be mapped to NORMAL unless
it’s in one of the fault statuses—usually CRITICAL, MAJOR, and MINOR. The list of fault
statuses can be modified by using the
setFaultSeverities( ) property. See the GSM
Scripting Manual for details.
6. Type a name for the new incident template in the Name field.
7. Type a path for the new incident template in the Path field. The path defines where the
overall alarm for the template will appear in the GSM Alarm Browser hierarchy. If you leave
this field blank, the overall alarm will appear in the Virtual alarms folder.
Tip: Click on a folder in the GSM Alarm Browser, and then click Use selected folder to copy
its path to the Path field. You can then edit the path text, if needed.
8. Click OK.
In a few moments, the new template appears in the Incident Templates window. If it does
not appear, click Refresh.
Modifying an Incident Log Template
To modify an incident log template
1. In Incident Log Viewer, on the File menu, click Incident templates.
The Incident Templates window appears.
2. Select the incident template you wish to modify.
3. Click Edit.
The Incident template configuration window appears.
NON-EXISTENT NON-EXISTENT
PENDING PENDING
DISABLED DISABLED
UNKNOWN UNKNOWN
Note: If the sub-alarm’s fault condition is cleared, its contribution will always be
green, unless the value specified in the Contribution column is black.
Note: For a given incident template, there can only be one incident open at a time.
Once the open incident is cleared, the template can be triggered at any time by a
subsequent alarm, whereupon a new incident (with a new ID) will be opened.
REQUIREMENT
Before beginning this procedure, make sure you have opened Incident Log Viewer
(see
page 569 ).
(Continued)
Sub-alarm Status Inverted Contribution