Genetec Mission Control™ incident - Workflow tab - Genetec Mission Control™

Genetec Mission Control™ Administrator Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > User guides
Genetec Mission Control™

On the incident Workflow page, you can define how the system changes the properties of an incident, and how it responds automatically to user actions, events, and other incident events.

Configure a flowchart using flowchart activities. The available activities are described in the three sections that follow. Errors found in your flowchart are signaled by error messages at the bottom of the Workflow page.

Incident management activities

The available incident management activities are:
Aggregate event
Must come immediately after the Wait for event activity. Add the event that matched the Wait for event activity to the event history associated to this incident.
NOTE: The Wait for event activity now incorporates auto-aggregation to the incident and an explicit Aggregate event activity is no longer required.
Change description
Replace the incident description with the specified text.
Change incident state
Forcibly change the incident to the specified state, regardless of its current state.
Change incident type
Change the incident type. You can transition from normal to normal, normal to collaborative or collaborative to collaborative incident types.

This activity must be the last one in the workflow, as it ends the current workflow and starts a new workflow using the new incident type.

NOTE: The Wait for TTR event, including time to response not respected and time to resolution not respected events can only be triggered once. Changing an incident type using this workflow activity does not allow these events to be triggered a second time.
Change priority
Change the incident priority to the specified priority.
Close incident
Close the incident when its state changes to the specified state. Specify the following:
Set the state that the incident must reach for the Close incident activity to be triggered.
Set the number of seconds, minutes, or hours after which the incident must be closed.
This activity must be the last one in the workflow.
Column color
Highlight the incident in the incident list by changing the background color of the selected columns or the entire row. To remove the highlight, change the color back to default. There is a custom palette of colors available in addition to the basic palette.
Pause the workflow for the specified duration.
Dispatch Incident
Sends the incident to selected users or user groups. Select one of the following options:
Forward the incident to additional recipients.
NOTE: Forwarding an incident does not change the ownership of that incident.
Transfer the incident to selected recipients.
NOTE: Transferring an incident releases ownership of that incident, when the owner does not see the incident in the incident monitoring list anymore.
Enable/Disable state transition
Enable or disable the option to manually change an incident's state in the Incident monitoring task.
NOTE: 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. Users who have the Forcibly close unresolved incidents or Forcibly resolve incidents having non-validated steps privilege can also override this selection.
Export incident
Export the incident with the default settings to a specified folder.
Display a reminder in the notification tray of all incident recipients who are online.
The interval at which the reminder notification is displayed throughout the life of the incident. Select one of the following:
Every minute
Every minute.
At a specified minute of every hour.
At a specified time every day.
At a specified day and time every week.
On startup
At a regular time interval in days, hours, and minutes, starting from the time the reminder is created.
Display a specific message
Display a text message with the incident reminder.
Trigger incident
Incident type to trigger every time the reminder is displayed.
Trigger and add sub-incident
Trigger a sub-incident and add it to a collaborative incident.
NOTE: This activity will be valid only when triggered in the workflow of either a collaborative incident or a sub-incident of a collaborative incident. When used in the workflow of a sub-incident, the incident triggered in this activity will be aggregated to the parent collaborative incident.
Trigger incident
Trigger an incident. You can optionally include a comment and the area where the incident occurred.
Wait for dynamic procedure steps
Wait for one dynamic procedure step from this incident type to be resolved with a specific answer. You can specify multiple steps, and this activity will wait for the first among the selected steps to be resolved.
Wait for event
Wait for an event to occur. You must specify the following:
Event category
Security Center, or any custom plugin that is installed.
Wait for event
The event you are waiting for. Select one of the following:
Any event
All events match your criteria.
Any event except
You must specify a list of events that do not match your criteria.
Specific events
You must specify a list of events that match your criteria.
Previous event
The event that must precede the event you are waiting for. Select one of the following:
Don't care
No previous event is necessary.
Any event
Any event is acceptable.
Any event except
Any event is acceptable except the ones you include in the exclusion list.
Specific events
Only an event found in the specified list is acceptable.
Event source and alarm configuration options:
Choose to configure Event sources and Related alarms or select the option to Aggregate all related alarm instances.
Event source
Specify the common source for your events.
Don't care
The source is not important.
Specific source
Specify a list of entities that are eligible as event source.
Any source except
Any source is acceptable as long as it is not found in the specified exclusion list.
Incident location
The entity on which the incident is active. It may be an area, video entity, door and so on.
Incident area
The area within which the incident is active. Child entities of this area are included, unless they are area entities.
Related alarms
Specify alarms associated with the incident.
Don't care
The source is not important.
Specific source
Specify a list of alarms that impact incident management.
Incident alarms
Aggregates events from a previously aggregated alarm.
Aggregate all related alarm instances
Select this option to aggregate all events of the previously aggregated alarm instance, irrespective of event source and related alarms selection.
Add custom field
You can select relevant custom fields such as Alarm context.
NOTE: When the Wait for event activity is used in a workflow, the event specified is always aggregated to the incident and you do not need to add an Aggregate event activity.
Wait for incident priority
Wait for any or a specified incident priority.
Wait for incident state
Wait for any or a specified incident state.
Wait for TTR event
Wait for incident response time not respected, incident resolution time not respected, or the first of either event to occur. You must specify one or more of the following:
Granted incident response time not respected
Trigger when the maximum response time granted to this incident type has not been met.
Granted incident resolution time not respected
Trigger when the Minimum or Maximum time granted to resolve this incident type has not been met.
Dynamic procedure step resolution time not respected
Trigger when the Minimum or Maximum time granted to resolve one or more dynamic procedure steps for this incident type has not been met.

Security Center activities

Only the following Security Center actions are supported as flowchart activities:
Acknowledge alarm
Acknowledges the alarm that triggered this incident and any additional alarm instances that have been aggregated to this incident. Select one of the following:
Acknowledged (Default)
The system automatically acknowledges the alarm.
Acknowledged (Alternate)
The system automatically acknowledges the alarm using the alternate mode.
Acknowledged (Forcibly)
The system forcibly acknowledges the alarm.
Arm zone
Arms the selected Virtual zone.
Disarm zone
Disarms the selected Virtual zone.
Display entity
Displays a selected entity in the Security Desk Monitoring task of configured recipients. You must specify the following:
User, User group
The user or user group who will receive the selected entity.
Owner only
When selected, only the incident owner will receive the selected entity. This setting overrides other configured recipients.
Display entity
The entity to display.
Video mode
The following options are available for camera entities:
  • Live
  • Playback from current time
  • Playback from incident trigger time
Play a sound
Plays a sound bite in a user or user group’s Incident monitoring task in Security Desk. This action is ignored if the user's Incident monitoring task is not open. You must specify the following:
User, User group
Select a user or user group.
Sound to play
Select the .wav file to play. The standard alert sound files that come with the installation are located in C:\Program files\Genetec Security Center <Version>\Audio.
PTZ command
Commands the PTZ camera to perform an action. You must specify the following:
The PTZ action to perform. Select on of the following:
Go to preset
Commands the PTZ camera to go to the specified preset.
Run a pattern
Commands the PTZ camera to run the specified pattern.
Go home
Commands the PTZ camera to go to its home position. Not all PTZ cameras support this feature.
The PTZ camera to perform the selected action.
Public addressing
Send an mp3 or wav audio message to selected recipients or to the incident location.
NOTE: A compatible Sipelia™ version must be installed on the Genetec Mission Control™ server. To know more about configuring Sipelia™ Public address, see the Sipelia™ User Guide.
Reset area people count
Resets the people counter in the selected Area.
Run a macro
Executes the selected Macro. You must specify one of the following execution contexts:
Use default execution context
Context variables are populated with values from the Default execution context page of the macro in Config Tool.
Override context manually
Context variables are populated with values you specify in the workflow activity.
Override context using incident properties
Specific context variables are populated with the matching incident property.
Send an email
Sends an email to a user or user group. All selected recipients must have an email address set up in their profile, and the mail server must be configured for Security Center, or the action is ignored. Specify the following:
The users or user groups who should receive the email.
The email subject.
The email message.
Add field
Add context variables such as Incident ID, Source entities, and more to the Subject, Message, or both. Before sending the email, these variables are automatically populated with information from the incident.
Latest Activity
Add placeholders one or more of the following to the Message field:
  • System actions
  • Comments
  • SOP completion
  • Monitoring
  • Warnings
  • TTR Events
  • Notes

These placeholders are automatically populated with the latest information when the email is sent.

Set threat level
Sets a threat level on your Security Center system, or the incident location. You must specify the following:
Threat level
The threat level to set.
The area to set the threat level on. The area can be your entire system, or the incident location.
Trigger alarm
Triggers one or more alarms. This action might generate additional events, depending on the alarm configuration. You can choose to aggregate all the alarms triggered to the incident by selecting the Aggregate alarms option.
NOTE: You must select the Aggregate alarms option for the alarm to be acknowledged by the Acknowledge alarm activity.
Trigger output
Triggers one or more entity outputs. You can select the desired output behavior.

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

Unlock door explicitly
Temporarily unlocks the specified door for five seconds, or the Standard grant time configured for that door.

Generic activities

The following activity types are generic flowchart activities. They can be used to hide details from your top-level flowchart.
Conditional activities
Add IF-ELSE conditions.
Add a flowchart.
Parallel tasks
Add a node for parallel tasks. Each parallel task can be an activity, a flowchart, or a sequence of activities. You can either exit the node the moment one of the parallel tasks is completed, or when all of the parallel tasks are completed (Default).
If a parallel task contains an infinite loop, selecting Exit when all branches are completed can cause this activity to continue until the incident is closed.
Add a sequence of activities.
NOTE: Although we do our best to keep our videos current, the information presented in this video might become outdated with each new release. If you find anything wrong with this video, feel free to contact us.