12.07.2015 Views

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Incident Groups for Tracking• The monitored activities and the message activities are generated withtheir tagged Incident ID as follows:12:02:15 [12:02:16] Input 1 activated [Incident 499712535_2820]12:02:15 Event B activated [Incident 499712535_2820]12:02:15 [12:02:16] Input 1 deactivated [Incident 499712535_2820]12:02:23 Manual action by Smith, Anne: acknowledge Event B [Incident499712535_2820]12:02:16 Event B deactivated [Incident 499712535_2820]12:02:23 Manual action by Smith, Anne: clear Event B [Incident499712535_2820]12:04:25 [12:04:26] Input 1 activated [Incident 499712601_2820]12:04:25 Event B activated [Incident 499712601_2820]NOTEIf you open a closed event from the Monitoring Station Activity or EventMonitor to add a new log message to it, the Review Event dialog boxdisplays the Incident ID for the most recent occurrence of the event,instead of the Incident ID for the event occurrence to which you areadding the message.Example:In the preceding Incident Group Example, if at 12:04:26 you openedthe Event B occurrence activated at 12:02:15 and deactivated at12:02:16 to log an important new message, the Incident ID thatdisplays on the Review Event dialog box—and that will be attachedto the log message—will be Incident 499712601_2820 for the mostrecent occurrence of Event B, instead of Incident 499712535_2820.25–12 C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Software</strong> <strong>Configuration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!