Go to documentation repository
...
Improved the window for adding multiple events to the Incident handler (the Add button on the Incident handler settings panel):
In the Incident manager, it is now possible to set the minimum and maximum height for a comment in the event handling logic
Added the UPDATE_ESCALATE_STATUS command to Incident manager. The command can be used in scripts for escalating the specified events INC_SERVER
It is now possible to use an external database for the Incident Server
In the Incident manager, updated the Last comment and All comments columns: now only the first line of the comment is displayed in them, and the full comment is displayed in the tooltip
Updated the Incident handler: now when you select the events for display and processing, you can select any camera events, not just alarms
...
Added events to the Map (MAP):
ACTIVATE_OBJECT—activation of the object. The event is received when an object is selected (activated by a single mouse click) on the Map and contains the layer parameter—the identifier of the layer on which the event occurred;
OBJDBLCLK—the event is received when you double-click an object on the Map MAP
...
Added a new SCRIPT_ERROR event for the SLAVE object. This event is generated if the script execution fails SLAVE
For the API request for receiving video subsystem events http://IP-address:port/web2/secure/events/ added the ability to specify several objects separated by commas in the objectId parameter, and to receive all triggers from objects of the same type Getting events of video subsystem in blocks
Added the support of the TLS version 1.2 certificate to the Web-Server.
Now Axxon Player generates an AxxonPlayer.lh text file, which contains the log of video archive views via the Player
If Axxon PSIM is installed as a Service, you can now specify the executable file of the program module using the core_module_name keyIn User permissions, added the Allow VMDA filters use option which allows the Operator to use templates
...