Exporting and Importing Data in QPR ProcessAnalyzer

QPR ProcessAnalyzer allows to import and export data in the following ways.

Export Data to CSV using ChartView

ChartView can export any data that is presented in tables to CSV, when clicking the Export CSV button. You can choose two show any process mining objects such as events, cases and event types. Also datatable contents can be exported.

When there is lots of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in the UI, and that's why ChartView has a limitation of 10 000 rows by default. ChartView can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export file separately.

Importing and Exporting .PACM Files

QPR ProcessAnalyzer models can be exported into .pacm files (pacm=QPR ProcessAnalyzer compressed model file). One .pacm file contains one model including case and event attributes and model specific user rights.

If importing a model from a .pacm file to the same database from which the model was exported, all data in the .pacm file is imported. If importing from a .pacm file to a different database than from which the model was exported, the following restrictions apply:

• Imported filters are restricted to those that were made by the user that exported the model.
• Model specific user rights are imported if the same UserID-Username combination exists in the target database.
• Users with the global administrator role in the source database aren't given any access rights to the model in the target database unless they also have model specific access rights in the source database, in which case only these model specific access rights are copied.

Importing .XES Files

QPR ProcessAnalyzer interprets .xes files as eXtensible Event Stream standard files and handles the file contents as follows:

• Trace entities are imported as cases
  • The immediate child entity of trace entity having concept:name as the value of key-attribute is imported as the name of the imported case.
  • Using all the other values not listed above, but listed as keys under the <global> entity having case as scope are imported as case attributes.
• Event entities (immediate child entities of trace entities) are imported as events.
  • The immediate child entity of event entity having concept:name as the value of key-attribute is imported as the identifier of the event type for the imported event.
  • The value of an immediate child entity of event entity having time:timestamp as the value of key-attribute is imported as the timestamp for the imported event.
  • The value of an immediate child entity of event entity having lifecycle:transition as the value of key-attribute is imported as the suffix used for event type identifier for the imported event.
    • If lifecycle:transition is defined, the format of the event type identifier will be <concept:name> - <lifecycle:transition>
    • If lifecycle:transition is defined for an event but concept:name is not defined, lifecycle:transition will be used as the name of the event type.
  • Using all the other values not listed above, but listed as keys under the <global> entity having event as scope are imported event attributes.

• All the values listed above support the following value types (also used as names of entities):
  • Date: the value will be converted into DateTime
  • Boolean: the value will be converted into Boolean
  • Int: the value will be converted into 32 bit integer
  • Float: the value will be converted into double using invariant culture
  • Id: the value will be converted into GUID
  • Any other value type will be converted into string using invariant culture