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™
2.11
GA:
| Issue | Description |
|---|---|
| 2140338 | When configuring event triggers for an incident type, you cannot set multiple sources for the same event type. |
| 2133451 | In the incident workflow, two or more parallel task activities with different exit conditions do not complete as expected. The final parallel task overrides the exit conditions of previous parallel tasks. |
| 2125708 | Workflow activities that activate on transition to a specific incident state will trigger if the incident previously passed through the required state. |
| 2107684 | The Incident Manager role and the Incident monitoring task hang with "Waiting for connection to server." after triggering 40,000 incidents on the server. |
| 2100829 | A memory leak crashes the Report Manager role when exporting incident reports on a repeating schedule. |
| 2046511 | Priority shows as UNKNOWN while importing incident types, but is correct in the incident type properties. |
| 1918320 | "Supervisors" is not shown in the Recipients column when importing collaborative incident types. |
| 1887742 | Under certain circumstances, after selecting an incident from the incident list and clearing the filters, clicking another incident in the list will select the new incident along with the currently selected incident instead of deselecting the previous incident first. |
| 1862427 | Closing the child of a collaborative incident while the parent incident is selected in another Security Desk session, causes the parent incident in that other session to be deselected. |
| 1745815 | Document management view in the Incident configuration task takes more than two minutes to load when there are 9000 documents. |
| 1526393 | If you are not the recipient of a linked incident, changing the state of the linked incident does not show in your incident dashboard. |
| 1423066 | When importing the incident configuration (JSON file) from another system, triggers that refer to entities in the other system are dropped without any warning. |
| 1231340 | Incident types are imported as In service by default, which poses the risk of disrupting live operations. |
| 1036591 | After exporting and importing incident types, the alert sound bites associated to the incident types are displayed as UNKNOWN, but function properly. |
| 947683 | When a priority is deleted from the Properties page of the Incident Manager role, the priority is not deleted from the incident list in the Incident monitoring task. |