Known issues in Genetec Mission Control™ 2.13.1.0 - Genetec Mission Control™ 2.13.1.0

Genetec Mission Control™ Release Notes 2.13.1.0

Applies to
Genetec Mission Control™ 2.13.1.0
Last updated
2020-01-30
Content type
Release notes
Language
English (United States)
Product
Genetec Mission Control™
Version
2.13

Known issues are software issues that have been discovered in the current release or a previous release, and have not yet been resolved.

Genetec Mission Control™ 2.13.1.0 includes the following known issues:

Issue First reported in Description
2366011 2.13.1.0 The profile assignment does not reset when an assigned user logs off Security Desk.
2363787 2.13.1.0 A Supervisor's Profile assignment manager shows supervisees who are offline and other supervisors.
2363467 2.13.1.0 The Monitored by column displaying the name of the Security Center user monitoring an incident does not reset even after a role restart.
2358890 2.13.1.0 When exporting incidents with aggregated events from Security Desk, the incident export fails if the Export video for aggregated events option is selected in Incident options > Export settings but the incident does not have any attached video.
2351518 2.13.1.0 If an area has no configured sub-areas and the Include subareas option is cleared when adding the area as Location in Incident configuration > Profiles > Properties, ​​​​​​​the selection list still displays the previously added area without the option to select it.
2298279 2.12.1.0 When configuring event filtering after too many triggers in the Triggers page of the Incident configuration task, clicking Apply deletes all triggers.
2236819 2.12.0.0 Sometimes the workflow does not run because the system reads it inaccurately.
2227787 2.12.0.0 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.
1868509 2.9 GA Modifications to the Incident Manager role are presented as raw XML in the Security Desk audit trail report.
Workaround: Generate the audit trail report in Config Tool.
1862616 2.9 GA When no default map is set and an incident is triggered in the Incident report task, the incident is not visible and the incident location is set to Security Desk map.
Workaround: Select a default map for the system.
1861305 2.9 GA Documents that are available on a schedule remain visible in the Documents widget on the incident dashboard, if an associated incident is selected when the scheduled period ends.
Workaround: Refresh the Documents widget by logging off and logging back on, or briefly switching to another incident.
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.