What's new in Mission Control 3.2.0.0 - Mission Control 3.2.0.0 | Mission Control Web API 2.10

Genetec Mission Controlâ„¢ Release Notes 3.2.0.0

Product
Mission Control
Content type
Release notes
Version
3.2
Release
3.2.0.0
ft:locale
en-US
Last updated
2025-01-22

Genetec Mission Controlâ„¢ 3.2.0.0 includes the following enhancements.

RabbitMQ compatibility notice

RabbitMQ version 3.12.1 is installed as part of the Mission Control installer depending on your system environment.

For more information, see Installing Mission Control 3.2 .

If you are upgrading RabbitMQ, kindly follow the steps in Upgrading RabbitMQ on the server or Upgrading RabbitMQ.

For more information about how to upgrade your RabbitMQ failover cluster, see the official RabbitMQ Clustering Guide.

General enhancements

Sound looping for incidents
Incidents can now be configured to play a sound on loop until the ownership is taken by an available operator. The sound can be muted manually or when the incident is closed.
Shunt or unshunt device inputs
Choose specific devices to shunt or unshunt based on the incident location or the related entities of the incident.
Workstation management privilege
Administrators can grant users access rights and privileges which can be restricted based on the workstation being used. This privilege will allow them to access partitions when they do not have required privileges.
Trigger an incident using Event-to-action
Configure an incident trigger from an event using the Security Center Event-to-action feature in the Config Tool.
Use Screen IDs to have the same layout on different workstations
Users can configure a screen ID to display a specific configured layout which is assigned to that workstation.
High-priority incidents skip the queue
Incidents which are queued to auto-opened in the Incident monitoring task, will be listed and opened first by the incidents priority and then by incident trigger time. Highest priority incidents with oldest trigger time will be the next to auto-open.

Web API enhancements

Mission Control Web API 2.11 includes the following enhancements:
Trigger incidents on non-georeferenced maps
There will be no restrictions on the range of coordinate values for longitude or latitude on non-georeferenced maps.

For technical information about API endpoints and other programming considerations, see the Web API developer documentation.

Important links