Genetec Mission Control™ 22.214.171.124 includes the following known issues.
|Issue||First reported in||Description|
|2542636||126.96.36.199||Opening an incident in tile view in the Monitoring task displays only the first map even when multiple maps are attached as related entities to the incident.|
|2358890||188.8.131.52||When exporting incidents with aggregated events from Security Desk, the incident export fails if the Export video for aggregated events option is selected in but the incident does not have any attached video.|
|2298279||184.108.40.206||When configuring event filtering after too many triggers in the Triggers page of the Incident configuration task, clicking Apply deletes all triggers.|
|2236819||220.127.116.11||Sometimes the workflow does not run because the system reads it
NOTE: For more details, see Unable to parse incident type workflow error.
|2227787||18.104.22.168||The alarm acknowledgment buttons do not work in the General
tab of the Incident Monitoring dashboard.
Workaround: For alarms, go directly to the Alarm monitoring window to acknowledge alarms.
|2100579||2.10 GA||If events in the sequence are separated by a Security Center server restart, then incidents that are triggered by a sequence of events are not triggered successfully.|
|2100477||2.10 GA||On new systems, the Incident Manager role can fail to initialize after automatic restarts of the Security Center server.|
|1962199||2.10 GA||Unable to cycle between live and playback streams from the dashboard Camera widget in Incident management.|
|1940528||2.10 GA||Reminder notifications for collaborative incidents are not shown in the
supervisor incident tray.
Workaround: Check the Reminder section of the incident dashboard.
|1787956||2.9 GA||After deleting a user who is the only recipient of a specific incident type,
new incidents of that type have an invalid state with no recipients.
Workaround: Configure incidents to fallback to other recipients if no one responds.
|1668680||2.10 GA||Activating Maintenance mode on the Incident Manager role has no effect.|
|1184508||2.7 GA||Genetec Mission Control™ is not compatible with earlier versions and does not display a warning message when incompatible versions are used together.|
|1108578||2.10 GA||Audit trails: Document changes made in the Document management view of the Incident configuration task, are not reported in the Audit trails task.|
|737204||2.2 GA||When an area that is referenced in the advanced dispatch configuration of an
incident type is deleted from the system, the configuration of the incident type is
not flagged as invalid.
Workaround: Reconfigure the incident type.