Export and import an investigation

You can use your investigations in different processes and workspaces. For that, you export your investigation and import it into another process. To speed up the creation of an investigation, you can even import it into the same process.

The export only includes references to process data, not the actual process data. Whether you need to configure an imported investigation depends on how much the data of the source and target process differ.

The following applies:

  • You can import an investigation in any process.

  • The more similar the data, the less configuration is required after an import.

  • Data conflicts are detected and you can then resolve them.

Investigations are exported as JSON files.

What's exported

The following settings and configurations are exported:

  • widgets

  • chapters

  • filters

  • the metrics bar

  • SIGNAL queries that are configured in widgets

  • metrics that are added to the process, including their variables

  • references to process data

  • references to custom attributes

The export doesn't include the following:

  • process data

  • custom attributes

  • the link to a BPMN process model

Export an investigation

Follow these steps:

  1. Open your process.

  2. Under All investigations, click > Export for the investigation you want to export.

    The investigation is exported as a JSON file. The file is saved to your browser's download folder.

Import an investigation

Follow these steps:

  1. Open your process.

  2. Click Import.

    The import dialog opens.

  3. Select the JSON file and the process view which you want to set for the investigation.

  4. Confirm with Next.

    The investigation to import is checked.

    If there aren't any conflicts, the investigation is imported.

    If there are conflicts, you have the following options:

    • Import the investigation as is.

      The investigation is imported. You then need to reconfigure the widgets that show an unexpected result.

    • Resolve the import conflicts.

      The dialog for resolving conflicts opens.

  5. Confirm with Save and import.

    The investigation is imported.

Resolve import conflicts

The following issues can cause import conflicts:

  • the same name is used for a metric in both the exported investigation and the target process, but the metrics have different SIGNAL code

  • the same name is used for a metric variable in both the exported investigation and the target process, but the variables have different values

  • widgets are configured with custom attributes

You resolve conflicting items as follows:

Metric variables

For each conflicting variable, a new name is suggested.

You have the following options:

  • Import a variable with a new name. You can use the suggested name or edit it. The variable is added to the process.

  • Keep the variable name from the source investigation. The variable in the target process is overwritten. Widgets of the target process using this variable can show a false or no result.
Metrics

For each conflicting metric, a new name is suggested.

You have the following options:

  • Import a metric with a new name. You can use the suggested name or edit it. The metric is added to the process.

  • Keep the metric name from the source investigation. The metric in the target process is overwritten. Widgets in existing investigations of the target process using this metric can show a false or no result.
Custom attributes

For each conflicting attribute, you can select an attribute to which you want to map it.

You have the following options:

  • Map an attribute. The attribute reference used in widgets of the investigation to import is updated.

  • Don't map an attribute. The attribute reference is outdated. Widgets using this reference in the investigation to import can show a false or wrong result.

Next steps

Share an investigation with other SAP Signavio Process Intelligence users

Work with metrics

Manage widgets