Exporting and Importing Data in QPR ProcessAnalyzer

Importing and Exporting .pacm files

QPR ProcessAnalyzer models can be exported into .pacm files. A single .pacm file contains one model including the following data:

• Case and Event attributes in the model.
• Views and 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.

If importing to a different database than from which the model was exported, the following restrictions exist:

• Imported Views and Bookmarks 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 <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.

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.

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.

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 import a model which has more than 300 attributes, all the attributes will be imported but you only have access to the first 300 attributes.

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 Limitations to Numbers in Attribute Values.