Creating snapshots of your Genetec Mission Control™ incident configuration - Genetec Mission Control™ 2.10

Genetec Mission Control™ User Guide 2.10

series
Genetec Mission Control™ 2.10
revised_modified
2018-11-30

You can create snapshots to export one or more Genetec Mission Control™ incident configurations, including your custom icons, to a JSON file and re-import them, without including the activity history.

What you should know

Create snapshots of your Genetec Mission Control™ system configuration to help you during the design and experimentation phase.
NOTE: If you have incident triggers and workflows that reference Security Center entities (cameras, doors, and so on), you cannot export your incident configuration from one system, and import that configuration to another system. Incident types refer to Security Center entities using unique internal IDs that are not portable from one system to another.
CAUTION:
Genetec Mission Control™ incident configurations must be exported and imported as a whole. For example, if you have two incident types, A and B, where A triggers B in its workflow. If you export your configuration and re-import it, the imported A will only trigger the imported B, not the existing B in your system.

Procedure

To export an incident configuration snapshot:

  1. From the Config Tool home page, open the Incident configuration task.
  2. Click the Incident configuration view (if not selected).
  3. Export the incident configurations.
    • Click Export to export all incident types together.
    • Select one or more incident types and incident categories in the browser pane, right-click one of the selected items and choose Export selected incidents to a file.
  4. In the file browser window that opens, browse to the folder you want, enter the name of the JSON file, and click Save.

To import an incident configuration snapshot:

  1. From the Config Tool home page, open the Incident configuration task.
  2. Click the Incident configuration view (if not selected).
  3. (Optional) Delete one or more of your existing incident types and categories.
    Best Practice: To avoid confusion, it is best to prevent incident duplication by importing a snapshot to a clean database, because the imported incident types are not related to the existing ones, even though they share the same names.
  4. Import the incident configurations.
    • Click Import.
    • Right-click anywhere in the browser pane and choose Import incidents from a file.
  5. In the file browser window that opens, select the JSON file you want and click Open.
    A preview window opens, showing you all incident types found in the snapshot.

  6. Click Save.
    All incident types found in the snapshot are imported as new incident types to an incident category named after the JSON file.