Resolved issues in Genetec Mission Control™ - Genetec Mission Control™

Genetec Mission Control™ Release Notes

Applies to
Genetec Mission Control™
Last updated
Content type
Release notes
Genetec Mission Control™

Resolved issues are software issues from previous releases that have been fixed in the current release.

The following software issues were resolved in Genetec Mission Control™
Issue Description
2310729 When there are multiple events with segmented titles, wherein the first part of the title is the same for all events and an underscore (_) separates the rest of the title, an incident configured to be triggered by one of these events will also be triggered by the activation of any event with a partial title match.
2270225 If the Column color activity in an incident workflow is configured with the default value, an in-progress workflow stops at that activity and cannot continue.
2269840 The Override context manually option in the Run a macro activity when selected in an incident workflow configuration is saved but the selection is not displayed in the UI.
2269656 When there are a large number of custom events, the Events dialog box in the Triggers tab of the Incident configuration task takes too long to load, causing the Config Tool to hang.
2258168 In the Privileges tab of the User management task, disabling user access to Incident reports also disables access to Profile reports.
2256892 The Incident report task does not generate any results when custom fields are used as filters.
2251009 The default RabbitMQ.config file only enables three ciphersuites. The most secure TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 cypher cannot be used with the default certificate generated by the Genetec Mission Control™ installer. The two remaining cyphers, TLS_RSA_WITH_AES_256_GCM_SHA384 and TLS_RSA_WITH_AES_256_CBC_SHA256 are considered insecure in some more secure environments and therefore disabled.
2244146 Incidents are not triggered when events exceed the threshold limit and accumulate in the RabbitMQ external Event queue.
2235672 Clicking Apply to save new activities added to an incident workflow makes the entire workflow disappear.
2227490 If parameters for the View filter in the Incident monitoring task changes, thereby including an incident that was previously excluded from view, sometimes the incident does not display on the map.
2227402 The Event source in the Triggers tab in the Incident configuration task does not allow selection of multiple inputs when Event selection is Input state change: Active.
2180190 The Filter for incident view in the Incident monitoring task is applied to all users using the same application instance of Security Desk.
2048038 Dashboard is cropped or absent when displaying three or more incidents in the Monitoring task.
1870536 Response time and Resolution time filter settings are not kept when reloading a saved Incident report task with filter errors.
1863505 Deleted incident states appear in Wait for incident state activity used in incident workflows until Config Tool is restarted to refresh the list.
1045821 When a collaborative incident is configured as only visible to supervisors and a supervisor transfers it to a user that the supervisor does not oversee, then the supervisor of that user sees both the collaborative incident and its sub-incidents instead of seeing only the collaborative incident.