Resolved issues in Mission Control 3.2.0.0 - Mission Control 3.2.0.0 | Mission Control Web API 2.10

Genetec Mission Control™ Release Notes 3.2.0.0

Product
Mission Control
Content type
Release notes
Version
3.2
Release
3.2.0.0
ft:locale
en-US
Last updated
2025-01-22

The following issues are resolved in Genetec Mission Control™ 3.2.0.0.

Issue Description
3475571 Incident ID is different when it is closed and viewed in the incident report.
3471439 Configuring an incident with the Video display option as Live and playback displays only the live camera tile without the playback tile in the Monitoring task.
3471329 Clicking on an incident trigger source results in the Config tool crashing.
3469364 Generating an incident report with more than 5000 incidents creates an error.
3468253 When an incident is triggered that is associated to a video entity it opens in multiple tiles in the Incident monitoring task.
3427505 Building a web host the Directory REST endpoints creates a certificate error when starting.
3425161 Removing an alarm from the trigger list of an incident removes other alarms associated with the incident.
3424858 In the Incident report task the Export incident to Clearance button is missing.
3422532 Triggered alarms from the C•CURE plugin is not displayed in Incident monitoring task.
3419073 Changing an incident location to a different map displays the incorrect location, which is not in the new map in Security Desk and Config Tool tasks.
3418673 When an alarm is triggered that is associated to an entity it opens in all tiles in the Incident monitoring task.
3417409 When an alarm is triggered that is associated to a video entity it opens in multiple tiles in the Monitoring task.
3417405 When an alarm with multiple attached websites is triggered, only one website is displayed when opening the incident in the Monitoring task.
3416538 When a user adds a single alarm in the trigger of an incident configuration, multiple alarms are added.
3393927 The Shunt reader activity on an incident location does not work on related entities.
2580015 When the Display entity automation activity is the first activity in an incident workflow, related entities of the active incident are not displayed in the Monitoring task, if the task is not already open.
Workaround: Add a Delay automation workflow activity before the Display entity automation activity.