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.11 GA includes the following known issues:
|2152388||When linking incidents, specifying an invalid incident ID of 0 does not highlight the entry in red.|
|2152371||When querying incident type modifications in the audit trail, the latest change
is not included if the number of modifications exceeds the query limit.
Workaround: Restrict the incident type modifications to a specific time range.
|2151991||The behavior of the View incident button for linked
incidents is inconsistent. If Synchronize incident monitoring
tasks is enabled, the incident opens in the current Incident
monitoring task. If it is disabled, the incident opens in the
Workaround: Select the linked incident from the incident list.
|2150524||After changing the retention period of the Incident Manager, the audit trail does not report correct values when switching the retention period for an incident type from Inherit from role to Indefinitely.|
|2150474||Users in the global partition cannot take ownership of incidents from users in another partition because the Confirmation of consent pop-up is not displayed.|
|2147743||Triggering an incident on an image map that is not georeferenced sets the latitude and longitude of the incident to the pixel position.|
|2146426||When a camera is attached to a basic incident and a collaborative incident at the same time, video from that camera is exported with the basic incident, but is not exported with the collaborative incident.|
|2138529||After selecting an alarm on a georeferenced map in Incident
monitoring, triggering an incident anywhere else on the map sets the
alarm as the location.
Workaround: Select another entity on the map and close it before triggering the incident.
|2133643||After grouping the incident list by a specific column, removing that column from the incident list also removes the selection from the Group by dialog box.|
|2132400||Incident filters are not applied to other Incident
monitoring tasks when Synchronize incident monitoring
tasks is enabled.
Workaround: Apply incident filters manually.
|2132264||Clicking column headers to sort the incident list only works for default
Workaround: Sort the incident list from the context menu.
|2123599||Incident shows In service operational status after using the Change incident type workflow activity to change the incident from an In service incident type to an incident type in Testing.|
|2100601||Using the workflow to change a standard incident type to a collaborative incident type fails to trigger child incidents automatically.|
|2100590||Incident triggers and other changes are lost when using an unresponsive SQL database.|
|2100579||Incidents that are triggered by a sequence of events are not triggered successfully, if events in the sequence are separated by a Security Center server restart.|
|2100477||On new systems, the Incident Manager role can fail to initialize after automatic restarts of the Security Center server.|
|2096196||Incident start time is shown out of sequence in the Latest activity list when refreshing the incident dashboard.|
|2049698||Incidents triggered in an area on a JPEG image map do not include the incident location (latitude/longitude).|
|2048552||Unable to close multiple unresolved incidents at the same time with the Forcibly close unresolved incidents privilege.|
|2048038||Dashboard is cropped or absent when displaying three or more incidents in the
Workaround: Expand the dashboard manually.
|2047653||In an SOP step with multiple documents, selecting All documents from the View document context menu only opens one document randomly.|
|2046172||Missing error when incident is configured with an empty Dispatch to
Workaround: Ensure that Dispatch to is properly configured.
|2012502||Incidents triggered by a door event are not triggered by events from federated doors.|
|1962199||Unable to cycle between live and playback streams from the dashboard camera widget in Incident management.|
|1961457||The View incident button in the Linked incidents widget does not work when monitoring tasks are not synchronized.|
|1958759||Workflows with an invalid activity stop at the point of the error without persistence, and do not proceed to the next activity, if there is one.|
|1940528||Reminder notifications for collaborative incidents are not shown in the
supervisor incident tray.
Workaround: Check the Reminder section of the incident dashboard.
|1870536||Response time and Resolution time filter settings are not kept when reloading a saved Incident report task with filter errors.|
|1868509||Modifications to the Incident Manager role are presented as raw XML in the
Desk audit trail report.
Workaround: Generate the audit trail report in Config Tool.
|1862616||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||Documents that are available on a schedule will 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.
|1821540||If a supervisor is monitoring an incident and the operator transfers that incident to the supervisor, then the supervisor is also removed from the list of people monitoring the incident.|
|1787956||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.
|1749005||Operators with the Link incidents privilege can link incidents they do not have permission to see using the incident ID.|
|1708941||If the option to Automatically change incident state is enabled, a non-recipient can take ownership of new incidents by opening them in the Monitoring task.|
|1704316||View on map button does not work if the incident is
Workaround: Deselect the incident and reselect it.
|1668930||Workflow: If the incident type is changed inside a Parallel tasks activity
before all branches complete, the other branches will continue to run with the new
incident type workflow.
|1668680||Activating Maintenance mode on the Incident Manager role has no effect.|
|1475849||After a user transfers an incident to a profile, and someone takes ownership of the incident, the Owner of incident is displayed as "Unavailable information".|
|1184508||Genetec Mission Control™ is not backward compatible with older versions and does not display a warning message when incompatible versions are used together.|
|1108578||Audit trails: Document changes made in the Document management view of the Incident configuration task, are not reported in the Audit trails task.|
|1045821||When a supervisor transfers a collaborative incident configured to be only
visible to supervisors, to a user that the supervisor does not oversee, the supervisor
of that user sees both the collaborative incident and its sub-incidents instead of
seeing only the collaborative incident.
Workaround: Log off and log back on.
|1044720||The incident workflow hangs at the Wait for event activity if the previous event source is a specific cardholder.|
|1028364||Some entity types, such as alarms, elevators, parking zones, and so on, are not
available as incident locations in the Trigger incident dialog
Workaround: Right-click an alarm on the map.
|954011||Incident states are not reflected in near real-time in the Incident report task.|
|944316||In the Incident monitoring task, if you lose your connection
to the network, the system might display a dialog box that says The configuration
of New incident was modified. Do you want to apply the changes?
Workaround: Click Cancel to close the dialog box.
|937870||When a supervisor is logged in while modifications are made to the list of users
they supervise, the changes are not updated in the Incident
Workaround: Log off and log back on.
|935322||Creating a database on a remote server for the Incident manager role does not work. An error is displayed, and the database is not created.|
|824206||Events for specific sources, such as access granted events on a door, might produce the same incident twice.|
|751818||Incident monitoring: Closed incidents are not always removed from the map
Workaround: Close and reopen the Incident monitoring task.
|737204||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.