Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.
Genetec Mission Control™ 2.8 GA includes the following limitations:
|1753448||When using the Change incident type workflow activity to change an incident to another type with TTR enforced, TTR events will not be triggered, if they were already triggered in the previous incident type.|
|1749816||When using the Change incident type workflow activity to change an incident to another type with different operational status (In service, Testing, Not in service), the incident will not take the new type's operational status.|
|1730440||Unable to Export current map view when exporting an incident with a map from the Incident report task or the Monitoring task.|
|1700802||Incident report tasks (public or private) saved in Genetec Mission Control™ 2.7 with the Profile report open are not visible in 2.8. If you previously scheduled exporting a profile report or emailing a profile report, the report will not be exported or emailed after the upgrade.|
|1700789||Incident report tasks (public or private) saved in Genetec Mission Control™ 2.7 are not visible in 2.8. If a workspace in Security Desk was saved with an Incident report task opened before 2.8, the Incident report will be not displayed after upgrading.|
|1633372||After generating an incident report with several incidents displayed on the same map, selecting one of the incident pins, does not select the corresponding incident in the incident list.|
|1617061||In the Incident report task, you cannot replace the content
of a tile by dragging and dropping an incident from the list onto an area defined in a
Workaround: Clear the tile before the drag and drop.
|1188735||Profile auto-assignment: When operators allowed to use profiles log on through a Security Desk workstation without Genetec Mission Control™ installed, the profiles are auto-assigned to them.|
|1108767||The incident configuration audit trails are never deleted.|
|815690||RabbitMQ: On machines that are running Windows 7 and Windows Server 2008 R2, you
cannot connect to RabbitMQ using an IPv4 address when IPv6 is enabled.
Workaround: Disable IPv6 from the machine's network configuration, or use the local name of the machine to connect instead of the IPv4 address.
|721822||When you delete an incident icon from the Properties tab, the icon is only removed for the selected incident not all incidents.|
|632319||Failover: After a failover occurs, the configured Delay for the workflow of an incident is not respected. The Delay duration reverts to the default setting (0).|
|591238||Monitoring task: When you save and close an incident workspace, the workspace reopens with the General tab displayed instead of the Incident tab.|
|583248||Incident report: If a custom State label contains underscore characters (_), these characters are not displayed in the contextual menu when you right-click on an incident to change the state.|
|545314||Incident monitoring: Grouping over 5000 incidents can take up to three minutes, and Security Desk does not respond during this time.|
|518515||Incident monitoring: When you maximize and restore a map in the task, the Incident pane size also changes.|