QPR ProcessAnalyzer Wiki - User contributions [en]

SQL Scripting Commands

2015-12-28T08:45:56Z

RiiPekk: 216460

This page lists all the QPR ProcessAnalyzer commands that are supported in scripts. Each command consists of queries, which are explained in the following subsections. 

= --#CallWebService =
Extracts data via Web Service. This command takes one SELECT query as parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are:
; 'Address'
: Defines the URI of the service to call. Mandatory.
; 'Method'
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.
; 'Body'
: Defines the message body text to send to the service. Default value is empty. Optional.
; 'Encoding'
: Defines the encoding method to use. The supported options are listed in [https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx]. Default value is UTF8. Optional.
; 'Timeout'
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.
; 'ExecuteInClientSide'
: Defines whether the web service call is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute in the client side. Supports only data table as the import destination. Default value is FALSE. Optional.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
;<nowiki><other parameters></nowiki>
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.

== Result ==

The result of the request is passed to the script following the CallWebService operation in the following variables:
: <code>@_ResponseText</code> The response text received from the remote server. If there was an error in processing the request, this will contain the received error message. NVARCHAR(MAX).
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT.
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.

== Example ==
<pre>
(SELECT 'Method', 'GET') UNION ALL
(SELECT 'Address', 'http://google.com') UNION ALL
(SELECT 'ContentType', 'application/json') UNION ALL
(SELECT 'Accept', '*/*')
--#CallWebService
PRINT SUBSTRING(@_ResponseText, 1, 50);
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log:

<pre>
Execution duration: 0,753 seconds
Execution Log:
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com
Method: GET
ContentType: application/json
Encoding: Unicode (UTF-8)
Body content length: 0
Timeout: 60000
ExecuteInClientSide: 0
Additional headers: Accept(3)
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200
<nowiki>
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/
</nowiki>
</pre>

= --#Exit =
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'Exit'
: Defines whether to stop the script execution:
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.
: 0 = if a value for the RunScriptId parameter is given, pause the execution of the current script and call the given script, then resume running the current script after the given script ends. If a value for RunScriptId is not given, do not pause or stop execution of the current script.
; 'MessageText'
: Text to be shown to the user after the script execution is finished if the script finished because of the Exit command, i.e. when Exit=1. The default value is "Script execution finished.", which is shown also when the script finished normally, i.e. when Exit=0. The text is also written to the script log.
; 'RunScriptId'
: Optional. The Id of the script to be run. Can be empty. Note that the script can call itself, so be careful not to create a looping script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The Exit command can in effect be used to "call" a script, i.e. run a different script and then return to continue the current script.
<pre>
(SELECT 'Exit', '0') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The Exit command can also be used to "goto" a script, i.e. stop the execution of the current script and run a different script.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example stops the script execution, gives a message, and runs a script with Id 12.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example script fragment checks if the previous ProcessAnalyzer command had any exceptions, and if it did, will goto script with Id 2. If the previous command didn't have any exceptions, the script execution is stopped.
<pre>
DECLARE @ScriptToRun VARCHAR(10)

IF @_ExceptionOccurred = 1
SET @ScriptToRun = '2'
ELSE SET @ScriptToRun = <nowiki>''</nowiki>

(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', @ScriptToRun)
--#Exit
</pre>

= --#GetAnalysis =
Creates an analysis from the data which the preceding SQL statements given as parameters provide. This command can take several queries, one for every analysis to be performed. These queries and analysis results are independent from one another.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.
: The --#GetAnalysis command supports the following analysis types:
: Flowchart Analysis (0)
: Variation Analysis in the Chart Mode (1)
: Path Analysis (3)
: Event Type Analysis in the Chart Mode (4)
: Case Analysis (5)
: Event Analysis (6)
: Event Type Analysis in the Table Mode (7)
: Variation Analysis in the Table Mode (8)
: Duration Analysis (9)
: Profiling Analysis (10)
: User Report (11)
: Operation Log Analysis (12)
: Flow Analysis (13)
: Influence Analysis (14)
: Data Table Analysis (18)
: Model Report (21)
: Project Report (22)
: Data Table Report (23)
: Script Report (24)
: Note that for the analysis types Model Report, Project Report, Data Table Report and Script Report, the information related to deleted models/projects/data tables/scripts is not shown by default but can be configured with parameters to be shown. For more information, see the parameters 'GetAll', 'IncludeDeletedProjects' and 'DeletedModelsOnly' in [[Analysis Parameters|the list of analysis parameters]].
; 'TargetTable'
: The temporary table to which the analysis is to be stored. Note that only table format analyses can be stored to a temporary table. If the specified temporary table already exists in the database then its contents are deleted before storing analysis.
: You can define the 'TargetTable' when using the following analysis types:
: - Case Analysis
: - Event Analysis
: - Event Type Analysis
: - Variation Analysis
: - User Permissions
: - Operation Log
: - Flow Analysis
: - Influence Analysis
: - Integration Table
: - Model Report
: - Project Report
: - Data Table Report
: - Script Report
; 'Show'
: Optional. If TRUE or 1, the analysis is opened after the script is run.
; 'Title'
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'SheetName'
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
Below are listed examples of each supported analysis type using the GetAnalysis command. 
The following example will get a Case analysis and open that analysis with "Case Analysis From Script" as the title on a sheet named "Case Analysis Sheet".
<pre>
(SELECT 'AnalysisType', '5') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'Title', 'Case Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Case Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>

The following example will get an Event analysis, open that analysis with "Analysis Title" as the title on a sheet named "Example Sheet Name", and store the Event analysis results to the "#ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'Title', 'Analysis Title') UNION ALL
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL
(SELECT 'TargetTable', '#ExampleTable')
--#GetAnalysis
</pre>
The following example will get a Duration analysis and open that analysis with "Duration Analysis From Script" as the title on a sheet named "Duration Analysis Sheet".
<pre>
SELECT 'AnalysisType', '9') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'Granularity', '1') UNION ALL
(SELECT 'Title', 'Duration Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Duration Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>
The following example will load data from the "ExampleTable" data table in the "ExampleProject" project and put that data into the "CSV1" table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis
</pre>

The following example will get a Model Report analysis, store the analysis results to a temporary table called "#ModelResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '21') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ModelResult')
--#GetAnalysis
</pre>

The following example will get a Project Report analysis, store the analysis results to a temporary table called "#ProjectResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '22') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ProjectResult')
--#GetAnalysis
</pre>
The following example will get a Data Table Report analysis, store the analysis results to a temporary table called "#DataTableResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Data_Tables|Data Tables]].
<pre>
(SELECT 'AnalysisType', '23') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#DataTableResult')
--#GetAnalysis
</pre>

The following example will get a Script Report analysis, store the analysis results to a temporary table called "#ScriptResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Manage Scripts dialog. For explanations of the columns, see [[Script_Management#Script_Manager|Manage Scripts]].
<pre>
(SELECT 'AnalysisType', '24') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ScriptResult')
--#GetAnalysis
</pre>

= --#ImportCaseAttributes =
Loads Case Attributes from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with an existing target model case attributes. TRUE or any other Integer than "0" = the existing case attributes in the target model are not deleted before import, FALSE or "0" = the existing case attributes of the target model are deleted before the import. If the target model is set to use another model as the [[Model Properties|Case Attribute Model]], those case attributes are not deleted. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> if there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportCaseAttributes command.

= --#ImportDataTable =
Imports data to a Data Table. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that if the query doesn't return any data, the data table is not created.

== Examples ==
The following example will load data from a model and put it into the "AnalysisResult" table and then add that data to the "ExampleTable" data table.
<pre>
SELECT 'START'
--#WriteLog

(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT 'DataLoaded'
--#WriteLog

SELECT count(*) from [#AnalysisResult]
--#WriteLog

(SELECT 'ProjectId', '1') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'Append', '1')
(SELECT * FROM [#AnalysisResult])
--#ImportDataTable
</pre>

The following example will load data from the "ExampleTable" data table in the "ExampleProject" project, put that data into the "CSV1" table and then show the contents of the "CSV" table. In effect, it shows the contents of the "ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis

(SELECT * FROM #CSV1)
(SELECT 'Title', 'CSV Table') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportEvents =
Loads Events from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with the existing target model events. TRUE or any other Integer than "0" = the existing events in the target model are not deleted before import, FALSE or "0" = the existing events of the target model are deleted before the import. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportEvents command.

= --#ImportOdbcQuery =
Extracts data directly from the ODBC data source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters. Columns are extracted as text data.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable': The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''ODBC specific parameters'''
; 'OdbcConnectionString'
: The ODBC driver connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcconnection.connectionstring%28v=vs.110%29.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 OdbcConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings. You can also configure a data source name for connecting to QPR ProcessAnalyzer, for instructions see [[How_to_Configure_an_ODBC_Data_Source_Name_for_Connecting_to_QPR_ProcessAnalyzer|How to Configure an ODBC Data Source Name for Connecting to QPR ProcessAnalyzer]].
; 'OdbcQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Example ==
The following script extracts data from an ODBC using a data source name configured as described in the link above and selects all columns from the table PA_MODEL.
<pre>
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL
(SELECT 'Append', '1')
--#ImportOdbcQuery
</pre>

= --#ImportOleDbQuery =
Extracts data from an OLE DB source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table(i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''OLE DB Query Parameters'''
; 'OleDbConnectionString'
: The OLE DB connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.connectionstring%28v=vs.110%29.aspx OleDbConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings.
; 'OleDbQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an OLE DB source (a sample database called DB1) and selects all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportOleDbQuery

(SELECT * FROM #TABLE) UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table from an OLE DB source and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE')
--#ImportOleDbQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSalesforceQuery =
Extracts data from Salesforce cloud and imports it into a data table as NVARCHAR(MAX) or SQL_VARIANT type data. Note that this command requires the Salesforce username and password to be visible in the script!

This command takes one SELECT query as its parameter.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''Salesforce Query Parameters'''
; 'SalesforceUser'
: Username for the Salesforce cloud.
; 'SalesforcePW'
: Password for the Salesforce cloud.
; 'SalesforceQueryMode'
: Optional. The Salesforce query function to be used. 1 (default) = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_queryall.htm queryall()], 2 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm query()], 3 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describesobject.htm describeSObject()].
; 'SalesforceQuery'
: The query to be run in the Salesforce cloud. Note that "*" cannot be used in the query. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] and [http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm SOQL Reference] for more information. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SalesforceQueryRetries'
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.
; 'SalesforceQueryRetryWait'
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.
; 'SalesforceBatchSize'
: Optional. The number of rows of data the query returns in one batch. Minimum = 200, Maximum = 2000, Default = 500. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] for more information.

== Example ==
The following example will load date data from the "Contact" table in the Salesforce cloud and put that data into the "ExampleDataTable" data table in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact')
--#ImportSalesforceQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSapQuery =
Extracts data from SAP and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters, e.g. "sap:Owner" -> "sap_Owner". Columns are extracted as text data. Note that using this command requires [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|some dlls]] not provided by QPR Software.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.
If the TargetTable parameter is not given, use the following destination parameters:
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''SAP Connection Parameters:'''
; 'SapUser'
: SAP username used to connect to SAP. Mandatory. Corresponds to the "USER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPW'
: Password of the SAP user used to connect to SAP. Mandatory. Corresponds to the "PASSWD" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapClient'
: The SAP backend client. Mandatory. Corresponds to the "CLIENT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapAppServerHost'
: The hostname or IP of the specific SAP application server, to which all connections shall be opened. Mandatory if SapMessageServerHost is not defined. Corresponds to the "ASHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapMessageServerHost'
: The hostname or IP of the SAP system’s message server (central instance). Mandatory if SapAppServerHost is not defined. Corresponds to the "MSHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemNumber'
: The SAP system’s system number. Mandatory if SapSystemID is not defined. Corresponds to the "SYSNR" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemID'
: The SAP system’s three-letter system ID. Mandatory if SapSystemNumber is not defined. Corresponds to the "SYSID" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

'''Other SAP Parameters:'''
; 'SapLanguage'
: SAP language used. Default value is "EN". Optional. Corresponds to the "LANG" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPoolSize'
: The maximum number of RFC connections that this destination will keep in its pool. Default value is "5". Optional. Corresponds to the "POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPeakConnectionsLimit'
: In order to prevent an unlimited number of connections to be opened, you can use this parameter. Default value is "10". Optional. Corresponds to the "MAX_POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapConnectionIdleTimeout'
: If a connection has been idle for more than SapIdleTimeout seconds, it will be closed and removed from the connection pool upon checking for idle connections or pools. Default value is "600". Optional. Corresponds to the "IDLE_TIMEOUT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRouter'
: A list of host names and service names / port numbers for the SAPRouter in the following format: /H/hostname/S/portnumber. Optional. Corresponds to the "SAPROUTER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapLogonGroup'
: The logon group from which the message server shall select an application server. Optional. Corresponds to the "GROUP" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryMode'
: If this number is set to "1", then the query result will have the SAP Table field names as data table column names and actual data rows as rows. If this is set to "3", the query result will get the field descriptions from the SAP query using NO_DATA parameter, i.e. the returned columns are the following (in this order): Field, Type, Description, Length, Offset. Default value is "1". Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryTable'
: Name of the SAP table to be extracted. Specifies the value for the parameter QUERY_TABLE in tab: 'Import' or function module 'rfc_read_table' in SAP. Mandatory. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SapRowcount'
: The maximum amount of rows to fetch. Specifies the value for parameter ROWCOUNT in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRowskips'
: The number of rows to skip. Specifies the value for parameter ROWSKIPS in tab: 'Import' or function module 'rfc_read_table'. in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClause'
: A comma separated list of WHERE clause elements passed for the SapQueryTable. Can be used with or without the SapWhereClauseSelect parameter. If used together with the SapWhereClauseSelect parameter, use the SapWhereClause parameter first. NOTE: The default maximum length for the Where Clause string is 72 characters in SAP, so the recommended maximum length of the SapWhereClause value is also 72 characters. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClauseSelect'
: The SELECT query to be executed in QPR ProcessAnalyzer sandbox. Used with or without the SapWhereClause parameter to pass WHERE clauses to SapQueryTable. If used together with the SapWhereClause parameter, use the SapWhereClause parameter first. The query is expected to return a table with at least one column, as the contents from the rows in the first column of the table are concatenated together to form the WHERE clause in SAP RFC_ReadTable. Therefore, it's recommended to first create the table with the WHERE clauses into a temporary table. In addition, it's recommended to have an order number column in the table and use that in the SELECT query to make sure the WHERE clause elements are concatenated in the correct order. The default maximum length for Where Clause string is 72 characters in SAP, so the recommended maximum length for the WHERE clause string in each row of the table is also 72. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. The contents up to the first 10 rows in the first column of the SELECT query are shown in the QPR ProcessAnalyzer [[Script Log]]. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. 
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.
; 'SapFieldNames'
: A comma separated list of field names for columns to be imported. Default value is empty, resulting in all columns being imported. Specifies the value for parameter FIELDNAME in tab: 'Tables' for table 'FIELDS' for function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapFunction'
: If you define a value for this parameter, then the new value specifies the SAP function that is called inside the #ImportSapQuery command. Optional. The default value is RFC_READ_TABLE. Another possible value is BBP_RFC_READ_TABLE. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.

== Examples ==
The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table in a SAP system and put them into a data table named "SapQueryTableExample".
<pre>
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', 'TRUE') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL
(SELECT 'SapQueryMode', '1') UNION ALL
(SELECT 'SapQueryTable', 'VBAK') UNION ALL
(SELECT 'SapDelimiter', '|') UNION ALL
(SELECT 'SapRowcount', '0') UNION ALL
(SELECT 'SapRowskips', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK')
--#ImportSapQuery
</pre>

The following script will extract values for the VBELN field from the VBAK table where the value of the VBELN field is between 0060000039` and `0060000041. It will also catch possible exceptions when getting the data and print out them on a separate sheet. The extracted data is also shown on its own sheet:
<pre>
(SELECT 'CatchOperationExceptions', '1') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'qpr') UNION ALL
(SELECT 'SapPW', 'demo') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'ExecuteInClientSide', '1') UNION ALL
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

DECLARE @_SuccessOrNot as NVARCHAR(MAX);
SET @_SuccessOrNot = CASE @_ExceptionOccurred
WHEN 1 THEN
'Exception(s) occurred!'
ELSE
'SAP import OK.'
END

SELECT
@_SuccessOrNot as Result,
@_ExceptionOccurred as ExceptionOccurred,
@_ExceptionType as ExceptionType,
@_ExceptionMessage as ExceptionMessage,
@_ExceptionDetails as ExceptionDetails
(SELECT 'SheetName' , 'ExceptionData')
--#ShowReport

(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will return the values for the VBELN, ERDAT, ERZET, ERNAM, NETWR, and WAERK fields from the VBAK table where the value of the VBELN field is between 0060000039 and 0060000041:
<pre>
/* First, create the temporary table that holds the WHERE clause. */
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2

/* Specify the target for the data that the script extracts from SAP */
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters */
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table */
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Show the results */
(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table where the value of the VBELN field is between 0060000039 and 0060000041 and put them into a data table named "SapQueryTableExample". The query is made on the client side.
<pre>
/* First, create the temporary table that holds the WHERE clause.*/
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2

/* Define that the command is executed in the client side.*/
(SELECT 'ExecuteInClientSide', 'True') UNION ALL

/* Specify the data table where the data is imported into.*/
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters.*/
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table.*/
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Create an analysis.*/
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'TargetTable', '#Result')
--#GetAnalysis

/* Show the results.*/
SELECT * FROM #Result
--#ShowReport
</pre>

= --#ImportSqlQuery =
Extracts data from an ADO.NET source (which in this case is the SQL Server database) and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''SQL Query Parameters'''
; 'SqlConnectionString'
: The SQL connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx SqlConnection.ConnectionString Property in Microsoft Development Network] for more information on the connection parameters.
; 'SqlQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an ADO.NET source (a sample database called DB1 on Microsoft SQL Server) and select all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table, and then show the contents of that table.
<pre>
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportSqlQuery

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table in SQL Server database and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')
--#ImportSqlQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#RemoveEvents =
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project.
; 'ModelId' or 'ModelName'
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
The optional database query that returns the event Id's to be removed. Note that if there are several columns in the query, the event Id's have to be in the first column of the query.

== Examples ==
The following example will remove all events in the model with Id "22931" in the project with Id "234".
<pre>
(SELECT 'ProjectId', '234') UNION ALL
(SELECT 'ModelId', '22931')
--#RemoveEvents
</pre>

The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'ModelId', '<ModelId>') UNION ALL
(SELECT 'IncludeEventIds', 'True') UNION ALL
(SELECT 'TargetTable', '#Events')
--#GetAnalysis

(SELECT 'ModelId', '<ModelId>')
(SELECT [Event Id] from [#Events])
--#RemoveEvents
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log, if event Id's to be removed had been specified in the query:
<pre>
Remove events for model id=41 started
Number of events in model (before): 641
Number of events to be removed: 100
Number of events removed: 10
Number of events not found: 90
Number of events in model (after): 631
</pre>
In the log "Number of events to be removed" refers to the number of values (in this case 100) fetched from the first column of the query so that these values can be converted into numeric format.

In case there are no event Id's specified in the query, the script log will show the following entries:
<pre>
Remove events for model id=41 started
Number of events in model (before): 621
Remove all events
Number of events in model (after): 0
</pre>

= --#Run =
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ScriptId'
: Mandatory. The Id of the called script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
== Following Queries ==
The following queries are optional and used for initializing the arguments which are passed to the script to be run. The maximum number of arguments is 10. Each argument is created as a temporary table with names #_Arg1, ... #_Arg10. In the created temporary tables, all columns are of the type SQL Variant. If the column names have not been specified, then "Value_0", "Value_1", etc. are used as column names.
The possible arguments are as follows:
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)
:* #_Arg1, ... #_Arg10: arguments passed to that script

Each argument exists in the called script until the next --#Run command is executed in that script. After the called script has finished, the main script continues its execution.

== Examples ==
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>.

<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL
(SELECT 'TargetTable', '#DataTable1')
--#GetAnalysis

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL
(SELECT 'TargetTable', '#DataTable2')
--#GetAnalysis

(SELECT 'ScriptId', '<ScriptId>')
SELECT * FROM #DataTable1;
SELECT * FROM #DataTable2;
--#Run
</pre>

Then it runs that script with the following parameters: the number of arguments is 2 (that is, @_Argv=2). #_Arg1 takes data from the <DataTableId_1> data table and #_Arg2 from the <DataTableId_2> data table.
<pre>
print 'Number of arguments: ' + cast(@_Argv as varchar(100));

SELECT * from #_Arg1;
(SELECT 'MaximumCount', '0')
--#ShowReport

SELECT * from #_Arg2;
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#SendEmail =
Sends an e-mail and writes a message to script log whether sending the email was successful or not. Script execution continues even when the sending isn't successful.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''E-mail Parameters'''
; 'EmailFrom'
: Defines the from address for this e-mail message. Mandatory.
; 'EmailTo'
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.
; 'EmailSubject'
: Defines the subject of the email. Default value is empty. Optional.
; 'EmailBody'
: Defines the message body. Default value is empty. Optional.
; 'EmailCc'
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailBcc'
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailIsBodyHtml'
: Defines whether the e-mail message body is in HTML. TRUE or any other Integer than "0" = body is in HTML, FALSE or "0" = body is not in HTML. Default value is FALSE. Optional.
; 'EmailSender'
: Defines the sender's address for this e-mail message. Default value is empty. Optional.
; 'EmailReplyTo'
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.
; 'EmailPriority',
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.
; 'EmailDeliveryNotification'
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.
; 'EmailBodyEncoding'
: Defines the encoding used to encode the message body. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.
; 'EmailSubjectEncoding'
: Defines the encoding used for the subject content for this e-mail message. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.

'''SMTP Server Parameters'''
; 'SmtpServer'
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.
; 'SmtpPort'
: Defines the port of the SMTP server. Default value is "25". Optional.
; 'SmtpAuthenticationUsername'
: Defines the user name for the SMTP server. Note that the user name is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpAuthenticationPassword'
: Defines the password for the SMTP server. Note that the password is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpEnableSSL'
: Defines whether SSL should be enabled for the SMTP connection. TRUE or any other Integer than "0" = SSL is enabled, FALSE or "0" = SSL is not enabled. Default value is "FALSE". Optional.

== Example ==
The following example will send an e-mail message to multiple recipients.
<pre>
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL
(SELECT 'SmtpServer', 'localhost')
--#SendEmail
</pre>

See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].

= --#ShowReport =
Creates a new Excel sheet containing a table that contains the results of the user specified SQL query. The result column names are the field names of the SQL query and the rows are the actual data rows of the SQL query. The report can be used to see, for example, the events that would be loaded into QPR ProcessAnalyzer before actually loading them. If the events have problems that cause errors when loaded it is useful to be able to see the row data in a report.
'''Note:''' Excel cannot handle more than 1 million rows to be shown so if the result set contains more rows than that, the data will be truncated to 1 million rows.

This command takes two SELECT queries as parameters.
== First Query ==
A user specified SQL query to be shown in the configured Excel sheet.
; <nowiki>'<data>'</nowiki>
: Mandatory. The database query whose results are to be returned.

== Second Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:
:; 'Title'
:: The title of the created report. If not given, "Report" will be used as a default.
:; 'SheetName'
:: The name of the Excel sheet to be created.
:; 'MaximumCount'
:: The maximum number of rows to show (0 = all, default = 1000).
; 'CatchOperationExceptions': Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Example ==
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'Test') UNION ALL
(SELECT 'DataTableName', 'SqlTable') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT * FROM #AnalysisResult;
(SELECT 'Title', 'Report1') UNION ALL
(SELECT 'SheetName', 'Sheet1') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#WriteLog =
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.

In addition to the WriteLog command, you can also use the [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] to generate log entries into the script execution log. The difference to the WriteLog command is that the Print statement can use also variables.

== Examples ==
The following example will write "Script started", "Example", "Print Example" into the log. Note that the WriteLog command and Print SQL statement represent two different ways of generating log entries, and you can use them also separately.
<pre>
SELECT 'Script started'
SELECT 'Example'
--#WriteLog
PRINT 'Print Example'
</pre>

QPR ProcessAnalyzer Release Notes

2015-12-22T11:35:46Z

RiiPekk: 306596

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite. 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog. 
-306592: Internal and product version numbers have been updated and changes have been made to database version backward compatibility. See [[Version Compatibility Matrix]] for more information. 
-306596: Changes have been made to some of the settings for [[Influence Analysis]]. For example, you can now limit the number of shown top and bottom rows.
 
'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 
-216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

SQL Scripting Commands

2015-12-22T09:26:46Z

RiiPekk: /* Query */

This page lists all the QPR ProcessAnalyzer commands that are supported in scripts. Each command consists of queries, which are explained in the following subsections. 

= --#CallWebService =
Extracts data via Web Service. This command takes one SELECT query as parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are:
; 'Address'
: Defines the URI of the service to call. Mandatory.
; 'Method'
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.
; 'Body'
: Defines the message body text to send to the service. Default value is empty. Optional.
; 'Encoding'
: Defines the encoding method to use. The supported options are listed in [https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx]. Default value is UTF8. Optional.
; 'Timeout'
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.
; 'ExecuteInClientSide'
: Defines whether the web service call is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute in the client side. Supports only data table as the import destination. Default value is FALSE. Optional.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
;<nowiki><other parameters></nowiki>
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.

== Result ==

The result of the request is passed to the script following the CallWebService operation in the following variables:
: <code>@_ResponseText</code> The response text received from the remote server. If there was an error in processing the request, this will contain the received error message. NVARCHAR(MAX).
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT.
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.

== Example ==
<pre>
(SELECT 'Method', 'GET') UNION ALL
(SELECT 'Address', 'http://google.com') UNION ALL
(SELECT 'ContentType', 'application/json') UNION ALL
(SELECT 'Accept', '*/*')
--#CallWebService
PRINT SUBSTRING(@_ResponseText, 1, 50);
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log:

<pre>
Execution duration: 0,753 seconds
Execution Log:
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com
Method: GET
ContentType: application/json
Encoding: Unicode (UTF-8)
Body content length: 0
Timeout: 60000
ExecuteInClientSide: 0
Additional headers: Accept(3)
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200
<nowiki>
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/
</nowiki>
</pre>

= --#Exit =
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'Exit'
: Defines whether to stop the script execution:
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.
: 0 = if a value for the RunScriptId parameter is given, pause the execution of the current script and call the given script, then resume running the current script after the given script ends. If a value for RunScriptId is not given, do not pause or stop execution of the current script.
; 'MessageText'
: Text to be shown to the user after the script execution is finished if the script finished because of the Exit command, i.e. when Exit=1. The default value is "Script execution finished.", which is shown also when the script finished normally, i.e. when Exit=0. The text is also written to the script log.
; 'RunScriptId'
: Optional. The Id of the script to be run. Can be empty. Note that the script can call itself, so be careful not to create a looping script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The Exit command can in effect be used to "call" a script, i.e. run a different script and then return to continue the current script.
<pre>
(SELECT 'Exit', '0') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The Exit command can also be used to "goto" a script, i.e. stop the execution of the current script and run a different script.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example stops the script execution, gives a message, and runs a script with Id 12.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example script fragment checks if the previous ProcessAnalyzer command had any exceptions, and if it did, will goto script with Id 2. If the previous command didn't have any exceptions, the script execution is stopped.
<pre>
DECLARE @ScriptToRun VARCHAR(10)

IF @_ExceptionOccurred = 1
SET @ScriptToRun = '2'
ELSE SET @ScriptToRun = <nowiki>''</nowiki>

(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', @ScriptToRun)
--#Exit
</pre>

= --#GetAnalysis =
Creates an analysis from the data which the preceding SQL statements given as parameters provide. This command can take several queries, one for every analysis to be performed. These queries and analysis results are independent from one another.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.
: The --#GetAnalysis command supports the following analysis types:
: Flowchart Analysis (0)
: Variation Analysis in the Chart Mode (1)
: Path Analysis (3)
: Event Type Analysis in the Chart Mode (4)
: Case Analysis (5)
: Event Analysis (6)
: Event Type Analysis in the Table Mode (7)
: Variation Analysis in the Table Mode (8)
: Duration Analysis (9)
: Profiling Analysis (10)
: User Report (11)
: Operation Log Analysis (12)
: Flow Analysis (13)
: Influence Analysis (14)
: Data Table Analysis (18)
: Model Report (21)
: Project Report (22)
: Data Table Report (23)
: Script Report (24)
: Note that for the analysis types Model Report, Project Report, Data Table Report and Script Report, the information related to deleted models/projects/data tables/scripts is not shown by default but can be configured with parameters to be shown. For more information, see the parameters 'GetAll', 'IncludeDeletedProjects' and 'DeletedModelsOnly' in [[Analysis Parameters|the list of analysis parameters]].
; 'TargetTable'
: The temporary table to which the analysis is to be stored. Note that only table format analyses can be stored to a temporary table. If the specified temporary table already exists in the database then its contents are deleted before storing analysis.
: You can define the 'TargetTable' when using the following analysis types:
: - Case Analysis
: - Event Analysis
: - Event Type Analysis
: - Variation Analysis
: - User Permissions
: - Operation Log
: - Flow Analysis
: - Influence Analysis
: - Integration Table
: - Model Report
: - Project Report
: - Data Table Report
: - Script Report
; 'Show'
: Optional. If TRUE or 1, the analysis is opened after the script is run.
; 'Title'
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'SheetName'
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
Below are listed examples of each supported analysis type using the GetAnalysis command. 
The following example will get a Case analysis and open that analysis with "Case Analysis From Script" as the title on a sheet named "Case Analysis Sheet".
<pre>
(SELECT 'AnalysisType', '5') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'Title', 'Case Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Case Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>

The following example will get an Event analysis, open that analysis with "Analysis Title" as the title on a sheet named "Example Sheet Name", and store the Event analysis results to the "#ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'Title', 'Analysis Title') UNION ALL
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL
(SELECT 'TargetTable', '#ExampleTable')
--#GetAnalysis
</pre>
The following example will get a Duration analysis and open that analysis with "Duration Analysis From Script" as the title on a sheet named "Duration Analysis Sheet".
<pre>
SELECT 'AnalysisType', '9') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'Granularity', '1') UNION ALL
(SELECT 'Title', 'Duration Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Duration Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>

The following example will get a Model Report analysis, store the analysis results to a temporary table called "#ModelResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '21') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ModelResult')
--#GetAnalysis
</pre>

The following example will get a Project Report analysis, store the analysis results to a temporary table called "#ProjectResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '22') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ProjectResult')
--#GetAnalysis
</pre>
The following example will get a Data Table Report analysis, store the analysis results to a temporary table called "#DataTableResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Data_Tables|Data Tables]].
<pre>
(SELECT 'AnalysisType', '23') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#DataTableResult')
--#GetAnalysis
</pre>

The following example will get a Script Report analysis, store the analysis results to a temporary table called "#ScriptResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Manage Scripts dialog. For explanations of the columns, see [[Script_Management#Script_Manager|Manage Scripts]].
<pre>
(SELECT 'AnalysisType', '24') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ScriptResult')
--#GetAnalysis
</pre>

= --#ImportCaseAttributes =
Loads Case Attributes from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with an existing target model case attributes. TRUE or any other Integer than "0" = the existing case attributes in the target model are not deleted before import, FALSE or "0" = the existing case attributes of the target model are deleted before the import. If the target model is set to use another model as the [[Model Properties|Case Attribute Model]], those case attributes are not deleted. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> if there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportCaseAttributes command.

= --#ImportDataTable =
Imports data to a Data Table. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that if the query doesn't return any data, the data table is not created.

== Examples ==
The following example will load data from a model and put it into the "AnalysisResult" table and then add that data to the "ExampleTable" data table.
<pre>
SELECT 'START'
--#WriteLog

(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT 'DataLoaded'
--#WriteLog

SELECT count(*) from [#AnalysisResult]
--#WriteLog

(SELECT 'ProjectId', '1') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'Append', '1')
(SELECT * FROM [#AnalysisResult])
--#ImportDataTable
</pre>

The following example will load data from the "ExampleTable" data table in the "ExampleProject" project, put that data into the "CSV1" table and then show the contents of the "CSV" table. In effect, it shows the contents of the "ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis

(SELECT * FROM #CSV1)
(SELECT 'Title', 'CSV Table') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportEvents =
Loads Events from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with the existing target model events. TRUE or any other Integer than "0" = the existing events in the target model are not deleted before import, FALSE or "0" = the existing events of the target model are deleted before the import. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportEvents command.

= --#ImportOdbcQuery =
Extracts data directly from the ODBC data source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters. Columns are extracted as text data.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable': The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''ODBC specific parameters'''
; 'OdbcConnectionString'
: The ODBC driver connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcconnection.connectionstring%28v=vs.110%29.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 OdbcConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings. You can also configure a data source name for connecting to QPR ProcessAnalyzer, for instructions see [[How_to_Configure_an_ODBC_Data_Source_Name_for_Connecting_to_QPR_ProcessAnalyzer|How to Configure an ODBC Data Source Name for Connecting to QPR ProcessAnalyzer]].
; 'OdbcQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Example ==
The following script extracts data from an ODBC using a data source name configured as described in the link above and selects all columns from the table PA_MODEL.
<pre>
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL
(SELECT 'Append', '1')
--#ImportOdbcQuery
</pre>

= --#ImportOleDbQuery =
Extracts data from an OLE DB source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table(i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''OLE DB Query Parameters'''
; 'OleDbConnectionString'
: The OLE DB connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.connectionstring%28v=vs.110%29.aspx OleDbConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings.
; 'OleDbQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an OLE DB source (a sample database called DB1) and selects all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportOleDbQuery

(SELECT * FROM #TABLE) UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table from an OLE DB source and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE')
--#ImportOleDbQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSalesforceQuery =
Extracts data from Salesforce cloud and imports it into a data table as NVARCHAR(MAX) or SQL_VARIANT type data. Note that this command requires the Salesforce username and password to be visible in the script!

This command takes one SELECT query as its parameter.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''Salesforce Query Parameters'''
; 'SalesforceUser'
: Username for the Salesforce cloud.
; 'SalesforcePW'
: Password for the Salesforce cloud.
; 'SalesforceQueryMode'
: Optional. The Salesforce query function to be used. 1 (default) = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_queryall.htm queryall()], 2 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm query()], 3 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describesobject.htm describeSObject()].
; 'SalesforceQuery'
: The query to be run in the Salesforce cloud. Note that "*" cannot be used in the query. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] and [http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm SOQL Reference] for more information. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SalesforceQueryRetries'
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.
; 'SalesforceQueryRetryWait'
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.
; 'SalesforceBatchSize'
: Optional. The number of rows of data the query returns in one batch. Minimum = 200, Maximum = 2000, Default = 500. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] for more information.

== Example ==
The following example will load date data from the "Contact" table in the Salesforce cloud and put that data into the "ExampleDataTable" data table in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact')
--#ImportSalesforceQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSapQuery =
Extracts data from SAP and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters, e.g. "sap:Owner" -> "sap_Owner". Columns are extracted as text data. Note that using this command requires [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|some dlls]] not provided by QPR Software.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.
If the TargetTable parameter is not given, use the following destination parameters:
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''SAP Connection Parameters:'''
; 'SapUser'
: SAP username used to connect to SAP. Mandatory. Corresponds to the "USER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPW'
: Password of the SAP user used to connect to SAP. Mandatory. Corresponds to the "PASSWD" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapClient'
: The SAP backend client. Mandatory. Corresponds to the "CLIENT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapAppServerHost'
: The hostname or IP of the specific SAP application server, to which all connections shall be opened. Mandatory if SapMessageServerHost is not defined. Corresponds to the "ASHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapMessageServerHost'
: The hostname or IP of the SAP system’s message server (central instance). Mandatory if SapAppServerHost is not defined. Corresponds to the "MSHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemNumber'
: The SAP system’s system number. Mandatory if SapSystemID is not defined. Corresponds to the "SYSNR" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemID'
: The SAP system’s three-letter system ID. Mandatory if SapSystemNumber is not defined. Corresponds to the "SYSID" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

'''Other SAP Parameters:'''
; 'SapLanguage'
: SAP language used. Default value is "EN". Optional. Corresponds to the "LANG" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPoolSize'
: The maximum number of RFC connections that this destination will keep in its pool. Default value is "5". Optional. Corresponds to the "POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPeakConnectionsLimit'
: In order to prevent an unlimited number of connections to be opened, you can use this parameter. Default value is "10". Optional. Corresponds to the "MAX_POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapConnectionIdleTimeout'
: If a connection has been idle for more than SapIdleTimeout seconds, it will be closed and removed from the connection pool upon checking for idle connections or pools. Default value is "600". Optional. Corresponds to the "IDLE_TIMEOUT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRouter'
: A list of host names and service names / port numbers for the SAPRouter in the following format: /H/hostname/S/portnumber. Optional. Corresponds to the "SAPROUTER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapLogonGroup'
: The logon group from which the message server shall select an application server. Optional. Corresponds to the "GROUP" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryMode'
: If this number is set to "1", then the query result will have the SAP Table field names as data table column names and actual data rows as rows. If this is set to "3", the query result will get the field descriptions from the SAP query using NO_DATA parameter, i.e. the returned columns are the following (in this order): Field, Type, Description, Length, Offset. Default value is "1". Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryTable'
: Name of the SAP table to be extracted. Specifies the value for the parameter QUERY_TABLE in tab: 'Import' or function module 'rfc_read_table' in SAP. Mandatory. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SapRowcount'
: The maximum amount of rows to fetch. Specifies the value for parameter ROWCOUNT in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRowskips'
: The number of rows to skip. Specifies the value for parameter ROWSKIPS in tab: 'Import' or function module 'rfc_read_table'. in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClause'
: A comma separated list of WHERE clause elements passed for the SapQueryTable. Can be used with or without the SapWhereClauseSelect parameter. If used together with the SapWhereClauseSelect parameter, use the SapWhereClause parameter first. NOTE: The default maximum length for the Where Clause string is 72 characters in SAP, so the recommended maximum length of the SapWhereClause value is also 72 characters. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClauseSelect'
: The SELECT query to be executed in QPR ProcessAnalyzer sandbox. Used with or without the SapWhereClause parameter to pass WHERE clauses to SapQueryTable. If used together with the SapWhereClause parameter, use the SapWhereClause parameter first. The query is expected to return a table with at least one column, as the contents from the rows in the first column of the table are concatenated together to form the WHERE clause in SAP RFC_ReadTable. Therefore, it's recommended to first create the table with the WHERE clauses into a temporary table. In addition, it's recommended to have an order number column in the table and use that in the SELECT query to make sure the WHERE clause elements are concatenated in the correct order. The default maximum length for Where Clause string is 72 characters in SAP, so the recommended maximum length for the WHERE clause string in each row of the table is also 72. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. The contents up to the first 10 rows in the first column of the SELECT query are shown in the QPR ProcessAnalyzer [[Script Log]]. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. 
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.
; 'SapFieldNames'
: A comma separated list of field names for columns to be imported. Default value is empty, resulting in all columns being imported. Specifies the value for parameter FIELDNAME in tab: 'Tables' for table 'FIELDS' for function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapFunction'
: If you define a value for this parameter, then the new value specifies the SAP function that is called inside the #ImportSapQuery command. Optional. The default value is RFC_READ_TABLE. Another possible value is BBP_RFC_READ_TABLE. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.

== Examples ==
The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table in a SAP system and put them into a data table named "SapQueryTableExample".
<pre>
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', 'TRUE') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL
(SELECT 'SapQueryMode', '1') UNION ALL
(SELECT 'SapQueryTable', 'VBAK') UNION ALL
(SELECT 'SapDelimiter', '|') UNION ALL
(SELECT 'SapRowcount', '0') UNION ALL
(SELECT 'SapRowskips', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK')
--#ImportSapQuery
</pre>

The following script will extract values for the VBELN field from the VBAK table where the value of the VBELN field is between 0060000039` and `0060000041. It will also catch possible exceptions when getting the data and print out them on a separate sheet. The extracted data is also shown on its own sheet:
<pre>
(SELECT 'CatchOperationExceptions', '1') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'qpr') UNION ALL
(SELECT 'SapPW', 'demo') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'ExecuteInClientSide', '1') UNION ALL
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

DECLARE @_SuccessOrNot as NVARCHAR(MAX);
SET @_SuccessOrNot = CASE @_ExceptionOccurred
WHEN 1 THEN
'Exception(s) occurred!'
ELSE
'SAP import OK.'
END

SELECT
@_SuccessOrNot as Result,
@_ExceptionOccurred as ExceptionOccurred,
@_ExceptionType as ExceptionType,
@_ExceptionMessage as ExceptionMessage,
@_ExceptionDetails as ExceptionDetails
(SELECT 'SheetName' , 'ExceptionData')
--#ShowReport

(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will return the values for the VBELN, ERDAT, ERZET, ERNAM, NETWR, and WAERK fields from the VBAK table where the value of the VBELN field is between 0060000039 and 0060000041:
<pre>
/* First, create the temporary table that holds the WHERE clause. */
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2

/* Specify the target for the data that the script extracts from SAP */
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters */
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table */
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Show the results */
(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table where the value of the VBELN field is between 0060000039 and 0060000041 and put them into a data table named "SapQueryTableExample". The query is made on the client side.
<pre>
/* First, create the temporary table that holds the WHERE clause.*/
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2

/* Define that the command is executed in the client side.*/
(SELECT 'ExecuteInClientSide', 'True') UNION ALL

/* Specify the data table where the data is imported into.*/
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters.*/
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table.*/
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Create an analysis.*/
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'TargetTable', '#Result')
--#GetAnalysis

/* Show the results.*/
SELECT * FROM #Result
--#ShowReport
</pre>

= --#ImportSqlQuery =
Extracts data from an ADO.NET source (which in this case is the SQL Server database) and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''SQL Query Parameters'''
; 'SqlConnectionString'
: The SQL connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx SqlConnection.ConnectionString Property in Microsoft Development Network] for more information on the connection parameters.
; 'SqlQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an ADO.NET source (a sample database called DB1 on Microsoft SQL Server) and select all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table, and then show the contents of that table.
<pre>
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportSqlQuery

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table in SQL Server database and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')
--#ImportSqlQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#RemoveEvents =
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project.
; 'ModelId' or 'ModelName'
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
The optional database query that returns the event Id's to be removed. Note that if there are several columns in the query, the event Id's have to be in the first column of the query.

== Examples ==
The following example will remove all events in the model with Id "22931" in the project with Id "234".
<pre>
(SELECT 'ProjectId', '234') UNION ALL
(SELECT 'ModelId', '22931')
--#RemoveEvents
</pre>

The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'ModelId', '<ModelId>') UNION ALL
(SELECT 'IncludeEventIds', 'True') UNION ALL
(SELECT 'TargetTable', '#Events')
--#GetAnalysis

(SELECT 'ModelId', '<ModelId>')
(SELECT [Event Id] from [#Events])
--#RemoveEvents
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log, if event Id's to be removed had been specified in the query:
<pre>
Remove events for model id=41 started
Number of events in model (before): 641
Number of events to be removed: 100
Number of events removed: 10
Number of events not found: 90
Number of events in model (after): 631
</pre>
In the log "Number of events to be removed" refers to the number of values (in this case 100) fetched from the first column of the query so that these values can be converted into numeric format.

In case there are no event Id's specified in the query, the script log will show the following entries:
<pre>
Remove events for model id=41 started
Number of events in model (before): 621
Remove all events
Number of events in model (after): 0
</pre>

= --#Run =
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ScriptId'
: Mandatory. The Id of the called script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
== Following Queries ==
The following queries are optional and used for initializing the arguments which are passed to the script to be run. The maximum number of arguments is 10. Each argument is created as a temporary table with names #_Arg1, ... #_Arg10. In the created temporary tables, all columns are of the type SQL Variant. If the column names have not been specified, then "Value_0", "Value_1", etc. are used as column names.
The possible arguments are as follows:
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)
:* #_Arg1, ... #_Arg10: arguments passed to that script

Each argument exists in the called script until the next --#Run command is executed in that script. After the called script has finished, the main script continues its execution.

== Examples ==
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>.

<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL
(SELECT 'TargetTable', '#DataTable1')
--#GetAnalysis

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL
(SELECT 'TargetTable', '#DataTable2')
--#GetAnalysis

(SELECT 'ScriptId', '<ScriptId>')
SELECT * FROM #DataTable1;
SELECT * FROM #DataTable2;
--#Run
</pre>

Then it runs that script with the following parameters: the number of arguments is 2 (that is, @_Argv=2). #_Arg1 takes data from the <DataTableId_1> data table and #_Arg2 from the <DataTableId_2> data table.
<pre>
print 'Number of arguments: ' + cast(@_Argv as varchar(100));

SELECT * from #_Arg1;
(SELECT 'MaximumCount', '0')
--#ShowReport

SELECT * from #_Arg2;
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#SendEmail =
Sends an e-mail and writes a message to script log whether sending the email was successful or not. Script execution continues even when the sending isn't successful.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''E-mail Parameters'''
; 'EmailFrom'
: Defines the from address for this e-mail message. Mandatory.
; 'EmailTo'
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.
; 'EmailSubject'
: Defines the subject of the email. Default value is empty. Optional.
; 'EmailBody'
: Defines the message body. Default value is empty. Optional.
; 'EmailCc'
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailBcc'
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailIsBodyHtml'
: Defines whether the e-mail message body is in HTML. TRUE or any other Integer than "0" = body is in HTML, FALSE or "0" = body is not in HTML. Default value is FALSE. Optional.
; 'EmailSender'
: Defines the sender's address for this e-mail message. Default value is empty. Optional.
; 'EmailReplyTo'
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.
; 'EmailPriority',
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.
; 'EmailDeliveryNotification'
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.
; 'EmailBodyEncoding'
: Defines the encoding used to encode the message body. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.
; 'EmailSubjectEncoding'
: Defines the encoding used for the subject content for this e-mail message. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.

'''SMTP Server Parameters'''
; 'SmtpServer'
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.
; 'SmtpPort'
: Defines the port of the SMTP server. Default value is "25". Optional.
; 'SmtpAuthenticationUsername'
: Defines the user name for the SMTP server. Note that the user name is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpAuthenticationPassword'
: Defines the password for the SMTP server. Note that the password is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpEnableSSL'
: Defines whether SSL should be enabled for the SMTP connection. TRUE or any other Integer than "0" = SSL is enabled, FALSE or "0" = SSL is not enabled. Default value is "FALSE". Optional.

== Example ==
The following example will send an e-mail message to multiple recipients.
<pre>
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL
(SELECT 'SmtpServer', 'localhost')
--#SendEmail
</pre>

See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].

= --#ShowReport =
Creates a new Excel sheet containing a table that contains the results of the user specified SQL query. The result column names are the field names of the SQL query and the rows are the actual data rows of the SQL query. The report can be used to see, for example, the events that would be loaded into QPR ProcessAnalyzer before actually loading them. If the events have problems that cause errors when loaded it is useful to be able to see the row data in a report.
'''Note:''' Excel cannot handle more than 1 million rows to be shown so if the result set contains more rows than that, the data will be truncated to 1 million rows.

This command takes two SELECT queries as parameters.
== First Query ==
A user specified SQL query to be shown in the configured Excel sheet.
; <nowiki>'<data>'</nowiki>
: Mandatory. The database query whose results are to be returned.

== Second Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:
:; 'Title'
:: The title of the created report. If not given, "Report" will be used as a default.
:; 'SheetName'
:: The name of the Excel sheet to be created.
:; 'MaximumCount'
:: The maximum number of rows to show (0 = all, default = 1000).
; 'CatchOperationExceptions': Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Example ==
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'Test') UNION ALL
(SELECT 'DataTableName', 'SqlTable') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT * FROM #AnalysisResult;
(SELECT 'Title', 'Report1') UNION ALL
(SELECT 'SheetName', 'Sheet1') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#WriteLog =
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.

In addition to the WriteLog command, you can also use the [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] to generate log entries into the script execution log. The difference to the WriteLog command is that the Print statement can use also variables.

== Examples ==
The following example will write "Script started", "Example", "Print Example" into the log. Note that the WriteLog command and Print SQL statement represent two different ways of generating log entries, and you can use them also separately.
<pre>
SELECT 'Script started'
SELECT 'Example'
--#WriteLog
PRINT 'Print Example'
</pre>

SQL Scripting Commands

2015-12-22T08:27:12Z

RiiPekk: 216460

This page lists all the QPR ProcessAnalyzer commands that are supported in scripts. Each command consists of queries, which are explained in the following subsections. 

= --#CallWebService =
Extracts data via Web Service. This command takes one SELECT query as parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are:
; 'Address'
: Defines the URI of the service to call. Mandatory.
; 'Method'
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.
; 'Body'
: Defines the message body text to send to the service. Default value is empty. Optional.
; 'Encoding'
: Defines the encoding method to use. The supported options are listed in [https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx]. Default value is UTF8. Optional.
; 'Timeout'
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.
; 'ExecuteInClientSide'
: Defines whether the web service call is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute in the client side. Supports only data table as the import destination. Default value is FALSE. Optional.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
;<nowiki><other parameters></nowiki>
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.

== Result ==

The result of the request is passed to the script following the CallWebService operation in the following variables:
: <code>@_ResponseText</code> The response text received from the remote server. If there was an error in processing the request, this will contain the received error message. NVARCHAR(MAX).
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT.
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.

== Example ==
<pre>
(SELECT 'Method', 'GET') UNION ALL
(SELECT 'Address', 'http://google.com') UNION ALL
(SELECT 'ContentType', 'application/json') UNION ALL
(SELECT 'Accept', '*/*')
--#CallWebService
PRINT SUBSTRING(@_ResponseText, 1, 50);
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log:

<pre>
Execution duration: 0,753 seconds
Execution Log:
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com
Method: GET
ContentType: application/json
Encoding: Unicode (UTF-8)
Body content length: 0
Timeout: 60000
ExecuteInClientSide: 0
Additional headers: Accept(3)
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200
<nowiki>
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/
</nowiki>
</pre>

= --#Exit =
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'Exit'
: Defines whether to stop the script execution:
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.
: 0 = if a value for the RunScriptId parameter is given, pause the execution of the current script and call the given script, then resume running the current script after the given script ends. If a value for RunScriptId is not given, do not pause or stop execution of the current script.
; 'MessageText'
: Text to be shown to the user after the script execution is finished if the script finished because of the Exit command, i.e. when Exit=1. The default value is "Script execution finished.", which is shown also when the script finished normally, i.e. when Exit=0. The text is also written to the script log.
; 'RunScriptId'
: Optional. The Id of the script to be run. Can be empty. Note that the script can call itself, so be careful not to create a looping script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The Exit command can in effect be used to "call" a script, i.e. run a different script and then return to continue the current script.
<pre>
(SELECT 'Exit', '0') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The Exit command can also be used to "goto" a script, i.e. stop the execution of the current script and run a different script.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example stops the script execution, gives a message, and runs a script with Id 12.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example script fragment checks if the previous ProcessAnalyzer command had any exceptions, and if it did, will goto script with Id 2. If the previous command didn't have any exceptions, the script execution is stopped.
<pre>
DECLARE @ScriptToRun VARCHAR(10)

IF @_ExceptionOccurred = 1
SET @ScriptToRun = '2'
ELSE SET @ScriptToRun = <nowiki>''</nowiki>

(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', @ScriptToRun)
--#Exit
</pre>

= --#GetAnalysis =
Creates an analysis from the data which the preceding SQL statements given as parameters provide. This command can take several queries, one for every analysis to be performed. These queries and analysis results are independent from one another.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.
: The --#GetAnalysis command supports the following analysis types:
: Flowchart Analysis (0)
: Variation Analysis in the Chart Mode (1)
: Path Analysis (3)
: Event Type Analysis in the Chart Mode (4)
: Case Analysis (5)
: Event Analysis (6)
: Event Type Analysis in the Table Mode (7)
: Variation Analysis in the Table Mode (8)
: Duration Analysis (9)
: Profiling Analysis (10)
: User Report (11)
: Operation Log Analysis (12)
: Flow Analysis (13)
: Influence Analysis (14)
: Data Table Analysis (18)
: Model Report (21)
: Project Report (22)
: Data Table Report (23)
: Script Report (24)
: Note that for the analysis types Model Report, Project Report, Data Table Report and Script Report, the information related to deleted models/projects/data tables/scripts is not shown by default but can be configured with parameters to be shown. For more information, see the parameters 'GetAll', 'IncludeDeletedProjects' and 'DeletedModelsOnly' in [[Analysis Parameters|the list of analysis parameters]].
; 'TargetTable'
: The temporary table to which the analysis is to be stored. Note that only table format analyses can be stored to a temporary table. If the specified temporary table already exists in the database then it's contents are deleted before storing analysis.
: You can define the 'TargetTable' when using the following analysis types:
: - Case Analysis
: - Event Analysis
: - Event Type Analysis
: - Variation Analysis
: - User Permissions
: - Operation Log
: - Flow Analysis
: - Influence Analysis
: - Integration Table
: - Model Report
: - Project Report
: - Data Table Report
: - Script Report
; 'Show'
: Optional. If TRUE or 1, the analysis is opened after the script is run.
; 'Title'
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'SheetName'
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
Below are listed examples of each supported analysis type using the GetAnalysis command. 
The following example will get a Case analysis and open that analysis with "Case Analysis From Script" as the title on a sheet named "Case Analysis Sheet".
<pre>
(SELECT 'AnalysisType', '5') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'Title', 'Case Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Case Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>

The following example will get an Event analysis, open that analysis with "Analysis Title" as the title on a sheet named "Example Sheet Name", and store the Event analysis results to the "#ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'Title', 'Analysis Title') UNION ALL
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL
(SELECT 'TargetTable', '#ExampleTable')
--#GetAnalysis
</pre>
The following example will get a Duration analysis and open that analysis with "Duration Analysis From Script" as the title on a sheet named "Duration Analysis Sheet".
<pre>
SELECT 'AnalysisType', '9') UNION ALL
(SELECT 'ProjectName', '<ProjectName>') UNION ALL
(SELECT 'ModelName', '<ModelName>') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'Granularity', '1') UNION ALL
(SELECT 'Title', 'Duration Analysis From Script') UNION ALL
(SELECT 'SheetName', 'Duration Analysis Sheet') UNION ALL
(SELECT 'Show', 'True')
--#GetAnalysis
</pre>

The following example will get a Model Report analysis, store the analysis results to a temporary table called "#ModelResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '21') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ModelResult')
--#GetAnalysis
</pre>

The following example will get a Project Report analysis, store the analysis results to a temporary table called "#ProjectResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '22') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ProjectResult')
--#GetAnalysis
</pre>
The following example will get a Data Table Report analysis, store the analysis results to a temporary table called "#DataTableResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Data_Tables|Data Tables]].
<pre>
(SELECT 'AnalysisType', '23') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#DataTableResult')
--#GetAnalysis
</pre>

The following example will get a Script Report analysis, store the analysis results to a temporary table called "#ScriptResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Manage Scripts dialog. For explanations of the columns, see [[Script_Management#Script_Manager|Manage Scripts]].
<pre>
(SELECT 'AnalysisType', '24') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ScriptResult')
--#GetAnalysis
</pre>

= --#ImportCaseAttributes =
Loads Case Attributes from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with an existing target model case attributes. TRUE or any other Integer than "0" = the existing case attributes in the target model are not deleted before import, FALSE or "0" = the existing case attributes of the target model are deleted before the import. If the target model is set to use another model as the [[Model Properties|Case Attribute Model]], those case attributes are not deleted. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> if there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportCaseAttributes command.

= --#ImportDataTable =
Imports data to a Data Table. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that if the query doesn't return any data, the data table is not created.

== Examples ==
The following example will load data from a model and put it into the "AnalysisResult" table and then add that data to the "ExampleTable" data table.
<pre>
SELECT 'START'
--#WriteLog

(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT 'DataLoaded'
--#WriteLog

SELECT count(*) from [#AnalysisResult]
--#WriteLog

(SELECT 'ProjectId', '1') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'Append', '1')
(SELECT * FROM [#AnalysisResult])
--#ImportDataTable
</pre>

The following example will load data from the "ExampleTable" data table in the "ExampleProject" project, put that data into the "CSV1" table and then show the contents of the "CSV" table. In effect, it shows the contents of the "ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis

(SELECT * FROM #CSV1)
(SELECT 'Title', 'CSV Table') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportEvents =
Loads Events from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with the existing target model events. TRUE or any other Integer than "0" = the existing events in the target model are not deleted before import, FALSE or "0" = the existing events of the target model are deleted before the import. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportEvents command.

= --#ImportOdbcQuery =
Extracts data directly from the ODBC data source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters. Columns are extracted as text data.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable': The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''ODBC specific parameters'''
; 'OdbcConnectionString'
: The ODBC driver connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcconnection.connectionstring%28v=vs.110%29.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 OdbcConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings. You can also configure a data source name for connecting to QPR ProcessAnalyzer, for instructions see [[How_to_Configure_an_ODBC_Data_Source_Name_for_Connecting_to_QPR_ProcessAnalyzer|How to Configure an ODBC Data Source Name for Connecting to QPR ProcessAnalyzer]].
; 'OdbcQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Example ==
The following script extracts data from an ODBC using a data source name configured as described in the link above and selects all columns from the table PA_MODEL.
<pre>
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL
(SELECT 'Append', '1')
--#ImportOdbcQuery
</pre>

= --#ImportOleDbQuery =
Extracts data from an OLE DB source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table(i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''OLE DB Query Parameters'''
; 'OleDbConnectionString'
: The OLE DB connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.connectionstring%28v=vs.110%29.aspx OleDbConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings.
; 'OleDbQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an OLE DB source (a sample database called DB1) and selects all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportOleDbQuery

(SELECT * FROM #TABLE) UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table from an OLE DB source and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE')
--#ImportOleDbQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSalesforceQuery =
Extracts data from Salesforce cloud and imports it into a data table as NVARCHAR(MAX) or SQL_VARIANT type data. Note that this command requires the Salesforce username and password to be visible in the script!

This command takes one SELECT query as its parameter.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''Salesforce Query Parameters'''
; 'SalesforceUser'
: Username for the Salesforce cloud.
; 'SalesforcePW'
: Password for the Salesforce cloud.
; 'SalesforceQueryMode'
: Optional. The Salesforce query function to be used. 1 (default) = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_queryall.htm queryall()], 2 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm query()], 3 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describesobject.htm describeSObject()].
; 'SalesforceQuery'
: The query to be run in the Salesforce cloud. Note that "*" cannot be used in the query. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] and [http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm SOQL Reference] for more information. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SalesforceQueryRetries'
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.
; 'SalesforceQueryRetryWait'
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.
; 'SalesforceBatchSize'
: Optional. The number of rows of data the query returns in one batch. Minimum = 200, Maximum = 2000, Default = 500. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] for more information.

== Example ==
The following example will load date data from the "Contact" table in the Salesforce cloud and put that data into the "ExampleDataTable" data table in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact')
--#ImportSalesforceQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSapQuery =
Extracts data from SAP and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters, e.g. "sap:Owner" -> "sap_Owner". Columns are extracted as text data. Note that using this command requires [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|some dlls]] not provided by QPR Software.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.
If the TargetTable parameter is not given, use the following destination parameters:
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''SAP Connection Parameters:'''
; 'SapUser'
: SAP username used to connect to SAP. Mandatory. Corresponds to the "USER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPW'
: Password of the SAP user used to connect to SAP. Mandatory. Corresponds to the "PASSWD" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapClient'
: The SAP backend client. Mandatory. Corresponds to the "CLIENT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapAppServerHost'
: The hostname or IP of the specific SAP application server, to which all connections shall be opened. Mandatory if SapMessageServerHost is not defined. Corresponds to the "ASHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapMessageServerHost'
: The hostname or IP of the SAP system’s message server (central instance). Mandatory if SapAppServerHost is not defined. Corresponds to the "MSHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemNumber'
: The SAP system’s system number. Mandatory if SapSystemID is not defined. Corresponds to the "SYSNR" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemID'
: The SAP system’s three-letter system ID. Mandatory if SapSystemNumber is not defined. Corresponds to the "SYSID" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

'''Other SAP Parameters:'''
; 'SapLanguage'
: SAP language used. Default value is "EN". Optional. Corresponds to the "LANG" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPoolSize'
: The maximum number of RFC connections that this destination will keep in its pool. Default value is "5". Optional. Corresponds to the "POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPeakConnectionsLimit'
: In order to prevent an unlimited number of connections to be opened, you can use this parameter. Default value is "10". Optional. Corresponds to the "MAX_POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapConnectionIdleTimeout'
: If a connection has been idle for more than SapIdleTimeout seconds, it will be closed and removed from the connection pool upon checking for idle connections or pools. Default value is "600". Optional. Corresponds to the "IDLE_TIMEOUT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRouter'
: A list of host names and service names / port numbers for the SAPRouter in the following format: /H/hostname/S/portnumber. Optional. Corresponds to the "SAPROUTER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapLogonGroup'
: The logon group from which the message server shall select an application server. Optional. Corresponds to the "GROUP" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryMode'
: If this number is set to "1", then the query result will have the SAP Table field names as data table column names and actual data rows as rows. If this is set to "3", the query result will get the field descriptions from the SAP query using NO_DATA parameter, i.e. the returned columns are the following (in this order): Field, Type, Description, Length, Offset. Default value is "1". Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryTable'
: Name of the SAP table to be extracted. Specifies the value for the parameter QUERY_TABLE in tab: 'Import' or function module 'rfc_read_table' in SAP. Mandatory. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SapRowcount'
: The maximum amount of rows to fetch. Specifies the value for parameter ROWCOUNT in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRowskips'
: The number of rows to skip. Specifies the value for parameter ROWSKIPS in tab: 'Import' or function module 'rfc_read_table'. in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClause'
: A comma separated list of WHERE clause elements passed for the SapQueryTable. Can be used with or without the SapWhereClauseSelect parameter. If used together with the SapWhereClauseSelect parameter, use the SapWhereClause parameter first. NOTE: The default maximum length for the Where Clause string is 72 characters in SAP, so the recommended maximum length of the SapWhereClause value is also 72 characters. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClauseSelect'
: The SELECT query to be executed in QPR ProcessAnalyzer sandbox. Used with or without the SapWhereClause parameter to pass WHERE clauses to SapQueryTable. If used together with the SapWhereClause parameter, use the SapWhereClause parameter first. The query is expected to return a table with at least one column, as the contents from the rows in the first column of the table are concatenated together to form the WHERE clause in SAP RFC_ReadTable. Therefore, it's recommended to first create the table with the WHERE clauses into a temporary table. In addition, it's recommended to have an order number column in the table and use that in the SELECT query to make sure the WHERE clause elements are concatenated in the correct order. The default maximum length for Where Clause string is 72 characters in SAP, so the recommended maximum length for the WHERE clause string in each row of the table is also 72. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. The contents up to the first 10 rows in the first column of the SELECT query are shown in the QPR ProcessAnalyzer [[Script Log]]. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. 
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.
; 'SapFieldNames'
: A comma separated list of field names for columns to be imported. Default value is empty, resulting in all columns being imported. Specifies the value for parameter FIELDNAME in tab: 'Tables' for table 'FIELDS' for function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapFunction'
: If you define a value for this parameter, then the new value specifies the SAP function that is called inside the #ImportSapQuery command. Optional. The default value is RFC_READ_TABLE. Another possible value is BBP_RFC_READ_TABLE. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.

== Examples ==
The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table in a SAP system and put them into a data table named "SapQueryTableExample".
<pre>
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', 'TRUE') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL
(SELECT 'SapQueryMode', '1') UNION ALL
(SELECT 'SapQueryTable', 'VBAK') UNION ALL
(SELECT 'SapDelimiter', '|') UNION ALL
(SELECT 'SapRowcount', '0') UNION ALL
(SELECT 'SapRowskips', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK')
--#ImportSapQuery
</pre>

The following script will extract values for the VBELN field from the VBAK table where the value of the VBELN field is between 0060000039` and `0060000041. It will also catch possible exceptions when getting the data and print out them on a separate sheet. The extracted data is also shown on its own sheet:
<pre>
(SELECT 'CatchOperationExceptions', '1') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'qpr') UNION ALL
(SELECT 'SapPW', 'demo') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'ExecuteInClientSide', '1') UNION ALL
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

DECLARE @_SuccessOrNot as NVARCHAR(MAX);
SET @_SuccessOrNot = CASE @_ExceptionOccurred
WHEN 1 THEN
'Exception(s) occurred!'
ELSE
'SAP import OK.'
END

SELECT
@_SuccessOrNot as Result,
@_ExceptionOccurred as ExceptionOccurred,
@_ExceptionType as ExceptionType,
@_ExceptionMessage as ExceptionMessage,
@_ExceptionDetails as ExceptionDetails
(SELECT 'SheetName' , 'ExceptionData')
--#ShowReport

(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will return the values for the VBELN, ERDAT, ERZET, ERNAM, NETWR, and WAERK fields from the VBAK table where the value of the VBELN field is between 0060000039 and 0060000041:
<pre>
/* First, create the temporary table that holds the WHERE clause. */
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2

/* Specify the target for the data that the script extracts from SAP */
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters */
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table */
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Show the results */
(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table where the value of the VBELN field is between 0060000039 and 0060000041 and put them into a data table named "SapQueryTableExample". The query is made on the client side.
<pre>
/* First, create the temporary table that holds the WHERE clause.*/
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2

/* Define that the command is executed in the client side.*/
(SELECT 'ExecuteInClientSide', 'True') UNION ALL

/* Specify the data table where the data is imported into.*/
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters.*/
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table.*/
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Create an analysis.*/
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'TargetTable', '#Result')
--#GetAnalysis

/* Show the results.*/
SELECT * FROM #Result
--#ShowReport
</pre>

= --#ImportSqlQuery =
Extracts data from an ADO.NET source (which in this case is the SQL Server database) and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''SQL Query Parameters'''
; 'SqlConnectionString'
: The SQL connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx SqlConnection.ConnectionString Property in Microsoft Development Network] for more information on the connection parameters.
; 'SqlQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an ADO.NET source (a sample database called DB1 on Microsoft SQL Server) and select all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table, and then show the contents of that table.
<pre>
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1')
--#ImportSqlQuery

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table in SQL Server database and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')
--#ImportSqlQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#RemoveEvents =
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project.
; 'ModelId' or 'ModelName'
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
The optional database query that returns the event Id's to be removed. Note that if there are several columns in the query, the event Id's have to be in the first column of the query.

== Examples ==
The following example will remove all events in the model with Id "22931" in the project with Id "234".
<pre>
(SELECT 'ProjectId', '234') UNION ALL
(SELECT 'ModelId', '22931')
--#RemoveEvents
</pre>

The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'ModelId', '<ModelId>') UNION ALL
(SELECT 'IncludeEventIds', 'True') UNION ALL
(SELECT 'TargetTable', '#Events')
--#GetAnalysis

(SELECT 'ModelId', '<ModelId>')
(SELECT [Event Id] from [#Events])
--#RemoveEvents
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log, if event Id's to be removed had been specified in the query:
<pre>
Remove events for model id=41 started
Number of events in model (before): 641
Number of events to be removed: 100
Number of events removed: 10
Number of events not found: 90
Number of events in model (after): 631
</pre>
In the log "Number of events to be removed" refers to the number of values (in this case 100) fetched from the first column of the query so that these values can be converted into numeric format.

In case there are no event Id's specified in the query, the script log will show the following entries:
<pre>
Remove events for model id=41 started
Number of events in model (before): 621
Remove all events
Number of events in model (after): 0
</pre>

= --#Run =
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ScriptId'
: Mandatory. The Id of the called script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
== Following Queries ==
The following queries are optional and used for initializing the arguments which are passed to the script to be run. The maximum number of arguments is 10. Each argument is created as a temporary table with names #_Arg1, ... #_Arg10. In the created temporary tables, all columns are of the type SQL Variant. If the column names have not been specified, then "Value_0", "Value_1", etc. are used as column names.
The possible arguments are as follows:
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)
:* #_Arg1, ... #_Arg10: arguments passed to that script

Each argument exists in the called script until the next --#Run command is executed in that script. After the called script has finished, the main script continues its execution.

== Examples ==
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>.

<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL
(SELECT 'TargetTable', '#DataTable1')
--#GetAnalysis

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL
(SELECT 'TargetTable', '#DataTable2')
--#GetAnalysis

(SELECT 'ScriptId', '<ScriptId>')
SELECT * FROM #DataTable1;
SELECT * FROM #DataTable2;
--#Run
</pre>

Then it runs that script with the following parameters: the number of arguments is 2 (that is, @_Argv=2). #_Arg1 takes data from the <DataTableId_1> data table and #_Arg2 from the <DataTableId_2> data table.
<pre>
print 'Number of arguments: ' + cast(@_Argv as varchar(100));

SELECT * from #_Arg1;
(SELECT 'MaximumCount', '0')
--#ShowReport

SELECT * from #_Arg2;
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#SendEmail =
Sends an e-mail and writes a message to script log whether sending the email was successful or not. Script execution continues even when the sending isn't successful.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''E-mail Parameters'''
; 'EmailFrom'
: Defines the from address for this e-mail message. Mandatory.
; 'EmailTo'
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.
; 'EmailSubject'
: Defines the subject of the email. Default value is empty. Optional.
; 'EmailBody'
: Defines the message body. Default value is empty. Optional.
; 'EmailCc'
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailBcc'
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailIsBodyHtml'
: Defines whether the e-mail message body is in HTML. TRUE or any other Integer than "0" = body is in HTML, FALSE or "0" = body is not in HTML. Default value is FALSE. Optional.
; 'EmailSender'
: Defines the sender's address for this e-mail message. Default value is empty. Optional.
; 'EmailReplyTo'
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.
; 'EmailPriority',
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.
; 'EmailDeliveryNotification'
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.
; 'EmailBodyEncoding'
: Defines the encoding used to encode the message body. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.
; 'EmailSubjectEncoding'
: Defines the encoding used for the subject content for this e-mail message. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.

'''SMTP Server Parameters'''
; 'SmtpServer'
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.
; 'SmtpPort'
: Defines the port of the SMTP server. Default value is "25". Optional.
; 'SmtpAuthenticationUsername'
: Defines the user name for the SMTP server. Note that the user name is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpAuthenticationPassword'
: Defines the password for the SMTP server. Note that the password is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpEnableSSL'
: Defines whether SSL should be enabled for the SMTP connection. TRUE or any other Integer than "0" = SSL is enabled, FALSE or "0" = SSL is not enabled. Default value is "FALSE". Optional.

== Example ==
The following example will send an e-mail message to multiple recipients.
<pre>
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL
(SELECT 'SmtpServer', 'localhost')
--#SendEmail
</pre>

See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].

= --#ShowReport =
Creates a new Excel sheet containing a table that contains the results of the user specified SQL query. The result column names are the field names of the SQL query and the rows are the actual data rows of the SQL query. The report can be used to see, for example, the events that would be loaded into QPR ProcessAnalyzer before actually loading them. If the events have problems that cause errors when loaded it is useful to be able to see the row data in a report.
'''Note:''' Excel cannot handle more than 1 million rows to be shown so if the result set contains more rows than that, the data will be truncated to 1 million rows.

This command takes two SELECT queries as parameters.
== First Query ==
A user specified SQL query to be shown in the configured Excel sheet.
; <nowiki>'<data>'</nowiki>
: Mandatory. The database query whose results are to be returned.

== Second Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:
:; 'Title'
:: The title of the created report. If not given, "Report" will be used as a default.
:; 'SheetName'
:: The name of the Excel sheet to be created.
:; 'MaximumCount'
:: The maximum number of rows to show (0 = all, default = 1000).
; 'CatchOperationExceptions': Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Example ==
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'Test') UNION ALL
(SELECT 'DataTableName', 'SqlTable') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT * FROM #AnalysisResult;
(SELECT 'Title', 'Report1') UNION ALL
(SELECT 'SheetName', 'Sheet1') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#WriteLog =
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.

In addition to the WriteLog command, you can also use the [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] to generate log entries into the script execution log. The difference to the WriteLog command is that the Print statement can use also variables.

== Examples ==
The following example will write "Script started", "Example", "Print Example" into the log. Note that the WriteLog command and Print SQL statement represent two different ways of generating log entries, and you can use them also separately.
<pre>
SELECT 'Script started'
SELECT 'Example'
--#WriteLog
PRINT 'Print Example'
</pre>

QPR ProcessAnalyzer Release Notes

2015-12-21T08:47:32Z

RiiPekk: 216770

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite. 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog. 
-306592: Internal and product version numbers have been updated and changes have been made to database version backward compatibility. See [[Version Compatibility Matrix]] for more information. 
-306596: Changes have been made to some of the default values for [[Influence Analysis]]. For example, the default subset number has been increased to 999.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 
-216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer System Requirements

2015-12-16T10:15:35Z

RiiPekk: 306474

__TOC__

== System Requirements for QPR ProcessAnalyzer Excel Client ==

The System Requirements for QPR ProcessAnalyzer Excel Client are:
*Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system
**Mac users need to use Windows as a pure virtual machine, created on e.g. [http://www.parallels.com/products/desktop/ Parallels Desktop] or [http://www.vmware.com/products/fusion/overview.html VMware Fusion], or as a virtualized Boot Camp partition created by either one.
*Microsoft Office 2007, 2010, 2013, or 2016.
*Internet connection for connecting to QPR ProcessAnalyzer Service
*The sapnco.dll and sapnco_utils.dll files distributed in the [http://service.sap.com/connectors SAP Connector for Microsoft .NET Version 3.0 (requires SAP Service Marketplace credentials)] package are needed in order to use the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] script command. See the instructions below for installing them.

The following components are also required and will be installed if not found on your computer:
*Microsoft .NET Framework 4.5.1 or 4.6
*Microsoft Visual Studio Tools for Office Runtime

=== Requirements for Using the Script Command --#ImportSapQuery ===

In order to use the script command [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], you need to [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|install the SAP Connector for Microsoft .NET Dll files]].

== System Requirements for QPR ProcessAnalyzer Xpress ==

The requirements specific to QPR ProcessAnalyzer Xpress include the following:
* SQL LocalDB 2012 database
* Internet connection in order to connect to the [[Activation|activation]] server

== System Requirements for QPR ProcessAnalyzer Server ==

The system requirements for QPR ProcessAnalyzer Server are as follows:
* Microsoft Windows Server 2008 R2 or 2012 operating system
* Sufficiently powerful enough hardware to run the operating system
* Microsoft SQL Server 2012 or 2014 database, with the following features:
** '''Instance Features''':
*** Database Engine Services
**** SQL Server Replication
**** Full-Text and Semantic Extractions for Search
**** Data Quality Services
** '''Shared Features''':
*** Data Quality Client
*** SQL Server Data Tools
*** Client Tools Connectivity
*** Integration Services
*** Client Tools Backwards Compatibility
*** Management Tools - Basic
**** Management Tools - Complete
*** Distributed Replay Controller
*** Distributed Replay Client
*** Master Data Services
* Microsoft Internet Information Services, with the following role services (features) enabled:
** '''Common HTTP Features''':
*** Default Document
*** Directory Browsing
*** HTTP Errors
*** Static Content
*** HTTP Redirection
** '''Health and Diagnostics''':
*** HTTP Logging
*** Logging Tools
*** Request Monitor
*** Tracing
** '''Security''':
*** Request Filtering
** '''Application Development''':
*** .Net Extensibility 3.5 & 4.5
*** ASP
*** ASP .NET 3.5 & 4.5
** '''Management Tools''':
*** IIS 6 Management Console
*** IIS 6 Management Compatibility
**** IIS 6 Management Console
** '''IIS Hostable Web Core'''

* The following Features need to be enabled:
** '''.Net Framework 3.5 Features''':
*** .Net Framework 3.5
** '''.Net Framework 4.5 Features''':
*** .Net 4.5
*** ASP.Net 4.5
*** WCF Services
**** HTTP Activation
**** TCP Port Sharing
** '''Background Intelligent Transfer Service (BIT)''':
***IIS Server Extension
** '''Remote server Administration Tools''':
*** Feature Administration Tools
**** BIT Server Extenstion Tools
** '''User Interfaces and Infrastructure''':
*** Graphical Management Tools and Infrastructure
*** Server Graphical Shell
** '''Windows Powershell''':
*** Windows Powershell 2.0, 3.0 and newer if available
*** Windows Powershell ISE
** '''Windows Process Activation Service''':
*** Process Model
*** Configuration APIs
** '''WoW64 Support'''
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]

If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:
<pre>
aspnet_regiis.exe -i -enable
</pre>

== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==

QPR ProcessAnalyzer Web Client supports the following web browsers:
*Microsoft Internet Explorer 9 or later
*Mozilla Firefox version 17 or later
*Google Chrome version 23 or later
*Apple Safari 5 or later

'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.

== Suggested Hardware for QPR ProcessAnalyzer Xpress ==

QPR ProcessAnalyzer Xpress Excel Client
* minimum 8GB Memory
* minimum 32GB available SSD Disk
* minimum 4 core processor

== Suggested Hardware for QPR ProcessAnalyzer Pro ==

QPR ProcessAnalyzer Excel Client
* minimum 4GB Memory

QPR ProcessAnalyzer Web Client
* minimum 2GB Memory

QPR ProcessAnalyzer Service
* minimum 4GB Memory

QPR ProcessAnalyzer - Microsoft SQL Server Database Server
* minimum 16GB Memory
* minimum 500GB available SSD disk for SQL Server temp database
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer
* minimum 4 processor cores

QPR ProcessAnalyzer Release Notes

2015-12-16T10:10:37Z

RiiPekk: 306474

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite. 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog. 
-306592: Internal and product version numbers have been updated and changes have been made to database version backward compatibility. See [[Version Compatibility Matrix]] for more information. 
-306596: Changes have been made to some of the default values for [[Influence Analysis]]. For example, the default subset number has been increased to 999.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-16T09:01:31Z

RiiPekk: 306596

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog. 
-306592: Internal and product version numbers have been updated and changes have been made to database version backward compatibility. See [[Version Compatibility Matrix]] for more information. 
-306596: Changes have been made to some of the default values for [[Influence Analysis]]. For example, the default subset number has been increased to 999.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-16T07:56:26Z

RiiPekk: 306592

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog. 
-306592: Internal and product version numbers have been updated and changes have been made to database version backward compatibility. See [[Version Compatibility Matrix]] for more information.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-16T07:50:57Z

RiiPekk: 306592

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-15T10:37:41Z

RiiPekk: 306592

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: , Stream version: 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==
Build number: 2016.1.0.xxxxx, Model compatibility version: 1, Database version: 50, Stream version: 7 
'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

=== Hotfix with version number 2015.5 (release date 7.10.2015) ===
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

=== Hotfix with version number 2015.5 (release date 26.8.2015) ===
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: , Stream version: 
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)===

Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: , Stream version: 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ===

Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: , Stream version: 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: , Stream version: 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: , Stream version: 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-03T07:55:10Z

RiiPekk: 306512

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306512: A new [[Workspace#Models|model compatibility version]] has been introduced to enable making backward compatibility breaking changes related to the way models are handled without having to break the backward compatibility of the whole QPR ProcessAnalyzer database. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-12-02T11:16:57Z

RiiPekk: 216729

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

SQL Scripting for ETL

2015-11-19T14:02:21Z

RiiPekk:

This page gives general information related to extracting, transforming and loading data in QPR ProcessAnalyzer. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''Limitations in size of SAP query result'''
:The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportSapQuery|--#ImportSapQuery]] for parameter explanations.

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.

:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException:
Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters)
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].

== [[QPR ProcessAnalyzer ETL Tutorial]] ==
There is also an [[QPR ProcessAnalyzer ETL Tutorial | ETL tutorial]] for learning the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer.

== [[ETL Script Examples]] ==
For more examples, see [[ETL Script Examples]].

[[Category:ETL]]
[[Category:API]]

SQL Scripting for ETL

2015-11-19T14:01:25Z

RiiPekk:

This page gives general information related to extracting, transforming and loading data in QPR ProcessAnalyzer. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''Limitations in size of SAP query result'''
:The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportSapQuery|--#ImportSapQuery]] for parameter explanations.

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.

:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException:
Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters)
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].

== [[QPR ProcessAnalyzer ETL Tutorial]] ==
There is also an [[QPR ProcessAnalyzer ETL Tutorial | ETL tutorial]] for learning the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer.

== [[ETL Script Examples]] ==
For more examples, see [[ETL Script Examples]].

[[Category:ETL]]
[[Category:API]]

QPR ProcessAnalyzer Wiki

2015-11-13T11:25:45Z

RiiPekk:

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence. Read [[What is QPR ProcessAnalyzer]] for an introduction of the tool.

== [[Installing QPR ProcessAnalyzer]] ==
See the [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started with QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[QPR ProcessAnalyzer Excel Add-In | Using QPR ProcessAnalyzer Excel Client]] ==
See the [[QPR ProcessAnalyzer Excel Add-In]] page for information on how to use QPR ProcessAnalyzer Excel Client.
 
[[File:Ribbon.png|986px|link=QPR ProcessAnalyzer Excel Add-In]]

== [[Data Extraction, Transformation, and Loading]] ==
Read information about ETL scripts on the [[Data Extraction, Transformation, and Loading]] page. The [[Supported QPR ProcessAnalyzer Commands in Scripts]] page lists and explains the QPR ProcessAnalyzer commands used in the scripts. 
Learn the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer on the [[QPR ProcessAnalyzer ETL Tutorial | ETL Tutorial]] page.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

QPR ProcessAnalyzer Wiki

2015-11-13T11:21:26Z

RiiPekk:

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence. See [[What is QPR ProcessAnalyzer]] for a brief description of the tool.

== [[Installing QPR ProcessAnalyzer]] ==
See the [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started with QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[QPR ProcessAnalyzer Excel Add-In | Using QPR ProcessAnalyzer Excel Client]] ==
See the [[QPR ProcessAnalyzer Excel Add-In]] page for information on how to use QPR ProcessAnalyzer Excel Client.
 
[[File:Ribbon.png|986px|link=QPR ProcessAnalyzer Excel Add-In]]

== [[Data Extraction, Transformation, and Loading]] ==
Read information about ETL scripts on the [[Data Extraction, Transformation, and Loading]] page. The [[Supported QPR ProcessAnalyzer Commands in Scripts]] page lists and explains the QPR ProcessAnalyzer commands used in the scripts. 
Learn the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer on the [[QPR ProcessAnalyzer ETL Tutorial | ETL Tutorial]] page.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

SQL Scripting for ETL

2015-11-13T11:17:40Z

RiiPekk:

This page gives general information related to extracting, transforming and loading data in QPR ProcessAnalyzer. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''Limitations in size of SAP query result'''
:The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportSapQuery|--#ImportSapQuery]] for parameter explanations.

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.

:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException:
Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters)
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

QPR ProcessAnalyzer Wiki

2015-11-13T11:12:29Z

RiiPekk:

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence. See [[What is QPR ProcessAnalyzer]] for a brief description of the tool.

== [[Installing QPR ProcessAnalyzer]] ==
See the [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started with QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[QPR ProcessAnalyzer Excel Add-In | Using QPR ProcessAnalyzer Excel Client]] ==

[[File:Ribbon.png|986px|link=QPR ProcessAnalyzer Excel Add-In]]
 
 
See the [[QPR ProcessAnalyzer Excel Add-In]] page for information on how to use QPR ProcessAnalyzer Excel Client.

== [[Data Extraction, Transformation, and Loading]] ==
Read information about ETL scripts on the [[Data Extraction, Transformation, and Loading]] page. The QPR ProcessAnalyzer commands used in them are explained in [[Supported QPR ProcessAnalyzer Commands in Scripts]]. 
Learn the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer on the [[QPR ProcessAnalyzer ETL Tutorial | ETL Tutorial]] page.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

QPR ProcessAnalyzer Wiki

2015-11-13T11:11:59Z

RiiPekk: reorganization of headings

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence. See the [[What is QPR ProcessAnalyzer]] page for a brief description of the tool.

== [[Installing QPR ProcessAnalyzer]] ==
See the [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started with QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[QPR ProcessAnalyzer Excel Add-In | Using QPR ProcessAnalyzer Excel Client]] ==

[[File:Ribbon.png|986px|link=QPR ProcessAnalyzer Excel Add-In]]
 
 
See the [[QPR ProcessAnalyzer Excel Add-In]] page for information on how to use QPR ProcessAnalyzer Excel Client.

== [[Data Extraction, Transformation, and Loading]] ==
Read information about ETL scripts on the [[Data Extraction, Transformation, and Loading]] page. The QPR ProcessAnalyzer commands used in them are explained in [[Supported QPR ProcessAnalyzer Commands in Scripts]]. 
Learn the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer on the [[QPR ProcessAnalyzer ETL Tutorial | ETL Tutorial]] page.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

QPR ProcessAnalyzer Wiki

2015-11-13T09:31:41Z

RiiPekk:

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence.

== [[What is QPR ProcessAnalyzer]] ==
Read a brief [[What is QPR ProcessAnalyzer|description]] about what QPR ProcessAnalyzer is.

== [[Installing QPR ProcessAnalyzer]] ==
See [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started on QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[Using QPR ProcessAnalyzer]] ==

[[File:Ribbon.png|986px|link=Using QPR ProcessAnalyzer]]
 
 
See the [[QPR ProcessAnalyzer Excel Add-In]] page for descriptions of the ribbon commands.

== [[QPR ProcessAnalyzer ETL Tutorial]] ==
Learn the basics of creating ETL scripts in SQL and using them for data extraction, transformation and loading in QPR ProcessAnalyzer. 
See also the [[Data Extraction, Transformation, and Loading]] page for more information on ETL scripts and the QPR ProcessAnalyzer commands used in them.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

QPR ProcessAnalyzer Wiki

2015-11-12T11:11:24Z

RiiPekk: /* Installing QPR ProcessAnalyzer */

This wiki contains documentation for QPR ProcessAnalyzer - the tool for turning event data into visual process intelligence.

== [[What is QPR ProcessAnalyzer]] ==
Read a brief [[What is QPR ProcessAnalyzer|description]] about what QPR ProcessAnalyzer is.

== [[Installing QPR ProcessAnalyzer]] ==
See [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.

== [[Get Started]] ==
Get started on QPR ProcessAnalyzer by following these [[Get Started|first steps]].

== [[Using QPR ProcessAnalyzer]] ==

[[File:Ribbon.png|986px|link=Using QPR ProcessAnalyzer]]
 
 
See the [[QPR ProcessAnalyzer Excel Add-In]] page for descriptions of the ribbon commands.

== [[Integration Service for Salesforce Cloud]] ==
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.

== [[QPR Connector for QPR ProcessAnalyzer]] ==
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.

== [[QPR ProcessAnalyzer Apps]] ==
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.

== [[QPR ProcessAnalyzer ETL Tutorial]] ==
Learn the basics of creating ETL scripts in SQL and using them for data extraction, transformation and loading in QPR ProcessAnalyzer. 
See also the [[Data Extraction, Transformation, and Loading]] page for more information on ETL scripts and the QPR ProcessAnalyzer commands used in them.

== [[QPR ProcessAnalyzer Certification]] ==
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.

== [[Agreements]] ==
[[Agreements]] page contains the end user license and software as a service agreements.

__NOTOC__

Filtering in QPR ProcessAnalyzer

2015-11-10T13:46:26Z

RiiPekk: 306509

There are two types of filtering available in QPR ProcessAnalyzer: [[Filtering#Runtime Selection|Runtime Selection]] and [[Filtering#Include / Exclude Filters|Include / Exclude Filters]].

== Runtime Selection ==
A runtime selection filter is applied when event types, transitions, cases, or attributes are selected and you click on any other analysis button on the ribbon except the Flowchart button. The data on the view that is opened will then be filtered based on what was selected. The runtime selection is not a persistent filter, so it is not added to the [[Filters#Filter History|Filter History]]. In addition, opening the Flowchart analysis will clear the runtime selection.

The runtime selection that is in use can be seen under the analysis name in the top left corner of the currently open analysis. For example, the Variation Analysis shown in the picture below contains cases that have events in the "Sales Order", "Outbound Delivery", and "Handling Unit" event types: 
[[File:RuntimeSelection.png]]

== Include / Exclude Filters ==

Using the '''Include Only''' and '''Exclude''' buttons, it is possible to filter the data. Depending on the active view, the buttons do the following:

=== Flowchart Analysis View with 1..n Event Types Selected, 1..n Transitions selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.

=== Flowchart Animation View with 1..n Cases Selected ===

*Include Only
: '''Cases''': Creates a new view containing only the selected cases.

*Exclude
: '''Cases''': Creates a new view excluding the selected cases.

=== Duration Analysis with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

=== Profiling Analysis with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

=== Path Analysis with 1..n Event Types Selected, 1..n Transitions selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.

=== Influence Analysis with Row(s) or Parts of Row(s) Selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).
:* If the selected case attribute(s) are the same that were used to open the Influence Analysis, the new filter will contain only the new selected value(s) for the case attribute(s).
:* If the selected case attribute(s) are not the same that were used to open the Influence Analysis, the original case selection that was used when opening the Influence Analysis isn't used.
*Exclude
: '''Cases''': Creates a new view excluding the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).

Note: Only one case attribute can be selected for the Include/Exclude filters in the Influence Analysis.

=== List of Cases with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the selected case(s).
*Exclude
: Creates a new view excluding the selected case(s).

=== List of Variations with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases that belong to selected variation(s).
* Exclude
: Creates a new view excluding the cases that belong to selected variation(s).

=== List of Event Types with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the event types that are selected.
*Exclude
: Creates a new view excluding the event types that are selected.

The filtered view that is created will be available in the [[Views#View Manager|Manage Filters]] dialog.

Note that if you use attribute values with exponents so that the value is bigger than 1E15 (that is, 1 times 10 to the power of 15) or smaller than 1E-15, the filtering does not work correctly. For example, if you have such cost as 2,31176835E+21 and 9,43E-15 and you select these attribute values for filtering, they will give incorrect results.

=== Case Sampling ===
Filtering also uses the sampling value set in [[Filters#Filter_Properties|Filter Properties]] for all case related analyses, such as Case, Event, Flow, Influence, Path, and Profiling Analysis. Cases are then sampled based on the filter sampling value. When a new filter is created, the default value of 10,000 cases is used. For every calculation, cases will be selected randomly.

=== More Information about Filters ===
Check the [[Filters]] page for more information about filters created with the Include/Exclude buttons.

{{Filtering Example}}

{{About Version}}

[[Category: Filtering]]

QPR ProcessAnalyzer Release Notes

2015-11-05T07:25:34Z

RiiPekk: 306509

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed. 
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-11-04T13:10:53Z

RiiPekk: /* Next Release: QPR ProcessAnalyzer 2016.1 */

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-11-04T13:10:32Z

RiiPekk: 306513

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 
-306513: The [[Filters#Filter_Properties|Filter]] dialog has been redesigned to enable access to filter rules directly from this dialog.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

Filtering in QPR ProcessAnalyzer

2015-11-04T09:02:15Z

RiiPekk: 306509

There are two types of filtering available in QPR ProcessAnalyzer: [[Filtering#Runtime Selection|Runtime Selection]] and [[Filtering#Include / Exclude Filters|Include / Exclude Filters]].

== Runtime Selection ==
A runtime selection filter is applied when event types, transitions, cases, or attributes are selected and you click on any other analysis button on the ribbon except the Flowchart button. The data on the view that is opened will then be filtered based on what was selected. The runtime selection is not a persistent filter, so it is not added to the [[Filters#Filter History|Filter History]]. In addition, opening the Flowchart analysis will clear the runtime selection.

The runtime selection that is in use can be seen under the analysis name in the top left corner of the currently open analysis. For example, the Variation Analysis shown in the picture below contains cases that have events in the "Sales Order", "Outbound Delivery", and "Handling Unit" event types: 
[[File:RuntimeSelection.png]]

== Include / Exclude Filters ==

Using the '''Include Only''' and '''Exclude''' buttons, it is possible to filter the data. Depending on the active view, the buttons do the following:

=== Flowchart Analysis View with 1..n Event Types Selected, 1..n Transitions selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.

=== Flowchart Animation View with 1..n Cases Selected ===

*Include Only
: '''Cases''': Creates a new view containing only the selected cases.

*Exclude
: '''Cases''': Creates a new view excluding the selected cases.

=== Duration Analysis with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

=== Profiling Analysis with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

=== Path Analysis with 1..n Event Types Selected, 1..n Transitions selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.

=== Influence Analysis with Row(s) or Parts of Row(s) Selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).
:* If the selected case attribute(s) are the same that were used to open the Influence Analysis, the new filter will contain only the new selected value(s) for the case attribute(s).
:* If the selected case attribute(s) are not the same that were used to open the Influence Analysis, the original case selection that was used when opening the Influence Analysis isn't used.
*Exclude
: '''Cases''': Creates a new view excluding the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).

Note: Only one case attribute can be selected for the Include/Exclude filters in the Influence Analysis.

=== List of Cases with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the selected case(s).
*Exclude
: Creates a new view excluding the selected case(s).

=== List of Variations with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases that belong to selected variation(s).
* Exclude
: Creates a new view excluding the cases that belong to selected variation(s).

=== List of Event Types with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the event types that are selected.
*Exclude
: Creates a new view excluding the event types that are selected.

The filtered view that is created will be available in the [[Views#View Manager|Manage Filters]] dialog.

Note that if you use attribute values with exponents so that the value is bigger than 1E15 (that is, 1 times 10 to the power of 15) or smaller than 1E-15, the filtering does not work correctly. For example, if you have such cost as 2,31176835E+21 and 9,43E-15 and you select these attribute values for filtering, they will give incorrect results.

=== Case Sampling ===
Filtering also uses the sampling value set in [[Filters#Filter_Properties|Filter Properties]] for all case related analyses, such as Case, Event, Flow, Influence, Path, and Profiling Analysis. Cases are then sampled based on the filter sampling value. If the value is zero (or null), no filtering will be done. When a new filter is created, the default value of 10,000 cases is used. For every calculation, cases will be selected randomly.

=== More Information about Filters ===
Check the [[Filters]] page for more information about filters created with the Include/Exclude buttons.

{{Filtering Example}}

{{About Version}}

[[Category: Filtering]]

QPR ProcessAnalyzer Release Notes

2015-11-03T14:01:03Z

RiiPekk:

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build number: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build number: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build number: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build number: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build number: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build number: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build number: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build number: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build number: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build number: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build number: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build number: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-11-03T13:54:30Z

RiiPekk: added build versions

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build version: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

Build version: 2015.4.0.33243 

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

Build version: 2015.3.0.32848 

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===
Build version: 2015.2.0.32408 
'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===
Build version: 2015.1.0.32120 
'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===
Build version: 2014.4.0.31422 
'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===
Build version: 2014.3.0.30795 
'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===
Build version: 2014.2.0.30286 
'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
Build version: 2014.1.0.28965 
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
Build version: 4.7.0.28641 
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
Build version: 4.6.0.28180 
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
Build version: 4.5.0.27571 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
Build version: 4.4.0.26819 
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
Build version: 4.3.0.26358 
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-11-03T13:42:14Z

RiiPekk: added build numbers

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==
Build version number: 2015.5.0.33554 
'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-11-03T13:40:31Z

RiiPekk:

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2016.1 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

SQL Scripting Commands

2015-11-03T11:09:30Z

RiiPekk:

This page lists all the QPR ProcessAnalyzer commands that are supported in scripts. Each command consists of queries, which are explained in the following subsections. 

= --#CallWebService =
Extracts data via Web Service. This command takes one SELECT query as parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are:
; 'Address'
: Defines the URI of the service to call. Mandatory.
; 'Method'
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.
; 'Body'
: Defines the message body text to send to the service. Default value is empty. Optional.
; 'Encoding'
: Defines the encoding method to use. The supported options are listed in [https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx]. Default value is UTF8. Optional.
; 'Timeout'
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.
; 'ExecuteInClientSide'
: Defines whether the web service call is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute in the client side. Supports only data table as the import destination. Default value is FALSE. Optional.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
;<nowiki><other parameters></nowiki>
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.

== Result ==

The result of the request is passed to the script following the CallWebService operation in the following variables:
: <code>@_ResponseText</code> The response text received from the remote server. If there was an error in processing the request, this will contain the received error message. NVARCHAR(MAX).
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT.
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.

== Example ==
<pre>
(SELECT 'Method', 'GET') UNION ALL
(SELECT 'Address', 'http://google.com') UNION ALL
(SELECT 'ContentType', 'application/json') UNION ALL
(SELECT 'Accept', '*/*')
--#CallWebService
PRINT SUBSTRING(@_ResponseText, 1, 50);
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log:

<pre>
Execution duration: 0,753 seconds
Execution Log:
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com
Method: GET
ContentType: application/json
Encoding: Unicode (UTF-8)
Body content length: 0
Timeout: 60000
ExecuteInClientSide: 0
Additional headers: Accept(3)
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200
<nowiki>
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/
</nowiki>
</pre>

= --#Exit =
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'Exit'
: Defines whether to stop the script execution:
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.
: 0 = if a value for the RunScriptId parameter is given, pause the execution of the current script and call the given script, then resume running the current script after the given script ends. If a value for RunScriptId is not given, do not pause or stop execution of the current script.
; 'MessageText'
: Text to be shown to the user after the script execution is finished if the script finished because of the Exit command, i.e. when Exit=1. The default value is "Script execution finished.", which is shown also when the script finished normally, i.e. when Exit=0. The text is also written to the script log.
; 'RunScriptId'
: Optional. The Id of the script to be run. Can be empty. Note that the script can call itself, so be careful not to create a looping script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The Exit command can in effect be used to "call" a script, i.e. run a different script and then return to continue the current script.
<pre>
(SELECT 'Exit', '0') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The Exit command can also be used to "goto" a script, i.e. stop the execution of the current script and run a different script.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example stops the script execution, gives a message, and runs a script with Id 12.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example script fragment checks if the previous ProcessAnalyzer command had any exceptions, and if it did, will goto script with Id 2. If the previous command didn't have any exceptions, the script execution is stopped.
<pre>
DECLARE @ScriptToRun VARCHAR(10)

IF @_ExceptionOccurred = 1
SET @ScriptToRun = '2'
ELSE SET @ScriptToRun = <nowiki>''</nowiki>

(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', @ScriptToRun)
--#Exit
</pre>

= --#GetAnalysis =
Creates an analysis from the data which the preceding SQL statements given as parameters provide. This command can take several queries, one for every analysis to be performed. These queries and analysis results are independent from one another.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.
: The --#GetAnalysis command supports the following analysis types:
: Flowchart Analysis (0)
: Variation Analysis in the Chart Mode (1)
: Path Analysis (3)
: Event Type Analysis in the Chart Mode (4)
: Case Analysis (5)
: Event Analysis (6)
: Event Type Analysis in the Table Mode (7)
: Variation Analysis in the Table Mode (8)
: Duration Analysis (9)
: Profiling Analysis (10)
: User Report (11)
: Operation Log Analysis (12)
: Flow Analysis (13)
: Influence Analysis (14)
: Data Table Analysis (18)
: Model Report (21)
: Project Report (22)
: Data Table Report (23)
: Script Report (24)
: Note that for the analysis types Model Report, Project Report, Data Table Report and Script Report, the information related to deleted models/projects/data tables/scripts is not shown by default but can be configured with parameters to be shown. For more information, see the parameters 'GetAll', 'IncludeDeletedProjects' and 'DeletedModelsOnly' in [[Analysis Parameters|the list of analysis parameters]].
; 'TargetTable'
: The temporary table to which the analysis is to be stored. Note that only table format analyses can be stored to a temporary table. If the specified temporary table already exists in the database then it's contents are deleted before storing analysis.
: You can define the 'TargetTable' when using the following analysis types:
: - Case Analysis
: - Event Analysis
: - Event Type Analysis
: - Variation Analysis
: - User Permissions
: - Operation Log
: - Flow Analysis
: - Influence Analysis
: - Integration Table
: - Model Report
: - Project Report
: - Data Table Report
: - Script Report
; 'Show'
: Optional. If TRUE or 1, the analysis is opened after the script is run.
; 'Title'
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'SheetName'
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The following example will get an Event analysis, open that analysis with "Analysis Title" as the title on a sheet named "Example Sheet Name", and store the Event analysis results to the "#ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'Title', 'Analysis Title') UNION ALL
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL
(SELECT 'TargetTable', '#ExampleTable')
--#GetAnalysis
</pre>

The following example will get a Model Report analysis, store the analysis results to a temporary table called "#ModelResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '21') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ModelResult')
--#GetAnalysis
</pre>

The following example will get a Project Report analysis, store the analysis results to a temporary table called "#ProjectResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '22') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ProjectResult')
--#GetAnalysis
</pre>
The following example will get a Data Table Report analysis, store the analysis results to a temporary table called "#DataTableResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Data_Tables|Data Tables]].
<pre>
(SELECT 'AnalysisType', '23') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#DataTableResult')
--#GetAnalysis
</pre>

The following example will get a Script Report analysis, store the analysis results to a temporary table called "#ScriptResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Manage Scripts dialog. For explanations of the columns, see [[Script_Management#Script_Manager|Manage Scripts]].
<pre>
(SELECT 'AnalysisType', '24') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ScriptResult')
--#GetAnalysis
</pre>

= --#ImportCaseAttributes =
Loads Case Attributes from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with an existing target model case attributes. TRUE or any other Integer than "0" = the existing case attributes in the target model are not deleted before import, FALSE or "0" = the existing case attributes of the target model are deleted before the import. If the target model is set to use another model as the [[Model Properties|Case Attribute Model]], those case attributes are not deleted. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> if there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportCaseAttributes command.

= --#ImportDataTable =
Imports data to a Data Table. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that if the query doesn't return any data, the data table is not created.

== Examples ==
The following example will load data from a model and put it into the "AnalysisResult" table and then add that data to the "ExampleTable" data table, and catch exceptions.
<pre>
SELECT 'START'
--#WriteLog

(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#GetAnalysis

SELECT 'DataLoaded'
--#WriteLog

SELECT count(*) from [#AnalysisResult]
--#WriteLog

(SELECT 'ProjectId', '1') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'Append', '1')
(SELECT * FROM [#AnalysisResult])
--#ImportDataTable
</pre>

The following example will load data from the "ExampleTable" data table in the "ExampleProject" project, put that data into the "CSV1" table and then show the contents of the "CSV" table. In effect, it shows the contents of the "ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis

(SELECT * FROM #CSV1)
(SELECT 'Title', 'CSV Table') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportEvents =
Loads Events from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with the existing target model events. TRUE or any other Integer than "0" = the existing events in the target model are not deleted before import, FALSE or "0" = the existing events of the target model are deleted before the import. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportEvents command.

= --#ImportOdbcQuery =
Extracts data directly from the ODBC data source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters. Columns are extracted as text data.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable': The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''ODBC specific parameters'''
; 'OdbcConnectionString'
: The ODBC driver connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcconnection.connectionstring%28v=vs.110%29.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 OdbcConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings. You can also configure a data source name for connecting to QPR ProcessAnalyzer, for instructions see [[How_to_Configure_an_ODBC_Data_Source_Name_for_Connecting_to_QPR_ProcessAnalyzer|How to Configure an ODBC Data Source Name for Connecting to QPR ProcessAnalyzer]].
; 'OdbcQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Example ==
The following script extracts data from an ODBC using a data source name configured as described in the link above and selects all columns from the table PA_MODEL, and catches exceptions.
<pre>
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportOdbcQuery
</pre>

= --#ImportOleDbQuery =
Extracts data from an OLE DB source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table(i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''OLE DB Query Parameters'''
; 'OleDbConnectionString'
: The OLE DB connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.connectionstring%28v=vs.110%29.aspx OleDbConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings.
; 'OleDbQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an OLE DB source (a sample database called DB1) and selects all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table and then show the contents of that table, and catch exceptions.
<pre>
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportOleDbQuery

(SELECT * FROM #TABLE) UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table from an OLE DB source and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE')
--#ImportOleDbQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSalesforceQuery =
Extracts data from Salesforce cloud and imports it into a data table as NVARCHAR(MAX) or SQL_VARIANT type data. Note that this command requires the Salesforce username and password to be visible in the script!

This command takes one SELECT query as its parameter.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''Salesforce Query Parameters'''
; 'SalesforceUser'
: Username for the Salesforce cloud.
; 'SalesforcePW'
: Password for the Salesforce cloud.
; 'SalesforceQueryMode'
: Optional. The Salesforce query function to be used. 1 (default) = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_queryall.htm queryall()], 2 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm query()], 3 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describesobject.htm describeSObject()].
; 'SalesforceQuery'
: The query to be run in the Salesforce cloud. Note that "*" cannot be used in the query. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] and [http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm SOQL Reference] for more information. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SalesforceQueryRetries'
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.
; 'SalesforceQueryRetryWait'
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.
; 'SalesforceBatchSize'
: Optional. The number of rows of data the query returns in one batch. Minimum = 200, Maximum = 2000, Default = 500. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] for more information.

== Example ==
The following example will load date data from the "Contact" table in the Salesforce cloud and put that data into the "ExampleDataTable" data table in the "ExampleProject" project, and catch exception when loading the data. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSalesforceQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSapQuery =
Extracts data from SAP and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters, e.g. "sap:Owner" -> "sap_Owner". Columns are extracted as text data. Note that using this command requires [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|some dlls]] not provided by QPR Software.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.
If the TargetTable parameter is not given, use the following destination parameters:
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''SAP Connection Parameters:'''
; 'SapUser'
: SAP username used to connect to SAP. Mandatory. Corresponds to the "USER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPW'
: Password of the SAP user used to connect to SAP. Mandatory. Corresponds to the "PASSWD" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapClient'
: The SAP backend client. Mandatory. Corresponds to the "CLIENT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapAppServerHost'
: The hostname or IP of the specific SAP application server, to which all connections shall be opened. Mandatory if SapMessageServerHost is not defined. Corresponds to the "ASHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapMessageServerHost'
: The hostname or IP of the SAP system’s message server (central instance). Mandatory if SapAppServerHost is not defined. Corresponds to the "MSHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemNumber'
: The SAP system’s system number. Mandatory if SapSystemID is not defined. Corresponds to the "SYSNR" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemID'
: The SAP system’s three-letter system ID. Mandatory if SapSystemNumber is not defined. Corresponds to the "SYSID" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

'''Other SAP Parameters:'''
; 'SapLanguage'
: SAP language used. Default value is "EN". Optional. Corresponds to the "LANG" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPoolSize'
: The maximum number of RFC connections that this destination will keep in its pool. Default value is "5". Optional. Corresponds to the "POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPeakConnectionsLimit'
: In order to prevent an unlimited number of connections to be opened, you can use this parameter. Default value is "10". Optional. Corresponds to the "MAX_POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapConnectionIdleTimeout'
: If a connection has been idle for more than SapIdleTimeout seconds, it will be closed and removed from the connection pool upon checking for idle connections or pools. Default value is "600". Optional. Corresponds to the "IDLE_TIMEOUT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRouter'
: A list of host names and service names / port numbers for the SAPRouter in the following format: /H/hostname/S/portnumber. Optional. Corresponds to the "SAPROUTER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapLogonGroup'
: The logon group from which the message server shall select an application server. Optional. Corresponds to the "GROUP" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryMode'
: If this number is set to "1", then the query result will have the SAP Table field names as data table column names and actual data rows as rows. If this is set to "3", the query result will get the field descriptions from the SAP query using NO_DATA parameter, i.e. the returned columns are the following (in this order): Field, Type, Description, Length, Offset. Default value is "1". Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryTable'
: Name of the SAP table to be extracted. Specifies the value for the parameter QUERY_TABLE in tab: 'Import' or function module 'rfc_read_table' in SAP. Mandatory. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SapRowcount'
: The maximum amount of rows to fetch. Specifies the value for parameter ROWCOUNT in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRowskips'
: The number of rows to skip. Specifies the value for parameter ROWSKIPS in tab: 'Import' or function module 'rfc_read_table'. in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClause'
: A comma separated list of WHERE clause elements passed for the SapQueryTable. Can be used with or without the SapWhereClauseSelect parameter. If used together with the SapWhereClauseSelect parameter, use the SapWhereClause parameter first. NOTE: The default maximum length for the Where Clause string is 72 characters in SAP, so the recommended maximum length of the SapWhereClause value is also 72 characters. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClauseSelect'
: The SELECT query to be executed in QPR ProcessAnalyzer sandbox. Used with or without the SapWhereClause parameter to pass WHERE clauses to SapQueryTable. If used together with the SapWhereClause parameter, use the SapWhereClause parameter first. The query is expected to return a table with at least one column, as the contents from the rows in the first column of the table are concatenated together to form the WHERE clause in SAP RFC_ReadTable. Therefore, it's recommended to first create the table with the WHERE clauses into a temporary table. In addition, it's recommended to have an order number column in the table and use that in the SELECT query to make sure the WHERE clause elements are concatenated in the correct order. The default maximum length for Where Clause string is 72 characters in SAP, so the recommended maximum length for the WHERE clause string in each row of the table is also 72. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. The contents up to the first 10 rows in the first column of the SELECT query are shown in the QPR ProcessAnalyzer [[Script Log]]. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. 
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.
; 'SapFieldNames'
: A comma separated list of field names for columns to be imported. Default value is empty, resulting in all columns being imported. Specifies the value for parameter FIELDNAME in tab: 'Tables' for table 'FIELDS' for function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapFunction'
: If you define a value for this parameter, then the new value specifies the SAP function that is called inside the #ImportSapQuery command. Optional. The default value is RFC_READ_TABLE. Another possible value is BBP_RFC_READ_TABLE. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.

== Examples ==
The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table in a SAP system and put them into a data table named "SapQueryTableExample", and catch exceptions when getting the data.
<pre>
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', 'TRUE') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL
(SELECT 'SapQueryMode', '1') UNION ALL
(SELECT 'SapQueryTable', 'VBAK') UNION ALL
(SELECT 'SapDelimiter', '|') UNION ALL
(SELECT 'SapRowcount', '0') UNION ALL
(SELECT 'SapRowskips', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSapQuery
</pre>

The following script will extract values for the VBELN field from the VBAK table where the value of the VBELN field is between 0060000039` and `0060000041. It will also catch possible exceptions when getting the data and print out them on a separate sheet. The extracted data is also shown on its own sheet:
<pre>
(SELECT 'CatchOperationExceptions', '1') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'qpr') UNION ALL
(SELECT 'SapPW', 'demo') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'ExecuteInClientSide', '1') UNION ALL
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

DECLARE @_SuccessOrNot as NVARCHAR(MAX);
SET @_SuccessOrNot = CASE @_ExceptionOccurred
WHEN 1 THEN
'Exception(s) occurred!'
ELSE
'SAP import OK.'
END

SELECT
@_SuccessOrNot as Result,
@_ExceptionOccurred as ExceptionOccurred,
@_ExceptionType as ExceptionType,
@_ExceptionMessage as ExceptionMessage,
@_ExceptionDetails as ExceptionDetails
(SELECT 'SheetName' , 'ExceptionData')
--#ShowReport

(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will return the values for the VBELN, ERDAT, ERZET, ERNAM, NETWR, and WAERK fields from the VBAK table where the value of the VBELN field is between 0060000039 and 0060000041:
<pre>
/* First, create the temporary table that holds the WHERE clause. */
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2

/* Specify the target for the data that the script extracts from SAP */
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters */
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table */
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Show the results */
(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table where the value of the VBELN field is between 0060000039 and 0060000041 and put them into a data table named "SapQueryTableExample". The query is made on the client side.
<pre>
/* First, create the temporary table that holds the WHERE clause.*/
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2

/* Define that the command is executed in the client side.*/
(SELECT 'ExecuteInClientSide', 'True') UNION ALL

/* Specify the data table where the data is imported into.*/
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters.*/
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table.*/
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Create an analysis.*/
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'TargetTable', '#Result')
--#GetAnalysis

/* Show the results.*/
SELECT * FROM #Result
--#ShowReport
</pre>

= --#ImportSqlQuery =
Extracts data from an ADO.NET source (which in this case is the SQL Server database) and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''SQL Query Parameters'''
; 'SqlConnectionString'
: The SQL connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx SqlConnection.ConnectionString Property in Microsoft Development Network] for more information on the connection parameters.
; 'SqlQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an ADO.NET source (a sample database called DB1 on Microsoft SQL Server) and select all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table, catch exceptions when doing this, and then show the contents of that table.
<pre>
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSqlQuery

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table in SQL Server database and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')
--#ImportSqlQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#RemoveEvents =
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project.
; 'ModelId' or 'ModelName'
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
The optional database query that returns the event Id's to be removed. Note that if there are several columns in the query, the event Id's have to be in the first column of the query.

== Examples ==
The following example will remove all events in the model with Id "22931" in the project with Id "234".
<pre>
(SELECT 'ProjectId', '234') UNION ALL
(SELECT 'ModelId', '22931')
--#RemoveEvents
</pre>

The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'ModelId', '<ModelId>') UNION ALL
(SELECT 'IncludeEventIds', 'True') UNION ALL
(SELECT 'TargetTable', '#Events')
--#GetAnalysis

(SELECT 'ModelId', '<ModelId>')
(SELECT [Event Id] from [#Events])
--#RemoveEvents
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log, if event Id's to be removed had been specified in the query:
<pre>
Remove events for model id=41 started
Number of events in model (before): 641
Number of events to be removed: 100
Number of events removed: 10
Number of events not found: 90
Number of events in model (after): 631
</pre>
In the log "Number of events to be removed" refers to the number of values (in this case 100) fetched from the first column of the query so that these values can be converted into numeric format.

In case there are no event Id's specified in the query, the script log will show the following entries:
<pre>
Remove events for model id=41 started
Number of events in model (before): 621
Remove all events
Number of events in model (after): 0
</pre>

= --#Run =
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ScriptId'
: Mandatory. The Id of the called script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
== Following Queries ==
The following queries are optional and used for initializing the arguments which are passed to the script to be run. The maximum number of arguments is 10. Each argument is created as a temporary table with names #_Arg1, ... #_Arg10. In the created temporary tables, all columns are of the type SQL Variant. If the column names have not been specified, then "Value_0", "Value_1", etc. are used as column names.
The possible arguments are as follows:
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)
:* #_Arg1, ... #_Arg10: arguments passed to that script

Each argument exists in the called script until the next --#Run command is executed in that script. After the called script has finished, the main script continues its execution.

== Examples ==
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>.

<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL
(SELECT 'TargetTable', '#DataTable1')
--#GetAnalysis

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL
(SELECT 'TargetTable', '#DataTable2')
--#GetAnalysis

(SELECT 'ScriptId', '<ScriptId>')
SELECT * FROM #DataTable1;
SELECT * FROM #DataTable2;
--#Run
</pre>

Then it runs that script with the following parameters: the number of arguments is 2 (that is, @_Argv=2). #_Arg1 takes data from the <DataTableId_1> data table and #_Arg2 from the <DataTableId_2> data table.
<pre>
print 'Number of arguments: ' + cast(@_Argv as varchar(100));

SELECT * from #_Arg1;
(SELECT 'MaximumCount', '0')
--#ShowReport

SELECT * from #_Arg2;
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#SendEmail =
Sends an e-mail and writes a message to script log whether sending the email was successful or not. Script execution continues even when the sending isn't successful.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''E-mail Parameters'''
; 'EmailFrom'
: Defines the from address for this e-mail message. Mandatory.
; 'EmailTo'
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.
; 'EmailSubject'
: Defines the subject of the email. Default value is empty. Optional.
; 'EmailBody'
: Defines the message body. Default value is empty. Optional.
; 'EmailCc'
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailBcc'
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailIsBodyHtml'
: Defines whether the e-mail message body is in HTML. TRUE or any other Integer than "0" = body is in HTML, FALSE or "0" = body is not in HTML. Default value is FALSE. Optional.
; 'EmailSender'
: Defines the sender's address for this e-mail message. Default value is empty. Optional.
; 'EmailReplyTo'
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.
; 'EmailPriority',
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.
; 'EmailDeliveryNotification'
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.
; 'EmailBodyEncoding'
: Defines the encoding used to encode the message body. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.
; 'EmailSubjectEncoding'
: Defines the encoding used for the subject content for this e-mail message. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.

'''SMTP Server Parameters'''
; 'SmtpServer'
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.
; 'SmtpPort'
: Defines the port of the SMTP server. Default value is "25". Optional.
; 'SmtpAuthenticationUsername'
: Defines the user name for the SMTP server. Note that the user name is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpAuthenticationPassword'
: Defines the password for the SMTP server. Note that the password is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpEnableSSL'
: Defines whether SSL should be enabled for the SMTP connection. TRUE or any other Integer than "0" = SSL is enabled, FALSE or "0" = SSL is not enabled. Default value is "FALSE". Optional.

== Example ==
The following example will send an e-mail message to multiple recipients.
<pre>
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL
(SELECT 'SmtpServer', 'localhost')
--#SendEmail
</pre>

See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].

= --#ShowReport =
Creates a new Excel sheet containing a table that contains the results of the user specified SQL query. The result column names are the field names of the SQL query and the rows are the actual data rows of the SQL query. The report can be used to see, for example, the events that would be loaded into QPR ProcessAnalyzer before actually loading them. If the events have problems that cause errors when loaded it is useful to be able to see the row data in a report.
'''Note:''' Excel cannot handle more than 1 million rows to be shown so if the result set contains more rows than that, the data will be truncated to 1 million rows.

This command takes two SELECT queries as parameters.
== First Query ==
A user specified SQL query to be shown in the configured Excel sheet.
; <nowiki>'<data>'</nowiki>
: Mandatory. The database query whose results are to be returned.

== Second Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:
:; 'Title'
:: The title of the created report. If not given, "Report" will be used as a default.
:; 'SheetName'
:: The name of the Excel sheet to be created.
:; 'MaximumCount'
:: The maximum number of rows to show (0 = all, default = 1000).
; 'CatchOperationExceptions': Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Example ==
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'Test') UNION ALL
(SELECT 'DataTableName', 'SqlTable') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT * FROM #AnalysisResult;
(SELECT 'Title', 'Report1') UNION ALL
(SELECT 'SheetName', 'Sheet1') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#WriteLog =
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.

In addition to the WriteLog command, you can also use the [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] to generate log entries into the script execution log. The difference to the WriteLog command is that the Print statement can use also variables.

== Examples ==
The following example will write "Script started", "Example", "Print Example" into the log. Note that the WriteLog command and Print SQL statement represent two different ways of generating log entries, and you can use them also separately.
<pre>
SELECT 'Script started'
SELECT 'Example'
--#WriteLog
PRINT 'Print Example'
</pre>

QPR ProcessAnalyzer Release Notes

2015-10-26T10:35:27Z

RiiPekk: /* Next Release: QPR ProcessAnalyzer 2015.6 */

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering has been changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-26T10:34:55Z

RiiPekk: 306508

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering. 
-306508: In this refactorization feature, the internal mechanism for filtering is changed to support incremental event loading. 

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-26T09:05:38Z

RiiPekk: /* Next Release: QPR ProcessAnalyzer 2015.6 */

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Features:''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-26T09:05:18Z

RiiPekk: 306485

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

'''Features''' 
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-09T08:39:26Z

RiiPekk: 216404

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216404: Fixed an issue where a Evaluator user could not log in to QPR ProcessAnalyzer when the user did not have rights to the model default filter. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-09T08:29:17Z

RiiPekk: 216205

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address. 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-09T08:23:13Z

RiiPekk: 216405

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-09T06:13:42Z

RiiPekk: hotfix added (build 2015.5.0.33631)

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 7.10.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33631. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-07T05:58:34Z

RiiPekk: 216566

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 
- 216566: Fixed an issue where the client-service polling was broken when exporting a model. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-10-01T12:44:11Z

RiiPekk: 216456

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
- 216456: Fixed an error that occurred when using the #ImportSapQuery command and transferring data from server to client and executing it in the client side. 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

SQL Scripting for ETL

2015-10-01T11:47:24Z

RiiPekk: /* Client Exception When Using #ImportSapQuery Command */

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]]. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''Limitations in size of SAP query result'''
:The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportSapQuery|--#ImportSapQuery]] for parameter explanations.

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter.

:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException:
Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters)
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

SQL Scripting for ETL

2015-10-01T11:46:52Z

RiiPekk: 216456

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]]. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''Limitations in size of SAP query result'''
:The SAP system has limitations as to how much data can be queried. The workaround for the error is to reduce the amount of data to be queried using 'SapRowcount', 'SapRowskips', 'SapWhereClauseSelect', 'SapFieldNames' and 'SapFunction' parameters. See [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportSapQuery|--#ImportSapQuery]] for parameter explanations.

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter. What causes this?

:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException:
Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters)
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
(Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP and the size of 'SapWhereClauseSelect' parameter value is too large. Reduce the size of the 'SapWhereClauseSelect' value.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

SQL Scripting for ETL

2015-10-01T11:18:53Z

RiiPekk:

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]]. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter. What causes this?
:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters) [...]
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface (Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP using 'SapWhereClauseSelect' parameter. The SAP system has limitations as to how much data can be queried. The workaround for this error is to reduce the amount of data to be queried with 'SapWhereClauseSelect' from SAP.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

SQL Scripting Commands

2015-10-01T10:55:35Z

RiiPekk: 216456

This page lists all the QPR ProcessAnalyzer commands that are supported in scripts. Each command consists of queries, which are explained in the following subsections. 

= --#CallWebService =
Extracts data via Web Service. This command takes one SELECT query as parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are:
; 'Address'
: Defines the URI of the service to call. Mandatory.
; 'Method'
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.
; 'Body'
: Defines the message body text to send to the service. Default value is empty. Optional.
; 'Encoding'
: Defines the encoding method to use. The supported options are listed in [https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx]. Default value is UTF8. Optional.
; 'Timeout'
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.
; 'ExecuteInClientSide'
: Defines whether the web service call is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute in the client side. Supports only data table as the import destination. Default value is FALSE. Optional.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
;<nowiki><other parameters></nowiki>
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.

== Result ==

The result of the request is passed to the script following the CallWebService operation in the following variables:
: <code>@_ResponseText</code> The response text received from the remote server. If there was an error in processing the request, this will contain the received error message. NVARCHAR(MAX).
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT.
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.

== Example ==
<pre>
(SELECT 'Method', 'GET') UNION ALL
(SELECT 'Address', 'http://google.com') UNION ALL
(SELECT 'ContentType', 'application/json') UNION ALL
(SELECT 'Accept', '*/*')
--#CallWebService
PRINT SUBSTRING(@_ResponseText, 1, 50);
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log:

<pre>
Execution duration: 0,753 seconds
Execution Log:
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com
Method: GET
ContentType: application/json
Encoding: Unicode (UTF-8)
Body content length: 0
Timeout: 60000
ExecuteInClientSide: 0
Additional headers: Accept(3)
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200
<nowiki>
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/
</nowiki>
</pre>

= --#Exit =
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'Exit'
: Defines whether to stop the script execution:
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.
: 0 = if a value for the RunScriptId parameter is given, pause the execution of the current script and call the given script, then resume running the current script after the given script ends. If a value for RunScriptId is not given, do not pause or stop execution of the current script.
; 'MessageText'
: Text to be shown to the user after the script execution is finished if the script finished because of the Exit command, i.e. when Exit=1. The default value is "Script execution finished.", which is shown also when the script finished normally, i.e. when Exit=0. The text is also written to the script log.
; 'RunScriptId'
: Optional. The Id of the script to be run. Can be empty. Note that the script can call itself, so be careful not to create a looping script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The Exit command can in effect be used to "call" a script, i.e. run a different script and then return to continue the current script.
<pre>
(SELECT 'Exit', '0') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The Exit command can also be used to "goto" a script, i.e. stop the execution of the current script and run a different script.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example stops the script execution, gives a message, and runs a script with Id 12.
<pre>
(SELECT 'Exit', '1') UNION ALL
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL
(SELECT 'RunScriptId', '12')
--#Exit
</pre>

The following example script fragment checks if the previous ProcessAnalyzer command had any exceptions, and if it did, will goto script with Id 2. If the previous command didn't have any exceptions, the script execution is stopped.
<pre>
DECLARE @ScriptToRun VARCHAR(10)

IF @_ExceptionOccurred = 1
SET @ScriptToRun = '2'
ELSE SET @ScriptToRun = <nowiki>''</nowiki>

(SELECT 'Exit', '1') UNION ALL
(SELECT 'RunScriptId', @ScriptToRun)
--#Exit
</pre>

= --#GetAnalysis =
Creates an analysis from the data which the preceding SQL statements given as parameters provide. This command can take several queries, one for every analysis to be performed. These queries and analysis results are independent from one another.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.
: The --#GetAnalysis command supports the following analysis types:
: Flowchart Analysis (0)
: Variation Analysis in the Chart Mode (1)
: Path Analysis (3)
: Event Type Analysis in the Chart Mode (4)
: Case Analysis (5)
: Event Analysis (6)
: Event Type Analysis in the Table Mode (7)
: Variation Analysis in the Table Mode (8)
: Duration Analysis (9)
: Profiling Analysis (10)
: User Report (11)
: Operation Log Analysis (12)
: Flow Analysis (13)
: Influence Analysis (14)
: Data Table Analysis (18)
: Model Report (21)
: Project Report (22)
: Data Table Report (23)
: Script Report (24)
: Note that for the analysis types Model Report, Project Report, Data Table Report and Script Report, the information related to deleted models/projects/data tables/scripts is not shown by default but can be configured with parameters to be shown. For more information, see the parameters 'GetAll', 'IncludeDeletedProjects' and 'DeletedModelsOnly' in [[Analysis Parameters|the list of analysis parameters]].
; 'TargetTable'
: The temporary table to which the analysis is to be stored. Note that only table format analyses can be stored to a temporary table. If the specified temporary table already exists in the database then it's contents are deleted before storing analysis.
: You can define the 'TargetTable' when using the following analysis types:
: - Case Analysis
: - Event Analysis
: - Event Type Analysis
: - Variation Analysis
: - User Permissions
: - Operation Log
: - Flow Analysis
: - Influence Analysis
: - Integration Table
: - Model Report
: - Project Report
: - Data Table Report
: - Script Report
; 'Show'
: Optional. If TRUE or 1, the analysis is opened after the script is run.
; 'Title'
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'SheetName'
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Examples ==
The following example will get an Event analysis, open that analysis with "Analysis Title" as the title on a sheet named "Example Sheet Name", and store the Event analysis results to the "#ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'Title', 'Analysis Title') UNION ALL
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL
(SELECT 'TargetTable', '#ExampleTable')
--#GetAnalysis
</pre>

The following example will get a Model Report analysis, store the analysis results to a temporary table called "#ModelResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '21') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ModelResult')
--#GetAnalysis
</pre>

The following example will get a Project Report analysis, store the analysis results to a temporary table called "#ProjectResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Models|Models]].
<pre>
(SELECT 'AnalysisType', '22') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ProjectResult')
--#GetAnalysis
</pre>
The following example will get a Data Table Report analysis, store the analysis results to a temporary table called "#DataTableResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Project Workspace. For explanations of the columns, see [[Workspace#Data_Tables|Data Tables]].
<pre>
(SELECT 'AnalysisType', '23') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#DataTableResult')
--#GetAnalysis
</pre>

The following example will get a Script Report analysis, store the analysis results to a temporary table called "#ScriptResult" and show the results on an Excel sheet. This table contains the same information as is visible in the Manage Scripts dialog. For explanations of the columns, see [[Script_Management#Script_Manager|Manage Scripts]].
<pre>
(SELECT 'AnalysisType', '24') UNION ALL
(SELECT 'Show', '1') UNION ALL
(SELECT 'TargetTable', '#ScriptResult')
--#GetAnalysis
</pre>

= --#ImportCaseAttributes =
Loads Case Attributes from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with an existing target model case attributes. TRUE or any other Integer than "0" = the existing case attributes in the target model are not deleted before import, FALSE or "0" = the existing case attributes of the target model are deleted before the import. If the target model is set to use another model as the [[Model Properties|Case Attribute Model]], those case attributes are not deleted. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> if there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportCaseAttributes command.

= --#ImportDataTable =
Imports data to a Data Table. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that if the query doesn't return any data, the data table is not created.

== Examples ==
The following example will load data from a model and put it into the "AnalysisResult" table and then add that data to the "ExampleTable" data table, and catch exceptions.
<pre>
SELECT 'START'
--#WriteLog

(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '3') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#GetAnalysis

SELECT 'DataLoaded'
--#WriteLog

SELECT count(*) from [#AnalysisResult]
--#WriteLog

(SELECT 'ProjectId', '1') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'Append', '1')
(SELECT * FROM [#AnalysisResult])
--#ImportDataTable
</pre>

The following example will load data from the "ExampleTable" data table in the "ExampleProject" project, put that data into the "CSV1" table and then show the contents of the "CSV" table. In effect, it shows the contents of the "ExampleTable" data table.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleTable') UNION ALL
(SELECT 'TargetTable', '#CSV1')
--#GetAnalysis

(SELECT * FROM #CSV1)
(SELECT 'Title', 'CSV Table') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportEvents =
Loads Events from the data which the preceding SQL statements given as parameters provide into the specified model. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project. If the given ProjectName doesn't exist, a new project is created.
; 'ModelId' or 'ModelName'
: The id or the name of the existing/new target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used. If the given ModelName doesn't exist, a new model is created.
; 'Append'
: Defines what to do with the existing target model events. TRUE or any other Integer than "0" = the existing events in the target model are not deleted before import, FALSE or "0" = the existing events of the target model are deleted before the import. Not used when creating a new model. Default value is TRUE.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
; <nowiki>'<data>'</nowiki>
: The database query whose results are to be imported. Note that the geometry, geography, hierarchyid, and image SQL data types are not supported by the ImportEvents command.

= --#ImportOdbcQuery =
Extracts data directly from the ODBC data source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters. Columns are extracted as text data.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable': The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''ODBC specific parameters'''
; 'OdbcConnectionString'
: The ODBC driver connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcconnection.connectionstring%28v=vs.110%29.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 OdbcConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings. You can also configure a data source name for connecting to QPR ProcessAnalyzer, for instructions see [[How_to_Configure_an_ODBC_Data_Source_Name_for_Connecting_to_QPR_ProcessAnalyzer|How to Configure an ODBC Data Source Name for Connecting to QPR ProcessAnalyzer]].
; 'OdbcQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Example ==
The following script extracts data from an ODBC using a data source name configured as described in the link above and selects all columns from the table PA_MODEL, and catches exceptions.
<pre>
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportOdbcQuery
</pre>

= --#ImportOleDbQuery =
Extracts data from an OLE DB source and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table(i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''OLE DB Query Parameters'''
; 'OleDbConnectionString'
: The OLE DB connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.connectionstring%28v=vs.110%29.aspx OleDbConnection.ConnectionString Property in Microsoft Development Network] for more information on the possible connection strings.
; 'OleDbQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an OLE DB source (a sample database called DB1) and selects all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table and then show the contents of that table, and catch exceptions.
<pre>
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportOleDbQuery

(SELECT * FROM #TABLE) UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table from an OLE DB source and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE')
--#ImportOleDbQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSalesforceQuery =
Extracts data from Salesforce cloud and imports it into a data table as NVARCHAR(MAX) or SQL_VARIANT type data. Note that this command requires the Salesforce username and password to be visible in the script!

This command takes one SELECT query as its parameter.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table contents. TRUE or any other Integer than "0" = the existing contents in the target data table are not deleted before import, FALSE or "0" = the existing contents of the target data table are deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''Salesforce Query Parameters'''
; 'SalesforceUser'
: Username for the Salesforce cloud.
; 'SalesforcePW'
: Password for the Salesforce cloud.
; 'SalesforceQueryMode'
: Optional. The Salesforce query function to be used. 1 (default) = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_queryall.htm queryall()], 2 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm query()], 3 = [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_describesobject.htm describeSObject()].
; 'SalesforceQuery'
: The query to be run in the Salesforce cloud. Note that "*" cannot be used in the query. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] and [http://www.salesforce.com/us/developer/docs/soql_sosl/index.htm SOQL Reference] for more information. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SalesforceQueryRetries'
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.
; 'SalesforceQueryRetryWait'
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.
; 'SalesforceBatchSize'
: Optional. The number of rows of data the query returns in one batch. Minimum = 200, Maximum = 2000, Default = 500. See [http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_query.htm Salesforce API] for more information.

== Example ==
The following example will load date data from the "Contact" table in the Salesforce cloud and put that data into the "ExampleDataTable" data table in the "ExampleProject" project, and catch exception when loading the data. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSalesforceQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#ImportSapQuery =
Extracts data from SAP and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. If a column name contains illegal characters for table names, the illegal characters are converted to be underscore characters, e.g. "sap:Owner" -> "sap_Owner". Columns are extracted as text data. Note that using this command requires [[Installing_QPR_ProcessAnalyzer#Installing_SAP_Connector_for_Microsoft_.NET_Version_3.0_Dll_Files|some dlls]] not provided by QPR Software.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.
If the TargetTable parameter is not given, use the following destination parameters:
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

'''SAP Connection Parameters:'''
; 'SapUser'
: SAP username used to connect to SAP. Mandatory. Corresponds to the "USER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPW'
: Password of the SAP user used to connect to SAP. Mandatory. Corresponds to the "PASSWD" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapClient'
: The SAP backend client. Mandatory. Corresponds to the "CLIENT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapAppServerHost'
: The hostname or IP of the specific SAP application server, to which all connections shall be opened. Mandatory if SapMessageServerHost is not defined. Corresponds to the "ASHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapMessageServerHost'
: The hostname or IP of the SAP system’s message server (central instance). Mandatory if SapAppServerHost is not defined. Corresponds to the "MSHOST" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemNumber'
: The SAP system’s system number. Mandatory if SapSystemID is not defined. Corresponds to the "SYSNR" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapSystemID'
: The SAP system’s three-letter system ID. Mandatory if SapSystemNumber is not defined. Corresponds to the "SYSID" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

'''Other SAP Parameters:'''
; 'SapLanguage'
: SAP language used. Default value is "EN". Optional. Corresponds to the "LANG" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPoolSize'
: The maximum number of RFC connections that this destination will keep in its pool. Default value is "5". Optional. Corresponds to the "POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapPeakConnectionsLimit'
: In order to prevent an unlimited number of connections to be opened, you can use this parameter. Default value is "10". Optional. Corresponds to the "MAX_POOL_SIZE" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapConnectionIdleTimeout'
: If a connection has been idle for more than SapIdleTimeout seconds, it will be closed and removed from the connection pool upon checking for idle connections or pools. Default value is "600". Optional. Corresponds to the "IDLE_TIMEOUT" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRouter'
: A list of host names and service names / port numbers for the SAPRouter in the following format: /H/hostname/S/portnumber. Optional. Corresponds to the "SAPROUTER" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapLogonGroup'
: The logon group from which the message server shall select an application server. Optional. Corresponds to the "GROUP" constant on SAP side. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryMode'
: If this number is set to "1", then the query result will have the SAP Table field names as data table column names and actual data rows as rows. If this is set to "3", the query result will get the field descriptions from the SAP query using NO_DATA parameter, i.e. the returned columns are the following (in this order): Field, Type, Description, Length, Offset. Default value is "1". Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapQueryTable'
: Name of the SAP table to be extracted. Specifies the value for the parameter QUERY_TABLE in tab: 'Import' or function module 'rfc_read_table' in SAP. Mandatory. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'SapRowcount'
: The maximum amount of rows to fetch. Specifies the value for parameter ROWCOUNT in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapRowskips'
: The number of rows to skip. Specifies the value for parameter ROWSKIPS in tab: 'Import' or function module 'rfc_read_table'. in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClause'
: A comma separated list of WHERE clause elements passed for the SapQueryTable. Can be used with or without the SapWhereClauseSelect parameter. If used together with the SapWhereClauseSelect parameter, use the SapWhereClause parameter first. NOTE: The default maximum length for the Where Clause string is 72 characters in SAP, so the recommended maximum length of the SapWhereClause value is also 72 characters. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapWhereClauseSelect'
: The SELECT query to be executed in QPR ProcessAnalyzer sandbox. Used with or without the SapWhereClause parameter to pass WHERE clauses to SapQueryTable. If used together with the SapWhereClause parameter, use the SapWhereClause parameter first. The query is expected to return a table with at least one column, as the contents from the rows in the first column of the table are concatenated together to form the WHERE clause in SAP RFC_ReadTable. Therefore, it's recommended to first create the table with the WHERE clauses into a temporary table. In addition, it's recommended to have an order number column in the table and use that in the SELECT query to make sure the WHERE clause elements are concatenated in the correct order. The default maximum length for Where Clause string is 72 characters in SAP, so the recommended maximum length for the WHERE clause string in each row of the table is also 72. In effect, specifies the value for parameter OPTIONS in tab: 'Import' or function module 'rfc_read_table' in SAP. Optional. The contents up to the first 10 rows in the first column of the SELECT query are shown in the QPR ProcessAnalyzer [[Script Log]]. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info. 
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.
; 'SapFieldNames'
: A comma separated list of field names for columns to be imported. Default value is empty, resulting in all columns being imported. Specifies the value for parameter FIELDNAME in tab: 'Tables' for table 'FIELDS' for function module 'rfc_read_table' in SAP. Optional. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.
; 'SapFunction'
: If you define a value for this parameter, then the new value specifies the SAP function that is called inside the #ImportSapQuery command. Optional. The default value is RFC_READ_TABLE. Another possible value is BBP_RFC_READ_TABLE. See the [http://help.sap.com/saphelp_nw04/helpdata/en/e9/23c80d66d08c4c8c044a3ea11ca90f/content.htm SAP .NET Connector documentation] for more info.

== Examples ==
The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table in a SAP system and put them into a data table named "SapQueryTableExample", and catch exceptions when getting the data.
<pre>
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', 'TRUE') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL
(SELECT 'SapQueryMode', '1') UNION ALL
(SELECT 'SapQueryTable', 'VBAK') UNION ALL
(SELECT 'SapDelimiter', '|') UNION ALL
(SELECT 'SapRowcount', '0') UNION ALL
(SELECT 'SapRowskips', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSapQuery
</pre>

The following script will extract values for the VBELN field from the VBAK table where the value of the VBELN field is between 0060000039` and `0060000041. It will also catch possible exceptions when getting the data and print out them on a separate sheet. The extracted data is also shown on its own sheet:
<pre>
(SELECT 'CatchOperationExceptions', '1') UNION ALL
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'qpr') UNION ALL
(SELECT 'SapPW', 'demo') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'ExecuteInClientSide', '1') UNION ALL
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

DECLARE @_SuccessOrNot as NVARCHAR(MAX);
SET @_SuccessOrNot = CASE @_ExceptionOccurred
WHEN 1 THEN
'Exception(s) occurred!'
ELSE
'SAP import OK.'
END

SELECT
@_SuccessOrNot as Result,
@_ExceptionOccurred as ExceptionOccurred,
@_ExceptionType as ExceptionType,
@_ExceptionMessage as ExceptionMessage,
@_ExceptionDetails as ExceptionDetails
(SELECT 'SheetName' , 'ExceptionData')
--#ShowReport

(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will return the values for the VBELN, ERDAT, ERZET, ERNAM, NETWR, and WAERK fields from the VBAK table where the value of the VBELN field is between 0060000039 and 0060000041:
<pre>
/* First, create the temporary table that holds the WHERE clause. */
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2

/* Specify the target for the data that the script extracts from SAP */
(SELECT 'TargetTable', '#SAPmode1') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters */
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table */
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Show the results */
(SELECT * FROM #SAPmode1)
(SELECT 'SheetName' , 'SAPmode1')
--#ShowReport
</pre>

The following script will get the "VBELN", "ERDAT", "ERZET", "ERNAM", "NETWR", and "WAERK" columns from the "VBAK" table where the value of the VBELN field is between 0060000039 and 0060000041 and put them into a data table named "SapQueryTableExample". The query is made on the client side.
<pre>
/* First, create the temporary table that holds the WHERE clause.*/
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2

/* Define that the command is executed in the client side.*/
(SELECT 'ExecuteInClientSide', 'True') UNION ALL

/* Specify the data table where the data is imported into.*/
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'Append', '0') UNION ALL

/* Define the SAP connection parameters.*/
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL
(SELECT 'SapSystemNumber', '10') UNION ALL
(SELECT 'SapUser', 'exampleuser') UNION ALL
(SELECT 'SapPW', 'examplepassword') UNION ALL
(SELECT 'SapRouter', '') UNION ALL
(SELECT 'SapClient', '200') UNION ALL
(SELECT 'SapLanguage', 'EN') UNION ALL
(SELECT 'SapPoolSize', '5') UNION ALL
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL

/* Use the WHERE clause defined in the temporary table.*/
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL
(SELECT 'SapQueryTable', 'VBAK')
--#ImportSapQuery

/* Create an analysis.*/
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL
(SELECT 'TargetTable', '#Result')
--#GetAnalysis

/* Show the results.*/
SELECT * FROM #Result
--#ShowReport
</pre>

= --#ImportSqlQuery =
Extracts data from an ADO.NET source (which in this case is the SQL Server database) and imports it to QPR ProcessAnalyzer Data Table or QPR ProcessAnalyzer temporary table. Column names are parsed from the query result. It is possible to both create new Data Tables as well as modify existing Data Tables with this command.
== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'TargetTable'
: The temporary table to which the data is to be imported. If not used, define the target using the ProjectId/ProjectName, DataTableId/DataTableName, and Append parameters described below.
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target data table exists.
; 'DataTableId' or 'DataTableName'
: The id or the name of the existing/new target data table.
; 'Append'
: Defines what to do with an existing target data table and its contents. TRUE or any other Integer than "0" = the target data table and its existing contents are not deleted before import. If a user imports into a data table with 'Append' = FALSE or "0", the contents of the data table are deleted before the import. If a user imports into a temporary table (i.e. TargetTable) with 'Append' = FALSE or "0", then the whole temporary table is deleted before the import. Not used when creating a new data table.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''SQL Query Parameters'''
; 'SqlConnectionString'
: The SQL connection string that includes the settings needed to establish the initial connection. Mandatory. See [http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28v=vs.110%29.aspx SqlConnection.ConnectionString Property in Microsoft Development Network] for more information on the connection parameters.
; 'SqlQueryString'
: The SQL query string. Mandatory. Note that if the query doesn't return any data, the target data table or temporary table is not created.
; 'ExecuteInClientSide'
: Defines whether the command is executed in the client side or in the server side when using QPR ProcessAnalyzer Pro. This parameter is used when there is no server connection available, for example. TRUE or any other Integer than "0" = the import query is executed in the client side. FALSE or "0" = the import query is executed in the server side. Not used with QPR ProcessAnalyzer Xpress or QPR ProcessAnalyzer Database as they always execute the command in the client side. Supports only data table as the import destination. If 'TargetTable' has been defined as the import destination and the value of this parameter is given as TRUE or any other Integer than "0", you will receive an error message. Optional. Default value is FALSE.

== Examples ==
The following example will load data from an ADO.NET source (a sample database called DB1 on Microsoft SQL Server) and select all columns from the table EXAMPLE. It will then put that data into the "#TABLE" temporary table, catch exceptions when doing this, and then show the contents of that table.
<pre>
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL
(SELECT 'TargetTable', '#TABLE') UNION ALL
(SELECT 'Append', '1') UNION ALL
(SELECT 'CatchOperationExceptions', '1')
--#ImportSqlQuery

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

The following example will load all the columns from "EXAMPLE" table in SQL Server database and will put that data into the "ExampleDataTable" in the "ExampleProject" project. It will then get the Data Table analysis from the "ExampleDataTable", put that into the "#TABLE" temporary table and then show the contents of that table.
<pre>
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'Append', '0') UNION ALL
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')
--#ImportSqlQuery

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL
(SELECT 'TargetTable', '#TABLE')
--#GetAnalysis

(SELECT * FROM #TABLE)
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#RemoveEvents =
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.
== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ProjectId' or 'ProjectName'
: The id or the name of the project in which the target model exists. Defaults to the current project.
; 'ModelId' or 'ModelName'
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Second Query ==
The optional database query that returns the event Id's to be removed. Note that if there are several columns in the query, the event Id's have to be in the first column of the query.

== Examples ==
The following example will remove all events in the model with Id "22931" in the project with Id "234".
<pre>
(SELECT 'ProjectId', '234') UNION ALL
(SELECT 'ModelId', '22931')
--#RemoveEvents
</pre>

The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.
<pre>
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '10') UNION ALL
(SELECT 'ModelId', '<ModelId>') UNION ALL
(SELECT 'IncludeEventIds', 'True') UNION ALL
(SELECT 'TargetTable', '#Events')
--#GetAnalysis

(SELECT 'ModelId', '<ModelId>')
(SELECT [Event Id] from [#Events])
--#RemoveEvents
</pre>

== Script Log Results ==
When the script is run, entries similar to the following will be shown in the script log, if event Id's to be removed had been specified in the query:
<pre>
Remove events for model id=41 started
Number of events in model (before): 641
Number of events to be removed: 100
Number of events removed: 10
Number of events not found: 90
Number of events in model (after): 631
</pre>
In the log "Number of events to be removed" refers to the number of values (in this case 100) fetched from the first column of the query so that these values can be converted into numeric format.

In case there are no event Id's specified in the query, the script log will show the following entries:
<pre>
Remove events for model id=41 started
Number of events in model (before): 621
Remove all events
Number of events in model (after): 0
</pre>

= --#Run =
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.

== First Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'ScriptId'
: Mandatory. The Id of the called script.
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
: <code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
== Following Queries ==
The following queries are optional and used for initializing the arguments which are passed to the script to be run. The maximum number of arguments is 10. Each argument is created as a temporary table with names #_Arg1, ... #_Arg10. In the created temporary tables, all columns are of the type SQL Variant. If the column names have not been specified, then "Value_0", "Value_1", etc. are used as column names.
The possible arguments are as follows:
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)
:* #_Arg1, ... #_Arg10: arguments passed to that script

Each argument exists in the called script until the next --#Run command is executed in that script. After the called script has finished, the main script continues its execution.

== Examples ==
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>.

<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL
(SELECT 'TargetTable', '#DataTable1')
--#GetAnalysis

(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL
(SELECT 'TargetTable', '#DataTable2')
--#GetAnalysis

(SELECT 'ScriptId', '<ScriptId>')
SELECT * FROM #DataTable1;
SELECT * FROM #DataTable2;
--#Run
</pre>

Then it runs that script with the following parameters: the number of arguments is 2 (that is, @_Argv=2). #_Arg1 takes data from the <DataTableId_1> data table and #_Arg2 from the <DataTableId_2> data table.
<pre>
print 'Number of arguments: ' + cast(@_Argv as varchar(100));

SELECT * from #_Arg1;
(SELECT 'MaximumCount', '0')
--#ShowReport

SELECT * from #_Arg2;
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#SendEmail =
Sends an e-mail and writes a message to script log whether sending the email was successful or not. Script execution continues even when the sending isn't successful.

== Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; 'CatchOperationExceptions'
: Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
'''E-mail Parameters'''
; 'EmailFrom'
: Defines the from address for this e-mail message. Mandatory.
; 'EmailTo'
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.
; 'EmailSubject'
: Defines the subject of the email. Default value is empty. Optional.
; 'EmailBody'
: Defines the message body. Default value is empty. Optional.
; 'EmailCc'
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailBcc'
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.
; 'EmailIsBodyHtml'
: Defines whether the e-mail message body is in HTML. TRUE or any other Integer than "0" = body is in HTML, FALSE or "0" = body is not in HTML. Default value is FALSE. Optional.
; 'EmailSender'
: Defines the sender's address for this e-mail message. Default value is empty. Optional.
; 'EmailReplyTo'
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.
; 'EmailPriority',
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.
; 'EmailDeliveryNotification'
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.
; 'EmailBodyEncoding'
: Defines the encoding used to encode the message body. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.
; 'EmailSubjectEncoding'
: Defines the encoding used for the subject content for this e-mail message. Supported encodings are listed in the "Remarks" section at http://msdn.microsoft.com/en-us/library/System.Text.Encoding.aspx. Optional.

'''SMTP Server Parameters'''
; 'SmtpServer'
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.
; 'SmtpPort'
: Defines the port of the SMTP server. Default value is "25". Optional.
; 'SmtpAuthenticationUsername'
: Defines the user name for the SMTP server. Note that the user name is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpAuthenticationPassword'
: Defines the password for the SMTP server. Note that the password is in plain text and visible to all users who have access to the script. Optional.
; 'SmtpEnableSSL'
: Defines whether SSL should be enabled for the SMTP connection. TRUE or any other Integer than "0" = SSL is enabled, FALSE or "0" = SSL is not enabled. Default value is "FALSE". Optional.

== Example ==
The following example will send an e-mail message to multiple recipients.
<pre>
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL
(SELECT 'SmtpServer', 'localhost')
--#SendEmail
</pre>

See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].

= --#ShowReport =
Creates a new Excel sheet containing a table that contains the results of the user specified SQL query. The result column names are the field names of the SQL query and the rows are the actual data rows of the SQL query. The report can be used to see, for example, the events that would be loaded into QPR ProcessAnalyzer before actually loading them. If the events have problems that cause errors when loaded it is useful to be able to see the row data in a report.
'''Note:''' Excel cannot handle more than 1 million rows to be shown so if the result set contains more rows than that, the data will be truncated to 1 million rows.

This command takes two SELECT queries as parameters.
== First Query ==
A user specified SQL query to be shown in the configured Excel sheet.
; <nowiki>'<data>'</nowiki>
: Mandatory. The database query whose results are to be returned.

== Second Query ==
Configures the command using a SELECT statement returning two columns: the first column is for a key and the second one is for a value of that key. The values in both the key column and in the value column are of type NVARCHAR. The supported keys for this command are: 
; '<Analysis Parameter>'
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:
:; 'Title'
:: The title of the created report. If not given, "Report" will be used as a default.
:; 'SheetName'
:: The name of the Excel sheet to be created.
:; 'MaximumCount'
:: The maximum number of rows to show (0 = all, default = 1000).
; 'CatchOperationExceptions': Optional. Defines whether to stop the script execution or to continue to run the script from the next statement if an exception occurs when running the script:
: 1 = don't stop execution of the script, continue running the script from the next statement.
: 0 = stop execution of the current script and show the exception.
: The following script variables will be set and are shown in the script log:
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
:<code>@_ExceptionDetails</code> If there was an exception, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.

== Example ==
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.
<pre>
(SELECT 'AnalysisType', '18') UNION ALL
(SELECT 'ProjectName', 'Test') UNION ALL
(SELECT 'DataTableName', 'SqlTable') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

SELECT * FROM #AnalysisResult;
(SELECT 'Title', 'Report1') UNION ALL
(SELECT 'SheetName', 'Sheet1') UNION ALL
(SELECT 'MaximumCount', '0')
--#ShowReport
</pre>

= --#WriteLog =
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.

In addition to the WriteLog command, you can also use the [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] to generate log entries into the script execution log. The difference to the WriteLog command is that the Print statement can use also variables.

== Examples ==
The following example will write "Script started", "Example", "Print Example" into the log.
<pre>
SELECT 'Script started'
SELECT 'Example'
--#WriteLog
PRINT 'Print Example'
</pre>

SQL Scripting for ETL

2015-10-01T10:46:54Z

RiiPekk: 216456

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]]. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''"Client exception" is thrown when running a script with #ImportSapQuery command using the 'SapWhereClauseSelect' parameter. What causes this?
:For example, the following error text can be displayed:
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters) in d:\DEV\SVN_PA2013\Source\ProcessAnalyzer\Common\Integration\Sap.cs:line 371
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQueryImport(Action`2 importOperation, SqlDatabaseOperationBase sandboxOperation, Boolean allowNonTemporaryTables, Boolean enableStreamCompression, IDictionary`2 parameters, Action`2 getSapWhereClauseSelect) in d:\DEV\SVN_PA2013\Source\ProcessAnalyzer\Common\Integration\Sap.cs:line 185
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface (Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP using 'SapWhereClauseSelect' parameter. The SAP system has limitations as to how much data can be queried. The workaround for this error is to reduce the amount of data to be queried with 'SapWhereClauseSelect' from SAP.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

SQL Scripting for ETL

2015-10-01T10:43:10Z

RiiPekk: 216456

It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via scripts using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.

A user with the ManageIntegrations and RunScripts permissions can define a script via the [[Script Management#Script Manager|Manage Scripts]] dialog. The script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.

For examples, see [[ETL Script Examples]]. The supported commands and their descriptions are listed in [[Supported QPR ProcessAnalyzer Commands in Scripts]].

__TOC__

== Script Variables ==
The scripts have the following variables available:
* '''@_ProjectId''': the Id of the project in whose context the script is being run. BIGINT.
* '''@_ModelId''': the Id of the model in whose context the script is being run. BIGINT.
* '''@_FilterId''': the Id of the filter in whose context the script is being run. BIGINT.
* '''@_QPRProcessAnalyzerVersion''': the QPR Process Analyzer core dll version as string in the format: <major>.<minor>.<build>.<revision>. NVARCHAR(64).
* '''@_ScriptingVersion''': The scripting version number that identifies the version which was used when script was saved. Can be used for indicating, for example, the version for which the script was originally planned. A script created for newer (bigger) scripting version doesn't necessarily work on a PA server supporting older (smaller) version. INT.
* '''@_UserId''': the Id of the user running the script. INT.
* '''@_ScriptId''': Id of the script being run. BIGINT.
* '''@_EngineScriptingVersion''': The scripting version that identifies the functionalities available from QPR ProcessAnalyzer server. A script created for newer (bigger) scripting version doesn't necessarily work on a QPR ProcessAnalyzer server supporting older (smaller) version. INT.
* '''@_DatabaseId''': the Id of the database in use. GUID.
* '''@_ExceptionOccurred''': if there was an exception when running the script, then this value is 1, otherwise 0. INT
* '''@_ExceptionType''': if there was an exception when running the script, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionMessage''': if there was an exception when running the script, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.
* '''@_ExceptionDetails''': if there was an exception when running the script, contains the details that would have been displayed, including the system stack trace, NVARCHAR(MAX), otherwise NULL.
* '''#_ViewSettings''': The Settings shown in the right-hand pane in Excel used to generate the selected view. Note that this doesn't include analysis results or QPR ProcessAnalyzer Server related information, such as FilterId, TotalEventCount, or DatabaseId. Represented as a table two column table variable. The columns are:
** Name: the name of the parameter. NVARCHAR(440).
** Value: the value of the parameter. NVARCHAR(MAX).
* '''#_Selection''': The objects the user has currently selected on the analysis. Supported objects are the event types and transitions in the Flowchart or Path analyses and the Excel cells in the Duration, Profiling, Cases, Variations, Event Types, or Flows analyses. Any filters already applied are included in the selection. The maximum supported amount for the selection is 1000 separate objects and 10000 cells and their values. Represented as a three column table variable. The columns are:
:* Type: the type of the selected object. INT.
:{|
|STYLE="vertical-align: top"|
{| class="wikitable"
! Type
! Description
|-
|0
|Common. Values for the Common Type are represented as a Value-IntValue pair. See the table on the right for descriptions.
|-
|2
|Activity
|-
|6
|Activity Path
|-
|8
|Attribute Value
|-
|10
|Case
|-
|12
|Count
|-
|14
|Duration
|-
|16
|Transition
|-
|18
|Variation
|}
|STYLE="vertical-align: top; padding-left: 20px"|
{| class="wikitable"
! Common Type Value
! Description
|-
|NumberOfActivities
|The amount of activities in the selection.
|-
|NumberOfActivityPaths
|The amount of activity paths in the selection.
|-
|NumberOfAttributeValues
|The amount of attribute values in the selection.
|-
|NumberOfCases
|The amount of cases in the selection.
|-
|NumberOfCounts
|See the "Group By Event Count" entry in the [[Variations]] page.
|-
|NumberOfDurations
|The amount of durations in the selection.
|-
|NumberOfTransitions
|The amount of transitions in the selection.
|-
|NumberOfVariations
|The amount of variations in the selection.
|-
|DurationGranularity
|The duration time unit used in the selection. See the "Group By" entry in the [[Duration Analysis]] page for reference.
|-
|DurationMaximum
|The duration limit in the selection. See the "Duration Limit" entry in the [[Duration Analysis]] page for reference.
|-
|ReversedPaths
|The value is "1" if the "Predecessors" Direction was selected in the [[Path Analysis]], otherwise "0".
|-
|SelectionType
|What was selected. The value for this parameter is shown on the "Value" column instead of the IntValue column.
|}
|}

* IntValue: the integer representation of the selection value (used for object IDs etc). BIGINT.
* Value: the string representation of the selected value. Used for selections that require more complex representation than single integer value. NVARCHAR(MAX).
 

Note that even when a script context hasn't been selected, the variables get their values from a default filter. The default filter is the filter that was last used by the user in the model the user has last opened. If the user hasn't opened any model before, the default filter is taken from the last created model to which the user has access rights.

: '''Example'''
: The following script fragment defines the ProjectId, ModelId, and FilterId parameters by using the script variables:
<pre>SELECT @_ProjectId as ProjectId, @_ModelId as ModelId, @_FilterId as FilterId;</pre>

: '''Example'''
: The following script gets the View Settings currently in use in the Settings pane in Excel and shows them as a table in a new Excel sheet:
<pre>(SELECT * FROM #_ViewSettings)
(SELECT 'SheetName', 'ViewSettings')
--#ShowReport</pre>

: '''Example'''
: The following script gets the current selection on the analysis and shows the data as a table in a new Excel sheet:
<pre>(SELECT * FROM #_Selection)
(SELECT 'SheetName' , 'Selection')
--#ShowReport</pre>

: '''Example'''
: The following script gets various information about the environment and shows them in a new Excel sheet:
<pre>SELECT @_QPRProcessAnalyzerVersion as QPRProcessAnalyzerVersion, @_ScriptingVersion as ScriptingVersion, @_EngineScriptingVersion as EngineScriptingVersion, @_UserId as Userid, @_DatabaseId as DatabaseId
(SELECT 'SheetName', 'Info')
--#ShowReport</pre>

== Exception Handling ==
In general, scripts are meant to be developed in such a way that in the end you can run the scripts without any errors. However, sometimes there may be some system issues (timeouts SAP etc.) that can cause for example data extraction scripts to fail. For these kind of situations and for development time and troubleshooting purposes, you can use the CatchOperationExceptions parameter and the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables with the QPR ProcessAnalyzer script commands to handle exceptions in ProcessAnalyzer. Out of these, the @_ExceptionOccurred is handy for example in defining some other command to be run in case there was an exception. For SQL errors, the TRY-CATCH error handling should be used. 
 
Note that the CatchOperationExceptions parameter is in effect only for the command it is used with, i.e. it isn't in effect in child scripts or scripts that are run via the --#Exit command. In addition, when there are multiple ProcessAnalyzer script commands in the script, the @_ExceptionOccurred, @_ExceptionType, @_ExceptionMessage, and @_ExceptionDetails script variables get updated each time, i.e. the variable values are available only until the next ProcessAnalyzer command is executed. To use the same variable values in multiple ProcessAnalyzer commands in the script, place the values into a temporary table: 
<pre>
SELECT
@_ExceptionOccurred 'ExceptionOccurred',
@_ExceptionType 'ExceptionType',
@_ExceptionMessage 'ExceptionMessage',
@_ExceptionDetails 'ExceptionDetails'
INTO #PACommandExceptions</pre>

== SQL Command Support ==
When transforming data in QPR ProcessAnalyzer Pro (i.e. when connected to the QPR ProcessAnalyzer Service), only temporary tables (#) should be used. Note that '''global''' temporary tables (##) should never be used in the SQL scripts, and using them is not allowed. When using QPR ProcessAnalyzer Xpress, these limitations do not apply.

==== Print ====
The [http://msdn.microsoft.com/en-us/library/ms176047.aspx Print SQL statement] can be used to generate log entries into the script execution log.

== Running Scripts ==
A script can be run in the following ways:

=== Running a Script from the Ribbon ===
# On the QPR tab of the ribbon, click '''Run'''.
# Select the script to be run from the Script Gallery that opens.

=== Running a Script from the Manage Scripts Dialog ===
# On the QPR tab of the ribbon, click '''Manage Scripts'''.
# From the dialog, select the context in which the script you wish to run exists.
# Select the script you wish to run.
# Click '''Run'''.

== Terminating Scripts ==
A script can be terminated by the following ways:
*The user running the script can click the '''Cancel''' button when the script is running.
*The script can use the "--#Exit" command to stop script execution.
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operation Log.
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.
*The Internet Information Services Administrator can recycle the application pool if the script has caused it to hang. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.
*The Windows Administrator can kill the w3wp.exe-process processing a problematic script. Note however, that this may also cause other requests by other users being processed at the same time to be aborted.

'''NOTE!''' 
Terminating the script will not revert any changes the script has already done in the database before the Cancel button is clicked.

== Things to Note About Scripts ==
When writing and using scripts, take the following things into account:
* Only those lines in the script that start with "--#" (without the quotes) are treated as QPR ProcessAnalyzer Commands, i.e. if there are leading whitespaces before the command, the line is treated as a comment.
* If you don't define a value for the MaximumCount parameter, 1000 will be used as default, i.e. only the 1000 first rows from a given table or model will be used.
* When doing more advanced operations with scripts, you may run into the error messages such as: "'''The data types sql_variant and varchar are incompatible in the add operation.'''", "'''Argument data type sql_variant is invalid for argument 1 of like function.'''", "'''Argument data type sql_variant is invalid for argument 1 of left function.'''". This is because [[Case Attribute|case attributes]], [[Event Attribute|event attributes]], and data inside [[Data Table|data tables]] are '''sql_variant''' type data. In order to use them with more advanced operations (e.g. Add), you need to CONVERT or CAST them into some other data type before the operations. See [[#ConvertExample|this example]].
* For certain characters in attribute values, you need to use escaping in order to have them interpreted correctly in the script. For more information, see [[Attribute Values|Escaping for Attribute Values]].

== Troubleshooting Scripts ==
After a script has been run, the [[Script Log]] dialog is shown. You can use it to troubleshoot your script.

=== Invalid Object Name ===
* '''"Invalid object name" exception is thrown when running a script with #GetAnalysis and #ImportEvents commands. What causes this?
: The issue may arise when there are no events to import, i.e. the #GetAnalysis command doesn't create any table. In this case, the missing event table needs to be created in the script between the #GetAnalysis and #ImportEvents commands:
<pre>
/*This is the GetAnalysis part */
(SELECT 'AnalysisType', '6') UNION ALL
(SELECT 'MaximumCount', '0') UNION ALL
(SELECT 'FilterId', '10') UNION ALL
(SELECT 'SelectedEventAttributes', '*') UNION ALL
(SELECT 'TargetTable', '#AnalysisResult')
--#GetAnalysis

/*Here we create the event table, if it is missing */
IF object_id('tempdb..#AnalysisResult') is null
BEGIN
CREATE TABLE #AnalysisResult (
CaseName NVARCHAR(MAX),
EventTypeName NVARCHAR(MAX),
TimeStamp DATETIME,
Cost FLOAT,
TotalCost FLOAT
);
END

/*Then we use the ImportEvents */
(SELECT 'ProjectName', 'ExampleProject') UNION ALL
(SELECT 'ModelName', 'ExampleModel')
(SELECT * FROM [#AnalysisResult])
--#ImportEvents
</pre>

=== Incorrect Syntax When Using ' Characters ===

* '''SQL error: Incorrect syntax near ' '''
:If you get this error message, check the ' characters in the parameter definitions. Note that you cannot use the ' character in the parameter value.

=== Incorrect Syntax When Running Scripts Copied from QPR ProcessAnalyzer Wiki ===

* '''SQL error: Incorrect syntax'''
: You may get this kind of error message when trying to run a script that you have copied and pasted directly from, for example, the examples given in [[Data Extraction, Transformation, and Loading#Supported QPR ProcessAnalyzer Commands in Scripts|Supported QPR ProcessAnalyzer Commands in Scripts]]. This happens because the scripts are then likely to contain non-breaking spaces (encoded as 0xA0 but not visible when pasted to the '''Script Code''' field) which cause the running of the scripts to fail as they are not accepted in the SQL syntax.

: The solution is to manually remove the non-breaking spaces after copying and pasting the script, so there are no extra spaces at the beginning of each line, for example.

=== Using "##" in a Script ===

* '''Using "##" in a script is not allowed. Did you mistype temporary table name?'''
: This error message is displayed if the name of the project or model name contains two consecutive # characters (i.e. ##) and you try creating a new project or a model using scripts. Note that you cannot use the ## character in the name of the project or the model.

=== The ? Character in Project and Model Names ===

* '''A project or model name contains question marks.'''
: The problem arises if you try to, for example, create a project or a model with a name containing multibyte characters using scripts. The created project or model will then include question mark characters instead of multibyte characters. The fix is to add a prefix N' to the name containing multibyte characters (for example, N'【隱藏▲】【純文字檢視】【複製到剪貼簿】'). Another workaround is not to use multibyte characters at all in scripts but instead ProjectId and ModelId, if possible. To do that, you can view the Id column in the Models tab of the Workspace dialog in the same way as described for data tables in [[Workspace#Adding_an_Id_Column_to_the_Data_Tables_List|Adding an Id Column to the Data Tables List]].

=== Multiple Projects with the Same Name ===

* '''"There are multiple projects with name '<ProjectName>'. Please, specify ProjectId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several projects with the same name and you refer to the project by name in the script. The fix for resolving this ambiguity is to refer to the project by its ID using the 'ProjectId' parameter instead of 'ProjectName'. An ID is always unique, whereas a name is not.

=== Multiple Models with the Same Name ===
* '''"There are multiple models with name '<ModelName>'. Please, specify ModelId in sandbox script operation: #<Operation>"'''
: This error message is displayed when trying to run a script if you have access to two or several models with the same name and you refer to the model by name in the script. The fix for resolving this ambiguity is to refer to the model by its ID using the 'ModelId' parameter instead of 'ModelName'. An ID is always unique, whereas a name is not.

{{UnicodeComparison}}
* For example, the following script will show characters that are treated similar as zero "0":
<pre>
DECLARE @referenceAscii int = 0

IF object_id('tempdb..#ids') is null
CREATE TABLE #ids ( id int)

DECLARE @i int = 0
WHILE @i < 70000 BEGIN
SET @i = @i + 1
INSERT #ids VALUES (@i)
END

select * FROM (
select
sys.fn_varbintohexstr(CONVERT(varBINARY(8), id)) as CharacterAsHex,
id as ASCIICode,
nchar(id) as Character,
(CASE WHEN Nchar(@referenceAscii) = NCHAR(id) THEN 1 ELSE 0 END) as ShownAsSimilar
FROM #ids ) as x
where x.ShownAsSimilar = 1
--#ShowReport
</pre>

=== Client Exception When Using #ImportSapQuery Command ===

* '''"Client exception" is thrown when running a script with #ImportSapQuery command (see below for an example error text). What causes this?
<pre>
#ImportSapQuery: SAP.Middleware.Connector.RfcAbapRuntimeException: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg()
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count)
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length)
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid)
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function)
at SAP.Middleware.Connector.RfcFunction.RfcDeserialize(RfcConnection conn, IRfcIOStream stream)
at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, IRfcIOStream stream, RFCID rid)
at SAP.Middleware.Connector.RfcFunction.Invoke(RfcDestination destination)
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQuery(RfcDestination destination, Action`2 getSapWhereClauseSelect, Boolean enableStreamCompression, IDictionary`2 parameters) in d:\DEV\SVN_PA2013\Source\ProcessAnalyzer\Common\Integration\Sap.cs:line 371
at Qpr.ProcessAnalyzer.Common.Integration.Sap.SapQueryImport(Action`2 importOperation, SqlDatabaseOperationBase sandboxOperation, Boolean allowNonTemporaryTables, Boolean enableStreamCompression, IDictionary`2 parameters, Action`2 getSapWhereClauseSelect) in d:\DEV\SVN_PA2013\Source\ProcessAnalyzer\Common\Integration\Sap.cs:line 185
System.ServiceModel.FaultException`1[Qpr.Utils.SapError]: SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface (Fault Detail is equal to SAP.Middleware.Connector.RfcAbapRuntimeException: Error in module RSQL of the database interface</pre>

:This issue may arise when you are extracting data from SAP with 'SapWhereClause' parameter. The SAP system has limitations as to how much data can be queried. The workaround for this error is to reduce the amount of data to be queried with 'SapWhereClauseSelect' from SAP.

== [[Supported QPR ProcessAnalyzer Commands in Scripts]] ==
For a list of supported commands and their descriptions, see page [[Supported QPR ProcessAnalyzer Commands in Scripts]].
[[Category:ETL]]
[[Category:API]]

QPR ProcessAnalyzer Release Notes

2015-10-01T07:03:03Z

RiiPekk: 216556

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Next Release: QPR ProcessAnalyzer 2015.6 ==

'''Bugs:''' 
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script. 

== Past Releases ==

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''

QPR ProcessAnalyzer Release Notes

2015-09-24T12:06:28Z

RiiPekk: 306475

This page introduces each new QPR ProcessAnalyzer release. 

For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].

== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==

'''Features:''' 
-306448: A new service product, [[QPR IntegrationPlatform]], is introduced. QPR IntegrationPlatform allows users to create new projects and data tables, and to run ETL scripts. Changes have also been made to the user interface of QPR ProcessAnalyzer Excel Client in order to improve user experience. 
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients. 
-306467: In preparation for upcoming support of the MS Office 2016 release and Windows 10 operating system, the installer for QPR ProcessAnalyzer has been updated. 
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service. 
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system. 
-306486: Four new demo models (SAP_OrderToCash_Extended, SAP_PurchaseToPay, LoanApproval, and ServiceTicket) have been added to [[Sample Files]] that come with QPR ProcessAnalyzer installation. 

'''Bugs:''' 
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side. 
- 216465: Fixed a performance issue with Influence Analysis. 
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments. 
__TOC__

== Past Releases ==

== Hotfix with version number 2015.5 (release date 26.8.2015) ==
This hotfix contains the following fix and is available as build 2015.5.0.33323. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information. 
'''Bugs:''' 
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.

== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==

'''Features:''' 
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters. 
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed. 
- 306406: Scripts can now be [[Script Encryption|encrypted]].

'''Fixed Bugs''': 
- 214282: Fixed an issue in old databases to comply with the current implementation where all models are considered base models (i.e. there are no child models anymore). 
- 215227: Fixed an issue when the value "(others)" is selected as a filter in Profiling Analysis so that an error message will now be shown. 
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client. 
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar. 
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file. 
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models. 
- 215999: Fixed an issue with user roles so that creating new data tables requires now also any one of the following global roles: Administrator, Model Creator or Evaluator. 
- 216057: Fixed an issue where QPR ProcessAnalyzer Excel Add-in crashed when a user opened an Excel file in protected mode and tried to enable editing. 
- 216070: Fixed an issue related to Evaluator user rights. 
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT. 
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script. 
- 216152: Fixed an issue where old data still existed in a temporary table when importing data to a temporary table with the import Data Table commands using the parameter Append = 0. 
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]]. 
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown. 
- 216189: Fixed an issue where the QPR ProcessAnalyzer Excel Client was connected to a database initialized with newer initialization script versions than the used client. 
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id". 
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped. 
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type. 
- 216218: Fixed the error message for a network connection problem. 
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel. 
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row. 
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon. 
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter. 
- 216262: Fixed an issue where after each import, all the variations that were not used by any case existing in the model were removed, causing variation dependent filters to no longer work as expected. 
- 216269: Fixed an incorrect label in the Bookmark Properties dialog. 
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog. 
- 216329: Fixed the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]] so that deleted models, projects, scripts or data tables are not returned in the analysis by default. 
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model. 
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations. 
- 216352: Fixed an issue where import of a model caused variations to be updated for all models. 
- 216355: Fixed an issue with the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ShowReport|ShowReport command]] related to an Excel limitation of showing only 1 million rows of data. 
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded. 
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service. 
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured. 
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit. 
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer. 
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights. 
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress. 
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark. 
- 216432: Fixed a performance issue with GetAnalysis operation. 
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.
 
- 216436: Fixed an issue with filters not working in a customer production environment. 

== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==

'''Features:''' 
- 306343: The SQL Server Express LocalDB Instance API has been taken into use for LocalDB instance startup. This makes it possible to support multiple different versions of LocalDB. 
- 306358: Several performance improvements have been implemented to enhance the Cancel operation, importing of attributes, and updating of variations, among other things. There is also a new ValidateModel function available for QPR ProcessAnalyzer [[Web Service API]]. 
- 306372: There is a a new tool, [[Using QPR ProcessAnalyzer Integration Kit|QPR ProcessAnalyzer Integration Kit]], which consists of QPR ProcessAnalyzer ETL scripts making integration to other systems, such as your own SAP or SQL system, easier. 
- 306377: A new [[Analysis Parameters|analysis parameter]], IncludeEventIds, has been added for use in the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command with Event Analysis when running scripts. This enables, for example, removing certain events from the model with the [[Data_Extraction,_Transformation,_and_Loading#--.23RemoveEvents|RemoveEvents]] command.
 
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.

'''Fixed Bugs:''' 
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client. 
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading. 
- 215490: Fixed an issue where the analysis parameters could not all be shown in the comment field of the A1 cell due to an Excel length limit. 
- 215775: Fixed an issue where having dots in database names was causing an error. 
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied. 
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings. 
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty. 
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties. 
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly. 
- 216162: Fixed an error which occurred when opening Case Analysis. 
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user. 
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client. 
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly. 
- 216190: Fixed a performance issue related to reading scripts from the server. 

=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===

'''Features''': 
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]]. 
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]]. 
- For users with Administrator rights, it is now possible to set any configured filter to be the Model Default filter in the [[Filters|Filter Manager]].

'''Fixed Bugs''': 
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset. 
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values. 
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view. 
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up. 
- 216091: Fixed an issue with importing data tables where the parameter "Append=0" did not remove the contents of the data table before the import. 
- 216122: Optimized the Workspace opening to take less time.

=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===

'''Features''': 
- Four new analysis types (Model Report, Project Report, Data Table Report, and Script Report) are now available for the [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis]] command when running scripts. 
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations. 
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]]. 

'''Fixed Bugs''': 

- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script. 
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace. 
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view. 
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system. 
- 215855: Fixed an issue related to timestamps when importing events. 
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function. 
- 215959: Fixed a performance issue related to importing events. 
- 215960: Fixed a performance issue related to opening Project Workspace. 
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views. 
- 216023: Instead of the Exit script command accepting invalid RunScriptId parameter values, an exception is now thrown. In addition, the RunScriptId parameter can now have an empty value. 
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed. 
- 215968: Fixed an issue where the number of events in a model that was copied was not correct. 

=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===

'''Features''': 
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]]. 
- When performing an operation in QPR ProcessAnalyzer, the status of each operation is now shown in more detail in the [[Progress Status]] dialog to enable monitoring its progress. 
- There is a new [[Progress Log]] listing the recent operations and their progress. 
- Microsoft .NET 4.5.1 Framework has been taken into use. 
- The contents of the SAP where clause parameters used in the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] are now visible in the [[Script Log]] after the script is finished. 
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.

'''Fixed Bugs''': 
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error. 
- 213703: Fixed an issue where list customization was lost when opening an element. 
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks. 
- 215381: A warning message is now displayed to the user before the start of copying a large model. 
- 215474: The HealthcareData sample file now contains instructions for using the sample data. 
- 215517: Fixed an issue where the user got a system exception when trying to open a model that was larger than allowed for the user's product activation. 
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail. 
- 215678: Fixed an issue related to the handling of broken bookmarks. 
- 215691: Fixed an issue where no log was written when opening a sample file failed. 
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened. 
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell. 
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel. 
- 215773: Fixed an issue where sandbox related information was missing from the Excel log. 
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly. 

=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===

'''Features''': 
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].

'''Fixed Bugs''': 
- 213234: Fixed an issue where an error message occurred after deleting a model. 
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report. 
- 213785: Fixed an issue where an overflow of text data in a single cell occurred. 
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client. 
- 214106: Fixed a script import issue by removing the support for .pasql import. 
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's. 
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception. 
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message. 
- 215044: Fixed an issue with client version mismatch dialog. 
- 215165: Fixed an issue where opening a Data Table with the name 'Events' in the Excel client resulted in opening the Settings pane for Event analysis. 
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'. 
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others. 
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database. 
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted. 
- 215394: Fixed an issue in the Web Client where event attributes in the Influence analysis were included in the attributes list in the Settings pane. 
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client. 
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute. 
- 215472: Fixed an issue where deleted filters were not removed completely from a model. 
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view. 
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI. 
- 215492: Fixed an issue where an error message was shown if a user tried to import large amount of case attributes, event attributes or a data table with many columns. 
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost. 
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing. 
- 215513: Fixed an issue where an error occurred when trying to load a big table to a temporary table in the script with the GetAnalysis command. 
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness. 
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB. 

=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===

'''Features''': 
- For optimization purposes, the internal database format has been changed for event and case attributes (see [[Migrating_to_QPR_ProcessAnalyzer_2014.2|Migrating to QPR ProcessAnalyzer 2014.2]]). 
- A limit has been introduced for the number of attributes in a model, so there can now be a maximum of 300 case attributes or event attributes in one model. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] command available for extracting data from an ADO.NET source (the SQL Server database) and importing it to QPR ProcessAnalyzer. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] command available for extracting data from an OLE DB source and importing it to QPR ProcessAnalyzer. 
- The commands [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]], [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOleDbQuery|ImportOleDbQuery]] and [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSqlQuery|ImportSqlQuery]] now have a new parameter 'ExecuteInClientSide' which makes it possible to execute these commands in the client side also when using QPR ProcessAnalyzer Pro. 
- The [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command now has a new parameter 'SapFunction' which makes it possible to specify the value for the SAP function to be called.

'''Fixed Bugs''': 
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view. 
- 214842: Fixed an issue where there are projects with the same name, calling the project by its name in an ETL script targeted one of the projects randomly. 
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings. 

=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===
'''Features''': 
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer. 
- Version numbering scheme in QPR ProcessAnalyzer was updated. 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportOdbcQuery|ImportOdbcQuery]] command available for extracting data from an ODBC source and importing it to QPR ProcessAnalyzer. 
- In [[Flowchart_Animation#Selecting_a_Case_for_Drill-down_Analysis|animation]], it is now possible to select one or several cases and perform drill-down analysis on them. 

'''Fixed Bugs''': 
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long. 
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows. 
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered. 
- 214736: Fixed an issue where transferring a large Data Table (1000000 rows containing more than 1GB data) to a temporary table resulted in a timeout exception. 
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables. 
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.

=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23ImportSapQuery|ImportSapQuery]] command available for extracting data from a SAP system and importing it to QPR ProcessAnalyzer. 
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].

=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===
'''Features''': 
- Added the "Show", "Title", and "SheetName" parameters for the [[Data Extraction, Transformation, and Loading#--.23GetAnalysis|GetAnalysis]] command and the "SheetName" parameter for the [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command. 
- It is now possible to start executing other scripts by using the new "RunScriptId" parameter of the [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command. 
- Added support for a number of [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|Script Variables]] that can be used for getting various information about the QPR ProcessAnalyzer environment as well as the Analysis Settings and analysis object selections that the current user has made. 
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes. 

'''Fixed Bugs''': 

- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service. 
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table. 
- 214393: Fixed an issue where bookmarks didn't remember excluded cases. 
- 214404: Fixed an issue where an error occurred after a project was deleted. 
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't. 
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models. 
- 214441: Fixed an issue where the @_FilterId variable was not updated properly. 
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer. 
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired. 
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session. 
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown. 
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]]. 

=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ImportSalesforceQuery|ImportSalesforceQuery]] command for importing data from Salesforce cloud into [[Data Table|Data Tables]] and temporary tables using a script. 
- To help in developing scripts, the Project Workspace dialog now has a tab that lists all the [[Workspace#Data_Tables|Data Tables]] in the selected project. 
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts. 
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.

'''Fixed Bugs''': 
- 213970: The import functionality was refactored. 
- 213988: The values shown in various analysis fields are now rounded to two or three decimal fractions depending on the analysis. In addition, if a value is exactly 0, only 0 is shown. 
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired. 
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013. 
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user. 
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users. 
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened. 
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation. 
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them. 
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands. 
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation. 
- 214040: Fixed an issue where the copied model and the source model were not identical. 
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu. 
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId". 
- 213686: The Flow Analysis performance was optimized a bit. 
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis. 
- 214115: Fixed an issue where exporting a deleted model caused an error. 

=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===
'''Features''': 
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting. 
- Importing data to [[Data Table|Data Tables]] using the Excel Client. 
- Support for Windows 8 and Microsoft Office 2013. 
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution. 
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.

'''Fixed Bugs''': 
- 213486: Querying event attribute values in Case Analysis is now faster. 
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models. 
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log. 
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given. 
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane. 
- 213873: In QPR ProcessAnalyzer Excel Client, fixed an issue where error was given if the A1 cell was in edit mode and a button was clicked. 
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis. 
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client. 
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes. 

=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts 
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis 
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation 
- Enhanced [[User Rights Report]] for easier user administration and access rights settings 
- 32-bit and 64-bit versions available from one installer package for easier delivery 
- New [[Start]] button and Login window allow automatic login and now also support logout 
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom 
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format 
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon... 

=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser 
- '''Collaboration''' – Share analysis results, comments and ideas within the project group 
- '''Project Workspace''' – Process models are grouped to projects 

=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer 
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud 

=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===
- Improved '''Security''' 
- Improved '''Performance''' 

=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' 
- Keep track of 'include/exclude' actions with '''View Filters''' 
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 

=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' 
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets 
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active 

=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations 
- '''User Groups''' for easier access rights settings 
- More informative '''Model, View & Report Managers''' 

=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===

- Show '''Case Attributes''' in Process Analysis 
- Show '''Event Attributes''' in Process Analysis 
- Profiling for '''Event Attributes''' 

=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===

- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution 
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ 
- '''64-bit version''' for 64-bit Microsoft Excel users 

=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===

- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level 
- [[Benchmarking|'''Benchmarking''']] for process analysis view 
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process 

=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===

- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis 
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis 
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems 

=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===

- '''Event Type Chart''' showing the order of activities as a Gantt chart 
- '''Process Cost Analysis''' with '''Weighted Durations''' 
- Improved filtering for '''Path Analysis''' 

=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===

- '''Easy navigation''' between filtered views 
- '''Graphical variation''' charts 
- '''Event attributes''' available in Cases list 

=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===

- '''Automated Business Process Discovery''' (ABPD) from Cloud 
- Support for '''large databases''' 
- Integration to '''SAP'''