Go to documentation repository
The INC_SERVER object corresponds to the Incident server system object.
The INC_SERVER object sends events presented in the table. The procedure is started when the corresponding event occurs.
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. 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:
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 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 UPDATE_STATUS |