Exporting and Importing Data in QPR ProcessAnalyzer: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 2: Line 2:


== Importing Data from CSV File ==
== Importing Data from CSV File ==
Data from CSV files can be imported to QPR ProcessAnalyzer using the [[Importing_Data_to_QPR_ProcessAnalyzer|Data import]] view. It's possible to import:
Data from CSV files can be imported to datatables using the [[Importing_Data_to_Datatable_from_CSV_File|Import dialog in the Workspace]].
* Cases and case attribute values
* Events and event attribute values
* Generic data to datatables.


== Export Data to CSV File==
== Export Data to CSV File==
[[ChartView]] can export any data that is presented in tables to CSV, when clicking the '''CSV Export''' button. You can choose two show any process mining objects such as events, cases and event types. Also datatable contents can be exported.
Datatable contents can be exported to a CSV file, in [[QPR_ProcessAnalyzer_Project_Workspace#Opening_Datatable|opened datatable contents]]. Click ''Settings'' and ''Export as.. in the ''Analyze'' tab.


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.
[[QPR_ProcessAnalyzer_Chart|Chart]] is able to export data that it's presenting to a CSV file, available in the ''Visual'' tab in the chart settings. You can choose to show any process mining objects such as events, cases and event types. When there is lot of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in a dashboard. Chart can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export separately.


== Importing and Exporting .PACM Files==
== Importing .XES File ==
QPR ProcessAnalyzer models can be exported into '''.pacm files''' (pacm=QPR ProcessAnalyzer compressed model file) using the [[QPR_ProcessAnalyzer_Deployment_Package#Model_Manager|Model Manager]]. Pacm files can be imported to QPR ProcessAnalyzer by using the [[Importing_Data_to_QPR_ProcessAnalyzer|Data import]] view.
Xes files [http://www.xes-standard.org/#ieee_1849-2016_xes_standard eXtensible Event Stream standard] can be imported to QPR ProcessAnalyzer. The file format is interpreted as follows:
 
* ''Trace entities'' are imported as cases
One .pacm file contains one model including case and event attributes and model specific user rights.
** The immediate child entity of trace entity having '''concept:name''' as the value of key-attribute is imported as the case id.
 
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 [http://www.xes-standard.org/#ieee_1849-2016_xes_standard 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.
** 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.
* Event entities (immediate child entities of trace entities) are imported as events.
Line 34: Line 21:
*** 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.
*** 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.
** 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''': value will be converted into date
** '''Boolean''': value will be converted into boolean
** '''Int''': value will be converted into integer
** '''Float''': value will be converted into double using invariant culture
** '''Id''': value will be converted into GUID
** Other values are converted into string using invariant culture


* All the values listed above support the following value types (also used as names of entities):
== Importing and Exporting .PACM File ==
** '''Date''': the value will be converted into DateTime
QPR ProcessAnalyzer models can be exported into .pacm files (QPR ProcessAnalyzer compressed model file format) in the [[QPR_ProcessAnalyzer_Project_Workspace#Exporting_Model|Workspace]].
** '''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


[[Category: QPR ProcessAnalyzer]]
[[Category: QPR ProcessAnalyzer]]

Latest revision as of 10:48, 25 July 2022

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

Importing Data from CSV File

Data from CSV files can be imported to datatables using the Import dialog in the Workspace.

Export Data to CSV File

Datatable contents can be exported to a CSV file, in opened datatable contents. Click Settings and Export as.. in the Analyze tab.

Chart is able to export data that it's presenting to a CSV file, available in the Visual tab in the chart settings. You can choose to show any process mining objects such as events, cases and event types. When there is lot of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in a dashboard. Chart can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export separately.

Importing .XES File

Xes files eXtensible Event Stream standard can be imported to QPR ProcessAnalyzer. The file format is interpreted 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 case id.
    • 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: value will be converted into date
    • Boolean: value will be converted into boolean
    • Int: value will be converted into integer
    • Float: value will be converted into double using invariant culture
    • Id: value will be converted into GUID
    • Other values are converted into string using invariant culture

Importing and Exporting .PACM File

QPR ProcessAnalyzer models can be exported into .pacm files (QPR ProcessAnalyzer compressed model file format) in the Workspace.

Retrieved from "https://wiki.onqpr.com/pa/index.php?title=Exporting_and_Importing_Data_in_QPR_ProcessAnalyzer&oldid=21544"