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