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:

1)

when the operator takes the event into processing;

2)

at each step of the event processing.

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:

...

.

You can enable full logging of all event parameters using the registry key inc_server_send_full_event (see Axxon PSIM base version). When inc_server_send_full_event=1:

the serializeBase64 parameter will contain an encoded string with the SourceMsgBase64 field, which contains the encoded event string. This event contains the full_event_base64 parameter with the full parameters of the source event;
if the event is escalated, an additional parameter inc_server_action<escalated> will also be added.

Please note that if you enable full parameter logging, it will increase the size of the event database (by default, Incident server events are stored in the Axxon PSIM database in the PROTOCOL_INC_SERVER table)

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

—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. Parameter values can be specified with a delimiter. This means that one OR the other value will be selected. Example: objids<1\|2>
	objtypes<>	Objects types
	objids<>	Objects identifiers
	actions<>	Actions
	status<>	Event status: 0

— Waiting

—Waiting to be processed

1

— Processing

—Processing

2—Suspended

3—Completed

2 — Suspended

3 — Completed

UPDATE_ESCALATE_STATUS

— change

—change the status of the event (incident) escalation in the Incident manager

escalated<>

Event escalation status:

0

— Waiting

—Waiting to be processed (not escalated)

1 — Escalated

1—Escalated
pks<>, objtypes<>, objids<>, actions<> are the same as for

UPDATE_STATUS

Example 1. On macro 1 change the status of the camera 1 Alarm event to Completed.

Code Block
OnEvent("MACRO","1","RUN") { DoReactStr("INC_SERVER","1","UPDATE_STATUS","status<3>,objtypes<CAM>,objids<1>,actions<MD_START>"); }

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)

...

UPDATE

...

_STATUS

...

Page tree

Versions Compared

Old Version 2

New Version Current

Key