What's new in Genetec Mission Control™ 2.13.3.0 - Genetec Mission Control™ 2.13.3.0

RabbitMQ updates

For details on how to upgrade your RabbitMQ failover cluster version, see Upgrading a RabbitMQ failover cluster to version 3.8.3

General enhancements

New workflow activities

Trigger output

You can use this activity in an incident workflow to trigger the outputs of selected entities. Some examples include locking or unlocking a door, triggering a camera output and so on.

You can select the desired output relays and the output behavior. For more details on output behaviors, see About output behaviors and Output behavior - Properties tab topics in the Security Center Administrator Guide.

Enable/Disable state transition

You can use this activity to enable or disable the option to manually change an incident's state in the Incident monitoring task.

This does not affect the system's ability to change the incident state if the Change incident state activity is configured in the incident workflow.

Wait for incident priority

You can use this activity when you want to direct the system to wait for either any or a specified incident priority before proceeding to the next activity.

Conditional activities

You can direct system or operator action based on the value of one or a combination of various incident properties using Conditional activities in the incident workflow.

You design IF-ELSE conditions using one or more of the following:

Incident properties

• Active duration
• Area
• Description
• External ID
• Latest Event
• Latest Event Time
• Location
• Owner
• Priority
• Procedure completed
• Recipients
• Resolution time
• Response time
• Source entity type
• State

Incident location

• Area
• Door
• Entity

Depending on the complexity of your requirements, you can have multiple conditions grouped using a combination of the following:

• Logical AND
• Logical OR
• Nested Conditional activities

Updates to existing workflow activities

Wait for event

The activity has an updated user interface and includes additional parameters for configuration.

• You can select the option to aggregate all events of the previously aggregated alarm instance, irrespective of event source and related alarms selection.
• Add custom field such as Alarm context.

Send an email

New context variables have been added to the message body Field menu in the Send an email activity:

• Cardholder: A valid read trigger at any door entity captures the cardholder information that you can send via email to selected recipients.
• Dynamic procedure: You can select this parameter to send the dynamic SOP steps, response times, operator responses and comments in a table format via email to selected recipients.

Updates to incident properties configuration

The Allow multiple occurrences within the same area and Allow multiple occurrences at the same location configuration options have been replaced with a Multiple occurrence restriction menu.

You can select one of the following Multiple occurrence restriction options to determine the active incident display in the Incident monitoring task:

None

Allow multiple active incidents of the selected incident type.

One per location

Allow only one active incident per incident type per location.

One per area

Allow only one active incident per incident type per area.

One per location per category

Allow only one active incident per incident type under the selected incident category per location.

One per area per category

Allow only one active incident per incident type under the selected incident category per area.

NOTE: You can also right click an incident type or category in the Incident configuration page of Config Tool to set the Multiple occurrence restriction for the incident type or all incident types under the selected incident category.

User interface upgrades

You can see the following changes in the dynamic SOP display in the Incident Monitoring task:

• When there are multiple user options configured for a dynamic SOP step:
  • If the response options are 4 or less they are displayed as stacked buttons.
  • If there are more than 4 options, one button with the text Select response is displayed. Clicking it expands the list of responses available.
• Shortcuts configured for a dynamic SOP step response are displayed as a tooltip.
• Custom actions are displayed as stacked buttons.
• Force comment option for dynamic SOP steps:
  • When selected during configuration, comment box opens automatically and you can proceed to the next step only after you enter text for the comment.
  • When cleared during configuration, Add comment is displayed as clickable text in the step and you can proceed to the next step whether your choose to enter comments or not.

View filter for the Latest activity log

You can filter the Latest activity log in the Incident details pane in the Incident monitoring task in Security Desk on one or more of the following criteria:

• Comments
• System actions
• Aggregated events
• Event aggregations
• SOP completion
• Monitoring
• Warnings
• TTR Events
• Notes

New terminology

Sipelia™ public addressing workflow activity and Sipelia™ call action in dynamic SOP step custom actions configuration are now referred to as Public addressing and Call action respectively.

UI SDK enhancements

UI SDK for Genetec Mission Control™ 2.13.3.0 includes the following enhancements:

Notes for custom action translated to UI language

All notes generated by the custom Sipelia™ call action in a dynamic SOP step will be automatically translated and logged in the incident’s latest activity report in the language of your Security Desk.

Retrieve incident type

You can use the Genetec Mission Control™ UI SDK to retrieve incident type details of any active incident using the incident type ID.

Manage edit mode in custom widgets

You can use the edit mode in custom widgets for an alternative way to edit or modify active incident information.

Important links