Genetec Mission Control™ 188.8.131.52 includes the following known limitations.
|Issue||First reported in||Description|
|2862461||184.108.40.206||When RabbitMQ logon password is changed in the web management portal, connection to RabbitMQ is still live in Config Tool with the old password configuration.|
|2835512||220.127.116.11||The Monitoring task does not refresh dynamically to show new location when active incident location is changed.|
|2833670||18.104.22.168||Right-clicking an incident not linked to an area or a map and triggered on a federated entity does not include the same list of options as an incident triggered on a non-federated entity.|
|2828081||22.214.171.124||The location of an incident is not refreshed in the Monitoring task, when the incident type's automation workflow includes a Wait for incident state activity before a Display entity activity.|
|2825388||126.96.36.199||When the workstation version of Genetec Mission Control™ is 188.8.131.52 and the server has a later version of Genetec Mission Control™, the Incident monitoring task displays a black screen.|
|2824205||184.108.40.206||The tile view is different when opening an incident in Monitoring task from Incident report or Incident monitoring task.|
|2822997||220.127.116.11||When selecting a value other than the default value for the Incident details pane font size option in , there are extra line breaks after incident description in the Overview widget in the Incident details pane.|
|2776991||18.104.22.168||When incident descriptions are long, exporting the incident report in CSV and JPG to include Charts mode of the report crops the image and description.|
|2765501||22.214.171.124||There is a delay in updating door state after a door event in Conditional
Workaround: Do not use door state check immediately after in incident type Conditional activities automation activity.
|2738978||126.96.36.199||Sometimes when multiple users are connected to the same system and are viewing the same incident, the dynamic SOP widget has a minor time lag.|
|2734972||188.8.131.52||Sometimes when an active incident automation workflow includes multiple video entities, Security Desk freezes while the video streams load.|
|2730468||184.108.40.206||When adding multiple auto validation conditions to a dynamic SOP step, the Edit option dialog box expands out of view.|
|2708341||220.127.116.11||When opening the Incident monitoring task, the incident Name and Locationcolumn widths are set to the width of the strings of the incident displayed and not to the maximum width needed for other incidents in the list.|
|2658251||18.104.22.168||Custom widget headers in the Incident details pane use the class name in the code instead of set display name.|
|2600265||22.214.171.124||When emailing an incident report from the Config Tool, the incident category detail is missing.in|
|2565676||126.96.36.199||If a user or user group assigned as recipient for an incident type is deleted when an incident's Recipients tab is open, the recipients list is not automatically updated to reflect the change.|
|2565626||188.8.131.52||If a new user group is created when the Incident
configuration page is open, the Auto-assign
recipients list is not automatically updated to show the new user group.
Workaround: Close and reopen the Incident configuration task.
|2562012||184.108.40.206||When an incident is triggered on an alarm with a door entity attached, the door entity is not visible in the General tab of the Incident monitoring task.|
|2542520||220.127.116.11||Triggered incident pins disappear when switching between maps in the Incident monitoring tasks.|
|2462156||18.104.22.168||When adding more than one output entity in the Trigger output workflow activity, the dialog box shows unnecessary entities.|
|2446797||22.214.171.124||When logging on to a saved workspace in Security
Desk with a triggered incident in
the Monitoring task, the Incident details
pane is not displayed accurately.
Workaround: Select another incident in the Incident monitoring task.
|2438786||126.96.36.199||When configuring the Trigger output workflow activity, the dialog box displays roles and entities that have no valid outputs.|
|2432621||188.8.131.52||The Contact entity list in the Call action configuration dialog box gets deselected when searching for the contact entity.|
|2431627||184.108.40.206||When the Export incident activity is used immediately after the Trigger and add sub-incident activity in an incident workflow, the exported information does not include sub-incident ID.|
|2421575||220.127.116.11||Activating or deactivating a profile for a user already logged into Security Desk, reloads the queue of incidents configured with auto-open in the notification tray in Security Desk.|
|2416095||18.104.22.168||When Synchronize incident monitoring tasks is selected in Security Desk for a set up with multiple monitors, selecting multiple incidents with different map configurations, displays the default map with missing incident details.|
|2372085||22.214.171.124||When multiple images are configured as documents for a dynamic SOP step, selecting the option All documents in the step displays only one of the images.|
|2371156||126.96.36.199||When an incident configured with Auto-open in Monitoring is triggered, the Monitoring task does not close automatically even when the incident is transferred to another recipient.|
|2370643||188.8.131.52||When saving an Incident report task in Security Desk, the default sort option for incident reports is not saved.|
|2236819||184.108.40.206||Sometimes the workflow does not run because the system reads it
NOTE: For more details, see Unable to parse incident type workflow error.
|2211429||2.11 SR1||If theactivity is at the beginning of the workflow, it will not be executed.|
|2119187||2.11 GA||Incidents triggered from the Web API with geographical coordinates do not display correctly on an image map if the map is not georeferenced, or if the map is georeferenced and the incident is triggered outside the image boundary.|
|2049698||2.11 GA||Incidents triggered in an area on a .jpeg image map do not include the incident location (latitude and longitude).|
|2020510||2.10 GA||Incident is not triggered by an Access denied event from a cardholder group, when the specific user is in a subgroup under that group.|
|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.
|1753448||2.8 GA||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.|
|1633372||2.8 GA||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.|
|1188735||2.7 GA||Profile auto-assignment: When operators who are allowed to use profiles log on through a Security Desk workstation without Genetec Mission Control™ installed, the profiles are auto-assigned to them.|
|1108767||2.7 GA||The incident configuration audit trails are never deleted.|
|721822||2.3 GA||When you delete an incident icon from the Properties tab, the icon is only removed for the selected incident, not all incidents.|
|632319||2.3 GA||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).|
|545314||2.3 GA||Incident monitoring: Grouping over 5000 incidents can take up to three minutes, and Security Desk does not respond during this time.|
|518515||2.3 GA||Incident monitoring: When you maximize and restore a map in the task, the Incident pane size also changes.|