Known issues in Genetec Mission Control™ 3.1.0.0 - Genetec Mission Control™ 3.1.0.0 | Genetec Mission Control™ Web API 2.7

Genetec Mission Control™ Release Notes 3.1.0.0

Applies to
Genetec Mission Control™ 3.1.0.0 | Genetec Mission Control™ Web API 2.7
Last updated
2022-09-13
Content type
Release notes
Language
English (United States)
Product
Genetec Mission Control™
Version
3.1

Genetec Mission Control™ 3.1.0.0 includes the following known issues.

Issue First reported in Description
3244543 3.0.5.0 The location pin does not display the correct location of the Incident in the Incident monitoring task.
3240389 3.1.0.0 When configuring a complex trigger strategy with multiple conditions in the Incident configuration task, an error occurs in the application when trying to modify the trigger after saving it.
3240131 3.1.0.0 Dynamic user procedure has an error when it is triggered and reset multiple times in the Security Desk.
3225324 3.1.0.0 The Incident Manager role remains valid and online when the RabbitMQ username field is left blank.
3224085 3.1.0.0 The Boolean type additional field value is displayed as True or False instead of Yes or No in the Audit trails.
3207862 3.1.0.0 Changes to the RabbitMQ failover configuration is not captured in when generating a report in Audit trails.
3206217 3.0.5.0 The Wait for event Incident management activity has broken aggregations.
3192252 3.0.5.0 When an incident has the Recipients configured as Auto assign and the group has no members, the triggered incident is not seen by any users.
3148367 3.1.0.0 Attaching multiple documents to an incident in Security Desk makes the application freeze.
3080516 3.0.5.0 When there are multiple Display entity activities in succession in an automation workflow, video feed from all the entities are not always displayed.
3075047 3.0.5.0 When entities are attached to an active incident through the Incident report task, the update is not reflected in the Monitoring tile.
3074845 3.0.5.0 When the Document type for an incident is configured with both File and URL in Config Tool > Incident configuration > Document Management, the user is unable to access the file or the link.
3073253 3.0.5.0 When using Display entity automation activity to display layouts with doors that do not have attached cameras, the doors are not displayed in the Monitoring task.
3066508 3.0.4.0 When the Alarm triggered event is configured as the second trigger for an incident, it does not work even after configuring the Advanced event filtering option.
3054541 3.0.4.0 When sending an email of a snapshot with the Industrial IoT plugin for a custom event, the email received by the recipient does not contain the snapshot.
3020988 3.0.4.0 If an incident is triggered on an ESRI map configured with Initial map zoom level for selected incidents, the zoom level cannot be changed on the map.
2989703 3.0.4.0 In the Monitoring task, door entities are missing from the display layout even when the Display entity activity is configured within the automation workflow of the incident.
2973873 3.0.3.0 When the Genetec™ Server is restarted with an unsaved incident type configuration in Config Tool, the Incident Manager role might do one of the following:
  • Display an error message
  • Lose the configuration
  • Prompt to save changes
2972219 3.0.3.0 The Acknowledge alarm button in the General pane of the Incident monitoring task does not work for active alarms associated with active incidents.
2936276 3.0.3.0 When an incident is triggered on a custom entity created using a plugin, the incident is not displayed in the Monitoring task.
2934726 3.0.3.0 If a user does not have the TTR Metrics privilege, TTR notifications are not displayed in Security Desk.
2922169 3.0.3.0 An active incident triggered by an Access denied event plays live video in the Monitoring task, even when the camera associated with the door is configured for playback.
2806862 3.0.2.0 When there are active incidents triggered on different maps, and the Show all incidents on default map option is selected in the Incident monitoring task Settings > Incident options dialog box, the map view does not refresh to display an accurate list of active incidents.
2777100 3.0.3.0 When an incident type is configured to be triggered by an Access denied event followed by the user starting a camera recording, sometimes the trigger rules are not followed.
2739311 3.0.1.0 Security Center users without TTR Metrics privilege can see TTR notifications in Security Desk.
2736539 3.0.1.0 Genetec Mission Control™ Web API and the Genetec™ Document Service displays the incorrect error code when the document upload request is large.