Go to documentation repository
...
| Section | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
To start handle an event processing, do the following:
The event gets the AcknowledgeAcknowledged status, and the first element is displayed in the event processing handling interface. After processing you handle each element, the next element will be is displayed. The last element will is always be the button.
There are seven different types of elements available:
Comment.
To continue the event processinghandling, enter a comment and click the Send button. The name of the button is set by the user (see . For more details, see Configuring the button).
| Info | ||
|---|---|---|
| ||
Depending on the incident manager settings, the comment can be filled in automatically and blocked protected from editing. For more details, see Configuring the comment. |
Image.
To continue the event processinghandling, add an image and click the button. The text on the button depends on the administrator settings (see Configuring the image). In the example below, it is the Next button.
The options of working with an element:
The element already displays the image specified by the settings, or the image from the camera or the map associated with the event. The event can be associated with several cameras, ; hence, when the event occurs, the images are generated from each associated camera, and you must select one of them. To do this, use the following buttons:
To update the image, click the + button (1). As a result, the image from the camera or the map will be is added at the moment when the event occurs. The button is applicable, for example, if the image has been deleted or it must needs to be updated.
To delete an image, click the - button (2).
To scroll images, use the < and > buttons (5, 6).
The field (3) displays the number of the selected image, and the field (4) displays the total number of image options. To go to a specific image, enter its number in the field (3).
| Info | ||
|---|---|---|
| ||
The event with the Acknowledged status is available for processing handling only for the operator who took it. To release the event without processinghandling, right-click the event and select Release: |
After you complete all stages, the event processing handling interface will closecloses, and, if it was specified in the logic settings, a report indicating the actions and the user who performed them will be is displayed (see Interim report).
...
...
If the operator goes to process handle another event without completing the processing handling of the current one, the event gets the Suspended status, and the processing handling elements become inactive. In this case, the event is unavailable for processing handling by other operators.
The operator can independently suspend the event processing handling if the appropriate permissions rights are given given (see Configuring user rights in Incident manager). To do this, right-click the event and select Suspend:
To continue processing handling the suspended event, right-click the event in the table again and select Acknowledge.
In the settings, you can set the ability to escalate an transfer the event for processing handling to another operator of the system—escalation (see Configuring user rights in Incident manager).
To escalate manually, do the following:
Click Escalate, and select to whom in the drop-down list:
All—escalation for to all users, that is, any user can take handle the escalated event into processing.
Specific user from the list—the escalated event is assigned to the selected user.
If you don't set the option to see and work with the escalated events in the settings (see Configuring user rights in Incident manager), after escalation, the event will disappear disappears from the list and will be is displayed for another operator with the Escalated/<Last name of the operator who escalated it> status. In this case, the event will be is in the state as it was at the time of escalation: if the operator started processinghandling it, the event will be is at the unfinished stage.
Additionally, you can automatically escalate events after the specified time (see Selecting events to display and handle). In this case, the automatically escalated event will become becomes unavailable for processing handling by the current operator and will be is displayed with the Escalated/Waiting for processinghandling status.
...
...
Handling of event groups Event group processing is possible if it is enabled in in the Configuring the events event grouping in Incident incident manager. Possible options:
If the operator processes handles an event from a group, all events of this group will be blocked are locked for other operators, and new events of a the group will automatically change their status. In other words, all events of the selected group, including incoming new events, will be are available for processing handling only to one operator until they process handle all events of a group. Other operators cannot process handle events from this group: if they try to process handle an event from this group, the message message Group is locked is blocked will be displayed.
| Info | ||
|---|---|---|
| ||
If the operator took handles one event from a group into processing and released releases it without processinghandling, the blocked locked events of a group are released again for other operators. |
The color of the group name can also be changed at the group processingchange during group handling, see Grouping eventsEvent grouping.
...
...
If you set the ability to close events without processing handling in the settings (see Configuring user rights in Incident manager), then two buttons are displayed in the upper right corner of the event table:
| Tip |
|---|
Event statuses are described on the in Event information page. |