Resolved issues are software issues from previous releases that have been fixed in the current release.
The following software issues are resolved in Genetec Mission Control™ 2.11 SR1.
|2211236||When there is a Wait for state in the workflow, there is no advancement to the next steps until there is a change in state of the incident by user or the system.|
|2208766||Trigger incident window in the Incident monitoring screen does not set the cursor at incident type search box on launch.|
|2198428||The Cancel button in the Trigger incident window in the Incident monitoring screen was bound to the Enter key on the keyboard. This allowed for user errors in canceling an incident instead of triggering it.|
|2171276||Incident monitoring is blank when the Sipelia™ 2.8 GA client is installed on the same machine as Security Desk. Interacting with an incident notification in this setup crashes Security Desk.|
|2156616||GetAllCategoriesAndIncidentTypesMessage calls from the Genetec Mission Control™ SDK fail with a not implemented exception.|
|2155618||Genetec Mission Control™ does not differentiate custom events that have the same name and come from different entities.|
|2140361||The video associated with an incident cannot be seen in Security Desk when that incident is triggered by an input.|