To ensure that imported incident configurations, include the same associations to entities as the source system. The GUID details of the entities in the target and source systems must be identical.
Importing incident configurations with attached entities
When you export incident configurations from one system to another, the JSON file includes all details of the Genetec Mission Control™ incidents and only the GUID information of the Security Center entities associated with the incidents.
When you import these incident configurations into your target system, the Mission Control import wizard looks for attached entities and other configurations by their GUID details as configured in the source system.
If entities with the same GUIDs exist in the target system, then the incident is imported and its entities are automatically associated in the target system.
However, if the entities in the target system have a different GUID, the incident type is imported by the import wizard but no entities are attached. It shows the entity as Unknown in the incident configuration.
Troubleshooting Unknown error when importing incident type configurations
Depending on your incident type configuration and where the entities are used, an Unknown error might affect the incident automation workflow, triggers, or recipients configuration in the target system.
When this happens, you must manually configure entities for incidents in the target system.
- Alarms and other Security Center entities (such as cameras, doors, and so on)
- Macros
- Incident states
- Incident priorities
- Users, user groups, and associated privileges
- Documents
- Profiles
- Federated entities (when federated from different sites)
- Schedules
- Threat levels
To ensure that there is no disconnect, it is recommended to verify the associated entity configurations in the target system in the listed order.
Exceptions when importing entity configurations
There are a few exceptions when importing configurations:
- Profiles
- Profile details are stored in the Incident Manager database. They cannot be exported or imported between different Mission Control systems. You must assign incidents to profiles in the target system manually as this association cannot be copied between systems.
- Additional fields
- You must ensure that the names of the additional fields in the target and source systems are identical.
- Federated entities
- GUIDs for federated entities are obtained from the federated site. If the source and target Mission Control systems are federating the same system, the GUID of the entities in both systems will be identical.
- Users and user groups
- You must ensure that the GUID of the user or user groups in the target and source system are identical. If the required user or user group does not exist, you must create one to configure details such as recipients for incident dispatch.
- Incident states and priority
- Default system incident states and priorities have the same GUIDs irrespective of the system environment. You must ensure same GUIDs in source and target systems only if you are using custom states or priorities.
- Documents
- If you have not used a shared network drive for documents related to incidents in both the source and target systems, you must copy the documents folder from the source to target system and manually configure documents for each incident type.