Go to documentation repository
Page History
...
The INC_SERVER object sends events presented in the table. The procedure is started when the corresponding event occurs. The format of the event procedure for the Incident server object:
| Code Block |
|---|
OnEvent("INC_SERVER","_id_","_event_") |
Events | Events description | Comment |
EVENT | The event (incident) is taken into processing in the Incident manager or is being processed by the operator | The event is generated: |
|
The serializeBase64 parameter of the event contains JSON with the detailed information about the processed event, including the steps performed by the operator |
The operator format for describing the actions with the Incident server object:
| Code Block |
|---|
DoReact("INC_SERVER","_id_","_command_" [,"_parameters_"]); |
The list of commands and parameters for the the INC_SERVER object is presented in the table.
| Command—description of the command | Parameters | Parameters description | Comment |
|---|---|---|---|
| UPDATE_STATUS—change the status of the event (incident) in the Incident manager | pks<> | Array of event identifiers | Parameters are filters and the presence of at least one parameter is mandatory. Example: objids<1|2> |
| objtypes<> | Objects types | ||
| objids<> | Objects identifiers | ||
| actions<> | Actions | ||
| status<> | Event status: 0—Waiting to be processed 1—Processing 2—Suspended 3—Completed | ||
| UPDATE_ESCALATE_STATUS—change the status of the event (incident) escalation in the Incident manager | escalated<> | Event escalation status: 0—Waiting to be processed (not escalated) 1—Escalated | |
| pks<>, objtypes<>, objids<>, actions<> are the same as for | |||
Example 1. On macro 1, change the status of the camera 1 Alarm event to Completed.
...
| UPDATE_STATUS |
...
Example 2. On macro 2, on the Incident server 2 change the escalation status of the camera 1 events to Waiting to be processed (not escalated)
...
Overview
Content Tools