Exporting and Importing Data in QPR ProcessAnalyzer: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
m (corrected a link)
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
QPR ProcessAnalyzer allows to import and export data in the following ways.


== Importing and Exporting .pacm files==
== Importing Data from CSV File ==
Data from CSV files can be imported to datatables using the [[Importing_Data_to_Datatable_from_CSV_File|Import dialog in the Workspace]].


QPR ProcessAnalyzer models can be exported into .pacm files. A single .pacm file contains one model including the following data:
== Export Data to CSV File==
*[[Case Attribute|Case]] and [[Event Attribute|Event]] attributes in the model.
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.
*[[Views]] and [[Bookmark|Bookmarks]] for which the user doing the export has at least View rights.
*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.
[[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.


If importing to a different database than from which the model was exported, the following restrictions exist:
== Importing .XES File ==
*Imported Views and Bookmarks are restricted to those that were made by the user that exported the model.
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:
*Model specific user rights are imported if the same UserID-Username combination exists in the target database.
* ''Trace entities'' are imported as cases
*Users with <All> Administrator rights 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.
** 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


For .pacm files created in QPR ProcessAnalyzer 2014.1 (and earlier versions of QPR ProcessAnalyzer), attribute values are not supported in bookmarks but from QPR ProcessAnalyzer 2014.2 onwards, they are supported.
== Importing and Exporting .PACM File ==
QPR ProcessAnalyzer models can be exported into .pacm files (QPR ProcessAnalyzer compressed model file format) in the [[QPR_ProcessAnalyzer_Project_Workspace#Exporting_Model|Workspace]].


Note that the export format has changed in QPR ProcessAnalyzer version 2014.2 and this format is not supported in previous versions. Thus, you cannot import a model exported from QPR ProcessAnalyzer version 2014.2 to an earlier version of QPR ProcessAnalyzer.
[[Category: QPR ProcessAnalyzer]]
 
== Importing and Exporting Attributes ==
 
You can have only 300 case attributes or event attributes in one model in QPR ProcessAnalyzer version 2014.2 onwards. If you try to import more than 300 attributes (i.e. from a model created in a previous version of QPR ProcessAnalyzer), it will fail and you will get an error message.
When exporting attributes, only the first 300 attributes are exported. This limitation does not concern models created in QPR ProcessAnalyzer version 2014.2 onwards, since a new model can never have more than 300 attributes.
 
=== Importing Cost ===
 
During import, case or event cost values are converted to SQL FLOAT type. Cost needs to be numerical, so non-numeric values will be ignored. The column name for cost is 'cost'.
 
For Excel limitations that apply to cost, see [[Attribute Values#Limitations to Numbers in Attribute Values|Limitations to Numbers in Attribute Values]].
 
{{About Version}}
 
[[Category: Models]]

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"