https://wiki.onqpr.com/pa/api.php?action=feedcontributions&user=TeeLeht&feedformat=atomQPR ProcessAnalyzer Wiki - User contributions [en]2024-03-29T06:41:07ZUser contributionsMediaWiki 1.39.1https://wiki.onqpr.com/pa/index.php?title=Snowflake_Connection_Configuration&diff=22380Snowflake Connection Configuration2023-01-27T11:25:40Z<p>TeeLeht: Move traditional method to the end of this page</p>
<hr />
<div>This page describes the ''native'' method to use Snowflake where the process mining queries are run in the Snowflake and the eventlog data stays in the Snowflake. There are two steps to configure: setup a [[#Snowflake account configuration|Snowflake account]] and configure QPR ProcessAnalyzer to use the account through an [[#Set Snowflake ODBC connection|ODBC connection]].<br />
<br />
==Snowflake account configuration ==<br />
These instructions provide one possible way to configure the Snowflake account for QPR ProcessAnalyzer. Configuration can also be done differently based on requirements, e.g., if there is other use for the same Snowflake account. These instructions optionally set the least possible permissions for the Snowflake user account (minimum privilege principle).<br />
<br />
#Create a new Snowflake account in the Snowflake site: https://www.snowflake.com/ (or use an existing account). The account is created to the selected cloud platform and site, so consider a location that is close to the QPR ProcessAnalyzer hosting site.<br />
# Go to https://app.snowflake.com and login in to your Snowflake account.<br />
#In '''Account''' > '''Roles''', click the '''Role''' button to create a new role. Define '''Name''' ''QPRPA'', and click '''Create Role'''.<br />
# In '''Account''' > '''Users''', click the '''User''' button to create a new user. Define '''User Name''' ''QPRPA'' and define a strong password. Check also that the '''Force user to change password on first time login''' is disabled. Click the '''Create User''' button.<br />
#Select the created user, and click the '''Grant Role''' button. In the '''Role to grant''' list, select ''QPRPA'', and click '''Grant'''.<br />
#In '''Compute''' > '''Warehouses''', click the '''Warehouse''' button to create a new warehouse. Define '''Name''' ''QPRPA'', and select a suitable '''Size''' for the warehouse. In the '''Advanced Warehouse Options''', check that '''Auto Resume''' and '''Auto Suspend''' are enabled. Set the '''Suspend After''' time based on your performance requirements (for example 5 minutes is a good initial value). Click '''Create Warehouse'''.<br />
#(Optional security hardening) Select the created warehouse and in the '''Privileges''' section and click the '''Privilege''' button. For '''Role''', select the ''QPRPA'' role. For '''Privileges''', select '''MONITOR''', '''OPERATE''' and '''USAGE'''. Click the '''Grant Privileges''' button.<br />
#In '''Data''' > '''Databases''', click the '''Database''' button to create a new database. Define '''Name''' ''QPRPA'', and click the '''Create''' button.<br />
# (Optional security hardening) Select the created database, and in the '''Privileges''' section, click the '''Privilege''' button. For '''Role''', select the ''QPRPA'' role. For '''Privileges''', select '''USAGE'''. Click '''Grant Privileges'''.<br />
#Select the created database, and click the '''Schema''' button to create a new schema. Define '''Name''' ''QPRPA'', and click the '''Create''' button.<br />
#(Optional security hardening) Select the created schema, and in the '''Privileges''' section, click the '''Privilege''' button. For '''Role''', select the ''QPRPA'' role. For '''Privileges''', select '''CREATE VIEW''', '''CREATE TABLE''', '''CREATE FILE FORMAT''' and '''USAGE'''. Click the '''Grant Privileges''' button.<br />
#(Optional) If the connection to Snowflake is lost for some reason, QPR ProcessAnalyzer may not be able to cancel pending queries. To get pending queries automatically cancelled to save costs, it's advisable to change the ABORT_DETACHED_QUERY session setting to ''true'': https://docs.snowflake.com/en/sql-reference/parameters.html#abort-detached-query.<br />
#(Optional) Running a Snowflake warehouse consumes credits in the Snowflake account, and thus it's a good practice to set resource monitoring to control the credit usage: In '''Compute''' > '''Resource Monitors''', click the '''Resource Monitor''' button to create a new resources monitor. Choose suitable monitor settings for your needs, and click the '''Create Resource Monitor''' button.<br />
<br />
== Set Snowflake ODBC connection==<br />
To add the Snowflake ODBC connection to QPR ProcessAnalyzer, following steps are required:<br />
#Install Snowflake ODBC driver in the machine running QPR ProcessAnalyzer Server. More information about the ODBC driver installation: https://docs.snowflake.com/en/user-guide/odbc.html.<br />
#Configure Snowflake ODBC connection string to the [[PA_Configuration_database_table|QPR ProcessAnalyzer configuration table]]. When configuring Snowflake as instructed above, the following connection string can be used:<br />
<pre><br />
Driver={SnowflakeDSIIDriver};Application=QPR_ProcessAnalyzer;Server=<account_identifier>.snowflakecomputing.com;Database=QPRPA;Schema=QPRPA;Warehouse=QPRPA;Role=QPRPA;uid=QPRPA;pwd=<password><br />
</pre><br />
<br />
Replace ''<password>'' with the password of the QPRPA user. In addition, replace ''<account_identifier>'' with the account identifier of your Snowflake account. More information about finding your Snowflake account identifier: https://docs.snowflake.com/en/user-guide/admin-account-identifier.html.<br />
<br />
Please also include the ''Application'' tag to the connection string, identifying QPR ProcessAnalyzer related usage for collecting usage statistics.<br />
<br />
More information about Snowflake ODBC connection strings: https://docs.snowflake.com/en/user-guide/odbc-parameters.html<br />
<br />
==Using Snowflake tables managed by QPR ProcessAnalyzer==<br />
When a datatable is created in QPR ProcessAnalyzer, corresponding table is created in the Snowflake storing the actual data. The table is not yet created when a new datatable is created, but when there is at least one column in the datatable. The Snowflake tables created by QPR ProcessAnalyzer are named as follows: qprpa_dt_<databaseId>_<datatableId>, where <databaseId> identifies the QPR ProcessAnalyzer environment and <datatableId> identifies the datatable within the environment. The database id is set in the [[PA_Configuration_database_table|QPR ProcessAnalyzer configuration table]]. Due to the naming, it's possible to configure multiple QPR ProcessAnalyzer environments to use the same Snowflake database and schema. Alternatively, there can be different schemas or databases for each environment.<br />
<br />
Datatables can managed both in the QPR ProcessAnalyzer web UI and in the Snowflake. When datatables are modified in the Snowflake, a synchronization (see [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Datatable|see synchronize function]]) needs to be called in QPR ProcessAnalyzer to inform that the underlying data in Snowflake has changed. Creating and deleting datatables are operations that need to be done in the QPR ProcessAnalyzer web UI. Deleting the underlying table in the Snowflake corresponds to removing all rows and columns from the datatable.<br />
<br />
==Using Snowflake views as datatable source==<br />
QPR ProcessAnalyzer can be connected to any data in Snowflake by using Snowflake ''views'' (https://docs.snowflake.com/en/user-guide/views-introduction.html) that are linked to the QPR ProcessAnalyzer datatables. When a process mining query is made to the cases and events datatables, the queries in the linked Snowflake views are executed as part of the process mining queries.<br />
<br />
The views need to be created to the same Snowflake database and schema as the tables used by QPR ProcessAnalyzer (defined by the [[#Set Snowflake ODBC connection|ODBC connection string]]). If QPR ProcessAnalyzer has already created a table for the datatable, the table needs to be removed before the view can be created (as there cannot be both a table and a view with the same name). If the datatable doesn't have columns yet, the table doesn't exist, and it's enough to create the view. Note that the Snowflake tables behind the QPR ProcessAnalyzer datatables are managed by QPR ProcessAnalyzer automatically, whereas the Snowflake views need to be managed by users directly in the Snowflake.<br />
<br />
The view linked to a datatable needs to have a specific name which can be queried using the [[Navigation_Menu#Expression_Designer|Expression Designer]] with following query (define your datatable id):<br />
<pre><br />
DatatableById(<datatableId>).NameInDatasource<br />
</pre><br />
<br />
New view can be created in Snowflake based on the following example (replace <ViewNameInDatasource> with the result from the previous expression):<br />
<pre><br />
CREATE OR REPLACE VIEW "<ViewNameInDatasource>" AS<br />
SELECT * FROM VALUES (1, 'red'), (2, 'orange'), (3, 'yellow'), (4, 'green') AS Colors(Id, Value)<br />
</pre><br />
<br />
Note that table and view names used by QPR ProcessAnalyzer are in lower case, and thus the object names need to be written in quotation marks, because without the marks Snowflake will create the view in upper case (which would be an incorrect name).<br />
<br />
The SELECT part in the above statement can be any query allowed by the Snowflake. The query can also contain data transformations which means that those transformation will be performed when the dashboards are used in QPR ProcessAnalyzer. This is following the ELT (extract, load, transform) principle, where the non-transformed data is loaded into the system and needed transformations are performed when the data is used by QPR ProcessAnalyzer. Note that there is a negative impact on the performance when performing transformations on demand.<br />
<br />
When the view has been created, the [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Datatable|Synchronize]] needs to be called to update the status to QPR ProcessAnalyzer (define your datatable id):<br />
<pre><br />
DatatableById(<datatableId>).Synchronize()<br />
</pre><br />
<br />
When a datatable with a Snowflake view is deleted, the view in the datasource is not deleted (this is unlike to tables which are deleted). For datatables with Snowflake view, following data modification operation are not allowed: Import, Persist, AddColumn, Merge, RemoveColumns, RenameColumns, and Truncate.<br />
<br />
Note that the query in the view is executed using permissions of the user account defined in the [[#Set Snowflake ODBC connection|ODBC connection string]], and thus the permissions are managed in Snowflake. Still, the normal QPR ProcessAnalyzer datatable permissions are applied for datatable with Snowflake views, so if user cannot see the datatable, user cannot access the data in the view either.<br />
<br />
==Automatic query cancellation==<br />
If the result of a pending query running in Snowflake is not needed anymore, the query is automatically cancelled by QPR ProcessAnalyzer, to save costs and reserve computing capacity for new queries. Queries are cancelled, e.g., when user makes filtering in a dashboard or changes chart settings, because the new filter or settings will make an updated query and the old query (if still pending) is cancelled.<br />
<br />
== Alternative traditional ODBC Import method==<br />
Alternatively, the ''traditional'' method can be used to import data from Snowflake to QPR ProcessAnalyzer and use the QPR ProcessAnalyzer's in-memory calculation engine. More information about importing data from an ODBC datasource:<br />
*[[QPR_ProcessAnalyzer_Model_Datasources#ODBC_Datasource|Load models directly from ODBC]]<br />
*[[DataFrame_in_Expression_Language#Extract_Data_to_DataFrame|Import data from ODBC using expression scripting]]<br />
*[[SQL_Scripting_Commands#--.23ImportOdbcQuery|Import data from ODBC using SQL scripting]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Generic_Functions_in_QPR_ProcessAnalyzer&diff=21141Generic Functions in QPR ProcessAnalyzer2022-03-29T09:08:55Z<p>TeeLeht: </p>
<hr />
<div>== Aggregation functions ==<br />
Following aggregation functions are available:<br />
* '''Average''': Average of the items (sum of items divided by count of items). Can be used for numbers, [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#DateTime|DateTimes]] and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
* '''Count''': Number of items. Can be used for any type of data.<br />
* '''Median''': Median, i.e. the middle value of the sorted data. If there are even number of items, the average of the two middle items. Can be used for numbers, [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#DateTime|DateTimes]] and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
* '''Min''': Lowest/first value in the data. Can be used for data that can be sorted.<br />
* '''Max''': Highest/last value in the data. Can be used for data that can be sorted.<br />
*'''Percentile''': Percentile value. Can be used for numbers, [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#DateTime|DateTimes]] and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
*'''Stdev''': (Sample) standard deviation. Can be calculated for numbers, [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#DateTime|DateTimes]] and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
*'''Stdevp''': (Population) standard deviation. Can be calculated for numbers, [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#DateTime|DateTimes]] and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
* '''Sum''': Sum of the items. Can be used for numbers and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan|Timespans]].<br />
* '''StringJoin''': Joins array of strings together. The first parameter is a string that is placed between the joined strings.<br />
*'''Var''': (Sample) variance. Can be used for numbers.<br />
*'''Varp''': (Population) variance. Can be used for numbers.<br />
<br />
Examples:<br />
<pre><br />
Sum([3, 2, 4])<br />
Returns: 9<br />
<br />
Count([[1, 2], [3, 4, 5]])<br />
Returns: [2, 3]<br />
<br />
Sum([[1, 2], [3, 4, 5]])<br />
Returns: [3, 12]<br />
<br />
Percentile([1,2,3,4,5], 0.75)<br />
Return: 4<br />
<br />
Sum([])<br />
Returns: null<br />
<br />
StringJoin(", ", ["one", "two", "three"])<br />
Returns: one, two, three<br />
</pre><br />
<br />
When aggregating numerical values, ''null'' values are treated as zeros. Nulls can be removed with ''RemoveNulls'' function. In the Min and Max functions, nulls are ignored. Null values can be removed before aggregating (the following example shows how).<br />
<pre><br />
Average([1, 5, null])<br />
Returns: 2<br />
<br />
Average(RemoveNulls([1, 5, null])<br />
Returns: 3<br />
</pre><br />
<br />
Aggregation operations are performed to the leaf level. i.e. the deepest level in the hierarchy. When aggregating, the leaf level arrays are replaced by the aggregated values, and thus the depth of the hierarchy decreases by one. In addition to the aggregation functions, functions that modify the contents of leaf arrays ('''OrderBy''', '''Distinct''', ...), the operation will be performed separately for every leaf array.<br />
<br />
<pre><br />
OrderByValue([[4, 3], [2, 1]])<br />
Returns: [[3, 4], [1, 2]]<br />
</pre><br />
<br />
== Mathematical functions ==<br />
<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||Abs (Number)<br />
||Number<br />
||<br />
Calculates the absolute value of a specified number. Examples:<br />
<pre><br />
Abs(4)<br />
Returns: 4<br />
<br />
Abs(-2.7)<br />
Returns: 2.7<br />
<br />
Abs(0)<br />
Returns: 0<br />
</pre><br />
|-<br />
||Acos (Number)<br />
||Number<br />
||<br />
Calculates the angle whose cosine is the specified number. The parameter is a number representing a cosine, which must be between -1 and 1. Examples:<br />
<pre><br />
Acos(0.3584)<br />
Returns: 1.204242852965772<br />
<br />
Acos(-0.3584)<br />
Returns: 1.9373498006240213<br />
</pre><br />
|-<br />
||ArgMax (Object)<br />
||<br />
# Array or hierarchical object<br />
# Value expression<br />
||<br />
Returns those objects in the array giving maximum values for the given expression when evaluated in the object's context. Examples:<br />
<pre><br />
ArgMax([5, 1, 6, 4, 3, 3, 6, 5, 4, 1, 1], _)<br />
Returns: [6, 6]<br />
<br />
ArgMax(EventLogById(1).Cases, Duration)<br />
Returns: An array of cases having the longest duration.<br />
</pre><br />
|-<br />
||ArgMin (Object)<br />
||<br />
# Array or hierarchical object<br />
# Value expression<br />
||<br />
Returns those objects in the array giving minimum values for the given expression when evaluated in the object's context. Examples:<br />
<pre><br />
ArgMin([5, 1, 6, 4, 3, 3, 6, 5, 4, 1, 1], _)<br />
Returns: [1, 1, 1]<br />
<br />
ArgMin(EventLogById(1).Cases, Duration)<br />
Returns: An array of cases having the shortest duration.<br />
</pre><br />
|-<br />
||Asin (Number)<br />
||Number<br />
||<br />
Calculates the angle whose sine is the specified number. The parameter is a number representing a sine, which must be between -1 and 1. Examples:<br />
<pre><br />
Asin(-0.3584)<br />
Returns: 0.36655347382912462<br />
<br />
Asin(+0.3584)<br />
Returns: -0.36655347382912462<br />
</pre><br />
|-<br />
||Atan (Number)<br />
||Number<br />
||<br />
Calculates the angle whose tangent is the specified number. Examples:<br />
<pre><br />
Atan(1)<br />
Returns: 0.78539816339744828<br />
<br />
Atan(-1)<br />
Returns: -0.78539816339744828<br />
</pre><br />
|-<br />
||Ceiling (Integer)<br />
||<br />
Number<br />
||<br />
Returns the smallest integer that is greater than or equal to the specified number. Example:<br />
<pre><br />
Ceiling(1.3)<br />
Returns: 2<br />
</pre><br />
|-<br />
||Cos (Number)<br />
||Number<br />
||<br />
Calculates the cosine of the specified angle measured in radians. Examples:<br />
<pre><br />
Cos(1)<br />
Returns: 0.54030230586813977<br />
<br />
Cos(-1)<br />
Returns: 0.54030230586813977<br />
</pre><br />
|-<br />
||Exp (Number)<br />
||Number<br />
||<br />
Calculates the e raised to the specified power. Examples:<br />
<pre><br />
Exp(1)<br />
Returns: 2.7182818284590451<br />
<br />
Exp(-1)<br />
Returns: 0.36787944117144233<br />
</pre><br />
|-<br />
||Floor (Integer)<br />
||<br />
Number<br />
||<br />
Returns the largest integer that is less than or equal to the specified number. Example:<br />
<pre><br />
Floor(1.9)<br />
Returns: 1<br />
</pre><br />
|-<br />
||IEEERemainder (Number)<br />
||<br />
# Dividend (Number)<br />
# Divisor (Number)<br />
||<br />
Calculates the remainder resulting from the division of a specified number by another specified number. Uses formula:<br />
<pre><br />
dividend - (divisor * Round(dividend / divisor))<br />
</pre><br />
<br />
Note that the formula is different than in the % operator, which uses formula:<br />
<pre><br />
(Abs(dividend) - (Abs(divisor) * (Floor(Math.Abs(dividend) / Abs(divisor))))) * Sign(dividend) <br />
</pre><br />
<br />
Examples:<br />
<pre><br />
IEEERemainder(26, 4)<br />
Returns: 2<br />
<br />
IEEERemainder(0, 0)<br />
Returns: NaN<br />
</pre><br />
|-<br />
||Log (Number)<br />
||<br />
# Number<br />
# Logarithm base (Number)<br />
||<br />
Calculates the logarithm of a specified number. If the second parameter is not provided, it's the natural logarithm (base e). The second parameter can be used to define another base for the logarithm. Examples:<br />
<pre><br />
Log(5)<br />
Returns: 1.6094379124341003<br />
<br />
Log(10, 2)<br />
Returns: 3.3219280948873626<br />
</pre><br />
|-<br />
||Log10 (Number)<br />
||<br />
Number<br />
||<br />
Calculates the base 10 logarithm of a specified number. Examples:<br />
<pre><br />
Log10(5)<br />
Returns: 0.69897000433601886<br />
<br />
Log10(-5)<br />
Returns: NaN<br />
</pre><br />
|-<br />
||Pow (Number)<br />
||<br />
# Base number<br />
# Exponent number<br />
||<br />
Calculate a specified number raised to the specified power. Examples:<br />
<pre><br />
Pow(5, 3)<br />
Returns: 125<br />
<br />
Pow(-5, 3)<br />
Returns: -125<br />
</pre><br />
|-<br />
||Round (Float)<br />
||<br />
Number of decimals (Integer)<br />
||<br />
For numbers, rounds the number to the specified number of decimal. Number of decimals can also be negative, in which case the number is rounded to the nearest tens, hundreds, thousands, etc.<br />
<br />
For DateTimes, rounds given date time by given time span or given number of seconds.<br />
<br />
Note that the number and DateTime to be rounded needs to be provided as a context object (not as a parameter).<br />
<br />
Examples:<br />
<pre><br />
(1.254).Round(1)<br />
Returns: 1.3<br />
<br />
(162.111111).Round(-2)<br />
Returns: 200<br />
<br />
DateTime(2017, 1, 2, 3, 4, 5).Round(10)<br />
Returns: DateTime(2017, 1, 2, 3, 4, 10)<br />
<br />
DateTime(2017, 1, 2, 3, 4, 5).Round(TimeSpan(1))<br />
Returns: DateTime(2017, 1, 2)<br />
</pre><br />
|-<br />
||Sign (Number)<br />
||<br />
Number<br />
||<br />
Calculates an integer that indicates the sign of a number, either -1, 0 or 1. Examples:<br />
<pre><br />
Sign(10)<br />
Returns: 1<br />
<br />
Sign(0)<br />
Returns: 0<br />
<br />
Sign(10)<br />
Returns: -1<br />
</pre><br />
|-<br />
||Sin (Number)<br />
||<br />
Number<br />
||<br />
Calculates the sine of the specified angle. Examples:<br />
<pre><br />
Sin(3.14)<br />
Returns: 0.0015926529164868282<br />
<br />
Sin(-3.14)<br />
Returns: -0.0015926529164868282<br />
</pre><br />
|-<br />
||Sqrt (Number)<br />
||<br />
Number<br />
||<br />
Calculates the square root of a specified number. Examples:<br />
<br />
<pre><br />
Sqrt(81)<br />
Returns: 9<br />
<br />
Sqrt(0.9)<br />
Returns: 0.3<br />
</pre><br />
|-<br />
||Tan (Number)<br />
||<br />
Number<br />
||<br />
Calculates the tangent of the specified angle. Examples:<br />
<br />
<pre><br />
Tan(1)<br />
Returns: 1.5574077246549023<br />
<br />
Tan(-1)<br />
Returns: -1.5574077246549023<br />
</pre><br />
|}<br />
<br />
== Conversion functions ==<br />
<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||ToFloat (Number)<br />
||<br />
Object to convert<br />
||Converts the given object to a decimal number.<br />
|-<br />
||ToInteger (Integer)<br />
||<br />
Object to convert<br />
||<br />
Converts the given object into an integer. If the object can not be converted into an integer, an exception will be thrown. If the object as a decimal number, it will also be rounded to the nearest integer.<br />
<br />
Examples:<br />
<pre><br />
ToInteger(1.234)<br />
Returns: 1<br />
<br />
ToInteger(-1.5)<br />
Returns: -2<br />
<br />
ToInteger(1313.6)<br />
Returns: 1314<br />
<br />
ToInteger(123456789012345678)<br />
Returns: 123456789012345678<br />
<br />
ToInteger("5")<br />
Returns: 5<br />
<br />
ToInteger("-5")<br />
Returns: -5<br />
</pre><br />
|-<br />
||ToString (String)<br />
||<br />
# Object to convert<br />
# Date/Number/Timespan format (String)<br />
||<br />
Converts the given object to a string.<br />
<br />
The optional second parameter defines formatting that is needed when converting the following data types:<br />
* Date: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings<br />
* Number: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings<br />
* Timespan: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-timespan-format-strings<br />
<br />
Examples:<br />
<pre><br />
ToString(1) + " < " + ToString(2)<br />
Returns: "1 < 2".<br />
<br />
"Case=\'" + ToString(a) + "\'"<br />
Returns: "Case='<string representation of object a>'"<br />
<br />
ToString(DateTime(2017,1,2,3,4,5,6))<br />
Returns: "2017-01-02T03:04:05"<br />
<br />
ToString(DateTime(2017,1,2,3,4,5,6), "dd.MM.yyyy")<br />
Returns "02.01.2017"<br />
<br />
ToString(1.2, "0.00")<br />
Returns "1.20"<br />
<br />
ToString(TimeSpan(16,4,3,17,250), "%d")<br />
Returns "16"<br />
</pre><br />
|}<br />
<br />
== Miscellaneous functions ==<br />
<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||Where<br />
||<br />
Condition expression<br />
||<br />
Returns the context object if the given expression evaluates to true.<br />
<br />
Examples:<br />
<pre><br />
[1,2,3,4].Where(_>2)<br />
Returns: [3,4]<br />
<br />
EventLogById(1).Cases.Where(Duration > TimeSpan(10))<br />
Returns all cases where duration is more than 10 days (in eventlog id 1).<br />
<br />
EventLogById(1).Events.Where(Timestamp < DateTime(2020, 1,1))<br />
Returns all events which occurred before 1.1.2020 (in eventlog id 1).<br />
</pre><br />
|-<br />
||<span id="If">If</span><br />
||<br />
# Condition expression<br />
# True expression<br />
# False expression<br />
||<br />
If the first parameter is true, returns the value of the second parameter. Otherwise returns the value of the third parameter. The function always evaluates only either the second or third parameter, but never both.<br />
<br />
Note that the function needs to starts with a capital letter, because otherwise it's interpreted as the [[QPR_ProcessAnalyzer_Expressions#Conditional_operator_.28if.29|if operator]].<br />
<br />
Examples:<br />
<pre><br />
If(Now.Second % 2 == 0, "Even second", "Odd second")<br />
Returns:<br />
"Event second" or "Odd second" depending on the time of the evaluation.<br />
<br />
For("i", 0, i < 10, i + 1, i).If(_ % 2 == 0, _, _remove)<br />
Returns:<br />
[0, 2, 4, 6, 8]<br />
</pre><br />
|-<br />
||<span id="RemoveNulls">RemoveNulls (Array)</span><br />
||<br />
Array<br />
||<br />
Removes all the supported null values from given hierarchical object. Never removes arrays containing removed null values. Returns given object with null values removed.<br />
<br />
Examples:<br />
<pre><br />
RemoveNulls([1, [], [null], [2, _remove, [_empty, 3, 4], _empty, null, 5]])<br />
Returns: [1, [], [], [2, [3, 4], 5]]<br />
<br />
RemoveNulls(["foo": null, "bar": 2, "poof": [1, _empty, 3]])<br />
Returns: [<br />
"foo": 0,<br />
"bar": 2,<br />
"poof": [ 1, 3 ]<br />
]<br />
</pre><br />
|-<br />
||Catch<br />
||<br />
# Expression to calculate<br />
# Result if exception (Object)<br />
||<br />
Calculates the given expression and if any exceptions are thrown during the calculation, catches that exception and returns the given result. Note that this function does not catch any syntactical errors.<br />
<br />
Examples:<br />
<pre><br />
Catch(1, 1234)<br />
Returns: 1<br />
<br />
Catch(undefined, 1234)<br />
Returns: 1234<br />
<br />
Catch([1,2].undefined, 1234)<br />
Returns: 1234<br />
<br />
Catch(EventLogById(-1), 1234)<br />
Returns: 1234<br />
</pre><br />
|-<br />
||AsParallel<br />
||<br />
Additional parameters<br />
||<br />
Performs all the following chaining operations in parallel to improve performance. Items are divided into parts which size is determined by the ParallelTaskSize parameter, and each part is executed as an independent task in parallel. Parallel execution has a certain cost, so it might not be optimal to run each item as a separate task (increase ParallelTaskSize to decrease number of tasks). On the other hand, to large ParallelTaskSize leads to too few parallel tasks, and then all processing capacity is not used.<br />
<br />
As a parameter, takes a dictionary that accepts optional property '''ParallelTaskSize''', which is the size of the segments the root array will be split into. If the length of the input array is not divisible by ParallelTaskSize, the last segment will have less items than this configured value. The default size is 1.<br />
<br />
The AsParallel function call doesn't need to be part of the chaining, and thus it can be called before the chaining.<br />
<br />
Examples:<br />
<pre><br />
Run several ODBC queries simultaneously:<br />
let regions = ["New York", "Los Angeles", "Dallas", "London"];<br />
AsParallel(["ParallelTaskSize": 1]);<br />
regions.ImportOdbc("...", "SELECT * FROM [Data] Where Region = '" + _ + "'")<br />
<br />
Run a complex filtering operation for cases:<br />
Cases.AsParallel(["ParallelTaskSize": 1000]).Where(...)<br />
<br />
Sum(Sum(([NumberRange(1, 100)].AsParallel(["ParallelTaskSize": 1]).For("i", 0, i < 100000, i + 1, i))[0]))<br />
Returns: 499995000000<br />
The same expression without parallel processing:<br />
Sum(Sum(NumberRange(1, 100).For("i", 0, i < 100000, i + 1, i)))<br />
Returns: 499995000000<br />
<br />
Sum([NumberRange(1, 100)].AsParallel(["ParallelTaskSize": 1]).WriteLog(_))<br />
Returns: 5050<br />
In addition, outputs all the numbers from 1 to 100 into log file in the order in which the tasks were executed.<br />
<br />
The previous example can also be written like this:<br />
AsParallel(["ParallelTaskSize": 1]);<br />
Sum(NumberRange(1, 100).WriteLog(_));<br />
Returns: 5050<br />
<br />
Count((([el.Cases].AsParallel(["ParallelTaskSize": 1000]):AnalyzeConformance(cm))[0]).Where(_==null))<br />
Returns the number of cases conforming to a design/conformance model cm.<br />
The same expression without parallel processing:<br />
Count((el.Cases:AnalyzeConformance(cm)).Where(_==null))<br />
<br />
AsParallel(["ParallelTaskSize": 1]);<br />
el.Cases.Events.Type.Name<br />
Returns a hierarchical object having cases of given event log (el) as root objects and array of event type names of the events in each case in the order of occurrence.<br />
The expressions related to every case in the returned hierarchical object are processed in a separate independent task (thus, each task will process "Events.Type.Name" expression in a separate task where the root object is a case).<br />
<br />
</pre><br />
|-<br />
||IsNull (Boolean)<br />
||<br />
Value to test (Object)<br />
||<br />
Tests whether given object is null, _empty or _remove. Returns ''true'' if it is any of those. If given a hierarchical object, applies the function as described in at the leaf level.<br />
<br />
Examples:<br />
<pre><br />
ForEach("item", [1, "a", null, _empty, _remove], IsNull(item))<br />
Returns: [false, false, true, true, true]<br />
<br />
IsNull(["foo":[null,"a"], "bar":[2,null]])<br />
Returns: [<br />
HierarchicalArray("foo", [true, false]),<br />
HierarchicalArray("bar", [false, true])<br />
]<br />
</pre><br />
|-<br />
||IsNullTop (Boolean)<br />
||<br />
Object to test (Object)<br />
||<br />
Tests whether given object is null, _empty or _remove. Returns ''true'' if it is any of those. The function does not aggregate values in hierarchical objects.<br />
<br />
Examples:<br />
<pre><br />
ForEach("item", [1, "a", null, _empty, _remove], IsNullTop(item))<br />
Returns: [false, false, true, true, true]<br />
<br />
IsNullTop(["foo":[null,"a"], "bar":[2,null]])<br />
Returns: false<br />
</pre><br />
|-<br />
||GroupBy<br />
||<br />
# Array to group<br />
# Group by expressions<br />
||<br />
Groups given array by given expressions. Returns the given array splitted into groups in a way that each specified group expression creates one level of hierarchical arrays having the root object the same as the group expression result.<br />
<br />
Examples:<br />
<pre><br />
GroupBy([1,2,2,3,3,4,5,5,4,4,4], _)<br />
<br />
Returns:<br />
[[1:[1], 2:[2, 2], 3:[3, 3], 4:[4, 4, 4, 4], 5:[5,5]]<br />
</pre><br />
|-<br />
||GroupByValue<br />
||Array to group<br />
||<br />
Groups all unique values in given array. Returns the given array in a format which has all the values in the original array only once as root objects and the root objects in the original array as contents of the arrays inside contexts.<br />
<br />
In a way, this just switches root objects of hierarchical arrays to be the actual values and actual values to be root objects (without duplicates).<br />
<br />
For every item in the array, the behavior is as follows:<br />
* If the item is not an array, the value is used also as the root object of the item.<br />
* If the item is an array, all the values are treated separately.<br />
* If the item is a hierarchical array, its root object will be used as root object and each separate value treated separately as scalars (ending up being root objects of the resulting object).<br />
<br />
Examples:<br />
<pre><br />
GroupByValue([1,2,2,3,3,4,5,5,4,4,4])<br />
Returns:<br />
(The same as GroupBy([1,2,2,3,3,4,5,5,4,4,4], _))<br />
[1:[1], 2:[2, 2], 3:[3, 3], 4:[4, 4, 4, 4], 5:[5,5]]<br />
<br />
GroupByValue([1:["a","b"],2:["b","c"],3:["c"],4:["d","e"],5:["d","d","d"]])<br />
Returns:<br />
["a":[1], "b":[1, 2], "c":[2, 3], "d":[4, 5, 5, 5], "e":[4]]<br />
<br />
Get count of item "2" in the array:<br />
Let(\"groupped\", GroupByValue([1,2,4,1,4,2,3,3,2,4])); Count(GetValueOfContext(2, groupped))<br />
Returns: 3<br />
</pre><br />
|-<br />
||Coalesce<br />
||<br />
# Object to coalesce<br />
# Result if Null<br />
||<br />
Returns the second parameter if the first parameter is null or empty. If the the given object is a hierarchical object, all the leaf level values are coalesced separately.<br />
<br />
Examples:<br />
<pre><br />
Coalesce(0, 1)<br />
Returns: 0<br />
<br />
Coalesce(null, 1)<br />
Coalesce(_empty, 1)<br />
Coalesce(_remove, 1)<br />
All return: 1<br />
<br />
Coalesce([[null, 1], [null, null]], 3)<br />
Returns: [[3, 1], [3, 3]]<br />
<br />
Coalesce([[null, 1], 2], 3)<br />
Returns: [[3, 1], null]<br />
<br />
Coalesce([1, [null, 2], null], 3)<br />
Returns: [1, [null, 2], 3]<br />
</pre><br />
|-<br />
||Transpose<br />
||<br />
Matrix to transpose<br />
||<br />
Transposes the given matrix.<br />
<br />
Examples:<br />
<pre><br />
Transpose([[1,2], [3,4], [1,4]])<br />
Returns: [[1, 3, 1], [2, 4, 4]]<br />
</pre><br />
|-<br />
||GarbageCollection<br />
||<br />
||Calling this function performs a garbage collection in the QPR ProcessAnalyzer Server. The function returns the maximum generation before the garbage collection was run. This function is an experimental functionality, which purpose is to investigate the memory consumption and memory handling behavior of the QPR ProcessAnalyzer Server.<br />
|-<br />
||GetContext<br />
||<br />
Hierarchical array<br />
||<br />
Returns the context of given hierarchical array, i.e. list of keys in the object. If the given object is not an hierarchical array, returns ''null''.<br />
<br />
Examples:<br />
<pre><br />
GetContext("a":1)<br />
Returns: "a"<br />
<br />
["a":1, "b":2, 2:3].GetContext(_)<br />
Returns: ["a", "b", 2]<br />
<br />
([1,2,3]:(_*2)).GetContext(_)<br />
Returns: [1, 2, 3]<br />
<br />
["a":1, 2, 3].GetContext(_)<br />
Returns: ["a", null, null]<br />
</pre><br />
|-<br />
||GetValueOfContext<br />
||<br />
# Context object<br />
# Hierarchical array<br />
||<br />
Returns the value of specified context object in given hierarchical array, i.e. the value behind the key. If the key if found multiple times, the first occurrence is returned. Returns ''_empty'' if the given key was not found.<br />
<br />
Examples:<br />
<pre><br />
GetValueOfContext("bar", ["foo":1, "bar":2])<br />
Returns: [2]<br />
<br />
GetValueOfContext("bar", ["foo":1, "bar":2, "bar":"second"])<br />
Returns: [2]<br />
<br />
GetValueOfContext("test", ["foo":1, "bar":2])<br />
Returns: _empty<br />
</pre><br />
|-<br />
||<span id="SendEmail">SendEmail</span><br />
||Parameters dictionary<br />
||Sends an email message using the provided parameters. [[PA_Configuration_database_table#SMTP_Server_Settings|SMTP server settings]] need to be configured to be able to send email messages. Following parameters are supported:<br />
* '''From''' (string) (mandatory): Email address where the email message appears to be coming from. Doesn't need to be a working address. If the From address is not defined, the system configured from address is used ([[PA Configuration database table#SMTP_Server_Settings|more information]]).<br />
* '''To''' (string array) (mandatory): List of email addresses where to send the message to. Note that there should be only one email address per string in the array.<br />
* '''Subject''' (string): Subject (title) of the email message.<br />
* '''Body''' (string): Body (text contents) of the email message.<br />
* '''Cc''' (string array): List of email addresses where to send the email as Cc.<br />
* '''Bcc''' (string array): List of email addresses where to send the email as Bcc.<br />
* '''IsBodyHtml''' (boolean): Defines whether the email message body is html (''true'') or plain text (''false''). By default false.<br />
* '''ReplyTo''' (string array): Defines a list of reply-to addresses for the email message.<br />
* '''BodyEncoding''' (string): Defines encoding for the message body. Supported encodings are ''ASCIIEncoding'', ''UTF7Encoding'', ''UTF8Encoding'' (default), ''UnicodeEncoding'' and ''UTF32Encoding''. More information: https://docs.microsoft.com/en-us/dotnet/api/system.text.encoding?redirectedfrom=MSDN&view=netcore-3.1#remarks.<br />
* '''SubjectEncoding''' (string): Defines encoding for the message subject. Supported encodings are same as in the ''BodyEncoding'' property. Default value is ''UTF8Encoding''.<br />
* '''Priority''' (string): Defines the email message priority. Available values are ''High'', ''Normal'' (default) and ''Low''. More information: https://docs.microsoft.com/en-us/dotnet/api/system.net.mail.mailpriority.<br />
* '''DeliveryNotification''' (string): Defines the delivery notifications for the email message. Specified as a comma separated list of following possible values ''Delay'', ''Never'', ''None'', ''OnFailure'' and ''OnSuccess''. More information: https://docs.microsoft.com/en-us/dotnet/api/system.net.mail.deliverynotificationoptions.<br />
* '''Sender''' (string): Defines the sender's email address. Usually the sender doesn't need to be defined. The sender is additional information for the email server.<br />
<br />
Example:<br />
<pre><br />
SendEmail(#{<br />
"From": "example.from@address.com",<br />
"To": ["recipient.one@address.com", "recipient.two@address.com", "recipient.three@address.com"],<br />
"Subject": "Example E-mail",<br />
"Body": "QPR ProcessAnalyzer example script started running"<br />
});<br />
</pre><br />
|-<br />
||WriteLog<br />
||<br />
message (Object)<br />
||<br />
When used in a script, writes the given text to the script log. The log entry is also made to the QPR ProcessAnalyzer log file. If the provided parameter is not a string, it's converted into string.<br />
<br />
The return value of the function is the provided message parameter, allowing to flexibly add the WriteLog into expressions (see the examples).<br />
<br />
Examples:<br />
<pre><br />
WriteLog("Calculation executed.")<br />
Writes to log: Calculation executed.<br />
<br />
Sum(WriteLog([1, 2, 3, 4]))<br />
Returns: 10<br />
Also writes an entry into the log showing the [1, 2, 3, 4] -array in the pretty printed fashion.<br />
<br />
NumberRange(0, 4).(WriteLog("Iteration #" + (_ + 1)), _)<br />
Returns: [0, 1, 2, 3, 4]<br />
Also writes the following entries into log:<br />
Iteration #1<br />
Iteration #2<br />
Iteration #3<br />
Iteration #4<br />
Iteration #5<br />
</pre><br />
|-<br />
||TakeSample<br />
||<br />
* Input array/DataFrame<br />
* Sample size (Integer)<br />
* Seed (Integer)<br />
* With replacements (Boolean)<br />
||<br />
Randomly chooses the defined number of items from the provided array or rows from the DataFrame, and returns a new array or DataFrame containing those items. If the sample size is larger than the number of items/rows, the TakeSample function has no effect. Note that the order of items may change from the original.<br />
<br />
The seed is optional, and if not provided, the seed to be used is automatically generated.<br />
<br />
The "with replacements" parameter is optional (by default false). When false, same items appear maximum of once in the resulting array. When true, same items may appear multiple times in the resulting array.<br />
<br />
Examples:<br />
<pre><br />
TakeSample([1,2,3,4,5,6,7,8,9,10], 4)<br />
Returns [1, 9, 3, 4] (note: results may change)<br />
<br />
TakeSample([1,2,3,4,5,6,7,8,9,10], 5, 9, true)<br />
Returns [5, 5, 1, 5, 3]<br />
<br />
TakeSample([1,2,3,4,5], 10)<br />
Returns [1,2,3,4,5]<br />
<br />
TakeSample(<br />
ToDataFrame(<br />
[[1,2],[3,4],[5,6]], ["a", "b"]<br />
),<br />
2<br />
).ToCsv()<br />
Returns<br />
a;b<br />
5;6<br />
3;4<br />
</pre><br />
|-<br />
||Sleep<br />
||Duration (Timespan or integer as milliseconds)<br />
||<br />
Suspends the expression execution for the given time duration. The parameter can either be a Timespan object or integer where the duration is specified as milliseconds.<br />
<br />
Examples:<br />
<pre><br />
Sleep(Timespan(0, 0, 1)));<br />
Result: Sleeps for 1 minute<br />
<br />
Sleep(1000);<br />
Sleep for 1 second<br />
</pre><br />
|-<br />
||<span id="ReadWebService">ReadWebService</span> (string)<br />
||Parameters dictionary<br />
||<br />
Performs an http/https request and returns the response content. The request is originated from the QPR ProcessAnalyzer server. Following parameters are supported:<br />
* '''Address''': Url of the http/https to call. This parameter is mandatory.<br />
* '''Method''': Defines the http method for the call. Following methods can be used: '''GET''' (default), '''POST''', '''PUT''', '''DELETE'''.<br />
* '''Body''': Defines payload of the http request. Default is empty.<br />
* '''Encoding''': Defines the encoding to use. The supported options are listed in https://msdn.microsoft.com/en-us/library/system.text.encoding%28v=vs.110%29.aspx. Default value is UTF8.<br />
* '''Timeout''': Milliseconds to wait before the request times out, in case no response is received earlier. Default value is 60000 ms (1 minute).<br />
* '''DefaultNetworkCredentials''': When ''true'', uses the default network credentials for the call. When ''false'', the default network credentials are not used. The default network credentials can be used only if in the server configuration [[Web.config_file#Common_Settings|AllowForwardingNetworkCredentials]] setting is enabled.<br />
* '''<other parameters>''': Rest of the passed parameters not listed above are added as http headers to the request. For example, '''Accept''', '''Accept-Encoding''' and '''Cache-Control''' headers can be used.<br />
<br />
To use the ReadWebService function, system level setting [[PA_Configuration_database_table#General_Settings|AllowExternalDatasources]] needs to be enabled.<br />
<br />
Examples:<br />
<pre><br />
let responseData = ReadWebService(#{<br />
"Address": "https://www.google.com/search?q=QPR+ProcessAnalyzer",<br />
"Method": "GET",<br />
"Accept": "*/*"<br />
});<br />
</pre><br />
<br />
<pre><br />
let responseData = ReadWebService(#{<br />
"Address": "https://processanalyzer.onqpr.com/qprpa/api/serverinfo",<br />
"Method": "GET",<br />
"Accept": "application/json"<br />
});<br />
</pre><br />
<br />
|}<br />
<br />
== Ordering functions ==<br />
<br />
{| class="wikitable"<br />
!'''Function'''<br />
! '''Parameters'''<br />
! '''Description'''<br />
|-<br />
||OrderBy (array)<br />
||<br />
# Array to order<br />
# Order expression<br />
||<br />
Orders the given array using values from the given order expression. The order expression is evaluated once for each item in the array. The order expression supports all atomic (=not collection) primitive value types.<br />
<br />
Examples:<br />
<pre><br />
OrderBy(["a", "x", "b", "z", "n", "l", "a"], _)<br />
Return:<br />
["a", "a", "b", "l", "n", "x", "z"]<br />
<br />
OrderBy([9,8,7,6,5,4,3,2,1], _%3)<br />
Returns:<br />
[9,6,3,7,4,1,8,5,2]<br />
<br />
OrderBy([9,8,7,6,5,4,3,2,1], _%3 + _/30)<br />
Returns:<br />
[3,6,9,1,4,7,2,5,8]<br />
</pre><br />
|-<br />
||OrderByDescending (array)<br />
||<br />
# Array to order<br />
# Order expression<br />
||Result is same as in the OrderBy function, except the order is reverse.<br />
|-<br />
||OrderByTop (array)<br />
||<br />
# Array to order<br />
# Order expression<br />
||<br />
Orders given top-level array by the value of given expression using ascending order. Supports all value types, including multi-dimensional arrays.<br />
<br />
Order expression is evaluated in the context of each array item whose value determines the order of that item.<br />
<br />
Examples:<br />
<pre><br />
OrderByTop([[1, 2, 3], [2, 2, 2], [3, 2, 1]], _[2])<br />
Returns: [[3, 2, 1], [2, 2, 2], [1, 2, 3]]<br />
</pre><br />
|-<br />
||OrderByValue (array)<br />
||<br />
# Array to order<br />
||<br />
Orders the given array using the natural order of items, for example numbers it's the increasing order, and for strings it's text ordering.<br />
<pre><br />
OrderByValue(["a", "x", "b", "z", "n", "l", "a"])<br />
Return:<br />
["a", "a", "b", "l", "n", "x", "z"]<br />
<br />
</pre><br />
|-<br />
||OrderByValueDescending (array)<br />
||<br />
# Array to order<br />
||<br />
Result is same as in the OrderByValue function, except the order is reverse.<br />
|}<br />
<br />
== Looping functions ==<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||For<br />
||<br />
# Iterated variable name (String)<br />
# Initial value for iterated property (object)<br />
# Iteration condition expression<br />
# Next iteration step expression<br />
# Expression to calculate iterated items<br />
||<br />
Iterates the given expression until the given condition is met, and returns the results of the iterated expressions for every iteration as an array.<br />
<br />
Examples:<br />
<pre><br />
For("i", 0, i < 4, i + 1, i)<br />
Returns: [0, 1, 2, 3]<br />
<br />
For("x", 0, x < 3, x + 1, For("y", 0, y < 3, y + 1, StringJoin(",", [x, y]))<br />
Returns: [["0,0", "0,1", "0,2"], ["1,0", "1,1", "1,2"], ["2,0", "2,1", "2,2"]]<br />
<br />
For("i", 0, i < 4, i + 1, DateTime(2010 + i))<br />
Returns: [DateTime(2010), DateTime(2011), DateTime(2012), DateTime(2013)]<br />
<br />
For("str", "a", str != "aaaaa", str + "a", str)<br />
Returns: ["a", "aa", "aaa", "aaaa"]<br />
</pre><br />
|-<br />
||ForEach (2 parameters)<br />
||<br />
# Array to iterate through<br />
# Function to call<br />
||<br />
Calls given function using all the elements of given array, where the calculation is done in the current context. The function must support calling with one parameter. Returns the results of the evaluation of given function for every iteration of the input array as an array.<br />
<br />
Examples:<br />
<pre><br />
let sourceModel = First(Models.Where(Name == "SAP_OrderToCash"));<br />
let attributes = sourceModel.EventAttributes;<br />
let events = sourceModel.EventLog.Events;<br />
let func = att => Attribute(att);<br />
events.ForEach(attributes, func)<br />
Returns an array containing arrays of all the event attribute values for all the events.<br />
<br />
let myFunction = item => _ + item * 2;<br />
(5).ForEach([1,2,3], myFunction)<br />
Returns 7, 9, 11 (=5+1*2, 5+2*2, 5+3*2)<br />
</pre><br />
|-<br />
||ForEach (3 parameters)<br />
||<br />
# Variable to repeat (String)<br />
# Array to repeat<br />
# Expression to calculate repeated items<br />
||<br />
Repeats the given expression as many times there are items in the given array. Item in the array is available as the given variable in the expression.<br />
Examples:<br />
<pre><br />
ForEach("i", [1,2,3], "Value is: " + i)<br />
Returns:<br />
Value is: 1<br />
Value is: 2<br />
Value is: 3<br />
<br />
ForEach("item", EventLogById(1).Cases, Let("c" + item.Name, item))<br />
Results: Creates expression variable variables like "c<casename>" for every case in the model.<br />
<br />
ForEach("myVariable", ["a", "b", "c"], myVariable + myVariable)<br />
Returns:<br />
aa<br />
bb<br />
cc<br />
</pre><br />
|-<br />
||NumberRange<br />
||<br />
# Start (Number)<br />
# End (Number)<br />
# Interval (Number)<br />
||<br />
Creates an array of numbers within the given range using the given interval. Interval parameter is optional, and by default it is one. The interval can also be negative to get a sequence of decreasing numbers (then the Start needs to be greater than the End).<br />
<br />
Examples:<br />
<pre><br />
NumberRange(1, 3)<br />
Returns: [1, 2, 3]<br />
<br />
NumberRange(-7, -1, 2)<br />
Returns: [-7, -5, -3, -1]<br />
<br />
NumberRange(1, 3, 0.5)<br />
Returns: [1, 1.5, 2, 2.5, 3]<br />
<br />
NumberRange(1, 3, 0.8)<br />
Returns: [1, 1.8, 2.6]<br />
<br />
NumberRange(6, 2, -2)<br />
Returns: [6, 4, 2]<br />
</pre><br />
|-<br />
||Repeat<br />
||<br />
# Number of times to repeat (Integer)<br />
# Expression to repeat<br />
||<br />
Repeats the defined expression the defined number of times.<br />
Examples:<br />
<pre><br />
Repeat(3, "Repeat me!")<br />
Returns:<br />
"Repeat me!"<br />
"Repeat me!"<br />
"Repeat me!"<br />
<br />
Repeat(1, 5)<br />
Returns<br />
5<br />
</pre><br />
|-<br />
||TimeRange<br />
||<br />
# Start (DateTime)<br />
# End (DateTime)<br />
# Interval (Timespan)<br />
||<br />
Generates a timestamp array starting from the start timestamp with the defined interval, and ending when the end timestamp is reached. Note that this function only creates timestamps with equal durations, so it's not possible to e.g. create timestamps for each month (to do that, you can use the loops).<br />
<pre><br />
Generate datetimes starting from Monday 2017-01-01 and ending to Monday 2017-12-31 including all Mondays between them:<br />
Timerange(Datetime(2018,1,1), Datetime(2018,1,1), Timespan(7))<br />
</pre><br />
|}<br />
<br />
== Recursion functions ==<br />
<br />
{| class="wikitable"<br />
!'''Function'''<br />
! '''Parameters'''<br />
! '''Description'''<br />
|-<br />
<br />
|-<br />
||Recurse<br />
||<br />
# Expression to call recursively<br />
# Stop condition expression<br />
# Maximum depth (Integer)<br />
||<br />
Evaluates the given expression recursively until given condition or recursion depth is met. The function returns all the traversed objects in a single array. When the stop condition expression evaluates to false, it will stop the current recursion without including the false evaluated object into the result. Default stop condition is '''!IsNull(_)'''. The default maximum depth is 1000.<br />
<br />
Examples:<br />
<pre><br />
(1).Recurse(_ + 1, _ < 5)<br />
Returns: [1, 2, 3, 4]<br />
<br />
event.Recurse(NextInCase)<br />
Returns: An array of all the events following given event inside the same case.<br />
<br />
event.Recurse(NextInCase, Type.Name != "Invoice")<br />
Returns: An array of all the events following given event inside the same case until event whose type name is "Invoice", which will itself not be included into the result.<br />
<br />
event.Recurse(NextInCase, Type.Name != "Invoice", 2)<br />
Returns: An array of all the events following given event inside the same case until event whose type name is "Invoice" or until the recursion depth of 2 has been reached, which will itself not be included into the result.<br />
</pre><br />
|-<br />
||RecurseWithHierarchy<br />
||<br />
# Expression to call recursively<br />
# Stop condition expression<br />
# Maximum depth (Integer)<br />
||<br />
Evaluates the given expression recursively until given condition or recursion depth is met. The function returns the traversed object hierarchy. When the stop condition expression evaluates to false, it will stop the current recursion without including the false evaluated object into the result. Default stop condition is '''!IsNull(_)'''. The default maximum depth is 1000.<br />
<br />
Examples:<br />
<pre><br />
[1,2].RecurseWithHierarchy([1,2], false, 2)<br />
Returns: [1:[1:[1,2],2:[1,2]],2:[1:[1,2], 2:[1,2]]]<br />
<br />
(1).RecurseWithHierarchy(_ + 1, _ < 5)<br />
Returns: 1:[2:[3:[4]]]<br />
<br />
RemoveLeaves(eventLog.Flows:From.Where(IsNull(_))).To.RecurseWithHierarchy(OutgoingFlows.To, !IsNull(_), 2)<br />
Returns: A hierarchy consisting of all the starter events of given event log and recursively all the event types reachable from them via flows until depth of 2 is reached.<br />
</pre><br />
|-<br />
||RecursiveFind<br />
||<br />
# Expression to call recursively<br />
# Find condition expression<br />
# Stop condition expression<br />
# Continue after finding (Boolean)<br />
# Maximum depth (Integer)<br />
||<br />
Evaluates given expression recursively until given condition or recursion depth is met. The function collects all the traversed objects that match the given find expression along the way. When the find condition expression evaluates to true for the current object, it causes the following:<br />
* Current object is added to the result array returned by the function call<br />
* If continue after finding is false, the recursion will not be continued on this branch<br />
<br />
When the stop condition expression evaluates to false, it will stop the current recursion without including the false evaluated object into the result. Default stop condition is '''!IsNull(_)'''. The default maximum depth is 1000.<br />
<br />
Continue after finding tells should the recursion be continued after a match has been found in the current branch.<br />
<br />
Examples:<br />
<pre><br />
(1).RecursiveFind(_ + 1, _ == 100)<br />
Returns: 100<br />
<br />
eventLog.Cases:GetAt(0, Events).RecursiveFind(NextInCase, Organization=="Finance", !IsNull(_))<br />
Returns: For each case, returns the first (by time) event whose organization equals to "Finance".<br />
<br />
eventLog.Cases:Events.Where(Organization=="Finance")<br />
eventLog.Cases:GetAt(0, Events).RecursiveFind(NextInCase, Organization=="Finance", true, true)<br />
Returns: Both return for each case all events whose organization equals to "Finance".<br />
</pre><br />
|}<br />
<br />
== Hierachical object functions ==<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||FindRepeats<br />
||<br />
# Array<br />
# Minimum repeated length (Integer)<br />
# Longest repeat length (Integer)<br />
||<br />
Searches for repeating patterns in given array. Parameters:<br />
# Array to search the patterns in.<br />
# Minimum integer length of a repeat that can be returned by this function (default = 0).<br />
# Boolean value indicating whether to return all the repeating patterns (true) or only the ones having the longest length (false) (default = false)<br />
Returns an array of arrays indicating the repeating patterns and their positions in the array formatted as follows:<br />
* Every repeating pattern has its own entry in the top-level array.<br />
* Every repeating pattern item in the top-level array is formatted internally as an array consisting of:<br />
** An array constining the repeating pattern itself.<br />
* An array consisting of all the indexes from which this pattern was found to start from.<br />
* Allows overlapping patterns.<br />
* Results are sorted primarily by the length of the pattern and secondarily by the number of indexes the pattern was found in.<br />
<br />
Examples:<br />
<pre><br />
FindRepeats([0, 1, 2, 0, 1, 2])<br />
Returns: [<br />
[[0, 1, 2], [0, 3]],<br />
[[0, 1], [0, 3]],<br />
[[1, 2], [1, 4]],<br />
[[0], [0, 3]],<br />
[[1], [1, 4]],<br />
[[2], [2, 5]]<br />
]<br />
<br />
FindRepeats([0, 1, 2, 0, 1, 2], 0, true)<br />
Returns: [[[0, 1, 2], [0, 3]]]<br />
<br />
FindRepeats([1, "b", DateTime(2017), 1, "b", DateTime(2017)], 3)<br />
Returns: [[1, "b", DateTime(2017)], [0, 3]]<br />
</pre><br />
|-<br />
||Flatten<br />
||<br />
# Array or hierarchical object<br />
# Include context object (boolean)<br />
||<br />
Collects all the actual leaf values from given array, array of arrays or hierarchical object and returns them in a single array. If given a hierarchical object, this function collects actual leaf values instead of leaf level values. Elements in the returned array are in the same order they were found when traversing the input object using depth first search.<br />
<br />
When context object is included, should context objects in the internal nodes of a hierarchical object be also included into the result. Default is false.<br />
<br />
Examples:<br />
<pre><br />
Flatten(1)<br />
Returns: 1<br />
<br />
Flatten([1, 2])<br />
Returns: [1,2]<br />
<br />
Flatten([[[1, 2],[3, 4]],[[5, 6]]])<br />
Returns: [1, 2, 3, 4, 5, 6]<br />
<br />
Flatten([[1, 2], 3])<br />
Returns: [1, 2, 3]<br />
<br />
Flatten([[1,2,3,4], null, [5], [1, null]])<br />
Returns: [1, 2, 3, 4, null, 5, 1, null]<br />
<br />
Flatten(["a":1, "b":2])<br />
Flatten(["a":1, "b":2], false)<br />
Returns: [1, 2]<br />
<br />
Flatten(["a":1, "b":2], true)<br />
Returns: ["a", 1, "b", 2]<br />
</pre><br />
|-<br />
||RemoveLeaves<br />
||<br />
# Hierarchical object<br />
||<br />
Remove one level of hierarchy from a hierarchical object replacing all the bottom level hierarchical arrays with the context objects of the hierarchical arrays. Returns the given object with all the bottom level hierarchical arrays with the context objects of the hierarchical arrays.<br />
<br />
Examples:<br />
<pre><br />
RemoveLeaves(["foo":1, "bar":2])<br />
Returns: ["foo", "bar"]<br />
<br />
RemoveLeaves(eventLog.Flows:From.Where(IsNull(_)))<br />
Results: All the flows starting the cases in the event log.<br />
</pre><br />
|-<br />
||ReplaceLeafValues<br />
||<br />
# Array or hierarchical object<br />
# Variable name used in the iteration (String)<br />
# Expression to get the result of each iteration<br />
# Number of levels up from the leaf level to operate (Integer)<br />
||<br />
Replace all leaf values of given array or hierarchical object at given levels up from the leaf level with results of given expression.<br />
<br />
Examples:<br />
<pre><br />
ReplaceLeafValues([1,2, null], "x", If(IsNull(x), null, x+1), 0)<br />
Result: [2, 4, null]<br />
<br />
ReplaceLeafValues([[[1,2],[2,3]],[[3,4],[4,5]]], "x", Flatten(x), 0)<br />
Result: [[[[1],[2]],[[2],[3]]],[[[3],[4]],[[4],[5]]]]<br />
<br />
ReplaceLeafValues([[[1,2],[2,3]],[[3,4],[4,5]]], "x", Flatten(x), 1)<br />
Result: [[[1,2],[2,3]],[[3,4],[4,5]]]<br />
<br />
ReplaceLeafValues([[[1,2],[2,3]],[[3,4],[4,5]]], "x", Flatten(x), 2)<br />
Result: [[1,2,2,3],[3,4,4,5]]<br />
<br />
ReplaceLeafValues([[[1,2],[2,3]],[[3,4],[4,5]]], "x", Flatten(x), 3)<br />
Result: [1,2,2,3,3,4,4,5]<br />
</pre><br />
|-<br />
||SliceMiddle<br />
||<br />
# Start index for the range to extract (Integer)<br />
# End index for the range to extract (Integer)<br />
# Levels up in the hierarchy (Integer)<br />
# Array to slice<br />
||<br />
Extracts a continuous range of an array or hierarchical object. If given a hierarchical object, applies the function at the level that is specified levels level up from the leaf level.<br />
<br />
Start index: Negative value means that the index is counting from the end of the array. If array does not have element at this given index, empty array is returned.<br />
<br />
End index: not included into the extracted range. Negative value means that the index is counting from the end of the array. If array does not have element at this given index, all the elements to the end from the start index will be extracted.<br />
<br />
Levels up: At which level of the hierarchical object are we operating (number of levels up from the leaf level). Should be at least 1 (since 0 level does not contain arrays).<br />
<br />
Examples:<br />
<pre><br />
SliceMiddle(1, 2, 1, [[0, 1, 2, 3], [4, 5, 6, 7]])<br />
Returns: [[1], [5]]<br />
<br />
SliceMiddle(2, 4, 1, [[0, 1, 2, 3], [4, 5, 6, 7]])<br />
Returns: [[2, 3], [6, 7]]<br />
<br />
SliceMiddle(0, 1, 2, [[0, 1, 2, 3], [4, 5, 6, 7]])<br />
Returns: [0, 1, 2, 3]<br />
<br />
SliceMiddle(3, 5, 1, [0, 1, 2, 3, 4, 5, 6, 7])<br />
Returns: [3, 4]<br />
<br />
SliceMiddle(-3, -1, 1, [0, 1, 2, 3, 4, 5, 6, 7])<br />
Returns: [5, 6]<br />
<br />
SliceMiddle(3, -1, 1, [0, 1, 2, 3, 4, 5, 6, 7])<br />
Returns: [3, 4, 5, 6]<br />
</pre><br />
|}</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Machine_Learning_Functions_in_Expression_Language&diff=17859Machine Learning Functions in Expression Language2021-03-14T06:39:44Z<p>TeeLeht: </p>
<hr />
<div>This pages describes functions and properties that are related to the machine learning functionality, such as '''clustering''' and '''prediction''', in the QPR ProcessAnalyzer expression language.<br />
<br />
== Machine Learning Functions ==<br />
{| class="wikitable"<br />
!'''Function'''<br />
! '''Parameters'''<br />
! '''Description'''<br />
|-<br />
||BalancedKMeans<br />
||jsonData (String)<br />
||<br />
Performs Balanced KMeans clustering for given numeric matrix. Algorithm is based on http://accord-framework.net/docs/html/T_Accord_MachineLearning_BalancedKMeans.htm. Parameters and return value structure is identical to the KMeans function.<br />
|-<br />
||Codify<br />
||Matrix to codify<br />
||<br />
Use Accord's Codify -functionality to encode all unique column values into unique numeric integer values. Based on: http://accord-framework.net/docs/html/T_Accord_Statistics_Filters_Codification.htm. Returns codified matrix of exactly the same dimensions as the input matrix.<br />
<br />
Examples:<br />
<pre><br />
Codify([[1,2], [3,4], [1,4]])<br />
Returns: [[0, 0], [1, 1], [0, 1]]<br />
<br />
Codify([[123, "foo"], [456, "bar"], [456, "foo"]])<br />
Returns: [[0, 0], [1, 1], [1, 0]]<br />
</pre><br />
|-<br />
||KMeans<br />
||<br />
* Matrix to cluster<br />
* Target number of clusters<br />
* Distance function<br />
* Additional parameters<br />
||<br />
Performs KMeans clustering for a numeric matrix. Implementation uses Accord.NET KMeans function (http://accord-framework.net/docs/html/T_Accord_MachineLearning_KMeans.htm).<br />
<br />
Parameters:<br />
# Matrix to cluster. Rows (1st dimension) represent data points and columns represent feature values (2nd dimension).<br />
# Target number of clusters<br />
# Distance function to be used in the clustering process.<br />
# Additional parameters: Optional key value pairs. Supported keys and values: ComputeCovariance: If true, the result will include covariance matrices. Default = false.<br />
<br />
Returns an array having the following elements:<br />
* Element 0: An array of all the cluster labels for all the rows in the input matrix in the same order as they were given in the matrix parameter.<br />
* Element 1: An array of length 2 having the following elements:<br />
** Element 0: Computed final error of the clustering.<br />
** Element 1: Number of iterations performed in the clustering.<br />
* Element 2: Only returned if computeCovariance is True.<br />
<br />
Examples:<br />
<pre><br />
KMeans([[1, 2], [2, 3], [2, 2]], 2)<br />
Returns (e.g.): [[0, 1, 0], [0.16667, 2]]<br />
<br />
KMeans([[1, 2], [2, 3], [2, 2]], 3)<br />
Returns (e.g.): [[2, 1, 0], [0, 1]]<br />
<br />
KMeans([[1, 2], [2, 3], [2, 2]], 2, "manhattan", true)<br />
Returns (e.g.): [[0, 1, 0], [0.33333, 2], <covariance matrices (k * columns * columns)>]<br />
<br />
KMeans(OneHot(Codify([[123, "foo"], [456, "bar"], [456, "foo"]])), 2)<br />
Returns (e.g.): [[0, 1, 0], [0.33333, 2]]<br />
</pre><br />
|-<br />
||KModes<br />
||<br />
* Matrix to cluster<br />
||<br />
Performs KModes clustering for a numeric matrix. Implementation uses Accord.NET KModes method (http://accord-framework.net/docs/html/T_Accord_MachineLearning_KModes.htm).<br />
<br />
Parameters:<br />
# Matrix to cluster. Rows (1st dimension) represent data points and columns represent feature values (2nd dimension)<br />
# Target number of clusters<br />
# distanceFunction: Distance function to be used in the clustering process (#48347#).<br />
<br />
Returns an array having the following elements:<br />
* Element 0: An array of all the cluster labels for all the rows in the input matrix in the same order as they were given in the matrix parameter.<br />
* Element 1: An array of length 2 having the following elements:<br />
** Element 0: Computed final error of the clustering.<br />
** Element 1: Number of iterations performed in the clustering.<br />
<br />
Examples:<br />
<pre><br />
KModes([[1, 2], [2, 3], [2, 2]], 2)<br />
Returns (e.g.): [[0, 1, 0], [0, 2]]<br />
<br />
KModes([[1, 2], [2, 3], [2, 2]], 3)<br />
Returns (e.g.): [[2, 1, 0], [0, 1]]<br />
</pre><br />
||<br />
|-<br />
||MLModel (MLModel)<br />
||<br />
* type (String)<br />
* parameters<br />
||<br />
Create a new machine learning model for predictions. Takes type of the prediction/classification model to create as a parameter. Currently the only supported value is '''randomforest''' which uses the Accord.NET's RandomForest algorithm.<br />
<br />
Parameters:<br />
* Type of the prediction/classification model to create. Only supported value is '''binarygbm''' (based on ML.NET's LightGBM)<br />
* Additional parameters as key value pairs. Only supported parameter is '''ComputeCovariance''': If true, the result will include covariance matrices. Default value is false.<br />
|-<br />
||OneHot<br />
||<br />
* Numeric matrix<br />
||<br />
One-hot encodes all matrix columns. Implementation uses Accord.NET OneHot method (http://accord-framework.net/docs/html/M_Accord_Math_Jagged_OneHot_1.htm)<br />
<br />
Returns a matrix consisting of a concatenation of one-hot encoding of each of the input matrix columns. The number of columns in the returned matrix is at least the same as in the input matrix. For each input column, the corresponding one-hot vector will have all the values of 0, except for one which will be 1.<br />
<br />
Examples:<br />
<pre><br />
OneHot([[0], [2], [1], [3]])<br />
Returns: [[1, 0, 0, 0], [0, 0, 1, 0], [0, 1, 0, 0], [0, 0, 0, 1]]<br />
<br />
OneHot(Codify([[123, "foo"], [456, "bar"], [456, "foo"]]))<br />
Returns: [[1, 0, 1, 0], [0, 1, 0, 1], [0, 1, 1, 0]]<br />
</pre><br />
<br />
|-<br />
|| Train (MLModel)<br />
||<br />
* Input data<br />
* Expected outcomes<br />
* Parameters<br />
||<br />
Trains given MLModel using given input data and expected outcomes.<br />
<br />
Parameters:<br />
* '''input data''': Two dimensional array where:<br />
** The first dimension (rows) specifies different data points.<br />
** The second dimension (columns) specifies the feature values.<br />
* '''expected outcomes''': An array of expected outcomes for each row in the input data. Must be in the same order as the rows in the input data.<br />
* '''parameters''': Additional parameters for the MLModel. Supported parameters:<br />
** NumberOfTrees: the number of trees in the random forest, default value is 10.<br />
** SampleRatio: the proportion of samples used to train each of the trees in the decision forest, default value is 0.632.<br />
<br />
Returns the trained MLModel object.<br />
|-<br />
||Transform (array)<br />
||<br />
Input data<br />
||<br />
Transforms given input data using the MLModel to generating predictions. Takes the input data as a parameter which is a two dimensional array where the first dimension (rows) specifies different data points and the second dimension (columns) specifies the feature values.<br />
<br />
Returns an array of predictions. Transformations for each row in the input data can be found at the same index of the returned array.<br />
|}<br />
<br />
== MLModel (Machine Learning Model) ==<br />
<br />
These properties are available for the MLModel object.<br />
<br />
{| class="wikitable"<br />
!'''MLModel properties'''<br />
! '''Description'''<br />
|-<br />
||Type<br />
||Returns the exact type of the MLModel.<br />
|}<br />
<br />
== Examples ==<br />
<br />
Example #1: Train a model using an event log and test its performance by replaying training data itself.<br />
<pre><br />
<br />
Def("GetOneHotColumnInformation", (<br />
Let("el", _),<br />
ToDictionary([<br />
"et": OrderByValue(el.EventTypes),<br />
"at": ToDictionary(ConcatTop(OrderByTop(el.CaseAttributes, Name).[_: Values]))<br />
])<br />
));<br />
<br />
Def("GenerateOneHot", "cases", (<br />
Let("columnInformation", _),<br />
cases.(<br />
Let("cas", _),<br />
Flatten(<br />
[<br />
columnInformation.Get("et").(Let("et", _), If(Count(cas.EventsByType(et)) > 0, 1, 0)),<br />
(<br />
Let("atColumns", columnInformation.Get("at")),<br />
OrderByValue(atColumns.Keys).(<br />
Let("key", _),<br />
Let("values", atColumns.Get(key)),<br />
Let("caseValue", cas.Attribute(key)),<br />
values.(If(_ == caseValue, 1, 0))<br />
)<br />
)<br />
]<br />
)<br />
)<br />
));<br />
<br />
Let("el", EventLogById(1));<br />
Let("columnInformation", el.GetOneHotColumnInformation());<br />
Let("allCases", el.Cases);<br />
Let("allCasesOH", columnInformation.GenerateOneHot(el.Cases));<br />
Let("trainDataOH", allCasesOH);<br />
Let("outcomes", allCases.(Duration > TimeSpan(24)));<br />
Let("testDataOH", allCasesOH);<br />
Let("predictions", <br />
MLModel("randomforest")<br />
.Train(trainDataOH, outcomes)<br />
.Transform(trainDataOH));<br />
Sum(Zip(outcomes, predictions).(_[0] == _[1] != 0)) / Count(outcomes)<br />
</pre><br />
<br />
Example #2: Train a model using an a 75% sample of an event log and test its performance by using the rest 25% of the event log.<br />
<pre><br />
Def("GetOneHotColumnInformation", (<br />
Let("el", _),<br />
ToDictionary([<br />
"et": OrderByValue(el.EventTypes),<br />
"at": ToDictionary(ConcatTop(OrderByTop(el.CaseAttributes, Name).[_: Values]))<br />
])<br />
));<br />
<br />
Def("GenerateOneHot", "cases", (<br />
Let("columnInformation", _),<br />
cases.(<br />
Let("cas", _),<br />
Flatten(<br />
[<br />
columnInformation.Get("et").(Let("et", _), If(Count(cas.EventsByType(et)) > 0, 1, 0)),<br />
(<br />
Let("atColumns", columnInformation.Get("at")),<br />
OrderByValue(atColumns.Keys).(<br />
Let("key", _),<br />
Let("values", atColumns.Get(key)),<br />
Let("caseValue", cas.Attribute(key)),<br />
values.(If(_ == caseValue, 1, 0))<br />
)<br />
)<br />
]<br />
)<br />
)<br />
));<br />
<br />
Let("el", EventLogById(1));<br />
Let("columnInformation", el.GetOneHotColumnInformation());<br />
Let("allCases", Shuffle(el.Cases));<br />
Let("lastTrainCaseIndex", 0.75 * CountTop(el.Cases));<br />
Let("trainCases", allCases[NumberRange(0, lastTrainCaseIndex)]);<br />
Let("testCases", allCases[NumberRange(lastTrainCaseIndex + 1, CountTop(el.Cases) - 1)]);<br />
Let("trainDataOH", columnInformation.GenerateOneHot(trainCases));<br />
Let("testDataOH", columnInformation.GenerateOneHot(testCases));<br />
Let("trainOutcomes", trainCases.(Duration > TimeSpan(24)));<br />
Let("testOutcomes", testCases.(Duration > TimeSpan(24)));<br />
Let("predictions", <br />
MLModel("randomforest")<br />
.Train(trainDataOH, trainOutcomes)<br />
.Transform(testDataOH));<br />
Sum(Zip(testOutcomes, predictions).(_[0] == _[1] != 0)) / Count(testOutcomes)<br />
</pre><br />
<br />
Example #3: Three sets of cases: training cases, target cases (subset of training cases) and test cases (independent set of cases). Try to predict which cases in the test set will eventually end up becoming a case in target cases.<br />
<br />
<pre><br />
Def("GetOneHotColumnInformation", (<br />
Let("el", _),<br />
ToDictionary([<br />
"et": OrderByValue(el.EventTypes),<br />
"at": ToDictionary(ConcatTop(OrderByTop(el.CaseAttributes, Name).[_: Values]))<br />
])<br />
));<br />
<br />
Def("GenerateOneHot", "cases", (<br />
Let("columnInformation", _),<br />
cases.(<br />
Let("cas", _),<br />
Flatten(<br />
[<br />
columnInformation.Get("et").(Let("et", _), If(Count(cas.EventsByType(et)) > 0, 1, 0)),<br />
(<br />
Let("atColumns", columnInformation.Get("at")),<br />
OrderByValue(atColumns.Keys).(<br />
Let("key", _),<br />
Let("values", atColumns.Get(key)),<br />
Let("caseValue", cas.Attribute(key)),<br />
values.(If(_ == caseValue, 1, 0))<br />
)<br />
)<br />
]<br />
)<br />
)<br />
));<br />
<br />
Let("el", <event log to use>);<br />
Let("trainCases", <cases to use for training>);<br />
Let("targetCases", <cases representing the properties we want to try to predict (subset of traincases)>);<br />
Let("testCases", <cases to use for testing>);<br />
Let("targetCasesDict", ToDictionary(targetCases:true));<br />
Let("outcomes", traincases.(Let("c", _), targetCasesDict.ContainsKey(c) ? 1 : 0));<br />
Let("columnInformation", el.GetOneHotColumnInformation());<br />
<br />
Let("mlModel", MLModel("randomforest"));<br />
mlModel.Train(columnInformation.GenerateOneHot(trainCases), outcomes);<br />
mlModel.Transform(columnInformation.GenerateOneHot(testCases));<br />
</pre><br />
<br />
Example #4: Customized version of example #3 using actual event type and attribute names. Three sets of cases: training cases, target cases (subset of training cases) and test cases (independent set of cases). Try to predict which cases in the test set will eventually end up becoming a case in target cases. Generate HTML result ready to be sent out in an email message.<br />
<br />
<pre><br />
Def("GenerateOneHot", "cases", { let columnInformation = _;<br />
cases.{ let cas = _;<br />
Flatten( [<br />
{ let etColumns = columnInformation.Get("et"); etColumns.{ let et = _; If(Count(cas.EventsByType(et)) > 0, 1, 0) } }, <br />
{ let atColumns = columnInformation.Get("at"); OrderByValue(atColumns.Keys).{ let key = _; let values = atColumns.Get(key); let caseValue = cas.Attribute(key); values.(If(_ == caseValue, 1, 0)) } }<br />
] )<br />
}<br />
});<br />
<br />
// Make predictions for the whole model:<br />
// let el = ModelById(39694).EventLog;<br />
<br />
// Make predictions for cases in a particular filter<br />
let el = EventLogById(109773);<br />
<br />
let currenttime = now;<br />
<br />
let trainCases = el.Cases.Where(Catch(currenttime - EventTimeStampsByType("hs_analytics_last_visit_timestamp")[0] > TimeSpan(30) , true));<br />
let targetCases = trainCases.Where(_.Attribute("Lifecycle Stage").In(["opportunity", "marketingqualifiedlead", "customer", "salesqualifiedlead"]));<br />
let testCases = el.Cases.Where(Catch(currenttime - EventTimeStampsByType("hs_analytics_last_visit_timestamp")[0] < TimeSpan(30) , false));<br />
<br />
let targetCasesDict = ToDictionary(targetCases:true);<br />
let outcomes = traincases.{ let c = _; targetCasesDict.ContainsKey(c) ? 1 : 0 };<br />
let columnInformation = ToDictionary([<br />
"et": OrderByValue(el.EventTypes).Where(_.Name.In(["hs_email_last_click_date","first_conversion_date", "hs_analytics_last_visit_timestamp"])),<br />
"at": ToDictionary(ConcatTop(OrderByTop(el.CaseAttributes.Where(_.Name.In(["Lifecycle Stage", "Original Source", "QPR Digest", "Unsubscribed from all email"])) , Name).[_: Values]))<br />
]);<br />
let mlModel = MLModel("randomforest");<br />
mlModel.Train(columnInformation.GenerateOneHot(trainCases), outcomes);<br />
<br />
let predictions = mlModel.Transform(columnInformation.GenerateOneHot(testCases));<br />
let predictedCases = ToDataFrame(Zip(testCases, predictions).Where(_[1] == 1) , ["id", "pred"]).id;<br />
<br />
let body = "<html><body><table><tr><td>Last visited</td><td>Name</td></tr><tr>" +<br />
StringJoin( "</tr><tr>", "<td>" + predictedCases.EventTimeStampsByType("hs_analytics_last_visit_timestamp")[0] + "</td><td>" + predictedCases.Name + "</td>") +<br />
"</tr></table></body></html>";<br />
<br />
body;<br />
</pre></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=15234QPR ProcessAnalyzer Release Notes2020-02-04T14:52:22Z<p>TeeLeht: /* Next Release: QPR ProcessAnalyzer 2020.2 (Planned release date 2020-02-25) */</p>
<hr />
<div>This page contains new features and fixed issues for each QPR ProcessAnalyzer release. For information on the compatibility of different versions, see [[QPR ProcessAnalyzer Version Compatibility|Version Compatibility Information]]. See also [[Planned Releases for QPR ProcessAnalyzer |next planned releases]].<br />
<br />
<div style="border:1px solid #dfdfdf;padding:0.5em 1em 1em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;"><br />
<b>Note for QPR ProcessAnalyzer 2019.9</b><br />
<br />
Starting from QPR ProcessAnalyzer 2019.9 (released 2019-12-10) the separately installed QPR UI is not needed anymore. Instead, the web UI is now part of QPR ProcessAnalyzer and does not require a separate installation. The new UI can be accessed in ''http(s)://SERVER/QPRPA/ui/'' (where SERVER is the hostname of your QPR ProcessAnalyzer server). QPR ProcessAnalyzer 2019.9 does not yet have a support for SAML 2.0, and to use SAML 2.0 to authenticate to QPR ProcessAnalyzer, QPR UI is still needed. Dashboards in the QPR UI environment are not moved automatically to QPR ProcessAnalyzer, and also the QPR UI dashboard export files are not directly compatible with the new QPR ProcessAnalyzer UI. Please contact QPR CustomerCare if you need any assistance (customercare@qpr.com).<br />
</div><br />
<br />
== Next Release: QPR ProcessAnalyzer 2020.2 (Planned release date 2020-02-25) == <br />
Build number: 2020.2.0.xxxxx, Model compatibility version: x, Database version: xx, PACM file version: x, Protocol version: xx.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307763: [[ QPR_ProcessAnalyzer_Analysis_Parameters | Case attributes multiselect in influence analysis for case attributes]].<br />
* 307776: [[ QPR_ProcessAnalyzer_Objects_in_Expression_Language#User.2FGroup | Get effective project permissions in expression language]].<br />
* 307819: Expression Language: Functions, variables and statements.<br />
* 307794: [[ QPR_ProcessAnalyzer_Objects_in_Expression_Language#Model | GenericWrite permission]] should see model object counts when case level permissions are in use.<br />
* 307841: Expression language function [[ Process_Mining_Objects_in_Expression_Language#Case | Case.DurationBetweenEvents]].<br />
* 307836: Expression language extension Flow.RemoveIfStartOrEnd.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219198: In PA web.config, empty setting names should be formatted as <value></value>.<br />
* 219199: Set default ResponsePollingInterval to 3600000.<br />
* 219200: Model.EstimatedMemory gives too large estimate for models with lot of event types.<br />
* 219222: AggregateOthers doesn't work with MaximumRowCount when dimensions is null in expression analysis.<br />
* 219276: It should be possible to set filter to be model default filter when the filter is created.<br />
* 219280: It should be possible to delete model default filter.<br />
* 219275: Changing model default filter should only be possible for ManageViews permission.<br />
* 219297: Designer user can delete other people published filter from PA web client but cannot delete it from PA Excel Client.<br />
* 219285: Expression filter gives "Value was either too large or too small for an Int32".<br />
* 219304: Expression analysis returning DataFrame doesn't work in SQL script that prints to Excel sheet.<br />
* 219251: Remove sample files from \\Release\Files\OfficeAddIns\Excel\Example Data.<br />
* 219293: AnalyzeConformance function throws KeyNotFoundException - variation data seems to be missing.<br />
* 219261: Restored model model could not be open.<br />
<br />
== QPR ProcessAnalyzer 2020.1 (release date 2020-01-21) == <br />
Build number: 2020.1.0.40909, Model compatibility version: 3, Database version: 65, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307749: Support for importing data to the datatable models.<br />
* 307813: DataSourceType parameter to --#ImportEvents and --#ImportCaseAttributes ETL scripting commands.<br />
* 307743: Backend support for saving the new filters.<br />
* 307775: Effective dashboard permissions are included to dashboard definition when fetched from the server.<br />
* 307772: Dashboard project path is added to dashboard definition when fetched from the server.<br />
* 307778: When saving a view, the view is not anymore reloaded unnecessary.<br />
* 307810: Expression language adjustments.<br />
* 307818: Drop support for QPR ProcessAnalyzer Excel Client for Excel 2013.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219236: Microsoft.AspNet.Identity.Core.dll and Microsoft.AspNet.Identity.Core.xml files missing when installing QPR ScriptLauncher from the installation package.<br />
* 219291: QPR ProcessAnalyzer didn't work in https only configuration.<br />
* 219264: DataFrameMode enabled for KPI analysis even if Values have been defined (but Dimensions is empty).<br />
* 219223: Variable function don't work with upper case variables.<br />
* 219267: Viewing DataFrame contents in KPI analysis gives incorrect results.<br />
* 219279: DataFrame columns by name is unavailable inside user defined functions in KPI analysis.<br />
* 219259: It should be possible to enable CORS from all origins.<br />
* 219274: "Inconsistent or unavailable ids" error when using all cases filter.<br />
* 219290: Getting contents of a dashboard is slow in a customer environment.<br />
* 219286: User could not open any models after using broken model.<br />
* 219227: Slowness in model creation when read data from datasource - event cost calculation improvements.<br />
* 219250: Slowness in event creation when read data from datasource - group by event sorting.<br />
* 219292: Performance issue in /api/uielements as it unnecessarily fetched dashboard contents.<br />
* 219295: Client side fix for 219292.<br />
* 219269: Query results were handled incorrectly in the client side - datatype is cell specific, not column specific.<br />
<br />
== Additional QPR ProcessAnalyzer 2019.9 (release date 2019-12-18) == <br />
Build number: 2019.9.0.40754, Model compatibility version: 2, Database version: 63, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307785: Angular Migration: Migrate ProcessAnalyserService.<br />
* 307786: Angular Migration: Migrate FieldPropertiesUtils.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219262: Login to PA UI is not possible when there is + character in the password<br />
* 219263: Opening dashboard which definition is large<br />
* 219257: It should be possible to get DataFrame cell value by column name in expression analysis<br />
<br />
== QPR ProcessAnalyzer 2019.9 (release date 2019-12-10) == <br />
Build number: 2019.9.0.40704, Model compatibility version: 2, Database version: 63, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307484: Implemented Excel client protocol version for improved compatibility for older Excel Clients.<br />
* 307564: [[Web.config_file_in_QPR_ProcessAnalyzer|Case sampling]] is disabled by default.<br />
* 307724: There is a support for self-signed certificate for QPR ProcessAnalyzer service.<br />
* 307705: User related information and session id is available for HTML presentation objects.<br />
* 307712: Error messages from the backend are shown in UI<br />
* 307750: PA UI Frontend (part 3)<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219170: Conformance checking didn't work when there is a non-existing bpmn task between parallel gateway and the end event.<br />
* 219152: Loading model into memory doesn't anymore require a ResetModelCache permission.<br />
* 219213: Improved model loading performance when using ODBC, datatable and expression datasources.<br />
* 219218: Order of the comparison rules incorrectly affected the influence analysis results.<br />
* 219240: Import model or export model from filter gave "Input string was not in a correct format" error.<br />
* 219238: Fix for error message "CommunicationException: The remote host closed the connection".<br />
* 219249: Access was incorrectly denied for non system admins when saving a new dashboard.<br />
<br />
== QPR ProcessAnalyzer 2019.8 (release date 2019-10-30) == <br />
Build number: 2019.8.0.40391, Model compatibility version: 2, Database version: 62, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307633: [[QPR_ProcessAnalyzer_Model_Datasources#Loading_Data_from_Datatables|Datatables]] can be used as a PA model datasource (part 1).<br />
* 307700: JSON filter rules should not give error for non-existing values, such as event type names.<br />
* 307721: Improvements to model [[QPR_ProcessAnalyzer_Model_JSON_Settings#Automatic_Loading_on_Server_Startup|Improvements to model LoadOnStartup]]: loading is done in a separate thread and in parallel.<br />
* 307693: [[QPR_ProcessAnalyzer_Objects_in_Expression_Language|Expression language: Return attributes in alphabetical order]].<br />
* 307738: Expression language: [[QPR_ProcessAnalyzer_Expressions#Null_conditional_operator_.28.3F._and_.3F:.29 | null-conditional]] and [[QPR_ProcessAnalyzer_Expressions#Null_coalescing_operator_.28.3F.3F.29 | null-coalescing operators]]. <br />
* 307725: Expression language: AsParallel function for making calculations in parallel to improve performance.<br />
* 307715: New PA Web UI Backend (part 3).<br />
* 307728: New PA Web UI Backend (part 4).<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219210: ScriptLaucher CSV export should quote string values with double quotes when the string value contains semicolon.<br />
* 219143: IIS https only setup does not work.<br />
* 219186: Event.IndexInCase had issue with event type filters.<br />
* 219167: Event.OutgoingFlowOccurrence and Event.IncomingFlowOccurrence had issues with event type filters.<br />
* 218689: _.Cases and _.Events doesn't work as a root in EventLog context in KPI Analysis.<br />
* 219004: PA license expiration causes unclear error in UI.<br />
* 219187: KeyNotFound exception occurred when include only all cases from the Path Analysis.<br />
* 219197: Minor issues in ODBC datasource.<br />
* 219207: Flowchart influence analysis does not work properly when using both Filter and Comparison parameters.<br />
<br />
== QPR ProcessAnalyzer 2019.7 (release date 2019-09-25) == <br />
Build number: 2019.7.0.40226, Model compatibility version: 2, Database version: 61, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307655: Drop support for SQL core as PA data source (Part 5 Memory optimization).<br />
* 307696: New PA Web UI Backend.<br />
* 307710: New PA Web UI Backend (part 2).<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219164: Event.NextInCase/PreviousInCase didn't work with event type filters.<br />
* 219136: ODBC model not support import and remove functionality.<br />
* 219171: Event.NextInCase and Event.PreviousInCase requires CaseEvents preprocessing.<br />
* 219173: Out of memory error and application pool crashing in customer environment.<br />
<br />
== QPR ProcessAnalyzer 2019.6 (release date 2019-08-08) == <br />
Build number: 2019.6.0.40009, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307260: Update to Visual Studio 2017 and update to .Net 4.7.1.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219106: Datetime ticks property in the expression language should be in UTC.<br />
<br />
== QPR ProcessAnalyzer 2019.5 (release date 2019-06-19) == <br />
Build number: 2019.5.0.39902, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307330: Filtering renewal: PAPO.<br />
* 307638: Angular Migration: Migrate Analysis classes part 3.<br />
* 307653: Angular Migration: Migrate Analysis classes part 4.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307649: Drop support for SQL core as PA data source (Part 4 Source code removal).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 219040: Clustering analysis expression doesn't take into account model without any case attributes.<br />
* 219001: Case Analysis always limited to 1000 rows (other analyses have the same problem).<br />
* 219042: PAPO: "Influence Analysis for Case Attributes", value is rounded to closest integer.<br />
* 218944: PAPO: Recycle bin icon in filter rule name is not visible when there is long text without spaces.<br />
* 219041: When duration limit 0, filters made from duration beams don't work.<br />
* 219099: Datetimes in expression language query don't show fraction of seconds (QPR UI).<br />
* 219103: PAPO: context menu is not working in KPI analysis.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 219062: GetModels is slow for admin.<br />
* 218978: Odd 1 million filter is adapted once you remove your custom filter.<br />
* 219015: Script Launcher million rows limit when exporting to excel csv.<br />
* 219022: GetModelAsStream webservice not support modelId.<br />
* 219080: JSON filtering does not work with flowchart analysis.<br />
* 219087: Increase from 1GB to 2GB limit in PA webservice.<br />
* 219032: PAPO Variation Analysis is not drawn.<br />
* 219017: Datetimes in expression language query don't show fraction of seconds (PA CORE).<br />
<br />
== Additional Release for QPR ProcessAnalyzer 2019.4 (release date 2019-05-31) ==<br />
Build number: 2019.4.0.39800, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 219078: PAPO loses saved filter when changing analysis<br />
* 219000: User with only Analyzer role can see and use private filter created by Administrator.<br />
* 219049: Copy of a model with odbc datasource doesn't have filters from the original model.<br />
* 219044: Calculated case attributes don't work with odbc model without defined cases.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307611: Drop support of PAIK.<br />
* 307636: Drop PA Excel client support for Excel 2010, Windows 7 and Windows 8.1.<br />
* 307628: Drop support for SQL core as PA data source (Part 3 Source code removal).<br />
<br />
== QPR ProcessAnalyzer 2019.4 (release date 2019-05-07) == <br />
Build number: 2019.4.0.39420, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* Custom dashboards for QPR ProcessAnalyzer can be browsed and edited more easily, as there is a Dashboards menu item available.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307419: Change the database connection type to use in-memory core (PA Core).<br />
* 307324: Drop support for SQL core as PA data source (Part 1: Export from EventLog).<br />
* 307619: Drop support for SQL core as PA data source (Part 2: Remove analysis 26, 27 and 28).<br />
* 307523: Refactor ModelInformation code in PA Core.<br />
* 307613: Quick & Easy memory usage optimizations: PA Core.<br />
* 307618: Prediction capability to expression language.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218909: Data grid based analysis jumping.<br />
* 218971: PAPO Variation analysis has both paths and counts at the same time.<br />
* 218972: PAPO Duration analysis missing the grouped by dimension (default value is not set in analysis). <br />
* 218969: Event attribute "Cost" doesn't work in Profiling Events analysis and in Expression language.<br />
* 219006: Case id's (case names) are interpreted as numbers by PAPO.<br />
* 219027: Numerical attributes are shown as zero decimals in some analysis in data grid presentations.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218938: Filter rules information is not showing names for odbc loaded models and calculated case/event attributes.<br />
* 218945: PA UI Profiling and Event type analysis with selections costs are lost.<br />
* 218976: Inconsistency in pre-processing CaseEvents results.<br />
* 219012: Pre-loaded models give null reference exception.<br />
* 219008: Key is not in dictionary is thrown when selecting benchmark case attribute.<br />
* 219034: Model calculation context for expression data source is not initialized correctly.<br />
* 218920: Private filters are visible for other users (which is fine for admins but not for other user types).<br />
<br />
== QPR ProcessAnalyzer 2019.3 (release date 2019-03-27) == <br />
Build number: 2019.3.0.38860, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* It's possible to add [[Calculated_Attributes_in_QPR_ProcessAnalyzer|calculated case and event attributes]] to QPR ProcessAnalyzer models using the expression language. Calculated attributes are created when the model is loaded into memory, and they are available in the analyses like the normal imported attributes. Calculated attributes allow e.g. data conversions and cleansing, and also making calculations beforehand to improve performance.<br />
* QPR ProcessAnalyzer has a new [[Clustering Analysis]], which divides cases into similar groups based in case attributes and occurred types of events. Clustering analysis provides a new way to understand and structure your process mining data.<br />
* In the expression language, the left out rows can be [[QPR_ProcessAnalyzer_Expression_Analysis#Expression_Analysis_JSON_Configuration|aggregated as the last row]], which is useful, e.g. when you want to present only the most important data but still see the total amount of cases in the model. Also ChartView contains a new setting Group and Show Others using this expression language feature.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307507: Disable rectangular selection in flowchart.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307545: KPI: Clustering analysis and related utility functions.<br />
* 307512: Expression language: Description attribute to Model.<br />
* 306900: Calculated case and event attributes.<br />
* 307533: Level of event log pre-processing can be set for [[QPR_ProcessAnalyzer_Expression_Analysis#KPI_Analysis_JSON_Configuration |expression analysis]].<br />
* 307575: [[Web.config_file_in_QPR_ProcessAnalyzer#Qpr.ProcessAnalyzer.Common.Properties.Settings_Section |Change items memory caching times]].<br />
* Support for Windows 8 has been dropped. Windows 8.1 is still supported.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218863: Model manager not updated after changing Filter Id.<br />
* 218874: Sorting and filtering icons overlap in datagrid.<br />
* 218922: There should be default maximum number of items for different analyses created from tool palette.<br />
* 218723: Empty analysis window after error thrown by PA service.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218908: Wrong Client data in operation log.<br />
* 218928: Expression filter doesn't work with integers.<br />
* 218940: Model eventlog can drop from memory.<br />
* 218927: JSON filtering for case attributes doesn't work with nulls.<br />
* 218779: Source data formatted to two decimals accuracy but PA total cost flowchart show much more decimals.<br />
* 218943: ODBC SQL boolean values does not work with filter CaseAttributeValue.<br />
* 218965: Accessing calculated event attribute value from EventType.Events -property does not work.<br />
<br />
== QPR ProcessAnalyzer 2019.2 (release date 2019-02-14) ==<br />
Build number: 2019.2.0.38539, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* Support for [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Excel_Client| Microsoft Office 2019]] for QPR ProcessAnalyzer Excel Client.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307423: Improved memory management: unused objects are automatically dropped from the memory. Settings can be configured in [[Web.config_file_in_QPR_ProcessAnalyzer#Qpr.ProcessAnalyzer.Common.Properties.Settings_Section | web.config]] or from the [[QPR_ProcessAnalyzer_Model_JSON_Settings#Memory_Usage_Settings | model JSON settings]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218838: KPI analysis: Event Occurrence Time isn't calculated properly, e.g. Period=Month fails.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218880: PAPO: odbc case and event attributes are not shown in dropdown menu.<br />
* 218877: Support material - Project admins are not able to create new users.<br />
* 218898: Importing XES file with xmlns -definition fails.<br />
* 218893: Model status shows incorrectly "offline" when Model event log is in memory and Model information not.<br />
* 218917: BaseContext.EvaluateChildExpression with given root object iterates the root object if it is an array.<br />
<br />
== Additional Release for QPR ProcessAnalyzer 2019.1 (release date 2019-01-23) ==<br />
Build number: 2019.1.0.38400, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
<br />
* 307357: PA model management: Analysis requests canceling. All operations have new parameters QueryIdentifier and CancelEarlierQueriesWithIdentifier.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218806: Variation filter doesn't filter correctly.<br />
* 218802: It should not be able to load deleted models into memory.<br />
* 218866: Case Analysis shows "0" for textual Case Attribute (SelectedActivityCounts=0 column count and data not match).<br />
* 218862: Case Analysis returns incorrect Start and End times when start or end transition is selected.<br />
* 218847: Variation Analysis Include Only Cases Filter Fails when using Event Counts and filter.<br />
* 218765: Event Occurrence Time calculation for KPI analysis (Server side).<br />
<br />
== QPR ProcessAnalyzer 2019.1 (release date 2019-01-03) ==<br />
Build number: 2019.1.0.38310, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* There are new training videos available for QPR ProcessAnalyzer in QPR Community. QPR ProcessAnalyzer users can access the videos by clicking Training Videos in the header menu of QPR ProcessAnalyzer UI.<br />
* ChartView can show several measures at the same time. In table, measures are in different columns, and in chart, measures are presented as different series.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer UI:'''<br />
* 218768: Number of decimals is not updated in KPI analysis due to HistoryId context variable.<br />
* 218787: Datagrid export fails with numerical values.<br />
* 218757: KPI analysis - null value shown as NaN.0 in table.<br />
* 218794: Popup menu is replicated when PAPO is drawn multiple times.<br />
* 218740: Case Analysis Year period should not show thousand separator.<br />
* 218805: Analysis not shown after adding duration analysis to panel using view designer "shortcuts buttons".<br />
* 218804: PAPO showing only Analysis Window doesn't show anything when other PAPO hides the Analysis window.<br />
* 218815: Flowchart influence analysis does not always show the results in an identical way.<br />
* 218791: Flowcharts visibility stepper don't work in PA deployment package Process benchmarking view.<br />
* 218844: KPI Analysis sorting is not saved to the context variable.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218755: If user selects Influence Analysis for Case Attributes into analysis window, it freezes the analysis window completely.<br />
* 218756: PA model - with event attributes - without case attributes = event attributes shown in profiling case attributes analysis.<br />
<br />
== QPR ProcessAnalyzer 2018.8 (release date 2018-11-29) ==<br />
Build number: 2018.8.0.38236, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* New types of charts have been added to the KPI Analysis in PAPO. In addition to the previously available column chart and table presentations, there are now bar, donut, area, line and spline charts.<br />
* Tool palette contains now items for each QPR ProcessAnalyzer analysis making it easier to create dashboards with different analyses. The analyses have also needed context variables predefined so that settings are saved to the dashboard.<br />
* Duration Influence Analysis is now calculated in the memory which makes it significantly faster than previously when it was calculated in the SQL Server.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307398: More chart types to KPI analysis, such as line chart, bar chart and donut chart.<br />
* 307473: PAPO tables exporting to Excel, Word and PDF<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307417: Duration Influence Analysis in In-Memory.<br />
* 307458: Performance improvement in reusing event logs.<br />
* 307456: Expression language plugin mechanism.<br />
* 307459: [[QPR_ProcessAnalyzer_Web_Service_API#Functions_in_the_Web_Service_API|PA service support for script generated reports as csv file (for QPR UI Script Manager)]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218711: PAPO duration analysis is failing.<br />
* 218663: PAPO - KPI Analysis - Number of decimals effects column height.<br />
* 218664: PAPO - KPI Analysis - Default number of decimals in the drop-down list should be 1.<br />
* 218669: PAPO - KPI Analysis duration from - to.<br />
* 218557: PAPO - Duplicate flows when increasing the flow amounts in flowchart.<br />
* 218718: PAPO - Flowchart sometimes shows portions of the flowchart completely unconnected from start/end nodes of the flowchart.<br />
* 218668: PAPO - KPI Analysis - wrong names in droplist and wrong chart title.<br />
* 218666: PAPO - KPI Analysis - CamelCase column headers.<br />
* 218670: PAPO - KPI Analysis - title Duration between "undefined" and "undefined". <br />
* 218665: PAPO - KPI Analysis - numerical data should be shown linear on X axis.<br />
* 218629: PAPO - KPI Analysis - Year period should not show thousand separator.<br />
* 218667: PAPO - KPI Analysis - units are missing in table.<br />
* 218725: PAPO - KPI Analysis - NumberOfDecimals should be enabled for numerical case&event attribute.<br />
* 218731: PAPO - layout issue when displaying error message.<br />
* 218747: PAPO - KPI analysis - Column header text is not consistent with x-axis label.<br />
* 218762: PAPO - KPI Analysis - Error message doesn't disappear when switching from wrong selections to correct ones.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218727: Null values don't work in GroupBy/GroupByValue functions.<br />
* 218708: Filtering with duration value 0 does not work in duration analysis.<br />
* 218770: Case analysis with variation Id -> Exception: The given key was not present in the dictionary.<br />
* 218771: Conformance: Parallel gateways having multiple branches with only one node aren't analyzed correctly.<br />
<br />
== QPR ProcessAnalyzer 2018.7 (release date 2018-10-10) ==<br />
Build number: 2018.7.0.38036, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307319: Expression language: [[Generic_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#Other_functions | GroupBy and GroupByValue -functions]].<br />
* 307370: PAPO/A1 cell case/event/event type/variation count should only show cases user has permissions in case level security.<br />
* 307369: String handling functions in the expression language.<br />
* 307424: KPI analysis in generic context.<br />
* 307439: Quick & easy expression language improvements.<br />
* 307336: PA performance improvement (part 1).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218673: Null values in PA expression language should appear as nulls in datasets.<br />
* 218693: Performance for PAPO's data grids has been optimized.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218453: .TMP files is not deleted always. After 65k .TMP files exist then PA service stop working. If issue is encountered, workaround is to manually delete .TMP files (e.g. files are located in folder C:\Windows\Temp or C:\Users\<pa_applicationpool_user>\AppData\Local\Temp).<br />
* 218643: InMemory: Open model after pacm file import fails to "Object reference not set to an instance of an object.".<br />
* 218652: Access denied. Unexpected ModelEventLog dropping object with from cache.<br />
* 218648: Import empty model with filter crash (evevenlog.Content is null).<br />
* 218685: XES import runs out of memory when importing BPIC2018 -model.<br />
* 218690: Expressions returning boolean values should be returned to QPR UI as booleans.<br />
* 218687: Average and Sum functions should return null for zero length arrays instead of zero.<br />
* 218705: InMemoryCore: TotalCost in event analysis has incorrect values.<br />
* 218704: Mismatch in case counts in Variation Analysis when event type filter has been applied.<br />
* 218709: FileType parameter not select correct stream compression mode in ImportFromStream.<br />
* 218698: The given key was not present in the dictionary - Variation Analysis error.<br />
* 218710: PAPO case analysis is currently failing.<br />
<br />
== QPR ProcessAnalyzer 2018.6 (release date 2018-08-29) ==<br />
Build number: 2018.6.0.37869, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights'''<br />
* KPI Analysis update: The KPI Analysis feature has new updates to it. The Analysis Menu design has new options that allow for efficient creation of KPI analysis presentations. Menu items have been grouped into sub-groups making finding analysis options much swifter. <br />
* Model load on startup: You can now define which models are loaded onto memory on startup allowing for quicker setup of QPR ProcessAnalyzer servers. This loads the key models needed directly into memory without any separate in-memory loading.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307351: KPI analysis UI - part 2<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307323: [[PA Migration to 2018.6 |Remove old PA web client]].<br />
* 307200: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Necessary_IIS_setup |PA model management: PA model automatic loading on startup]]. <br />
* 307350: KPI analysis UI - part 2 (server side).<br />
* 307208: PA model management: PA model status information to expression language.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218391: PA UI Flowchart selection does not clear automatically.<br />
* 218606: Edit mode is ON > Floating Action Buttons are not clickable.<br />
* 218626: PAPO: some popup menus are not closed properly in IE 11.<br />
* 218607: PAPO: popup menu is not displayed in IE 11.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218597: PA Exception details show null in QPR UI.<br />
* 218575: Incorrect results in conformance analysis calculation. <br />
* 218540: KPI analysis not working properly.<br />
* 218314: Variation analysis shows duplicate variations if there are excluded event types.<br />
* 218604: PA Excel client does not log enough during connection creation.<br />
* 218624: Estimatedmemory not calculated correctly when model not have events.<br />
* 218396: KPI analysis - ApplyAnalysisFilters. InvalidOperationException: Sequence contains no elements.´<br />
* 218628: PAPO: Error popup appears, "Error processing QPR ProcessAnalyzer request.<br />
* 218631: Performance improvements (Path analysis was slow).<br />
* 218485: ProcessAnalyzer Excel client cannot be removed from Programs and Features, as it wont show up there.<br />
* 217775: GetAnalysis(18) should write a progress log entry after each chunk.<br />
* 217653: SQL command not in log when ODBC connection failed.<br />
<br />
== QPR ProcessAnalyzer 2018.5 (release date 2018-07-17) ==<br />
Build number: 2018.5.0.37716, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights'''<br />
*QPR ProcessAnalyzer Deployment Package for QPR UI: The new version comes with preloaded QPR UI views that can instantly kickstart your Process Mining experience. These views are readymade and require no extra configuration. These views introduce new functionalities, such as ready made conformance views, for deploying a more varied Process Mining offering. <br />
*New Dashboard Design features: Panels can be now instantly developed and evaluated in viewer mode, allowing for a more powerful dashboard creation. The object placing logic has been overhauled, allowing for new options in creating dashboards. <br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307338: [[QPR_ProcessAnalyzer_API:_ResetModelCache | Web service support to load and drop PA models]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218536: PAPO: KPI Analysis should not be available from Control Windows.<br />
* 218519: The numerical values in QPR ProcessAnalyzer Influence Analysis were aligned to the left.<br />
* 217888: Selection lost from influence analysis table when user slightly adjusts browser window or panel/presentation object window size.<br />
* 218465: PAPO: Newly created filters are not displayed in the list.<br />
* 218556: PAPO: An unnecessary vertical scrollbar was shown after PAPO Case Analysis was resized.<br />
* 218520: PAPO: Filter does not recognize decimal separators.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218537: ODBC xlsx loading failed with data format issue.<br />
* 218495: Changing default filter does not drop cached model information.<br />
* 218550: Accessing projects from expression language fails in some cases.<br />
* 218549: Datatable import from Excel sheet data corruption if first column value is empty.<br />
* 218558: Errors in default.aspx. Login fails.<br />
<br />
== QPR ProcessAnalyzer 2018.4 (release date 2018-06-11) ==<br />
Build number: 2018.4.0.37669, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ODBC driver support for QPR ProcessAnalyzer: Use external data sources to create a dynamic model that is updated every time the model is loaded. Using the ODBC driver, the model data can be accessed from a separate data source. All the event data information can be defined in JSON format allowing for automatic model creation.<br />
* KPI Analysis: A new analysis is added to QPR ProcessAnalyzer. KPI Analysis utilizes the KPI expression engine for creating visualizations of data. KPI Analysis is a fully fledged analysis that can be used in conjuction with the existing QPR ProcessAnalyzer analysis for more focused results. In addition, KPI Analysis is available as a separate QPR UI view for creation of dashboards that present real-time data taken from QPR ProcessAnalyzer.<br />
* Tabular Analysis results updated with data types: Analysis featuring tabulated data are now automatically updated with correct data types. Automatic data types allow for exporting the data in a format that can be used in other compatible tools as the data types are automatically defined into the data.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307265: KPI analysis UI - part 1 (KPI).<br />
* 307278: The tabular analyses (e.g. Case analysis) in QPR ProcessAnalyzer UI now have the correct column data types based on the information from the QPR ProcessAnalyzer server.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307204: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Model Datasources|Load PA model from ODBC datasource]].<br />
* 307313: Expression language improvements - part 7 (performance).<br />
* 307317: Update new [[QPR_End_User_Software_License_Agreement|EULA]] to QPR ProcessAnalyzer.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218487: Influence analysis for Flowchart changes the flowchart settings.<br />
* 218498: No history entry is created while changing visibility threshold via stepper or context variable.<br />
* 218508: PAPO variation analysis should limit the queried number of variations.<br />
* 218513: PAPO settings buttons cover analysis content.<br />
* 218532: PAPO: Profiling analysis does not work with data loaded via ODBC.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218515: IIS crashes in kernel during Odbc query reading csv/xlsx file with Microsoft Access Text Driver and Microsoft Excel Driver.<br />
* 218484: ImportEvents fails in StartBackground mode.<br />
* 218525: InMemory CaseAnalysis ShowAllCases not work if there is cases without events.<br />
* 218463: Issue to install excel client (part 2).<br />
<br />
== QPR ProcessAnalyzer 2018.3 (release date 2018-04-23) ==<br />
Build number: 2018.3.0.37545, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
*Conformance Checking is supported in QPR ProcessAnalyzer. Using the KPI Expression Language as a basis, process mining models can be compared to BPMN notation and analyzed if the process data conforms to the BPMN design. These results are implemented in ChartView and KPI Expression Language allows them to be implemented into dashboards.<br />
*BPMN Editor has been added to ChartView. You can now import and design BPMN process maps for use in conformance analysis. The BPMN editor is a web component that is used in the browser, allowing for quick and easy process design. The designs can also be exported for further use.<br />
*Flowchart Visibility Settings have been overhauled with a new visual presentation. New stepper elements allow for more flexible flow threshold settings while maintaining a user-friendly approach.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307276: Remove PAPO Offline mode.<br />
* 307193 & 307298: The [[Flowchart_Analysis#Visibility_Settings|Flowchart Visibility Settings]] were improved.<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307077: [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Server | Support for Windows Server 2016 (PA Service)]].<br />
* 307246: Expression function to calculate conformance to BPMN.<br />
* 307297: Expression language improvements - part 6.<br />
* 307301: In-memory memory usage optimizations.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218306: PAPO control window is affected by analysis window's 'Show as' setting.<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218241: PA Duration Analysis In-Memory - numbers for Events and Cases too high (focus flow).<br />
* 218456: Issue to install excel client (part 1).<br />
<br />
== QPR ProcessAnalyzer 2018.2 (release date 2018-03-12) ==<br />
Build number: 2018.2.0.37453, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* Case Permissions have been added to the data security featureset. Case Permissions allow for limiting model visibility based on rules that reference the case attributes of a set model. Case permissions can refer to usernames or user groups, creating a link between the attributes and groups.<br />
* Influence Analysis for Case Attributes has been simplified. The feature presents basic information relating to the root causes when it is opened. If further information is needed, this can be accessed via the feature menu. <br />
* DataGrids support Excel exporting. You are now able to export data from fixed dashboards featuring datagrids. With this feature, you can take your data for further manipulation using Microsoft Excel.<br />
* Chartview has been improved with a new layout and excel exporting. The new layout allows for quicker access to creating charts using the ChartView tool. With the exporting functionality, the views created are exported for use in presentations in Microsoft Excel.<br />
* KPI Expression Language has been added with support for Influence Analysis for Case Attributes. This allows for further creation of dashboards with specific analysis result queries. Using the KPI expression language, dashboards can be made to present up-to-date data based on influence analysis results.<br />
* Dataset tag support for data visualization. Adding dataset tags will help in creating more dynamic chart presentations as the data can be inserted into the JSON settings of charts and datagrids. <br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307220: The Influence Analysis for Case Attributes settings now has a toggle for showing and hiding the detail columns.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307273: [[QPR ProcessAnalyzer Web Service API#Example| PA model JSON settings]].<br />
* 307269: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Case_Permissions |Case permissions]].<br />
* 307261: PA InMemory core, part 8 (Path Analysis).<br />
* 307282: PA KPI's and expressions (part 5).<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218426: Using PAPO with customers model crashes PA Server (Entice Changes).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218371: Event types aren't provided to PAPO by PA server.<br />
* 218372: Having multiple expressions in one selection item in a JSON filter does not work.<br />
* 218375: Empty comparison -setting with nonempty filter -setting causes influence analysis to return incorrect results.<br />
* 218380: PA Activation ends one day before the actual end date.<br />
* 218362: WebService GetAnalysisAsImage does not work.<br />
* 218389, 218397: Performance issues in PA in-memory core with multiple simultaneous users.<br />
* 218412: PercentageNumber property is not set properly in PA analyses.<br />
* 218410: Event attribute profiling event amount mismatch.<br />
* 218404: Using PAPO with customers model crashes PA Server (PA changes).<br />
* 218430: Pre-release mandatory PA bugfixes.<br />
<br />
== QPR ProcessAnalyzer 2018.1 (release date 2018-01-31) ==<br />
Build number: 2018.1.0.37330, Model compatibility version: 2, Database version: 57, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ChartView is introduced as a new QPR UI view. This interactive view allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. ChartView comes preloaded with numerous different presentation features for the creation of customized charts fit for any business need.<br />
* New Table Filtering for Data Table Views. A new Excel-style filtering feature has been added to the different analysis features, such as Influence Analysis for Case Attributes and Event Analysis. The feature allows the presentation and comparison of different data using robust filters.<br />
* The QPR UI version of QPR ProcessAnalyzer has an overhauled popup menu. Selecting different analysis and creating new filters is quicker and new icons have been added for added clarity.<br />
* XES filetype importing support. The IEEE TaskForce standardized XES logs are now supported by QPR ProcessAnalyzer. This filetype aims to unify the transactional data produced by information systems and makes them usable in tools used in data analysis. <br />
<br />
'''Full Features for QPR ProcessAnalyzer UI:'''<br />
* 307244: The various tables (e.g. Case Analysis) in QPR ProcessAnalyzer UI received filtering functionality familiar to the one in Microsoft Excel.<br />
* 307163: Popup menu improvements.<br />
* 307224: Cache model information into browser side.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307271: PA InMemory core, part 7 (Canceling analysis).<br />
* 307247: XES Event log file format support.<br />
* 307257, 307270: PA KPI's and expressions (part 3, 4).<br />
* 307211: Enable custom data sources: Selections as JSON.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218327: PAPO Grid view row selection issues when opening popup menu.<br />
* 218328: PAPO Missing null check in ModelState.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218324: Fixed an issue where a dataset wasn't refreshed when a context variable was changed from PAPO.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218288: PA service installation with DeployPAService.ps1.<br />
* 218291: Problem with --#GetAnalysis type 31 (filter rules).<br />
* 218315: PAPO: InMemoryCore: Offline mode shows incorrect case attribute values.<br />
* 217922: Filtering Flow Table with Case Attribute is too slow.<br />
* 218321: PA core - Internal server error in PAPO when duration analysis result is empty.<br />
* 218322: Flow analysis results not always in same order (InMemory).<br />
* 218340: Not allow to delete default filter ("No access/Access denied").<br />
* 218345: Unknown filter rule. The given key was not present in the dictionary.<br />
* 218363: Attribute values are sent to clients as strings from InMemory profiling analysis.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218379: PAPO: Side panels visible in multi papo even if they should be closed and invisible.<br />
<br />
== Old Releases ==<br />
See older releases in [[QPR ProcessAnalyzer Release Archive]]<br />
__NOTOC__</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=15233QPR ProcessAnalyzer Release Notes2020-02-04T14:51:53Z<p>TeeLeht: /* QPR ProcessAnalyzer 2020.1 (release date 2020-01-21) */</p>
<hr />
<div>This page contains new features and fixed issues for each QPR ProcessAnalyzer release. For information on the compatibility of different versions, see [[QPR ProcessAnalyzer Version Compatibility|Version Compatibility Information]]. See also [[Planned Releases for QPR ProcessAnalyzer |next planned releases]].<br />
<br />
<div style="border:1px solid #dfdfdf;padding:0.5em 1em 1em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;"><br />
<b>Note for QPR ProcessAnalyzer 2019.9</b><br />
<br />
Starting from QPR ProcessAnalyzer 2019.9 (released 2019-12-10) the separately installed QPR UI is not needed anymore. Instead, the web UI is now part of QPR ProcessAnalyzer and does not require a separate installation. The new UI can be accessed in ''http(s)://SERVER/QPRPA/ui/'' (where SERVER is the hostname of your QPR ProcessAnalyzer server). QPR ProcessAnalyzer 2019.9 does not yet have a support for SAML 2.0, and to use SAML 2.0 to authenticate to QPR ProcessAnalyzer, QPR UI is still needed. Dashboards in the QPR UI environment are not moved automatically to QPR ProcessAnalyzer, and also the QPR UI dashboard export files are not directly compatible with the new QPR ProcessAnalyzer UI. Please contact QPR CustomerCare if you need any assistance (customercare@qpr.com).<br />
</div><br />
<br />
== Next Release: QPR ProcessAnalyzer 2020.2 (Planned release date 2019-02-25) == <br />
Build number: 2020.2.0.xxxxx, Model compatibility version: x, Database version: xx, PACM file version: x, Protocol version: xx.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307763: [[ QPR_ProcessAnalyzer_Analysis_Parameters | Case attributes multiselect in influence analysis for case attributes]].<br />
* 307776: [[ QPR_ProcessAnalyzer_Objects_in_Expression_Language#User.2FGroup | Get effective project permissions in expression language]].<br />
* 307819: Expression Language: Functions, variables and statements.<br />
* 307794: [[ QPR_ProcessAnalyzer_Objects_in_Expression_Language#Model | GenericWrite permission]] should see model object counts when case level permissions are in use.<br />
* 307841: Expression language function [[ Process_Mining_Objects_in_Expression_Language#Case | Case.DurationBetweenEvents]].<br />
* 307836: Expression language extension Flow.RemoveIfStartOrEnd.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219198: In PA web.config, empty setting names should be formatted as <value></value>.<br />
* 219199: Set default ResponsePollingInterval to 3600000.<br />
* 219200: Model.EstimatedMemory gives too large estimate for models with lot of event types.<br />
* 219222: AggregateOthers doesn't work with MaximumRowCount when dimensions is null in expression analysis.<br />
* 219276: It should be possible to set filter to be model default filter when the filter is created.<br />
* 219280: It should be possible to delete model default filter.<br />
* 219275: Changing model default filter should only be possible for ManageViews permission.<br />
* 219297: Designer user can delete other people published filter from PA web client but cannot delete it from PA Excel Client.<br />
* 219285: Expression filter gives "Value was either too large or too small for an Int32".<br />
* 219304: Expression analysis returning DataFrame doesn't work in SQL script that prints to Excel sheet.<br />
* 219251: Remove sample files from \\Release\Files\OfficeAddIns\Excel\Example Data.<br />
* 219293: AnalyzeConformance function throws KeyNotFoundException - variation data seems to be missing.<br />
* 219261: Restored model model could not be open.<br />
<br />
== QPR ProcessAnalyzer 2020.1 (release date 2020-01-21) == <br />
Build number: 2020.1.0.40909, Model compatibility version: 3, Database version: 65, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307749: Support for importing data to the datatable models.<br />
* 307813: DataSourceType parameter to --#ImportEvents and --#ImportCaseAttributes ETL scripting commands.<br />
* 307743: Backend support for saving the new filters.<br />
* 307775: Effective dashboard permissions are included to dashboard definition when fetched from the server.<br />
* 307772: Dashboard project path is added to dashboard definition when fetched from the server.<br />
* 307778: When saving a view, the view is not anymore reloaded unnecessary.<br />
* 307810: Expression language adjustments.<br />
* 307818: Drop support for QPR ProcessAnalyzer Excel Client for Excel 2013.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219236: Microsoft.AspNet.Identity.Core.dll and Microsoft.AspNet.Identity.Core.xml files missing when installing QPR ScriptLauncher from the installation package.<br />
* 219291: QPR ProcessAnalyzer didn't work in https only configuration.<br />
* 219264: DataFrameMode enabled for KPI analysis even if Values have been defined (but Dimensions is empty).<br />
* 219223: Variable function don't work with upper case variables.<br />
* 219267: Viewing DataFrame contents in KPI analysis gives incorrect results.<br />
* 219279: DataFrame columns by name is unavailable inside user defined functions in KPI analysis.<br />
* 219259: It should be possible to enable CORS from all origins.<br />
* 219274: "Inconsistent or unavailable ids" error when using all cases filter.<br />
* 219290: Getting contents of a dashboard is slow in a customer environment.<br />
* 219286: User could not open any models after using broken model.<br />
* 219227: Slowness in model creation when read data from datasource - event cost calculation improvements.<br />
* 219250: Slowness in event creation when read data from datasource - group by event sorting.<br />
* 219292: Performance issue in /api/uielements as it unnecessarily fetched dashboard contents.<br />
* 219295: Client side fix for 219292.<br />
* 219269: Query results were handled incorrectly in the client side - datatype is cell specific, not column specific.<br />
<br />
== Additional QPR ProcessAnalyzer 2019.9 (release date 2019-12-18) == <br />
Build number: 2019.9.0.40754, Model compatibility version: 2, Database version: 63, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307785: Angular Migration: Migrate ProcessAnalyserService.<br />
* 307786: Angular Migration: Migrate FieldPropertiesUtils.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219262: Login to PA UI is not possible when there is + character in the password<br />
* 219263: Opening dashboard which definition is large<br />
* 219257: It should be possible to get DataFrame cell value by column name in expression analysis<br />
<br />
== QPR ProcessAnalyzer 2019.9 (release date 2019-12-10) == <br />
Build number: 2019.9.0.40704, Model compatibility version: 2, Database version: 63, PACM file version: 7, Protocol version: 32.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307484: Implemented Excel client protocol version for improved compatibility for older Excel Clients.<br />
* 307564: [[Web.config_file_in_QPR_ProcessAnalyzer|Case sampling]] is disabled by default.<br />
* 307724: There is a support for self-signed certificate for QPR ProcessAnalyzer service.<br />
* 307705: User related information and session id is available for HTML presentation objects.<br />
* 307712: Error messages from the backend are shown in UI<br />
* 307750: PA UI Frontend (part 3)<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219170: Conformance checking didn't work when there is a non-existing bpmn task between parallel gateway and the end event.<br />
* 219152: Loading model into memory doesn't anymore require a ResetModelCache permission.<br />
* 219213: Improved model loading performance when using ODBC, datatable and expression datasources.<br />
* 219218: Order of the comparison rules incorrectly affected the influence analysis results.<br />
* 219240: Import model or export model from filter gave "Input string was not in a correct format" error.<br />
* 219238: Fix for error message "CommunicationException: The remote host closed the connection".<br />
* 219249: Access was incorrectly denied for non system admins when saving a new dashboard.<br />
<br />
== QPR ProcessAnalyzer 2019.8 (release date 2019-10-30) == <br />
Build number: 2019.8.0.40391, Model compatibility version: 2, Database version: 62, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307633: [[QPR_ProcessAnalyzer_Model_Datasources#Loading_Data_from_Datatables|Datatables]] can be used as a PA model datasource (part 1).<br />
* 307700: JSON filter rules should not give error for non-existing values, such as event type names.<br />
* 307721: Improvements to model [[QPR_ProcessAnalyzer_Model_JSON_Settings#Automatic_Loading_on_Server_Startup|Improvements to model LoadOnStartup]]: loading is done in a separate thread and in parallel.<br />
* 307693: [[QPR_ProcessAnalyzer_Objects_in_Expression_Language|Expression language: Return attributes in alphabetical order]].<br />
* 307738: Expression language: [[QPR_ProcessAnalyzer_Expressions#Null_conditional_operator_.28.3F._and_.3F:.29 | null-conditional]] and [[QPR_ProcessAnalyzer_Expressions#Null_coalescing_operator_.28.3F.3F.29 | null-coalescing operators]]. <br />
* 307725: Expression language: AsParallel function for making calculations in parallel to improve performance.<br />
* 307715: New PA Web UI Backend (part 3).<br />
* 307728: New PA Web UI Backend (part 4).<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219210: ScriptLaucher CSV export should quote string values with double quotes when the string value contains semicolon.<br />
* 219143: IIS https only setup does not work.<br />
* 219186: Event.IndexInCase had issue with event type filters.<br />
* 219167: Event.OutgoingFlowOccurrence and Event.IncomingFlowOccurrence had issues with event type filters.<br />
* 218689: _.Cases and _.Events doesn't work as a root in EventLog context in KPI Analysis.<br />
* 219004: PA license expiration causes unclear error in UI.<br />
* 219187: KeyNotFound exception occurred when include only all cases from the Path Analysis.<br />
* 219197: Minor issues in ODBC datasource.<br />
* 219207: Flowchart influence analysis does not work properly when using both Filter and Comparison parameters.<br />
<br />
== QPR ProcessAnalyzer 2019.7 (release date 2019-09-25) == <br />
Build number: 2019.7.0.40226, Model compatibility version: 2, Database version: 61, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307655: Drop support for SQL core as PA data source (Part 5 Memory optimization).<br />
* 307696: New PA Web UI Backend.<br />
* 307710: New PA Web UI Backend (part 2).<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219164: Event.NextInCase/PreviousInCase didn't work with event type filters.<br />
* 219136: ODBC model not support import and remove functionality.<br />
* 219171: Event.NextInCase and Event.PreviousInCase requires CaseEvents preprocessing.<br />
* 219173: Out of memory error and application pool crashing in customer environment.<br />
<br />
== QPR ProcessAnalyzer 2019.6 (release date 2019-08-08) == <br />
Build number: 2019.6.0.40009, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307260: Update to Visual Studio 2017 and update to .Net 4.7.1.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer:'''<br />
* 219106: Datetime ticks property in the expression language should be in UTC.<br />
<br />
== QPR ProcessAnalyzer 2019.5 (release date 2019-06-19) == <br />
Build number: 2019.5.0.39902, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307330: Filtering renewal: PAPO.<br />
* 307638: Angular Migration: Migrate Analysis classes part 3.<br />
* 307653: Angular Migration: Migrate Analysis classes part 4.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307649: Drop support for SQL core as PA data source (Part 4 Source code removal).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 219040: Clustering analysis expression doesn't take into account model without any case attributes.<br />
* 219001: Case Analysis always limited to 1000 rows (other analyses have the same problem).<br />
* 219042: PAPO: "Influence Analysis for Case Attributes", value is rounded to closest integer.<br />
* 218944: PAPO: Recycle bin icon in filter rule name is not visible when there is long text without spaces.<br />
* 219041: When duration limit 0, filters made from duration beams don't work.<br />
* 219099: Datetimes in expression language query don't show fraction of seconds (QPR UI).<br />
* 219103: PAPO: context menu is not working in KPI analysis.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 219062: GetModels is slow for admin.<br />
* 218978: Odd 1 million filter is adapted once you remove your custom filter.<br />
* 219015: Script Launcher million rows limit when exporting to excel csv.<br />
* 219022: GetModelAsStream webservice not support modelId.<br />
* 219080: JSON filtering does not work with flowchart analysis.<br />
* 219087: Increase from 1GB to 2GB limit in PA webservice.<br />
* 219032: PAPO Variation Analysis is not drawn.<br />
* 219017: Datetimes in expression language query don't show fraction of seconds (PA CORE).<br />
<br />
== Additional Release for QPR ProcessAnalyzer 2019.4 (release date 2019-05-31) ==<br />
Build number: 2019.4.0.39800, Model compatibility version: 2, Database version: 59, PACM file version: 7.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 219078: PAPO loses saved filter when changing analysis<br />
* 219000: User with only Analyzer role can see and use private filter created by Administrator.<br />
* 219049: Copy of a model with odbc datasource doesn't have filters from the original model.<br />
* 219044: Calculated case attributes don't work with odbc model without defined cases.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307611: Drop support of PAIK.<br />
* 307636: Drop PA Excel client support for Excel 2010, Windows 7 and Windows 8.1.<br />
* 307628: Drop support for SQL core as PA data source (Part 3 Source code removal).<br />
<br />
== QPR ProcessAnalyzer 2019.4 (release date 2019-05-07) == <br />
Build number: 2019.4.0.39420, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* Custom dashboards for QPR ProcessAnalyzer can be browsed and edited more easily, as there is a Dashboards menu item available.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307419: Change the database connection type to use in-memory core (PA Core).<br />
* 307324: Drop support for SQL core as PA data source (Part 1: Export from EventLog).<br />
* 307619: Drop support for SQL core as PA data source (Part 2: Remove analysis 26, 27 and 28).<br />
* 307523: Refactor ModelInformation code in PA Core.<br />
* 307613: Quick & Easy memory usage optimizations: PA Core.<br />
* 307618: Prediction capability to expression language.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218909: Data grid based analysis jumping.<br />
* 218971: PAPO Variation analysis has both paths and counts at the same time.<br />
* 218972: PAPO Duration analysis missing the grouped by dimension (default value is not set in analysis). <br />
* 218969: Event attribute "Cost" doesn't work in Profiling Events analysis and in Expression language.<br />
* 219006: Case id's (case names) are interpreted as numbers by PAPO.<br />
* 219027: Numerical attributes are shown as zero decimals in some analysis in data grid presentations.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218938: Filter rules information is not showing names for odbc loaded models and calculated case/event attributes.<br />
* 218945: PA UI Profiling and Event type analysis with selections costs are lost.<br />
* 218976: Inconsistency in pre-processing CaseEvents results.<br />
* 219012: Pre-loaded models give null reference exception.<br />
* 219008: Key is not in dictionary is thrown when selecting benchmark case attribute.<br />
* 219034: Model calculation context for expression data source is not initialized correctly.<br />
* 218920: Private filters are visible for other users (which is fine for admins but not for other user types).<br />
<br />
== QPR ProcessAnalyzer 2019.3 (release date 2019-03-27) == <br />
Build number: 2019.3.0.38860, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* It's possible to add [[Calculated_Attributes_in_QPR_ProcessAnalyzer|calculated case and event attributes]] to QPR ProcessAnalyzer models using the expression language. Calculated attributes are created when the model is loaded into memory, and they are available in the analyses like the normal imported attributes. Calculated attributes allow e.g. data conversions and cleansing, and also making calculations beforehand to improve performance.<br />
* QPR ProcessAnalyzer has a new [[Clustering Analysis]], which divides cases into similar groups based in case attributes and occurred types of events. Clustering analysis provides a new way to understand and structure your process mining data.<br />
* In the expression language, the left out rows can be [[QPR_ProcessAnalyzer_Expression_Analysis#Expression_Analysis_JSON_Configuration|aggregated as the last row]], which is useful, e.g. when you want to present only the most important data but still see the total amount of cases in the model. Also ChartView contains a new setting Group and Show Others using this expression language feature.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307507: Disable rectangular selection in flowchart.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307545: KPI: Clustering analysis and related utility functions.<br />
* 307512: Expression language: Description attribute to Model.<br />
* 306900: Calculated case and event attributes.<br />
* 307533: Level of event log pre-processing can be set for [[QPR_ProcessAnalyzer_Expression_Analysis#KPI_Analysis_JSON_Configuration |expression analysis]].<br />
* 307575: [[Web.config_file_in_QPR_ProcessAnalyzer#Qpr.ProcessAnalyzer.Common.Properties.Settings_Section |Change items memory caching times]].<br />
* Support for Windows 8 has been dropped. Windows 8.1 is still supported.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218863: Model manager not updated after changing Filter Id.<br />
* 218874: Sorting and filtering icons overlap in datagrid.<br />
* 218922: There should be default maximum number of items for different analyses created from tool palette.<br />
* 218723: Empty analysis window after error thrown by PA service.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218908: Wrong Client data in operation log.<br />
* 218928: Expression filter doesn't work with integers.<br />
* 218940: Model eventlog can drop from memory.<br />
* 218927: JSON filtering for case attributes doesn't work with nulls.<br />
* 218779: Source data formatted to two decimals accuracy but PA total cost flowchart show much more decimals.<br />
* 218943: ODBC SQL boolean values does not work with filter CaseAttributeValue.<br />
* 218965: Accessing calculated event attribute value from EventType.Events -property does not work.<br />
<br />
== QPR ProcessAnalyzer 2019.2 (release date 2019-02-14) ==<br />
Build number: 2019.2.0.38539, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* Support for [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Excel_Client| Microsoft Office 2019]] for QPR ProcessAnalyzer Excel Client.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307423: Improved memory management: unused objects are automatically dropped from the memory. Settings can be configured in [[Web.config_file_in_QPR_ProcessAnalyzer#Qpr.ProcessAnalyzer.Common.Properties.Settings_Section | web.config]] or from the [[QPR_ProcessAnalyzer_Model_JSON_Settings#Memory_Usage_Settings | model JSON settings]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218838: KPI analysis: Event Occurrence Time isn't calculated properly, e.g. Period=Month fails.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218880: PAPO: odbc case and event attributes are not shown in dropdown menu.<br />
* 218877: Support material - Project admins are not able to create new users.<br />
* 218898: Importing XES file with xmlns -definition fails.<br />
* 218893: Model status shows incorrectly "offline" when Model event log is in memory and Model information not.<br />
* 218917: BaseContext.EvaluateChildExpression with given root object iterates the root object if it is an array.<br />
<br />
== Additional Release for QPR ProcessAnalyzer 2019.1 (release date 2019-01-23) ==<br />
Build number: 2019.1.0.38400, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
<br />
* 307357: PA model management: Analysis requests canceling. All operations have new parameters QueryIdentifier and CancelEarlierQueriesWithIdentifier.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218806: Variation filter doesn't filter correctly.<br />
* 218802: It should not be able to load deleted models into memory.<br />
* 218866: Case Analysis shows "0" for textual Case Attribute (SelectedActivityCounts=0 column count and data not match).<br />
* 218862: Case Analysis returns incorrect Start and End times when start or end transition is selected.<br />
* 218847: Variation Analysis Include Only Cases Filter Fails when using Event Counts and filter.<br />
* 218765: Event Occurrence Time calculation for KPI analysis (Server side).<br />
<br />
== QPR ProcessAnalyzer 2019.1 (release date 2019-01-03) ==<br />
Build number: 2019.1.0.38310, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* There are new training videos available for QPR ProcessAnalyzer in QPR Community. QPR ProcessAnalyzer users can access the videos by clicking Training Videos in the header menu of QPR ProcessAnalyzer UI.<br />
* ChartView can show several measures at the same time. In table, measures are in different columns, and in chart, measures are presented as different series.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer UI:'''<br />
* 218768: Number of decimals is not updated in KPI analysis due to HistoryId context variable.<br />
* 218787: Datagrid export fails with numerical values.<br />
* 218757: KPI analysis - null value shown as NaN.0 in table.<br />
* 218794: Popup menu is replicated when PAPO is drawn multiple times.<br />
* 218740: Case Analysis Year period should not show thousand separator.<br />
* 218805: Analysis not shown after adding duration analysis to panel using view designer "shortcuts buttons".<br />
* 218804: PAPO showing only Analysis Window doesn't show anything when other PAPO hides the Analysis window.<br />
* 218815: Flowchart influence analysis does not always show the results in an identical way.<br />
* 218791: Flowcharts visibility stepper don't work in PA deployment package Process benchmarking view.<br />
* 218844: KPI Analysis sorting is not saved to the context variable.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218755: If user selects Influence Analysis for Case Attributes into analysis window, it freezes the analysis window completely.<br />
* 218756: PA model - with event attributes - without case attributes = event attributes shown in profiling case attributes analysis.<br />
<br />
== QPR ProcessAnalyzer 2018.8 (release date 2018-11-29) ==<br />
Build number: 2018.8.0.38236, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights''':<br />
* New types of charts have been added to the KPI Analysis in PAPO. In addition to the previously available column chart and table presentations, there are now bar, donut, area, line and spline charts.<br />
* Tool palette contains now items for each QPR ProcessAnalyzer analysis making it easier to create dashboards with different analyses. The analyses have also needed context variables predefined so that settings are saved to the dashboard.<br />
* Duration Influence Analysis is now calculated in the memory which makes it significantly faster than previously when it was calculated in the SQL Server.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307398: More chart types to KPI analysis, such as line chart, bar chart and donut chart.<br />
* 307473: PAPO tables exporting to Excel, Word and PDF<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307417: Duration Influence Analysis in In-Memory.<br />
* 307458: Performance improvement in reusing event logs.<br />
* 307456: Expression language plugin mechanism.<br />
* 307459: [[QPR_ProcessAnalyzer_Web_Service_API#Functions_in_the_Web_Service_API|PA service support for script generated reports as csv file (for QPR UI Script Manager)]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218711: PAPO duration analysis is failing.<br />
* 218663: PAPO - KPI Analysis - Number of decimals effects column height.<br />
* 218664: PAPO - KPI Analysis - Default number of decimals in the drop-down list should be 1.<br />
* 218669: PAPO - KPI Analysis duration from - to.<br />
* 218557: PAPO - Duplicate flows when increasing the flow amounts in flowchart.<br />
* 218718: PAPO - Flowchart sometimes shows portions of the flowchart completely unconnected from start/end nodes of the flowchart.<br />
* 218668: PAPO - KPI Analysis - wrong names in droplist and wrong chart title.<br />
* 218666: PAPO - KPI Analysis - CamelCase column headers.<br />
* 218670: PAPO - KPI Analysis - title Duration between "undefined" and "undefined". <br />
* 218665: PAPO - KPI Analysis - numerical data should be shown linear on X axis.<br />
* 218629: PAPO - KPI Analysis - Year period should not show thousand separator.<br />
* 218667: PAPO - KPI Analysis - units are missing in table.<br />
* 218725: PAPO - KPI Analysis - NumberOfDecimals should be enabled for numerical case&event attribute.<br />
* 218731: PAPO - layout issue when displaying error message.<br />
* 218747: PAPO - KPI analysis - Column header text is not consistent with x-axis label.<br />
* 218762: PAPO - KPI Analysis - Error message doesn't disappear when switching from wrong selections to correct ones.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218727: Null values don't work in GroupBy/GroupByValue functions.<br />
* 218708: Filtering with duration value 0 does not work in duration analysis.<br />
* 218770: Case analysis with variation Id -> Exception: The given key was not present in the dictionary.<br />
* 218771: Conformance: Parallel gateways having multiple branches with only one node aren't analyzed correctly.<br />
<br />
== QPR ProcessAnalyzer 2018.7 (release date 2018-10-10) ==<br />
Build number: 2018.7.0.38036, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307319: Expression language: [[Generic_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#Other_functions | GroupBy and GroupByValue -functions]].<br />
* 307370: PAPO/A1 cell case/event/event type/variation count should only show cases user has permissions in case level security.<br />
* 307369: String handling functions in the expression language.<br />
* 307424: KPI analysis in generic context.<br />
* 307439: Quick & easy expression language improvements.<br />
* 307336: PA performance improvement (part 1).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218673: Null values in PA expression language should appear as nulls in datasets.<br />
* 218693: Performance for PAPO's data grids has been optimized.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218453: .TMP files is not deleted always. After 65k .TMP files exist then PA service stop working. If issue is encountered, workaround is to manually delete .TMP files (e.g. files are located in folder C:\Windows\Temp or C:\Users\<pa_applicationpool_user>\AppData\Local\Temp).<br />
* 218643: InMemory: Open model after pacm file import fails to "Object reference not set to an instance of an object.".<br />
* 218652: Access denied. Unexpected ModelEventLog dropping object with from cache.<br />
* 218648: Import empty model with filter crash (evevenlog.Content is null).<br />
* 218685: XES import runs out of memory when importing BPIC2018 -model.<br />
* 218690: Expressions returning boolean values should be returned to QPR UI as booleans.<br />
* 218687: Average and Sum functions should return null for zero length arrays instead of zero.<br />
* 218705: InMemoryCore: TotalCost in event analysis has incorrect values.<br />
* 218704: Mismatch in case counts in Variation Analysis when event type filter has been applied.<br />
* 218709: FileType parameter not select correct stream compression mode in ImportFromStream.<br />
* 218698: The given key was not present in the dictionary - Variation Analysis error.<br />
* 218710: PAPO case analysis is currently failing.<br />
<br />
== QPR ProcessAnalyzer 2018.6 (release date 2018-08-29) ==<br />
Build number: 2018.6.0.37869, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights'''<br />
* KPI Analysis update: The KPI Analysis feature has new updates to it. The Analysis Menu design has new options that allow for efficient creation of KPI analysis presentations. Menu items have been grouped into sub-groups making finding analysis options much swifter. <br />
* Model load on startup: You can now define which models are loaded onto memory on startup allowing for quicker setup of QPR ProcessAnalyzer servers. This loads the key models needed directly into memory without any separate in-memory loading.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307351: KPI analysis UI - part 2<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307323: [[PA Migration to 2018.6 |Remove old PA web client]].<br />
* 307200: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Necessary_IIS_setup |PA model management: PA model automatic loading on startup]]. <br />
* 307350: KPI analysis UI - part 2 (server side).<br />
* 307208: PA model management: PA model status information to expression language.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218391: PA UI Flowchart selection does not clear automatically.<br />
* 218606: Edit mode is ON > Floating Action Buttons are not clickable.<br />
* 218626: PAPO: some popup menus are not closed properly in IE 11.<br />
* 218607: PAPO: popup menu is not displayed in IE 11.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218597: PA Exception details show null in QPR UI.<br />
* 218575: Incorrect results in conformance analysis calculation. <br />
* 218540: KPI analysis not working properly.<br />
* 218314: Variation analysis shows duplicate variations if there are excluded event types.<br />
* 218604: PA Excel client does not log enough during connection creation.<br />
* 218624: Estimatedmemory not calculated correctly when model not have events.<br />
* 218396: KPI analysis - ApplyAnalysisFilters. InvalidOperationException: Sequence contains no elements.´<br />
* 218628: PAPO: Error popup appears, "Error processing QPR ProcessAnalyzer request.<br />
* 218631: Performance improvements (Path analysis was slow).<br />
* 218485: ProcessAnalyzer Excel client cannot be removed from Programs and Features, as it wont show up there.<br />
* 217775: GetAnalysis(18) should write a progress log entry after each chunk.<br />
* 217653: SQL command not in log when ODBC connection failed.<br />
<br />
== QPR ProcessAnalyzer 2018.5 (release date 2018-07-17) ==<br />
Build number: 2018.5.0.37716, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights'''<br />
*QPR ProcessAnalyzer Deployment Package for QPR UI: The new version comes with preloaded QPR UI views that can instantly kickstart your Process Mining experience. These views are readymade and require no extra configuration. These views introduce new functionalities, such as ready made conformance views, for deploying a more varied Process Mining offering. <br />
*New Dashboard Design features: Panels can be now instantly developed and evaluated in viewer mode, allowing for a more powerful dashboard creation. The object placing logic has been overhauled, allowing for new options in creating dashboards. <br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307338: [[QPR_ProcessAnalyzer_API:_ResetModelCache | Web service support to load and drop PA models]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218536: PAPO: KPI Analysis should not be available from Control Windows.<br />
* 218519: The numerical values in QPR ProcessAnalyzer Influence Analysis were aligned to the left.<br />
* 217888: Selection lost from influence analysis table when user slightly adjusts browser window or panel/presentation object window size.<br />
* 218465: PAPO: Newly created filters are not displayed in the list.<br />
* 218556: PAPO: An unnecessary vertical scrollbar was shown after PAPO Case Analysis was resized.<br />
* 218520: PAPO: Filter does not recognize decimal separators.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218537: ODBC xlsx loading failed with data format issue.<br />
* 218495: Changing default filter does not drop cached model information.<br />
* 218550: Accessing projects from expression language fails in some cases.<br />
* 218549: Datatable import from Excel sheet data corruption if first column value is empty.<br />
* 218558: Errors in default.aspx. Login fails.<br />
<br />
== QPR ProcessAnalyzer 2018.4 (release date 2018-06-11) ==<br />
Build number: 2018.4.0.37669, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ODBC driver support for QPR ProcessAnalyzer: Use external data sources to create a dynamic model that is updated every time the model is loaded. Using the ODBC driver, the model data can be accessed from a separate data source. All the event data information can be defined in JSON format allowing for automatic model creation.<br />
* KPI Analysis: A new analysis is added to QPR ProcessAnalyzer. KPI Analysis utilizes the KPI expression engine for creating visualizations of data. KPI Analysis is a fully fledged analysis that can be used in conjuction with the existing QPR ProcessAnalyzer analysis for more focused results. In addition, KPI Analysis is available as a separate QPR UI view for creation of dashboards that present real-time data taken from QPR ProcessAnalyzer.<br />
* Tabular Analysis results updated with data types: Analysis featuring tabulated data are now automatically updated with correct data types. Automatic data types allow for exporting the data in a format that can be used in other compatible tools as the data types are automatically defined into the data.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307265: KPI analysis UI - part 1 (KPI).<br />
* 307278: The tabular analyses (e.g. Case analysis) in QPR ProcessAnalyzer UI now have the correct column data types based on the information from the QPR ProcessAnalyzer server.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307204: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Model Datasources|Load PA model from ODBC datasource]].<br />
* 307313: Expression language improvements - part 7 (performance).<br />
* 307317: Update new [[QPR_End_User_Software_License_Agreement|EULA]] to QPR ProcessAnalyzer.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218487: Influence analysis for Flowchart changes the flowchart settings.<br />
* 218498: No history entry is created while changing visibility threshold via stepper or context variable.<br />
* 218508: PAPO variation analysis should limit the queried number of variations.<br />
* 218513: PAPO settings buttons cover analysis content.<br />
* 218532: PAPO: Profiling analysis does not work with data loaded via ODBC.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218515: IIS crashes in kernel during Odbc query reading csv/xlsx file with Microsoft Access Text Driver and Microsoft Excel Driver.<br />
* 218484: ImportEvents fails in StartBackground mode.<br />
* 218525: InMemory CaseAnalysis ShowAllCases not work if there is cases without events.<br />
* 218463: Issue to install excel client (part 2).<br />
<br />
== QPR ProcessAnalyzer 2018.3 (release date 2018-04-23) ==<br />
Build number: 2018.3.0.37545, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
*Conformance Checking is supported in QPR ProcessAnalyzer. Using the KPI Expression Language as a basis, process mining models can be compared to BPMN notation and analyzed if the process data conforms to the BPMN design. These results are implemented in ChartView and KPI Expression Language allows them to be implemented into dashboards.<br />
*BPMN Editor has been added to ChartView. You can now import and design BPMN process maps for use in conformance analysis. The BPMN editor is a web component that is used in the browser, allowing for quick and easy process design. The designs can also be exported for further use.<br />
*Flowchart Visibility Settings have been overhauled with a new visual presentation. New stepper elements allow for more flexible flow threshold settings while maintaining a user-friendly approach.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307276: Remove PAPO Offline mode.<br />
* 307193 & 307298: The [[Flowchart_Analysis#Visibility_Settings|Flowchart Visibility Settings]] were improved.<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307077: [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Server | Support for Windows Server 2016 (PA Service)]].<br />
* 307246: Expression function to calculate conformance to BPMN.<br />
* 307297: Expression language improvements - part 6.<br />
* 307301: In-memory memory usage optimizations.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218306: PAPO control window is affected by analysis window's 'Show as' setting.<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218241: PA Duration Analysis In-Memory - numbers for Events and Cases too high (focus flow).<br />
* 218456: Issue to install excel client (part 1).<br />
<br />
== QPR ProcessAnalyzer 2018.2 (release date 2018-03-12) ==<br />
Build number: 2018.2.0.37453, Model compatibility version: 2, Database version: 58, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* Case Permissions have been added to the data security featureset. Case Permissions allow for limiting model visibility based on rules that reference the case attributes of a set model. Case permissions can refer to usernames or user groups, creating a link between the attributes and groups.<br />
* Influence Analysis for Case Attributes has been simplified. The feature presents basic information relating to the root causes when it is opened. If further information is needed, this can be accessed via the feature menu. <br />
* DataGrids support Excel exporting. You are now able to export data from fixed dashboards featuring datagrids. With this feature, you can take your data for further manipulation using Microsoft Excel.<br />
* Chartview has been improved with a new layout and excel exporting. The new layout allows for quicker access to creating charts using the ChartView tool. With the exporting functionality, the views created are exported for use in presentations in Microsoft Excel.<br />
* KPI Expression Language has been added with support for Influence Analysis for Case Attributes. This allows for further creation of dashboards with specific analysis result queries. Using the KPI expression language, dashboards can be made to present up-to-date data based on influence analysis results.<br />
* Dataset tag support for data visualization. Adding dataset tags will help in creating more dynamic chart presentations as the data can be inserted into the JSON settings of charts and datagrids. <br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307220: The Influence Analysis for Case Attributes settings now has a toggle for showing and hiding the detail columns.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307273: [[QPR ProcessAnalyzer Web Service API#Example| PA model JSON settings]].<br />
* 307269: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Case_Permissions |Case permissions]].<br />
* 307261: PA InMemory core, part 8 (Path Analysis).<br />
* 307282: PA KPI's and expressions (part 5).<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218426: Using PAPO with customers model crashes PA Server (Entice Changes).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218371: Event types aren't provided to PAPO by PA server.<br />
* 218372: Having multiple expressions in one selection item in a JSON filter does not work.<br />
* 218375: Empty comparison -setting with nonempty filter -setting causes influence analysis to return incorrect results.<br />
* 218380: PA Activation ends one day before the actual end date.<br />
* 218362: WebService GetAnalysisAsImage does not work.<br />
* 218389, 218397: Performance issues in PA in-memory core with multiple simultaneous users.<br />
* 218412: PercentageNumber property is not set properly in PA analyses.<br />
* 218410: Event attribute profiling event amount mismatch.<br />
* 218404: Using PAPO with customers model crashes PA Server (PA changes).<br />
* 218430: Pre-release mandatory PA bugfixes.<br />
<br />
== QPR ProcessAnalyzer 2018.1 (release date 2018-01-31) ==<br />
Build number: 2018.1.0.37330, Model compatibility version: 2, Database version: 57, PACM file version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ChartView is introduced as a new QPR UI view. This interactive view allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. ChartView comes preloaded with numerous different presentation features for the creation of customized charts fit for any business need.<br />
* New Table Filtering for Data Table Views. A new Excel-style filtering feature has been added to the different analysis features, such as Influence Analysis for Case Attributes and Event Analysis. The feature allows the presentation and comparison of different data using robust filters.<br />
* The QPR UI version of QPR ProcessAnalyzer has an overhauled popup menu. Selecting different analysis and creating new filters is quicker and new icons have been added for added clarity.<br />
* XES filetype importing support. The IEEE TaskForce standardized XES logs are now supported by QPR ProcessAnalyzer. This filetype aims to unify the transactional data produced by information systems and makes them usable in tools used in data analysis. <br />
<br />
'''Full Features for QPR ProcessAnalyzer UI:'''<br />
* 307244: The various tables (e.g. Case Analysis) in QPR ProcessAnalyzer UI received filtering functionality familiar to the one in Microsoft Excel.<br />
* 307163: Popup menu improvements.<br />
* 307224: Cache model information into browser side.<br />
<br />
'''Features for QPR ProcessAnalyzer:'''<br />
* 307271: PA InMemory core, part 7 (Canceling analysis).<br />
* 307247: XES Event log file format support.<br />
* 307257, 307270: PA KPI's and expressions (part 3, 4).<br />
* 307211: Enable custom data sources: Selections as JSON.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218327: PAPO Grid view row selection issues when opening popup menu.<br />
* 218328: PAPO Missing null check in ModelState.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218324: Fixed an issue where a dataset wasn't refreshed when a context variable was changed from PAPO.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer:'''<br />
* 218288: PA service installation with DeployPAService.ps1.<br />
* 218291: Problem with --#GetAnalysis type 31 (filter rules).<br />
* 218315: PAPO: InMemoryCore: Offline mode shows incorrect case attribute values.<br />
* 217922: Filtering Flow Table with Case Attribute is too slow.<br />
* 218321: PA core - Internal server error in PAPO when duration analysis result is empty.<br />
* 218322: Flow analysis results not always in same order (InMemory).<br />
* 218340: Not allow to delete default filter ("No access/Access denied").<br />
* 218345: Unknown filter rule. The given key was not present in the dictionary.<br />
* 218363: Attribute values are sent to clients as strings from InMemory profiling analysis.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218379: PAPO: Side panels visible in multi papo even if they should be closed and invisible.<br />
<br />
== Old Releases ==<br />
See older releases in [[QPR ProcessAnalyzer Release Archive]]<br />
__NOTOC__</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=DataFrame_in_Expression_Language&diff=15177DataFrame in Expression Language2020-01-21T08:41:20Z<p>TeeLeht: </p>
<hr />
<div>DataFrame represents a two dimensional array of data with one-to-many columns and zero-to-many rows, like a relational database table, an Excel sheet or a CSV data file. Each column in the DataFrame has a name, and there must not be more than one column with the same name. DataFrame is the generic data structure used to manage all kinds data in QPR ProcessAnalyzer expression engine that run in-memory. DataFrames as linked to other entities in QPR ProcessAnalyzer as follows:<br />
* Datatable contents is fetched into the memory as a DataFrame object<br />
* DataFrame can be stored (persisted) to a Datatable<br />
* ETL operations, such as joining, unions, filtering and grouping are based on the DataFrames<br />
* Data extracted from an external data source, e.g. using ODBC, is fetched to the in-memory calculation as a DataFrame.<br />
* When using a [[QPR_ProcessAnalyzer_Model_Datasources#Loading Data using Loading Script|loading scripts]], cases and events data is fed to the model using the DataFrame.<br />
<br />
== DataFrame Properties ==<br />
<br />
{| class="wikitable"<br />
!'''DataFrame properties'''<br />
! '''Description'''<br />
|-<br />
||Columns (String*)<br />
||DataFrame columns names as an array in the order the columns are in the DataFrame.<br />
|-<br />
||Rows (Object**)<br />
||Returns the data content of the DataFrame as a two-dimensional array (matrix). The column names are not part of the data content.<br />
<br />
Examples:<br />
<pre><br />
DatatableById(5).DataFrame.Rows[0][0]<br />
Returns: the value in the first row and first column in a datatable with id 5.<br />
</pre><br />
|-<br />
||<column name> (Object*)<br />
||<br />
Returns an array of values of given column in the datatable. If the column name contains spaces, the Column function needs to be used to refer to a column.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).right<br />
Returns: [zero, two, three]<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).right[2]<br />
Returns: three<br />
</pre><br />
|-<br />
|}<br />
<br />
== DataFrame Functions ==<br />
<br />
{| class="wikitable"<br />
!'''DataFrame&nbsp;functions'''<br />
! '''Parameters'''<br />
! '''Description'''<br />
|-<br />
||Append (DataFrame)<br />
||<br />
* DataFrame which data to append <br />
||<br />
Creates a new DataFrame that has the contents of given DataFrame added to the end of this DataFrame. When the data is combined, the order of columns matters, not the names of the columns. The resulting DataFrame gets column names from this DataFrame.<br />
<br />
If the number of columns is different between this DataFrame and the other DataFrame, an exception is thrown.<br />
<br />
Examples:<br />
<pre><br />
Let("dataframe1", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]));<br />
Let("dataframe2", ToDataFrame([[1, "one"], [4, "four"]], ["id", "text"]));<br />
dataframe1.Append(dataframe2);<br />
<br />
Returns:<br />
id;text<br />
0;zero<br />
2;two<br />
3;three<br />
1;one<br />
4;four<br />
</pre><br />
|-<br />
||ColumnIndexes (Integer*)<br />
||<br />
* Column names (String*)<br />
||<br />
Convert DataFrame column names into column indexes. The indexes are starting from zero. If a column is not found, an exception is given.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ColumnIndexes(["right", "id"])<br />
Returns: [1, 0]<br />
</pre><br />
|-<br />
||Column (Object*)<br />
||<br />
* Column name<br />
||<br />
Returns an array of values of given column in the order rows are in the datatable.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Column("right")<br />
Returns: [zero, two, three]<br />
</pre><br />
|-<br />
||Columns (DataFrame)<br />
||<br />
* Array of column names<br />
||<br />
Creates a new DataFrame having only the defined columns of the original DataFrame. Note that Columns function is different than Columns property (difference is that the function has parameters).<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Columns(["right"]).ToCsv()<br />
Returns:<br />
right<br />
zero<br />
two<br />
three<br />
<br />
</pre><br />
|-<br />
||Head (DataFrame)<br />
||<br />
* Number of rows<br />
||<br />
Creates a new DataFrame that only contains top number of rows of this DataFrame. If the DataFrame has less than n rows, all its rows are returned.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Head(2).ToCsv()<br />
Results string:<br />
id;right<br />
0;zero<br />
2;two<br />
</pre><br />
|-<br />
||Join (DataFrame)<br />
||<br />
# Other DataFrame<br />
# Columns to join<br />
# join type<br />
||<br />
See [[#Joining_DataFrames|Joining DataFrames]].<br />
<br />
|-<br />
||GroupBy (DataFrame)<br />
||<br />
# Array of columns to group<br />
# Array of grouping expressions<br />
||<br />
Creates a new DataFrame based on the current DataFrame. The resulting DataFrame has rows grouped by given columns and values aggregated using given functions. In the resulting DataFrame one row in the end result corresponds with one group.<br />
<br />
Parameters:<br />
# '''Columns''': Columns to group identified by column names.<br />
# '''Aggregation expressions''': Array containing the column name as a key and the aggregation expression as a value.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [0, "zero2"], [2, "two"], [2, "two"], [2, "two3"], [3, "three"]], ["id", "text"]).GroupBy(["id"],<br />
[<br />
"ids": Def("", Sum(id)),<br />
"texts": Def("", StringJoin(",", text)),<br />
"constant": 123<br />
]).ToCsv()<br />
Returns:<br />
ids;texts;constant<br />
0;zero,zero2;123<br />
6;two,two,two3;123<br />
3;three;123<br />
<br />
ToDataFrame([[0, "zero"], [0, "zero2"], [2, "two"], [2, "two"], [2, "two3"], [3, "three"]], ["id", "text"]).GroupBy(["id", "text"],<br />
[<br />
"ids": Def("", Sum(id)),<br />
"texts": Def("", StringJoin(",", text)),<br />
"constant": 123<br />
]).ToCsv()<br />
Returns:<br />
ids;texts;constant<br />
0;zero;123<br />
0;zero2;123<br />
4;two,two;123<br />
2;two3;123<br />
3;three;123<br />
<br />
Analysis("OperationLog")<br />
.GroupBy(<br />
["User Name"],<br />
[<br />
"User Name": Def("", Column("User Name")[0]),<br />
"Count": Def("Rows", CountTop(Rows)),<br />
"Avg. Duration": Def("", Average(Duration)),<br />
"Max. Duration": Def("", Max(Duration))<br />
]<br />
).ToCsv()<br />
<br />
Returns (similar to this):<br />
User Name;Count;Avg. Duration;Max. Duration<br />
;207;0.617434782608696;20.556<br />
Administrator;665;16.3750631578947;4225.497<br />
qpr;128;2.158765625;20.346<br />
</pre><br />
|-<br />
||Merge (DataFrame)<br />
||<br />
||<br />
See [[#Merging_DataFrames|Merging DataFrames]].<br />
|-<br />
||OrderBy (DataFrame)<br />
||<br />
* ordering expression<br />
||<br />
Creates a new DataFrame having rows ordered in an ascending order using the given expression evaluated on each row.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).OrderBy(text).ToCsv()<br />
Returns:<br />
id;right<br />
3;three<br />
2;two<br />
0;zero<br />
<br />
Analysis("OperationLog").OrderBy(Duration).Head(1)<br />
Results string:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||OrderByDescending (DataFrame)<br />
||<br />
* ordering expression<br />
||<br />
Creates a new DataFrame having rows ordered in an descending order using the given expression evaluated on each row. See OrderBy above for examples.<br />
<br />
|-<br />
||Persist (DataTable)<br />
||<br />
* DataTable name<br />
* Additional parameters<br />
||<br />
Writes a DataFrame into a DataTable in the QPR ProcessAnalyzer database. If a DataTable with that name does not exist in the project, a new DataTable is created. If a DataTable with that name already exists, the DataFrame will be stored into that DataTable. The function returns the written DataTable object.<br />
<br />
The additional parameters support:<br />
* Append: Can be used to determine whether to append (true) or overwrite (false) the existing data. Default is ''false''.<br />
* ProjectName: Name of the project under which the DataTable is to be created.<br />
* ProjectId: Id of the project under which the DataTable is to be created.<br />
<br />
Examples:<br />
<pre><br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
right.Persist("RightDataTable", ["ProjectName": "TestData"])<br />
Results: Id of the new data table named "RightDataTable" created into project named TestData (which is created if it doesn't already exist). If the table already existed, its contents will be overwritten by the new content.<br />
<br />
Let("newData", ToDataFrame([[4, "four"]], ["id", "right"]));<br />
newData.Persist("RightDataTable", ["ProjectName": "TestData", "Append": true])<br />
Results: Id of the new data table named "RightDataTable" created into project named TestData (which is created if it doesn't already exist). If the table already existed, new content will be appended into the end of the table.<br />
</pre><br />
|-<br />
||SetColumns (DataFrame)<br />
||<br />
* new/modified columns as array<br />
||<br />
Creates a new DataFrame based on the current DataFrame, where new columns have been created and/or existing columns have been modified. New and modified columns are defined using an array, where the column name is as a key and as a value there is the expression to calculate the new or modified column. When specifying a column that already exists, the column values are modified. When specifying a new column name, that column is created as a new column to the resulting DataFrame.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["both": Def("", text + "=" + id)]).ToCsv()<br />
Returns:<br />
id;text;both<br />
0;zero;zero=0<br />
2;two;two=2<br />
3;three;three=3<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["text": Def("", text + "=" + id)]).ToCsv()<br />
Returns:<br />
id;text<br />
0;zero=0<br />
2;two=2<br />
3;three=3<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["both": Def("", text + "=" + id), "both+1": Def("", both + 1), "text": Def("", "Done: " + Column("both+1")), "constant": 1234]).ToCsv()<br />
Returns:<br />
id;text;both;both+1;constant<br />
0;Done: zero=01;zero=0;zero=01;1234<br />
2;Done: two=21;two=2;two=21;1234<br />
3;Done: three=31;three=3;three=31;1234<br />
</pre><br />
|-<br />
||Tail (DataFrame)<br />
||<br />
* Number of rows<br />
||<br />
Creates a new DataFrame that has only the bottom number of rows of this DataFrame. If the DataFrame has less than n rows, all its rows are returned.<br />
<br />
Example:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Tail(2).ToCsv()<br />
Results string:<br />
id;right<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||ToCsv (String)<br />
||(none)<br />
||<br />
Converts a DataFrame into a CSV data. The CSV data has the following formatting:<br />
* Column separator: semicolon<br />
* Decimal separator in numeric fields: period<br />
* Quotation character for text fields: double quotes (used when the textual value contains semicolon, double quotes, linebreak or tabulator)<br />
* Escape character: Double quotes in textual fields are escaped with two double quotes.<br />
* Date format for date fields: yyyy-MM-dd HH:mm:ss,fff<br />
* First line: contains column headers<br />
<br />
Example:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ToCsv()<br />
Returns:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||Where (DataFrame)<br />
||<br />
* condition expression<br />
||<br />
Creates a new DataFrame having only rows for which the given condition expression returns true. The condition expression can refer to the columns of the DataFrame (see the example below).<br />
<br />
Examples:<br />
<pre><br />
Let("df", ToDataFrame([[0, "zero"], [2, "two", true], [3, "three"]], ["id", "string"]));<br />
<br />
All the following expression return the same:<br />
df.Where(id < 3);<br />
df.Where(Column("id") < 3);<br />
df.Where(_[0] < 3);<br />
<br />
Returns:<br />
id;string<br />
0;zero<br />
2;two<br />
</pre><br />
|-<br />
||Zip (DataFrame)<br />
||<br />
* DataFrame<br />
||<br />
Creates a new DataFrame that has the contents of given DataFrame appended as new columns into the end of this DataFrame. Returns a new DataFrame that has the colums from both the data frames so that the columns from the other DataFrame are appended to the end of the columns of this DataFrame. If the number of rows is different between this DataFrame and the other DataFrame, an exception is thrown. There must not be duplicate column names in the DataFrames - otherwise an exception is thrown.<br />
<br />
Examples:<br />
<pre><br />
Let("df1", ToDataFrame([[0, "zero"], [1, "one"], [4, "four"]], ["id", "text"]));<br />
Let("df2", ToDataFrame([[1, "one"], [2, "two"], [3, "three"]], ["id2", "text2"]));<br />
df1.Zip(df2).ToCsv();<br />
Returns:<br />
id;text;id2;text2<br />
0;zero;1;one<br />
1;one;2;two<br />
4;four;3;three<br />
</pre><br />
|-<br />
|}<br />
<br />
The following functions can be used to initialize DataFrame objects:<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||ToDataFrame<br />
||<br />
# matrix<br />
# column names array<br />
||<br />
Creates a DataFrame based on the given matrix (two dimensional array) and column names. Number of column names should be the same as the number of columns in the matrix.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ToCsv()<br />
Returns:<br />
A string containing:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
|}<br />
<br />
== Joining DataFrames ==<br />
Performs a [https://en.wikipedia.org/wiki/Relational_algebra#Joins_and_join-like_operators joining operation] between two DataFrames.<br />
<br />
Parameters:<br />
# '''DataFrame''': The other DataFrame to join.<br />
# '''Columns to match''': Columns which the joining is based on, can be defined as follows:<br />
#* If joining using '''one column having the same name in both DataFrames''', the column name is specified as as string.<br />
#* If joining using '''several columns having the same names in both DataFrames''', the column names are specified as a string array.<br />
#* If joining using '''columns having different names between the DataFrames''', columns are specified as an array of key-value pairs, where the key is the column name in the left side DataFrame, and value is the column name in the right side DataFrame.<br />
# '''Join type''' which can be<br />
#* '''inner''' (default): row is generated if both DataFrames have the key.<br />
#* '''leftouter''': at least one row is generated for each left side DataFrame row, even if there is no matching other row, in which case null is given as value for the other columns.<br />
<br />
Examples:<br />
<pre><br />
Let("left", ToDataFrame([[0, "zero"], [1, "one"]], ["id", "left"]));<br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
left.join(right, "id").ToCsv()<br />
Returns:<br />
id;left;right<br />
0;zero;zero<br />
<br />
Let("left", ToDataFrame([[0, "zero"], [1, "one"]], ["id", "left"]));<br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
left.join(right, "id", "leftouter").ToCsv()<br />
Returns:<br />
id;left;right<br />
0;zero;zero<br />
1;one;<br />
<br />
Let("left", ToDataFrame([[0, 0, "zerozeroleft"], [0, 1, "zeroleft"], [1, 2, "oneleft"]], ["idleft1", "idleft2", "left"]));<br />
Let("right", ToDataFrame([[0, 0, "zerozeroright"], [0, 1, "zeroright"], [2, 3, "tworight"], [3, 4, "threeright"]], ["idright1", "idright2", "right"]));<br />
left.join(right, ["idleft1": "idright1"], "inner");<br />
Returns:<br />
idleft1;idleft2;left;idright2;right<br />
0;0;zerozeroleft;0;zerozeroright<br />
0;0;zerozeroleft;1;zeroright<br />
0;1;zeroleft;0;zerozeroright<br />
0;1;zeroleft;1;zeroright<br />
<br />
Let("left", ToDataFrame([[0, 0, "zerozeroleft"], [0, 1, "zeroleft"], [1, 2, "oneleft"]], ["idleft1", "idleft2", "left"]));<br />
Let("right", ToDataFrame([[0, 0, "zerozeroright"], [0, 1, "zeroright"], [2, 3, "tworight"], [3, 4, "threeright"]], ["idright1", "idright2", "right"]));<br />
left.join(right, ["idleft1": "idright1", "idleft2": "idright2"], "inner");<br />
Returns:<br />
idleft1;idleft2;left;right<br />
0;0;zerozeroleft;zerozeroright<br />
0;1;zeroleft;zeroright<br />
</pre><br />
<br />
== Merging DataFrames ==<br />
<br />
Creates a new DataFrame that has the contents of a DataFrame (target) merged with another DataFrame (source). The merging works in the same principle as in the [https://en.wikipedia.org/wiki/Merge_(SQL) SQL language]. Note that the merging does not create new columns but the result DataFrame has the same columns as the target DataFrame. Merging has the following principle:<br />
<br />
[[File:Merge.png|650px]]<br />
<br />
Parameters:<br />
# '''Source DataFrame''': DataFrame to be merged with the target DataFrame.<br />
# '''Columns to used for matching''': Columns used to match the source and target DataFrames. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function.<br />
# '''Columns to UPDATE for matching rows''': Columns to update from the source DataFrame to the target DataFrame for the rows that match between the DataFrames. Note that the matching columns cannot be updated because they always have same values due to the matching logic. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function. Following special values can also be used:<br />
#* If the value is ''_remove'', all matching rows are be deleted from the resulting DataFrame.<br />
#* If the value is ''[]'', no columns are updated to the resulting DataFrame.<br />
#* If the value is ''null'' (default), all columns are copied from the source to target (the ones having matching names).<br />
# '''Columns to CREATE for non-match rows in source''': Columns to create to the result DataFrame, if a matching row in the source DataFrame is not found in the target DataFrame. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function. Following special values can also be used:<br />
#* If the value is ''_remove'', no new rows are created to the resulting DataFrame.<br />
#* If the value is ''[]'', new rows are created to the resulting DataFrame but all columns of the created rows get empty values.<br />
#* If the value is ''null'' (default), when creating rows, all columns are copied from the source to target (the ones having matching names).<br />
# '''Keep or DELETE non-matching rows in target''': Boolean value that defines whether those rows in the target DataFrame where no matching row in the source DataFrame is found, are included in the result DataFrame (true) or deleted (false). The default value is ''true''.<br />
<br />
Examples:<br />
<br />
Update case attribute values for some cases and create non-existing:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id").tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;2<br />
5;;2<br />
</pre><br />
<br />
Update case attribute values for some cases and don't create non-existing:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id", null, _remove).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;2<br />
</pre><br />
<br />
Update case attribute values for some cases (create non-existing) where columns to match have different names in the source and target DataFrames ("Case id" in target and "Case" in source are used to match, and "Cost" in target is updated from "Variable Cost" in source):<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7, 4],<br />
["1", 5, 2],<br />
["4", 2, 0],<br />
["5", 2, 1]<br />
], ["Case", "Cost", "Variable Cost"]));<br />
CaseData.Merge(UpdatedData, ["Case id": "Case"], ["Cost": "Variable Cost"]).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;4<br />
1;Dallas;2<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;0<br />
5;;1<br />
</pre><br />
<br />
Delete matching cases (don't create non-matching):<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0"],<br />
["1"],<br />
["4"],<br />
["5"]<br />
], ["Case id"]));<br />
CaseData.Merge(UpdatedData, "Case id", _remove, _remove).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
2;Dallas;8<br />
3;Chicago;4<br />
</pre><br />
<br />
Update matching cases, create non-matching by source as new, and delete non-matching by target:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id", null, null, false).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
4;New York;2<br />
5;;2<br />
</pre><br />
<br />
<pre><br />
Let("target", ToDataFrame([[0, "zero", "target"], [1, "", "target"]], ["id", "text", "frame"]));<br />
Let("source", ToDataFrame([[1, "one", "source"], [2, "two", "source"], [3, "three", "source"]], ["id", "text", "frame"]));<br />
<br />
target.Merge(source, "id").ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns):<br />
id;text;frame<br />
0;zero;target<br />
1;one;source<br />
2;two;source<br />
3;three;source<br />
<br />
target.Merge(source, "id", ["text"]).ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns, copy only text column from source):<br />
id;text;frame<br />
0;zero;target<br />
1;one;target<br />
2;two;<br />
3;three;<br />
<br />
target.Merge(source, "id", ["text"], _remove).ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns, copy only text column from source, remove rows found only in source):<br />
id;text;frame<br />
0;zero;target<br />
1;one;target<br />
<br />
target.Merge(source, "id", ["text"], _remove, false).ToCsv()<br />
Returns (one key, identical dataframe columns, copy only text column from source, remove rows found only in source or only in target):<br />
id;text;frame<br />
1;one;target<br />
<br />
target.Merge(source, "id", _remove, _remove, false).ToCsv()<br />
Returns (one key, identical dataframe columns, remove all rows):<br />
id;text;frame<br />
<br />
<br />
Let("target", ToDataFrame([[0, 0, "zerozeroleft", "target"], [0, 1, "zeroleft", "target"], [1, 2, "left", "target"], [4, 5, "fourleft", "target"]], ["idleft1", "idleft2", "textleft", "frame"]));<br />
Let("source", ToDataFrame([[0, 0, "zerozeroright", "source"], [0, 1, "zeroright", "target"], [1, 2, "oneright", "source"], [2, 3, "tworight", "source"], [3, 4, "threeright", "source"]], ["idright1", "idright2", "textright", "frame"]));<br />
<br />
target.Merge(source, ["idleft1": "idright1"]).ToCsv()<br />
Returns (one key, default parameters, different dataframe columns, copy all matching columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;0;zerozeroleft;target<br />
0;1;zeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;;;source<br />
3;;;source<br />
<br />
target.Merge(source, ["idleft1": "idright1"], []).ToCsv()<br />
Returns (one key, default parameters, different dataframe columns, copy only key column):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;target<br />
0;0;zerozeroleft;target<br />
0;1;zeroleft;target<br />
0;1;zeroleft;target<br />
1;2;left;target<br />
4;5;fourleft;target<br />
2;;;<br />
3;;;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy all matching columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;3;;source<br />
3;4;;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright -column):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright", "frame"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy textright and frame -columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;source<br />
0;1;zeroright;target<br />
1;2;oneright;source<br />
4;5;fourleft;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], _remove).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, remove all matching rows, copy only matching columns):<br />
idleft1;idleft2;textleft;frame<br />
4;5;fourleft;target<br />
2;3;;<br />
3;4;;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id columns and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright", "frame"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id, frame and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], null, ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, don't copy any columns from source for matching columns, copy id columns and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright", "frame"], false).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id, frame and textright-column for rows not found in target, remove all rows not found in source):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
</pre></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=DataFrame_in_Expression_Language&diff=15176DataFrame in Expression Language2020-01-21T08:38:31Z<p>TeeLeht: </p>
<hr />
<div>DataFrame represents a two dimensional array of data with one-to-many columns and zero-to-many rows, like a relational database table, an Excel sheet or a CSV data file. Each column in the DataFrame has a name, and there must not be more than one column with the same name. DataFrame is the generic data structure used to manage all kinds data in QPR ProcessAnalyzer expression engine that run in-memory. DataFrames as linked to other entities in QPR ProcessAnalyzer as follows:<br />
* Datatable contents is fetched into the memory as a DataFrame object<br />
* DataFrame can be stored (persisted) to a Datatable<br />
* ETL operations, such as joining, unions, filtering and grouping are based on the DataFrames<br />
* Data extracted from an external data source, e.g. using ODBC, is fetched to the in-memory calculation as a DataFrame.<br />
* When using a [[QPR_ProcessAnalyzer_Model_Datasources#Loading Data using Loading Script|loading scripts]], cases and events data is fed to the model using the DataFrame.<br />
<br />
{| class="wikitable"<br />
!'''DataFrame properties'''<br />
! '''Description'''<br />
|-<br />
||Columns (String*)<br />
||DataFrame columns names as an array in the order the columns are in the DataFrame.<br />
|-<br />
||Rows (Object**)<br />
||Returns the data content of the DataFrame as a two-dimensional array (matrix). The column names are not part of the data content.<br />
<br />
Examples:<br />
<pre><br />
DatatableById(5).DataFrame.Rows[0][0]<br />
Returns: the value in the first row and first column in a datatable with id 5.<br />
</pre><br />
|-<br />
||<column name> (Object*)<br />
||<br />
Returns an array of values of given column in the datatable. If the column name contains spaces, the Column function needs to be used to refer to a column.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).right<br />
Returns: [zero, two, three]<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).right[2]<br />
Returns: three<br />
</pre><br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
!'''DataFrame&nbsp;functions'''<br />
! '''Parameters'''<br />
! '''Description'''<br />
|-<br />
||Append (DataFrame)<br />
||<br />
* DataFrame which data to append <br />
||<br />
Creates a new DataFrame that has the contents of given DataFrame added to the end of this DataFrame. When the data is combined, the order of columns matters, not the names of the columns. The resulting DataFrame gets column names from this DataFrame.<br />
<br />
If the number of columns is different between this DataFrame and the other DataFrame, an exception is thrown.<br />
<br />
Examples:<br />
<pre><br />
Let("dataframe1", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]));<br />
Let("dataframe2", ToDataFrame([[1, "one"], [4, "four"]], ["id", "text"]));<br />
dataframe1.Append(dataframe2);<br />
<br />
Returns:<br />
id;text<br />
0;zero<br />
2;two<br />
3;three<br />
1;one<br />
4;four<br />
</pre><br />
|-<br />
||ColumnIndexes (Integer*)<br />
||<br />
* Column names (String*)<br />
||<br />
Convert DataFrame column names into column indexes. The indexes are starting from zero. If a column is not found, an exception is given.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ColumnIndexes(["right", "id"])<br />
Returns: [1, 0]<br />
</pre><br />
|-<br />
||Column (Object*)<br />
||<br />
* Column name<br />
||<br />
Returns an array of values of given column in the order rows are in the datatable.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Column("right")<br />
Returns: [zero, two, three]<br />
</pre><br />
|-<br />
||Columns (DataFrame)<br />
||<br />
* Array of column names<br />
||<br />
Creates a new DataFrame having only the defined columns of the original DataFrame. Note that Columns function is different than Columns property (difference is that the function has parameters).<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Columns(["right"]).ToCsv()<br />
Returns:<br />
right<br />
zero<br />
two<br />
three<br />
<br />
</pre><br />
|-<br />
||Head (DataFrame)<br />
||<br />
* Number of rows<br />
||<br />
Creates a new DataFrame that only contains top number of rows of this DataFrame. If the DataFrame has less than n rows, all its rows are returned.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Head(2).ToCsv()<br />
Results string:<br />
id;right<br />
0;zero<br />
2;two<br />
</pre><br />
|-<br />
||Join (DataFrame)<br />
||<br />
# Other DataFrame<br />
# Columns to join<br />
# join type<br />
||<br />
See [[#Joining_DataFrames|Joining DataFrames]].<br />
<br />
|-<br />
||GroupBy (DataFrame)<br />
||<br />
# Array of columns to group<br />
# Array of grouping expressions<br />
||<br />
Creates a new DataFrame based on the current DataFrame. The resulting DataFrame has rows grouped by given columns and values aggregated using given functions. In the resulting DataFrame one row in the end result corresponds with one group.<br />
<br />
Parameters:<br />
# '''Columns''': Columns to group identified by column names.<br />
# '''Aggregation expressions''': Array containing the column name as a key and the aggregation expression as a value.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [0, "zero2"], [2, "two"], [2, "two"], [2, "two3"], [3, "three"]], ["id", "text"]).GroupBy(["id"],<br />
[<br />
"ids": Def("", Sum(id)),<br />
"texts": Def("", StringJoin(",", text)),<br />
"constant": 123<br />
]).ToCsv()<br />
Returns:<br />
ids;texts;constant<br />
0;zero,zero2;123<br />
6;two,two,two3;123<br />
3;three;123<br />
<br />
ToDataFrame([[0, "zero"], [0, "zero2"], [2, "two"], [2, "two"], [2, "two3"], [3, "three"]], ["id", "text"]).GroupBy(["id", "text"],<br />
[<br />
"ids": Def("", Sum(id)),<br />
"texts": Def("", StringJoin(",", text)),<br />
"constant": 123<br />
]).ToCsv()<br />
Returns:<br />
ids;texts;constant<br />
0;zero;123<br />
0;zero2;123<br />
4;two,two;123<br />
2;two3;123<br />
3;three;123<br />
<br />
Analysis("OperationLog")<br />
.GroupBy(<br />
["User Name"],<br />
[<br />
"User Name": Def("", Column("User Name")[0]),<br />
"Count": Def("Rows", CountTop(Rows)),<br />
"Avg. Duration": Def("", Average(Duration)),<br />
"Max. Duration": Def("", Max(Duration))<br />
]<br />
).ToCsv()<br />
<br />
Returns (similar to this):<br />
User Name;Count;Avg. Duration;Max. Duration<br />
;207;0.617434782608696;20.556<br />
Administrator;665;16.3750631578947;4225.497<br />
qpr;128;2.158765625;20.346<br />
</pre><br />
|-<br />
||Merge (DataFrame)<br />
||<br />
||<br />
See [[#Merging_DataFrames|Merging DataFrames]].<br />
|-<br />
||OrderBy (DataFrame)<br />
||<br />
* ordering expression<br />
||<br />
Creates a new DataFrame having rows ordered in an ascending order using the given expression evaluated on each row.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).OrderBy(text).ToCsv()<br />
Returns:<br />
id;right<br />
3;three<br />
2;two<br />
0;zero<br />
<br />
Analysis("OperationLog").OrderBy(Duration).Head(1)<br />
Results string:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||OrderByDescending (DataFrame)<br />
||<br />
* ordering expression<br />
||<br />
Creates a new DataFrame having rows ordered in an descending order using the given expression evaluated on each row. See OrderBy above for examples.<br />
<br />
|-<br />
||Persist (DataTable)<br />
||<br />
* DataTable name<br />
* Additional parameters<br />
||<br />
Writes a DataFrame into a DataTable in the QPR ProcessAnalyzer database. If a DataTable with that name does not exist in the project, a new DataTable is created. If a DataTable with that name already exists, the DataFrame will be stored into that DataTable. The function returns the written DataTable object.<br />
<br />
The additional parameters support:<br />
* Append: Can be used to determine whether to append (true) or overwrite (false) the existing data. Default is ''false''.<br />
* ProjectName: Name of the project under which the DataTable is to be created.<br />
* ProjectId: Id of the project under which the DataTable is to be created.<br />
<br />
Examples:<br />
<pre><br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
right.Persist("RightDataTable", ["ProjectName": "TestData"])<br />
Results: Id of the new data table named "RightDataTable" created into project named TestData (which is created if it doesn't already exist). If the table already existed, its contents will be overwritten by the new content.<br />
<br />
Let("newData", ToDataFrame([[4, "four"]], ["id", "right"]));<br />
newData.Persist("RightDataTable", ["ProjectName": "TestData", "Append": true])<br />
Results: Id of the new data table named "RightDataTable" created into project named TestData (which is created if it doesn't already exist). If the table already existed, new content will be appended into the end of the table.<br />
</pre><br />
|-<br />
||SetColumns (DataFrame)<br />
||<br />
* new/modified columns as array<br />
||<br />
Creates a new DataFrame based on the current DataFrame, where new columns have been created and/or existing columns have been modified. New and modified columns are defined using an array, where the column name is as a key and as a value there is the expression to calculate the new or modified column. When specifying a column that already exists, the column values are modified. When specifying a new column name, that column is created as a new column to the resulting DataFrame.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["both": Def("", text + "=" + id)]).ToCsv()<br />
Returns:<br />
id;text;both<br />
0;zero;zero=0<br />
2;two;two=2<br />
3;three;three=3<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["text": Def("", text + "=" + id)]).ToCsv()<br />
Returns:<br />
id;text<br />
0;zero=0<br />
2;two=2<br />
3;three=3<br />
<br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "text"]).SetColumns(["both": Def("", text + "=" + id), "both+1": Def("", both + 1), "text": Def("", "Done: " + Column("both+1")), "constant": 1234]).ToCsv()<br />
Returns:<br />
id;text;both;both+1;constant<br />
0;Done: zero=01;zero=0;zero=01;1234<br />
2;Done: two=21;two=2;two=21;1234<br />
3;Done: three=31;three=3;three=31;1234<br />
</pre><br />
|-<br />
||Tail (DataFrame)<br />
||<br />
* Number of rows<br />
||<br />
Creates a new DataFrame that has only the bottom number of rows of this DataFrame. If the DataFrame has less than n rows, all its rows are returned.<br />
<br />
Example:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).Tail(2).ToCsv()<br />
Results string:<br />
id;right<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||ToCsv (String)<br />
||(none)<br />
||<br />
Converts a DataFrame into a CSV data. The CSV data has the following formatting:<br />
* Column separator: semicolon<br />
* Decimal separator in numeric fields: period<br />
* Quotation character for text fields: double quotes (used when the textual value contains semicolon, double quotes, linebreak or tabulator)<br />
* Escape character: Double quotes in textual fields are escaped with two double quotes.<br />
* Date format for date fields: yyyy-MM-dd HH:mm:ss,fff<br />
* First line: contains column headers<br />
<br />
Example:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ToCsv()<br />
Returns:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
||Where (DataFrame)<br />
||<br />
* condition expression<br />
||<br />
Creates a new DataFrame having only rows for which the given condition expression returns true. The condition expression can refer to the columns of the DataFrame (see the example below).<br />
<br />
Examples:<br />
<pre><br />
Let("df", ToDataFrame([[0, "zero"], [2, "two", true], [3, "three"]], ["id", "string"]));<br />
<br />
All the following expression return the same:<br />
df.Where(id < 3);<br />
df.Where(Column("id") < 3);<br />
df.Where(_[0] < 3);<br />
<br />
Returns:<br />
id;string<br />
0;zero<br />
2;two<br />
</pre><br />
|-<br />
||Zip (DataFrame)<br />
||<br />
* DataFrame<br />
||<br />
Creates a new DataFrame that has the contents of given DataFrame appended as new columns into the end of this DataFrame. Returns a new DataFrame that has the colums from both the data frames so that the columns from the other DataFrame are appended to the end of the columns of this DataFrame. If the number of rows is different between this DataFrame and the other DataFrame, an exception is thrown. There must not be duplicate column names in the DataFrames - otherwise an exception is thrown.<br />
<br />
Examples:<br />
<pre><br />
Let("df1", ToDataFrame([[0, "zero"], [1, "one"], [4, "four"]], ["id", "text"]));<br />
Let("df2", ToDataFrame([[1, "one"], [2, "two"], [3, "three"]], ["id2", "text2"]));<br />
df1.Zip(df2).ToCsv();<br />
Returns:<br />
id;text;id2;text2<br />
0;zero;1;one<br />
1;one;2;two<br />
4;four;3;three<br />
</pre><br />
|-<br />
|}<br />
<br />
The following functions can be used to initialize DataFrame objects:<br />
{| class="wikitable"<br />
!'''Function'''<br />
!'''Parameters'''<br />
! '''Description'''<br />
|-<br />
||ToDataFrame<br />
||<br />
# matrix<br />
# column names array<br />
||<br />
Creates a DataFrame based on the given matrix (two dimensional array) and column names. Number of column names should be the same as the number of columns in the matrix.<br />
<br />
Examples:<br />
<pre><br />
ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]).ToCsv()<br />
Returns:<br />
A string containing:<br />
id;right<br />
0;zero<br />
2;two<br />
3;three<br />
</pre><br />
|-<br />
|}<br />
<br />
== Joining DataFrames ==<br />
Performs a [https://en.wikipedia.org/wiki/Relational_algebra#Joins_and_join-like_operators joining operation] between two DataFrames.<br />
<br />
Parameters:<br />
# '''DataFrame''': The other DataFrame to join.<br />
# '''Columns to match''': Columns which the joining is based on, can be defined as follows:<br />
#* If joining using '''one column having the same name in both DataFrames''', the column name is specified as as string.<br />
#* If joining using '''several columns having the same names in both DataFrames''', the column names are specified as a string array.<br />
#* If joining using '''columns having different names between the DataFrames''', columns are specified as an array of key-value pairs, where the key is the column name in the left side DataFrame, and value is the column name in the right side DataFrame.<br />
# '''Join type''' which can be<br />
#* '''inner''' (default): row is generated if both DataFrames have the key.<br />
#* '''leftouter''': at least one row is generated for each left side DataFrame row, even if there is no matching other row, in which case null is given as value for the other columns.<br />
<br />
Examples:<br />
<pre><br />
Let("left", ToDataFrame([[0, "zero"], [1, "one"]], ["id", "left"]));<br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
left.join(right, "id").ToCsv()<br />
Returns:<br />
id;left;right<br />
0;zero;zero<br />
<br />
Let("left", ToDataFrame([[0, "zero"], [1, "one"]], ["id", "left"]));<br />
Let("right", ToDataFrame([[0, "zero"], [2, "two"], [3, "three"]], ["id", "right"]));<br />
left.join(right, "id", "leftouter").ToCsv()<br />
Returns:<br />
id;left;right<br />
0;zero;zero<br />
1;one;<br />
<br />
Let("left", ToDataFrame([[0, 0, "zerozeroleft"], [0, 1, "zeroleft"], [1, 2, "oneleft"]], ["idleft1", "idleft2", "left"]));<br />
Let("right", ToDataFrame([[0, 0, "zerozeroright"], [0, 1, "zeroright"], [2, 3, "tworight"], [3, 4, "threeright"]], ["idright1", "idright2", "right"]));<br />
left.join(right, ["idleft1": "idright1"], "inner");<br />
Returns:<br />
idleft1;idleft2;left;idright2;right<br />
0;0;zerozeroleft;0;zerozeroright<br />
0;0;zerozeroleft;1;zeroright<br />
0;1;zeroleft;0;zerozeroright<br />
0;1;zeroleft;1;zeroright<br />
<br />
Let("left", ToDataFrame([[0, 0, "zerozeroleft"], [0, 1, "zeroleft"], [1, 2, "oneleft"]], ["idleft1", "idleft2", "left"]));<br />
Let("right", ToDataFrame([[0, 0, "zerozeroright"], [0, 1, "zeroright"], [2, 3, "tworight"], [3, 4, "threeright"]], ["idright1", "idright2", "right"]));<br />
left.join(right, ["idleft1": "idright1", "idleft2": "idright2"], "inner");<br />
Returns:<br />
idleft1;idleft2;left;right<br />
0;0;zerozeroleft;zerozeroright<br />
0;1;zeroleft;zeroright<br />
</pre><br />
<br />
== Merging DataFrames ==<br />
<br />
Creates a new DataFrame that has the contents of a DataFrame (target) merged with another DataFrame (source). The merging works in the same principle as in the [https://en.wikipedia.org/wiki/Merge_(SQL) SQL language]. Note that the merging does not create new columns but the result DataFrame has the same columns as the target DataFrame. Merging has the following principle:<br />
<br />
[[File:Merge.png|650px]]<br />
<br />
Parameters:<br />
# '''Source DataFrame''': DataFrame to be merged with the target DataFrame.<br />
# '''Columns to used for matching''': Columns used to match the source and target DataFrames. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function.<br />
# '''Columns to UPDATE for matching rows''': Columns to update from the source DataFrame to the target DataFrame for the rows that match between the DataFrames. Note that the matching columns cannot be updated because they always have same values due to the matching logic. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function. Following special values can also be used:<br />
#* If the value is ''_remove'', all matching rows are be deleted from the resulting DataFrame.<br />
#* If the value is ''[]'', no columns are updated to the resulting DataFrame.<br />
#* If the value is ''null'' (default), all columns are copied from the source to target (the ones having matching names).<br />
# '''Columns to CREATE for non-match rows in source''': Columns to create to the result DataFrame, if a matching row in the source DataFrame is not found in the target DataFrame. This parameter has similar syntax as the 2. parameter in the [[#Joining DataFrames|join]] function. Following special values can also be used:<br />
#* If the value is ''_remove'', no new rows are created to the resulting DataFrame.<br />
#* If the value is ''[]'', new rows are created to the resulting DataFrame but all columns of the created rows get empty values.<br />
#* If the value is ''null'' (default), when creating rows, all columns are copied from the source to target (the ones having matching names).<br />
# '''Keep or DELETE non-matching rows in target''': Boolean value that defines whether those rows in the target DataFrame where no matching row in the source DataFrame is found, are included in the result DataFrame (true) or deleted (false). The default value is ''true''.<br />
<br />
Examples:<br />
<br />
Update case attribute values for some cases and create non-existing:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id").tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;2<br />
5;;2<br />
</pre><br />
<br />
Update case attribute values for some cases and don't create non-existing:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id", null, _remove).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;2<br />
</pre><br />
<br />
Update case attribute values for some cases (create non-existing) where columns to match have different names in the source and target DataFrames ("Case id" in target and "Case" in source are used to match, and "Cost" in target is updated from "Variable Cost" in source):<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7, 4],<br />
["1", 5, 2],<br />
["4", 2, 0],<br />
["5", 2, 1]<br />
], ["Case", "Cost", "Variable Cost"]));<br />
CaseData.Merge(UpdatedData, ["Case id": "Case"], ["Cost": "Variable Cost"]).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;4<br />
1;Dallas;2<br />
2;Dallas;8<br />
3;Chicago;4<br />
4;New York;0<br />
5;;1<br />
</pre><br />
<br />
Delete matching cases (don't create non-matching):<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0"],<br />
["1"],<br />
["4"],<br />
["5"]<br />
], ["Case id"]));<br />
CaseData.Merge(UpdatedData, "Case id", _remove, _remove).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
2;Dallas;8<br />
3;Chicago;4<br />
</pre><br />
<br />
Update matching cases, create non-matching by source as new, and delete non-matching by target:<br />
<pre><br />
Let("CaseData", ToDataFrame([<br />
["0", "New York", 6],<br />
["1", "Dallas", 3],<br />
["2", "Dallas", 8],<br />
["3", "Chicago", 4],<br />
["4", "New York", 2]<br />
], ["Case id", "Region", "Cost"]));<br />
Let("UpdatedData", ToDataFrame([<br />
["0", 7],<br />
["1", 5],<br />
["4", 2],<br />
["5", 2]<br />
], ["Case id", "Cost"]));<br />
CaseData.Merge(UpdatedData, "Case id", null, null, false).tocsv();<br />
<br />
Returns:<br />
Case id;Region;Cost<br />
0;New York;7<br />
1;Dallas;5<br />
4;New York;2<br />
5;;2<br />
</pre><br />
<br />
<pre><br />
Let("target", ToDataFrame([[0, "zero", "target"], [1, "", "target"]], ["id", "text", "frame"]));<br />
Let("source", ToDataFrame([[1, "one", "source"], [2, "two", "source"], [3, "three", "source"]], ["id", "text", "frame"]));<br />
<br />
target.Merge(source, "id").ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns):<br />
id;text;frame<br />
0;zero;target<br />
1;one;source<br />
2;two;source<br />
3;three;source<br />
<br />
target.Merge(source, "id", ["text"]).ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns, copy only text column from source):<br />
id;text;frame<br />
0;zero;target<br />
1;one;target<br />
2;two;<br />
3;three;<br />
<br />
target.Merge(source, "id", ["text"], _remove).ToCsv()<br />
Returns (one key, default parameters, identical dataframe columns, copy only text column from source, remove rows found only in source):<br />
id;text;frame<br />
0;zero;target<br />
1;one;target<br />
<br />
target.Merge(source, "id", ["text"], _remove, false).ToCsv()<br />
Returns (one key, identical dataframe columns, copy only text column from source, remove rows found only in source or only in target):<br />
id;text;frame<br />
1;one;target<br />
<br />
target.Merge(source, "id", _remove, _remove, false).ToCsv()<br />
Returns (one key, identical dataframe columns, remove all rows):<br />
id;text;frame<br />
<br />
<br />
Let("target", ToDataFrame([[0, 0, "zerozeroleft", "target"], [0, 1, "zeroleft", "target"], [1, 2, "left", "target"], [4, 5, "fourleft", "target"]], ["idleft1", "idleft2", "textleft", "frame"]));<br />
Let("source", ToDataFrame([[0, 0, "zerozeroright", "source"], [0, 1, "zeroright", "target"], [1, 2, "oneright", "source"], [2, 3, "tworight", "source"], [3, 4, "threeright", "source"]], ["idright1", "idright2", "textright", "frame"]));<br />
<br />
target.Merge(source, ["idleft1": "idright1"]).ToCsv()<br />
Returns (one key, default parameters, different dataframe columns, copy all matching columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;0;zerozeroleft;target<br />
0;1;zeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;;;source<br />
3;;;source<br />
<br />
target.Merge(source, ["idleft1": "idright1"], []).ToCsv()<br />
Returns (one key, default parameters, different dataframe columns, copy only key column):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;target<br />
0;0;zerozeroleft;target<br />
0;1;zeroleft;target<br />
0;1;zeroleft;target<br />
1;2;left;target<br />
4;5;fourleft;target<br />
2;;;<br />
3;;;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy all matching columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;3;;source<br />
3;4;;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright -column):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright", "frame"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy textright and frame -columns):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;source<br />
0;1;zeroright;target<br />
1;2;oneright;source<br />
4;5;fourleft;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], _remove).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, remove all matching rows, copy only matching columns):<br />
idleft1;idleft2;textleft;frame<br />
4;5;fourleft;target<br />
2;3;;<br />
3;4;;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id columns and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright", "frame"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id, frame and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
4;5;fourleft;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], null, ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright"]).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, don't copy any columns from source for matching columns, copy id columns and textright-column for rows not found in target):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroleft;source<br />
0;1;zeroleft;target<br />
1;2;left;source<br />
4;5;fourleft;target<br />
2;3;tworight;<br />
3;4;threeright;<br />
<br />
target.Merge(source, ["idleft1": "idright1", "idleft2": "idright2"], ["textleft": "textright"], ["idleft1": "idright1", "idleft2": "idright2", "textleft": "textright", "frame"], false).ToCsv()<br />
Returns (two keys, default parameters, different dataframe columns, copy only textright-column for matching columns, copy id, frame and textright-column for rows not found in target, remove all rows not found in source):<br />
idleft1;idleft2;textleft;frame<br />
0;0;zerozeroright;target<br />
0;1;zeroright;target<br />
1;2;oneright;target<br />
2;3;tworight;source<br />
3;4;threeright;source<br />
</pre></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Calculated_Attributes_in_QPR_ProcessAnalyzer&diff=13617Calculated Attributes in QPR ProcessAnalyzer2019-06-06T09:00:59Z<p>TeeLeht: </p>
<hr />
<div>Calculated attributes enable to create case and event attributes using an expression (calculation formula) based on data in the QPR ProcessAnalyzer model.<br />
<br />
== Introduction and Usecases==<br />
Data to '''case attributes''' and '''event attributes''' can be originated as follows:<br />
* '''importing''' them into QPR ProcessAnalyzer from a source system, csv file etc.<br />
* '''calculating''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions|expression]].<br />
<br />
Calculated attributes have following use cases:<br />
* Conversions: If an imported attribute data is not in a suitable format, the data can be overridden by defining a calculated attribute with the same name. The calculated attribute expression performs conversions for the data.<br />
* Aggregations: It's possible to aggregate e.g. event level information to case level using a calculated case attribute.<br />
* Performance: If there is an expression to aggregate event level information to a case level, the aggregation can be done already in the model loading using a calculated case attribute for better performance.<br />
<br />
== Functioning Principle ==<br />
Calculated attributes work as follows:<br />
* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.<br />
* Calculated attributes are calculated when the model is loaded, and thus calculated attribute values don't change after the model loading during the time the model is in the memory. If attributes need to be calculated again, the model needs to be reloaded.<br />
* Calculated attribute values are stored into the memory like the imported attributes, meaning the model requires more memory, the more there are calculated attributes.<br />
* For calculated case attributes, the expression is evaluated in each case's context, and for calculated event attributes, for each event's context. It's thus possible to access the entire model data in the expressions, such as variations, event types, flow and flow occurrences.<br />
* Calculated event attributes are processed before calculated case attributes, so it's possible to use calculated event attributes in calculated case attributes expressions. Also, calculated case and event attributes are processed in the order they are defined, so it's possible to use an earlier defined calculated attribute in expressions of later attributes.<br />
* Calculated attribute will replace an imported attribute, if there is an imported attribute with the same name. Note that it's not possible to override event timestamp, event type name or case id.<br />
* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.<br />
<br />
Calculated case and event attributes are configured to the model JSON settings are follows:<br />
{| class="wikitable"<br />
!'''Property'''<br />
! '''Description'''<br />
|-<br />
||<br />
CaseAttributes<br />
||<br />
Array of calculated case attributes with the following properties:<br />
* '''name''': Calculated attribute name. There are no restrictions for the attribute names, but avoid names starting or ending with spaces to avoid confusion.<br />
*'''expression''': Expression to calculate the calculated attribute. The expression is calculated in the case's or event's context. Only when an expression has been defined, the attribute is a calculated attribute.<br />
|-<br />
||<br />
EventAttributes<br />
||<br />
Calculated event attributes are defined using the same structure as calculated case attributes.<br />
|}<br />
<br />
== Examples ==<br />
Example 1: One calculated case attribute:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "Cost",<br />
"expression": "Cost * 1.5"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 2: Two calculated event attributes:<br />
<pre><br />
{<br />
"EventAttributes": [<br />
{<br />
"name": "Event Month",<br />
"expression": "Timestamp.Truncate(\"month\")"<br />
},<br />
{<br />
"name": "Duration to Next Event",<br />
"expression": "If(IsNull(_.NextInCase), null, (_.NextInCase.Timestamp-_.Timestamp))"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 3: Several calculated case and event attributes:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "myBooleanAttribute1",<br />
"expression": "CURRENCYCODE == \"RUB\""<br />
},<br />
{<br />
"name": "Combined status",<br />
"expression": "PurchaseStatus+ \" \" + PurchaseType"<br />
},<br />
{<br />
"name": "Repeated Events Count",<br />
"expression": "Count(_.Events)-Count(Distinct(_.Events.Type))"<br />
},<br />
{<br />
"name": "Duration between \"Invoice Sent\" and \"Payment Received\"",<br />
"expression": "if(Count(_.EventsByType(\"Invoice Sent\")) == 0 || Count(_.EventsByType(\"Purchase Order Line Created\")) == 0, null, (GetAtReverse(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp-GetAt(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp))"<br />
}<br />
],<br />
"EventAttributes": [<br />
{<br />
"name": "Event type occurrence number",<br />
"expression": "Let(\"name\", _.Typename);Count(_.Recurse(_.PreviousInCase).Where(_.Typename==name))"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 4: Segragation of duties:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "KPI_SegragationOfDuties",<br />
"expression": <br />
"If(Count(<br />
Intersect(<br />
_.EventsByType(\"Purchase Order Created\").Attribute(\"User\"),<br />
_.EventsByType(\"Purchase Order Approved\").Attribute(\"User\")).<br />
Where(!Isnull(_) && _!=\"\"))>0, \"False\", \"True\") "<br />
}<br />
]<br />
}</pre><br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Calculated_Attributes_in_QPR_ProcessAnalyzer&diff=13616Calculated Attributes in QPR ProcessAnalyzer2019-06-06T08:56:41Z<p>TeeLeht: </p>
<hr />
<div>Calculated attributes enable to create case and event attributes using an expression (calculation formula) based on data in the QPR ProcessAnalyzer model.<br />
<br />
== Introduction and Usecases==<br />
Data to '''case attributes''' and '''event attributes''' can be originated as follows:<br />
* '''importing''' them into QPR ProcessAnalyzer from a source system, csv file etc.<br />
* '''calculating''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions|expression]].<br />
<br />
Calculated attributes have following use cases:<br />
* Conversions: If an imported attribute data is not in a suitable format, the data can be overridden by defining a calculated attribute with the same name. The calculated attribute expression performs conversions for the data.<br />
* Aggregations: It's possible to aggregate e.g. event level information to case level using a calculated case attribute.<br />
* Performance: If there is an expression to aggregate event level information to a case level, the aggregation can be done already in the model loading using a calculated case attribute for better performance.<br />
<br />
== Functioning Principle ==<br />
Calculated attributes work as follows:<br />
* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.<br />
* Calculated attributes are calculated when the model is loaded, and thus calculated attribute values don't change after the model loading during the time the model is in the memory. If attributes need to be calculated again, the model needs to be reloaded.<br />
* Calculated attribute values are stored into the memory like the imported attributes, meaning the model requires more memory, the more there are calculated attributes.<br />
* For calculated case attributes, the expression is evaluated in each case's context, and for calculated event attributes, for each event's context. It's thus possible to access the entire model data in the expressions, such as variations, event types, flow and flow occurrences.<br />
* Calculated event attributes are processed before calculated case attributes, so it's possible to use calculated event attributes in calculated case attributes expressions. Also, calculated case and event attributes are processed in the order they are defined, so it's possible to use an earlier defined calculated attribute in expressions of later attributes.<br />
* Calculated attribute will replace an imported attribute, if there is an imported attribute with the same name. Note that it's not possible to override event timestamp, event type name or case id.<br />
* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.<br />
<br />
Calculated case and event attributes are configured to the model JSON settings are follows:<br />
{| class="wikitable"<br />
!'''Property'''<br />
! '''Description'''<br />
|-<br />
||<br />
CaseAttributes<br />
||<br />
Array of calculated case attributes with the following properties:<br />
* '''name''': Calculated attribute name. There are no restrictions for the attribute names, but avoid names starting or ending with spaces to avoid confusion.<br />
*'''expression''': Expression to calculate the calculated attribute. The expression is calculated in the case's or event's context. Only when an expression has been defined, the attribute is a calculated attribute.<br />
|-<br />
||<br />
EventAttributes<br />
||<br />
Calculated event attributes are defined using the same structure as calculated case attributes.<br />
|}<br />
<br />
== Examples ==<br />
Example 1: One calculated case attribute:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "Cost",<br />
"expression": "Cost * 1.5"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 2: Two calculated event attributes:<br />
<pre><br />
{<br />
"EventAttributes": [<br />
{<br />
"name": "Event Month",<br />
"expression": "Timestamp.Truncate(\"month\")"<br />
},<br />
{<br />
"name": "Duration to Next Event",<br />
"expression": "If(IsNull(_.NextInCase), null, (_.NextInCase.Timestamp-_.Timestamp))"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 3: Several calculated case and event attributes:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "myBooleanAttribute1",<br />
"expression": "CURRENCYCODE == \"RUB\""<br />
},<br />
{<br />
"name": "Combined status",<br />
"expression": "PurchaseStatus+ \" \" + PurchaseType"<br />
},<br />
{<br />
"name": "Repeated Events Count",<br />
"expression": "Count(_.Events)-Count(Distinct(_.Events.Type))"<br />
},<br />
{<br />
"name": "Duration between \"Invoice Sent\" and \"Payment Received\"",<br />
"expression": "if(Count(_.EventsByType(\"Invoice Sent\")) == 0 || Count(_.EventsByType(\"Purchase Order Line Created\")) == 0, null, (GetAtReverse(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp-GetAt(0,_.EventsByType([\"Invoice Sent\", \"Payment Received\"])).Timestamp))"<br />
}<br />
],<br />
"EventAttributes": [<br />
{<br />
"name": "Event type occurrence number",<br />
"expression": "Let(\"name\", _.Typename);Count(_.Recurse(_.PreviousInCase).Where(_.Typename==name))"<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example 4: Segragation of duties:<br />
<pre><br />
{<br />
"CaseAttributes": [<br />
{<br />
"name": "KPI_SegragationOfDuties",<br />
"expression": <br />
"If(Count(<br />
Intersect(<br />
_.EventsByType(\"Purchase Order Created\").Attribute(\"User\"),<br />
_.EventsByType(\"Purchase Order Approved\").Attribute(\"User\")).<br />
Where(!Isnull(_) && _!=\"\"))>0, \"True\", \"False\") "<br />
}<br />
]<br />
}</pre><br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Clustering_Analysis&diff=13201Clustering Analysis2019-04-04T07:05:16Z<p>TeeLeht: </p>
<hr />
<div>The Clustering Analysis view groups cases in the model in a way that the cases inside a group are similar to each other (e.g. cases have the same case attribute values are in the same group). Clustering is based on advanced Machine Learning and Artificial Intelligence algorithms. By default Clustering Analysis uses in-memory built-in kmodes algorithm with categorized values for Event Type occurrences and Case Attribute values. The algorithm does not guarantee convergence to the global optimum which means that subsequent Clustering Analysis runs may result in slightly different clustering results. See this [https://en.wikipedia.org/wiki/Cluster_analysis Wikipedia article] for more about the idea behind clustering.<br />
<br />
You can use the Clustering Analysis View, for example, to check data integrity. That is, the Clustering Analysis might reveal that the model actually contains data from two different processes.<br />
<br />
== Left Panel ==<br />
You can use the left panel to filter cases. Note that you are not bound to using just the Flowchart analysis, as you can change the analysis by right-clicking the analysis and selecting a different type of analysis shown on the panel.<br />
<br />
== Right Panel ==<br />
The right panel contains the clustering analysis. The table shows the clusters, how many cases are in each cluster, and the following details for each cluster:<br />
* '''Feature''' and '''Value''': These two columns list the case attribute and other values that are common to the cases in the cluster.<br />
* '''Cluster Density %''': Share of cases having this feature value within the cluster (i.e. the number of cases having the value shown on the row in this particular cluster divided by the number of cases in the cluster * 100).<br />
* '''Total Density %''': Share of cases having this feature value in the whole data set (i.e. the total number of cases having the value shown on the row divided by the total number of cases * 100).<br />
* '''Contribution %''': Amount of cases that can be explained to belong to this cluster because of this feature value. The scale is such that 0% means that the feature value isn't specific to this cluster and 100% means that all cases belonging to this cluster can be explained by this feature value.<br />
<br />
[[Category: QPR ProcessAnalyzer]]<br />
[[Category: Deployment Packages]]<br />
[[Category: QPR UI]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Clustering_Analysis&diff=13200Clustering Analysis2019-04-04T07:03:13Z<p>TeeLeht: </p>
<hr />
<div>The Clustering Analysis view groups cases in the model in a way that the cases inside a group are similar to each other (e.g. cases have the same case attribute values are in the same group). Clustering is based on advanced machine learning and artificial intelligence algorithms. By default Clustering Analysis uses in-memory built-in kmodes algorithm with categorized values for Event Type occurrences and Case Attribute values. The algorithm does not guarantee convergence to the global optimum which means that subsequent Clustering Analysis runs may result in slightly different clustering results. See this [https://en.wikipedia.org/wiki/Cluster_analysis Wikipedia article] for more about the idea behind clustering.<br />
<br />
You can use the Clustering Analysis View, for example, to check data integrity. That is, the Clustering Analysis might reveal that the model actually contains data from two different processes.<br />
<br />
== Left Panel ==<br />
You can use the left panel to filter cases. Note that you are not bound to using just the Flowchart analysis, as you can change the analysis by right-clicking the analysis and selecting a different type of analysis shown on the panel.<br />
<br />
== Right Panel ==<br />
The right panel contains the clustering analysis. The table shows the clusters, how many cases are in each cluster, and the following details for each cluster:<br />
* '''Feature''' and '''Value''': These two columns list the case attribute and other values that are common to the cases in the cluster.<br />
* '''Cluster Density %''': Share of cases having this feature value within the cluster (i.e. the number of cases having the value shown on the row in this particular cluster divided by the number of cases in the cluster * 100).<br />
* '''Total Density %''': Share of cases having this feature value in the whole data set (i.e. the total number of cases having the value shown on the row divided by the total number of cases * 100).<br />
* '''Contribution %''': Amount of cases that can be explained to belong to this cluster because of this feature value. The scale is such that 0% means that the feature value isn't specific to this cluster and 100% means that all cases belonging to this cluster can be explained by this feature value.<br />
<br />
[[Category: QPR ProcessAnalyzer]]<br />
[[Category: Deployment Packages]]<br />
[[Category: QPR UI]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=13086QPR ProcessAnalyzer Release Notes2019-03-21T14:05:37Z<p>TeeLeht: </p>
<hr />
<div>This page contains new features and fixed issues for each QPR ProcessAnalyzer release. For information on the compatibility of different versions, see [[QPR ProcessAnalyzer Version Compatibility|Version Compatibility Information]]. See also [[Planned Releases for QPR ProcessAnalyzer and QPR UI|next planned releases]].<br />
<br />
== Next Release: QPR ProcessAnalyzer 2019.3 (planned release date 2019-03-26) == <br />
Build number: 2019.3.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br />
<br />
'''Release Highlights''':<br />
* Clustering analysis and related machine learning utilities<br />
* Calculated Case and event attributes<br />
* ChartView - Group and show others <br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307507: Disable rectangular selection in flowchart.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307545: KPI: Clustering analysis and related utility functions.<br />
* 307512: Expression language: [[ Object_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#Model | Description attribute to Model]].<br />
* 306900: Calculated case and event attributes.<br />
* 307533: Level of event log pre-processing can be set for [[QPR_ProcessAnalyzer_Expression_Analysis#KPI_Analysis_JSON_Configuration |expression analysis]].<br />
* 307575: Change items memory caching times.<br />
* Support for Windows 8 has been dropped. Windows 8.1 is still supported.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218863: Model manager not updated after changing Filter Id.<br />
* 218874: Sorting and filtering icons overlap in datagrid.<br />
* 218922: There should be default maximum number of items for different analyses created from tool palette.<br />
* 218723: Empty analysis window after error thrown by PA service.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218908: Wrong Client data in operation log.<br />
* 218928: Expression filter doesn't work with integers.<br />
* 218940: Model eventlog can drop from memory.<br />
* 218927: JSON filtering for case attributes doesn't work with nulls.<br />
* 218779: Source data formatted to two decimals accuracy but PA total cost flowchart show much more decimals.<br />
* 218943: ODBC SQL boolean values does not work with filter CaseAttributeValue.<br />
* 218965: Accessing calculated event attribute value from EventType.Events -property does not work.<br />
<br />
== QPR ProcessAnalyzer 2019.2 (release date 2019-02-14) ==<br />
Build number: 2019.2.0.38539, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights''':<br />
* Support for [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Excel_Client| Microsoft Office 2019]] for QPR ProcessAnalyzer Excel Client.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307423: Improved memory management: unused objects are automatically dropped from the memory. Settings can be configured in [[Web.config_file_in_QPR_ProcessAnalyzer#Qpr.ProcessAnalyzer.Common.Properties.Settings_Section | web.config]] or from the [[QPR_ProcessAnalyzer_Model_JSON_Settings#Memory_Usage_Settings | model JSON settings]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218838: KPI analysis: Event Occurrence Time isn't calculated properly, e.g. Period=Month fails.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218880: PAPO: odbc case and event attributes are not shown in dropdown menu.<br />
* 218877: Support material - Project admins are not able to create new users.<br />
* 218898: Importing XES file with xmlns -definition fails.<br />
* 218893: Model status shows incorrectly "offline" when Model event log is in memory and Model information not.<br />
* 218917: BaseContext.EvaluateChildExpression with given root object iterates the root object if it is an array.<br />
<br />
== Additional Release for QPR ProcessAnalyzer 2019.1 (release date 2019-01-23) ==<br />
Build number: 2019.1.0.38400, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
<br />
* 307357: PA model management: Analysis requests canceling. All operations have new parameters QueryIdentifier and CancelEarlierQueriesWithIdentifier.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218806: Variation filter doesn't filter correctly.<br />
* 218802: It should not be able to load deleted models into memory.<br />
* 218866: Case Analysis shows "0" for textual Case Attribute (SelectedActivityCounts=0 column count and data not match).<br />
* 218862: Case Analysis returns incorrect Start and End times when start or end transition is selected.<br />
* 218847: Variation Analysis Include Only Cases Filter Fails when using Event Counts and filter.<br />
* 218765: Event Occurrence Time calculation for KPI analysis (Server side).<br />
<br />
== QPR ProcessAnalyzer 2019.1 (release date 2019-01-03) ==<br />
Build number: 2019.1.0.38310, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights''':<br />
* There are new training videos available for QPR ProcessAnalyzer in QPR Community. QPR ProcessAnalyzer users can access the videos by clicking Training Videos in the header menu of QPR ProcessAnalyzer UI.<br />
* ChartView can show several measures at the same time. In table, measures are in different columns, and in chart, measures are presented as different series.<br />
<br />
'''Fixed bugs for QPR ProcessAnalyzer UI:'''<br />
* 218768: Number of decimals is not updated in KPI analysis due to HistoryId context variable.<br />
* 218787: Datagrid export fails with numerical values.<br />
* 218757: KPI analysis - null value shown as NaN.0 in table.<br />
* 218794: Popup menu is replicated when PAPO is drawn multiple times.<br />
* 218740: Case Analysis Year period should not show thousand separator.<br />
* 218805: Analysis not shown after adding duration analysis to panel using view designer "shortcuts buttons".<br />
* 218804: PAPO showing only Analysis Window doesn't show anything when other PAPO hides the Analysis window.<br />
* 218815: Flowchart influence analysis does not always show the results in an identical way.<br />
* 218791: Flowcharts visibility stepper don't work in PA deployment package Process benchmarking view.<br />
* 218844: KPI Analysis sorting is not saved to the context variable.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218755: If user selects Influence Analysis for Case Attributes into analysis window, it freezes the analysis window completely.<br />
* 218756: PA model - with event attributes - without case attributes = event attributes shown in profiling case attributes analysis.<br />
<br />
== QPR ProcessAnalyzer 2018.8 (release date 2018-11-29) ==<br />
Build number: 2018.8.0.38236, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights''':<br />
* New types of charts have been added to the KPI Analysis in PAPO. In addition to the previously available column chart and table presentations, there are now bar, donut, area, line and spline charts.<br />
* Tool palette contains now items for each QPR ProcessAnalyzer analysis making it easier to create dashboards with different analyses. The analyses have also needed context variables predefined so that settings are saved to the dashboard.<br />
* Duration Influence Analysis is now calculated in the memory which makes it significantly faster than previously when it was calculated in the SQL Server.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307398: [[KPI_Analysis_(PAPO)#Settings |More chart types to KPI analysis]], such as line chart, bar chart and donut chart.<br />
* 307473: PAPO tables exporting to Excel, Word and PDF<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307417: Duration Influence Analysis in In-Memory.<br />
* 307458: Performance improvement in reusing event logs.<br />
* 307456: Expression language plugin mechanism.<br />
* 307459: [[QPR_ProcessAnalyzer_Web_Service_API#Functions_in_the_Web_Service_API|PA service support for script generated reports as csv file (for QPR UI Script Manager)]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218711: PAPO duration analysis is failing.<br />
* 218663: PAPO - KPI Analysis - Number of decimals effects column height.<br />
* 218664: PAPO - KPI Analysis - Default number of decimals in the drop-down list should be 1.<br />
* 218669: PAPO - KPI Analysis duration from - to.<br />
* 218557: PAPO - Duplicate flows when increasing the flow amounts in flowchart.<br />
* 218718: PAPO - Flowchart sometimes shows portions of the flowchart completely unconnected from start/end nodes of the flowchart.<br />
* 218668: PAPO - KPI Analysis - wrong names in droplist and wrong chart title.<br />
* 218666: PAPO - KPI Analysis - CamelCase column headers.<br />
* 218670: PAPO - KPI Analysis - title Duration between "undefined" and "undefined". <br />
* 218665: PAPO - KPI Analysis - numerical data should be shown linear on X axis.<br />
* 218629: PAPO - KPI Analysis - Year period should not show thousand separator.<br />
* 218667: PAPO - KPI Analysis - units are missing in table.<br />
* 218725: PAPO - KPI Analysis - NumberOfDecimals should be enabled for numerical case&event attribute.<br />
* 218731: PAPO - layout issue when displaying error message.<br />
* 218747: PAPO - KPI analysis - Column header text is not consistent with x-axis label.<br />
* 218762: PAPO - KPI Analysis - Error message doesn't disappear when switching from wrong selections to correct ones.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218727: Null values don't work in GroupBy/GroupByValue functions.<br />
* 218708: Filtering with duration value 0 does not work in duration analysis.<br />
* 218770: Case analysis with variation Id -> Exception: The given key was not present in the dictionary.<br />
* 218771: Conformance: Parallel gateways having multiple branches with only one node aren't analyzed correctly.<br />
<br />
== QPR ProcessAnalyzer 2018.7 (release date 2018-10-10) ==<br />
Build number: 2018.7.0.38036, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307319: Expression language: [[Generic_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#Other_functions | GroupBy and GroupByValue -functions]].<br />
* 307370: PAPO/A1 cell case/event/event type/variation count should only show cases user has permissions in case level security.<br />
* 307369: String handling functions in the expression language.<br />
* 307424: KPI analysis in generic context.<br />
* 307439: Quick & easy expression language improvements.<br />
* 307336: PA performance improvement (part 1).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218673: Null values in PA expression language should appear as nulls in datasets.<br />
* 218693: Performance for PAPO's data grids has been optimized.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218453: .TMP files is not deleted always. After 65k .TMP files exist then PA service stop working. If issue is encountered, workaround is to manually delete .TMP files (e.g. files are located in folder C:\Windows\Temp or C:\Users\<pa_applicationpool_user>\AppData\Local\Temp).<br />
* 218643: InMemory: Open model after pacm file import fails to "Object reference not set to an instance of an object.".<br />
* 218652: Access denied. Unexpected ModelEventLog dropping object with from cache.<br />
* 218648: Import empty model with filter crash (evevenlog.Content is null).<br />
* 218685: XES import runs out of memory when importing BPIC2018 -model.<br />
* 218690: Expressions returning boolean values should be returned to QPR UI as booleans.<br />
* 218687: Average and Sum functions should return null for zero length arrays instead of zero.<br />
* 218705: InMemoryCore: TotalCost in event analysis has incorrect values.<br />
* 218704: Mismatch in case counts in Variation Analysis when event type filter has been applied.<br />
* 218709: FileType parameter not select correct stream compression mode in ImportFromStream.<br />
* 218698: The given key was not present in the dictionary - Variation Analysis error.<br />
* 218710: PAPO case analysis is currently failing.<br />
<br />
== QPR ProcessAnalyzer 2018.6 (release date 2018-08-29) ==<br />
Build number: 2018.6.0.37869, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights'''<br />
* KPI Analysis update: The KPI Analysis feature has new updates to it. The Analysis Menu design has new options that allow for efficient creation of KPI analysis presentations. Menu items have been grouped into sub-groups making finding analysis options much swifter. <br />
* Model load on startup: You can now define which models are loaded onto memory on startup allowing for quicker setup of QPR ProcessAnalyzer servers. This loads the key models needed directly into memory without any separate in-memory loading.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307351: KPI analysis UI - part 2<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307323: [[PA Migration to 2018.6 |Remove old PA web client]].<br />
* 307200: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Necessary_IIS_setup |PA model management: PA model automatic loading on startup]]. <br />
* 307350: KPI analysis UI - part 2 (server side).<br />
* 307208: PA model management: PA model status information to expression language.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218391: PA UI Flowchart selection does not clear automatically.<br />
* 218606: Edit mode is ON > Floating Action Buttons are not clickable.<br />
* 218626: PAPO: some popup menus are not closed properly in IE 11.<br />
* 218607: PAPO: popup menu is not displayed in IE 11.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218597: PA Exception details show null in QPR UI.<br />
* 218575: Incorrect results in conformance analysis calculation. <br />
* 218540: KPI analysis not working properly.<br />
* 218314: Variation analysis shows duplicate variations if there are excluded event types.<br />
* 218604: PA Excel client does not log enough during connection creation.<br />
* 218624: Estimatedmemory not calculated correctly when model not have events.<br />
* 218396: KPI analysis - ApplyAnalysisFilters. InvalidOperationException: Sequence contains no elements.´<br />
* 218628: PAPO: Error popup appears, "Error processing QPR ProcessAnalyzer request.<br />
* 218631: Performance improvements (Path analysis was slow).<br />
* 218485: ProcessAnalyzer Excel client cannot be removed from Programs and Features, as it wont show up there.<br />
* 217775: GetAnalysis(18) should write a progress log entry after each chunk.<br />
* 217653: SQL command not in log when ODBC connection failed.<br />
<br />
== QPR ProcessAnalyzer 2018.5 (release date 2018-07-17) ==<br />
Build number: 2018.5.0.37716, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights'''<br />
*QPR ProcessAnalyzer Deployment Package for QPR UI: The new version comes with preloaded QPR UI views that can instantly kickstart your Process Mining experience. These views are readymade and require no extra configuration. These views introduce new functionalities, such as ready made conformance views, for deploying a more varied Process Mining offering. <br />
*New Dashboard Design features: Panels can be now instantly developed and evaluated in viewer mode, allowing for a more powerful dashboard creation. The object placing logic has been overhauled, allowing for new options in creating dashboards. <br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307338: [[QPR_ProcessAnalyzer_API:_ResetModelCache | Web service support to load and drop PA models]].<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218536: PAPO: KPI Analysis should not be available from Control Windows.<br />
* 218519: The numerical values in QPR ProcessAnalyzer Influence Analysis were aligned to the left.<br />
* 217888: Selection lost from influence analysis table when user slightly adjusts browser window or panel/presentation object window size.<br />
* 218465: PAPO: Newly created filters are not displayed in the list.<br />
* 218556: PAPO: An unnecessary vertical scrollbar was shown after PAPO Case Analysis was resized.<br />
* 218520: PAPO: Filter does not recognize decimal separators.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218537: ODBC xlsx loading failed with data format issue.<br />
* 218495: Changing default filter does not drop cached model information.<br />
* 218550: Accessing projects from expression language fails in some cases.<br />
* 218549: Datatable import from Excel sheet data corruption if first column value is empty.<br />
* 218558: Errors in default.aspx. Login fails.<br />
<br />
== QPR ProcessAnalyzer 2018.4 (release date 2018-06-11) ==<br />
Build number: 2018.4.0.37669, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ODBC driver support for QPR ProcessAnalyzer: Use external data sources to create a dynamic model that is updated every time the model is loaded. Using the ODBC driver, the model data can be accessed from a separate data source. All the event data information can be defined in JSON format allowing for automatic model creation.<br />
* KPI Analysis: A new analysis is added to QPR ProcessAnalyzer. KPI Analysis utilizes the KPI expression engine for creating visualizations of data. KPI Analysis is a fully fledged analysis that can be used in conjuction with the existing QPR ProcessAnalyzer analysis for more focused results. In addition, KPI Analysis is available as a separate QPR UI view for creation of dashboards that present real-time data taken from QPR ProcessAnalyzer.<br />
* Tabular Analysis results updated with data types: Analysis featuring tabulated data are now automatically updated with correct data types. Automatic data types allow for exporting the data in a format that can be used in other compatible tools as the data types are automatically defined into the data.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307265: [[KPI_Analysis_(PAPO)|KPI analysis UI]] - part 1 (KPI).<br />
* 307278: The tabular analyses (e.g. Case analysis) in QPR ProcessAnalyzer UI now have the correct column data types based on the information from the QPR ProcessAnalyzer server.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307204: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Model Datasources|Load PA model from ODBC datasource]].<br />
* 307313: Expression language improvements - part 7 (performance).<br />
* 307317: Update new [[QPR_End_User_Software_License_Agreement|EULA]] to QPR ProcessAnalyzer.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218487: Influence analysis for Flowchart changes the flowchart settings.<br />
* 218498: No history entry is created while changing visibility threshold via stepper or context variable.<br />
* 218508: PAPO variation analysis should limit the queried number of variations.<br />
* 218513: PAPO settings buttons cover analysis content.<br />
* 218532: PAPO: Profiling analysis does not work with data loaded via ODBC.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218515: IIS crashes in kernel during Odbc query reading csv/xlsx file with Microsoft Access Text Driver and Microsoft Excel Driver.<br />
* 218484: ImportEvents fails in StartBackground mode.<br />
* 218525: InMemory CaseAnalysis ShowAllCases not work if there is cases without events.<br />
* 218463: Issue to install excel client (part 2).<br />
<br />
== QPR ProcessAnalyzer 2018.3 (release date 2018-04-23) ==<br />
Build number: 2018.3.0.37545, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
*Conformance Checking is supported in QPR ProcessAnalyzer. Using the KPI Expression Language as a basis, process mining models can be compared to BPMN notation and analyzed if the process data conforms to the BPMN design. These results are implemented in ChartView and KPI Expression Language allows them to be implemented into dashboards.<br />
*BPMN Editor has been added to ChartView. You can now import and design BPMN process maps for use in conformance analysis. The BPMN editor is a web component that is used in the browser, allowing for quick and easy process design. The designs can also be exported for further use.<br />
*Flowchart Visibility Settings have been overhauled with a new visual presentation. New stepper elements allow for more flexible flow threshold settings while maintaining a user-friendly approach.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307276: Remove PAPO Offline mode.<br />
* 307193 & 307298: The [[Flowchart_Analysis_(PAPO)#Visibility_Settings|Flowchart Visibility Settings]] were improved.<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307077: [[QPR_ProcessAnalyzer_System_Requirements#System_Requirements_for_QPR_ProcessAnalyzer_Server | Support for Windows Server 2016 (PA Service)]].<br />
* 307246: Expression function to calculate conformance to BPMN.<br />
* 307297: Expression language improvements - part 6.<br />
* 307301: In-memory memory usage optimizations.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218306: PAPO control window is affected by analysis window's 'Show as' setting.<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218241: PA Duration Analysis In-Memory - numbers for Events and Cases too high (focus flow).<br />
* 218456: Issue to install excel client (part 1).<br />
<br />
== QPR ProcessAnalyzer 2018.2 (release date 2018-03-12) ==<br />
Build number: 2018.2.0.37453, Model compatibility version: 2, Database version: 58, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
* Case Permissions have been added to the data security featureset. Case Permissions allow for limiting model visibility based on rules that reference the case attributes of a set model. Case permissions can refer to usernames or user groups, creating a link between the attributes and groups.<br />
* Influence Analysis for Case Attributes has been simplified. The feature presents basic information relating to the root causes when it is opened. If further information is needed, this can be accessed via the feature menu. <br />
* DataGrids support Excel exporting. You are now able to export data from fixed dashboards featuring datagrids. With this feature, you can take your data for further manipulation using Microsoft Excel.<br />
* Chartview has been improved with a new layout and excel exporting. The new layout allows for quicker access to creating charts using the ChartView tool. With the exporting functionality, the views created are exported for use in presentations in Microsoft Excel.<br />
* KPI Expression Language has been added with support for Influence Analysis for Case Attributes. This allows for further creation of dashboards with specific analysis result queries. Using the KPI expression language, dashboards can be made to present up-to-date data based on influence analysis results.<br />
* Dataset tag support for data visualization. Adding dataset tags will help in creating more dynamic chart presentations as the data can be inserted into the JSON settings of charts and datagrids. <br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307220: The [[Influence_Analysis_for_Case_Attributes_(PAPO)|Influence Analysis for Case Attributes]] settings now has a toggle for showing and hiding the detail columns.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307273: [[QPR ProcessAnalyzer Web Service API#Example| PA model JSON settings]].<br />
* 307269: [[QPR_ProcessAnalyzer_Model_JSON_Settings#Case_Permissions |Case permissions]].<br />
* 307261: PA InMemory core, part 8 (Path Analysis).<br />
* 307282: PA KPI's and expressions (part 5).<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218426: Using PAPO with customers model crashes PA Server (Entice Changes).<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218371: Event types aren't provided to PAPO by PA server.<br />
* 218372: Having multiple expressions in one selection item in a JSON filter does not work.<br />
* 218375: Empty comparison -setting with nonempty filter -setting causes influence analysis to return incorrect results.<br />
* 218380: PA Activation ends one day before the actual end date.<br />
* 218362: WebService GetAnalysisAsImage does not work.<br />
* 218389, 218397: Performance issues in PA in-memory core with multiple simultaneous users.<br />
* 218412: PercentageNumber property is not set properly in PA analyses.<br />
* 218410: Event attribute profiling event amount mismatch.<br />
* 218404: Using PAPO with customers model crashes PA Server (PA changes).<br />
* 218430: Pre-release mandatory PA bugfixes.<br />
<br />
== QPR ProcessAnalyzer 2018.1 (release date 2018-01-31) ==<br />
Build number: 2018.1.0.37330, Model compatibility version: 2, Database version: 57, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
* ChartView is introduced as a new QPR UI view. This interactive view allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. ChartView comes preloaded with numerous different presentation features for the creation of customized charts fit for any business need.<br />
* New Table Filtering for Data Table Views. A new Excel-style filtering feature has been added to the different analysis features, such as Influence Analysis for Case Attributes and Event Analysis. The feature allows the presentation and comparison of different data using robust filters.<br />
* The QPR UI version of QPR ProcessAnalyzer has an overhauled popup menu. Selecting different analysis and creating new filters is quicker and new icons have been added for added clarity.<br />
* XES filetype importing support. The IEEE TaskForce standardized XES logs are now supported by QPR ProcessAnalyzer. This filetype aims to unify the transactional data produced by information systems and makes them usable in tools used in data analysis. <br />
<br />
'''Full Features for QPR ProcessAnalyzer UI:'''<br />
* 307244: The various tables (e.g. Case Analysis) in QPR ProcessAnalyzer UI received filtering functionality familiar to the one in Microsoft Excel.<br />
* 307163: Popup menu improvements.<br />
* 307224: Cache model information into browser side.<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307271: PA InMemory core, part 7 (Canceling analysis).<br />
* 307247: XES Event log file format support.<br />
* 307257, 307270: PA KPI's and expressions (part 3, 4).<br />
* 307211: Enable custom data sources: Selections as JSON.<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218327: PAPO Grid view row selection issues when opening popup menu.<br />
* 218328: PAPO Missing null check in ModelState.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218324: Fixed an issue where a dataset wasn't refreshed when a context variable was changed from PAPO.<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218288: PA service installation with DeployPAService.ps1.<br />
* 218291: Problem with --#GetAnalysis type 31 (filter rules).<br />
* 218315: PAPO: InMemoryCore: Offline mode shows incorrect case attribute values.<br />
* 217922: Filtering Flow Table with Case Attribute is too slow.<br />
* 218321: PA core - Internal server error in PAPO when duration analysis result is empty.<br />
* 218322: Flow analysis results not always in same order (InMemory).<br />
* 218340: Not allow to delete default filter ("No access/Access denied").<br />
* 218345: Unknown filter rule. The given key was not present in the dictionary.<br />
* 218363: Attribute values are sent to clients as strings from InMemory profiling analysis.<br />
* 218365: PAPO: Settings etc. buttons not visible in the latest chrome version (automatically updated).<br />
* 218379: PAPO: Side panels visible in multi papo even if they should be closed and invisible.<br />
<br />
== QPR ProcessAnalyzer 2017.9 (release date 2017-12-19) ==<br />
Build number: 2017.9.0.37199, Model compatibility version: 2, Database version: 57, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
* The Filtering system on the WebUI has been updated. The user can now easily rename filters, add specific permissions to control privacy of the filters and delete filters easily. The filtering system has an improved interface for easier handling of the filters. <br />
* New Expression language for KPI calculation. This new language allows power users to create analysis that are customized to their needs and creates the possibility for caluclating KPIs inside the server core. This JSON based language allows users to take their analysis functions even further.<br />
* Other improvements in this release include performance improvements and further development of the in-memory mode.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307237: PAPO: There's now a new "DisabledFunctionalities" [[QPR_ProcessAnalyzer_Presentation_Object_(PAPO)#PAPO.27s_Context_Variables|context variable for using with PAPO]] to define which PAPO functionalities should not be.<br />
* 307173: It's now possible to edit the Name and Privacy of a filter in QPR ProcessAnalyzer UI, as well as delete a filter.<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307235: PA InMemory core, part 5 (Flow Analysis).<br />
* 307262: PA InMemory core, part 6 (Canceling model loading).<br />
* 307257: PA KPI's and expressions (part 2).<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218251: Multi-PAPO: Model page shows when model button of one papo has been disabled.<br />
* 218275: Change PA WS methods from GET to POST.<br />
* 218132: PAPO: Zoom change when item is selected from Variation Analysis.<br />
* 218196: PAPO: Variation Analysis: graph bar lengths doesn't match with data.<br />
* 218157: PAPO: QPR UI Graphics messed in Influence Analysis for Flowchart.<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218241: Duration Analysis In-Memory - numbers for Events, Median duration and Average duration are too high.<br />
* 218046: System.ArgumentException: Value of '-170' is not valid for 'red'. 'red' should be greater than or equal to 0 and less than or equal to 255.<br />
* 218275: Change PA WS methods from GET to POST.<br />
<br />
== QPR ProcessAnalyzer 2017.8 (release date 2017-11-07) ==<br />
Build number: 2017.8.0.37022, Model compatibility version: 2, Database version: 57, Stream version: 7.<br />
<br />
'''Release Highlights:'''<br />
* The QPR UI interface features a new feature: Profiling Event Analysis. Now you can drilldown to your events and see what event attributes the event types in your data contain. You can also use this knowledge to benchmark your process.<br />
* The Selection logic in the QPR UI has been updated. You no longer have to update after making a selection, as the selections are responsive and updated automatically. This leads to more responsive and effective analysis.<br />
* In-Memory Engine has been improved upon, allowing for more efficient analysis for small-to-mid-size models. This update gives you improved performance in your analysis operations. This feature applies for all analysis features and improves the performance of the software immensely, giving you faster operations.<br />
* The Excel Client has been preloaded with new and updated demo models that demonstrate the power of QPR ProcessAnalyzer. New Models include Healthcare and Insurance claims process models. These give you a great idea on how to utilize QPR ProcessAnalyzer.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307161: When selecting items in PAPO, the "Selected" context variables are now updated without the need to explicitly do the update. As a result, the "Select into UI Context" item was removed from the PAPO popup menu. This means that the TempSelectedActivities, TempSelectedTransitions, TempSelectedVariations, and TempSelectedCounts context variables were removed, and their functionality changed to be in the SelectedActivities, SelectedTransitions, SelectedVariations, and SelectedCounts context variables.<br />
* 307061: PAPO now has the [[Profiling_Case_Analysis_(PAPO)#Profiling_Event_Analysis|Profiling Event Analysis]] available.<br />
<br />
'''Features for QPR ProcessAnalyzer Server:'''<br />
* 307219: Excel client demo model changes.<br />
* 307216: To improve performance, QPR ProcessAnalyzer can now be configured to run the analyses in the server memory instead of the database.<br />
<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 218060: PAPO doesn't add transition duration but case duration filter rule type when Duration analysis shows transition duration.<br />
* 218039: PAPO: Analysis window has incorrect width when opening view (splitter issue).<br />
* 218036: PAPO: Web UI shows archived/recycled PA models.<br />
* 218100: PAPO: Once Analysis view show "No records to display" message, then switch to other analysis view is not possible for current model.<br />
* 218159: PAPO: Popup menus don't work in tabular analyses in IE11.<br />
* 218169: PAPO: SelectedAttributeType parameter in PA request has invalid value when switching model and applying filter that requires model change.<br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218148: InMemory: Include Only Event Types does not work with sampled models.<br />
* 218179: InMemory: Amount of cases in Duration analysis when flow is selected.<br />
<br />
== QPR ProcessAnalyzer 2017.7 (release date 2017-09-25) ==<br />
Build number: 2017.7.0.36871 <s>36762</s>, Model compatibility version: 2, Database version: 57, Stream version: 7. <br />
<br />
'''Release Highlights:'''<br />
* New In-Memory core for Process Analysis calculation. This server-side improvement can improve Analysis Performance speed up to 20 times faster than previous releases. This is achieved by offloading the memory functions directly to the application server where in the previous versions of the software, the SQL server handledthe workload.<br />
* This release also features different bug fixes and performance improvements, aiming to improve your process analysis experience. Combining these features with the new WebUI platform release, the implementation of your data for analysis and improvement is smoother than ever.<br />
<br />
'''Features for QPR ProcessAnalyzer UI:'''<br />
* 307060: CSS styling and grid configuration improvements (technical feature).<br />
'''Fixed bugs in QPR ProcessAnalyzer UI:'''<br />
* 217986: The pie (in profiling analysis) is rendered initially too small.<br />
* 217721: One extra scroll position / zoom -history entry created when PAPO is initialized. <br />
* 218052: Flowchart shows incorrect duration. <br />
* 217978: Profiling analysis is empty in Analysis window when opening splitter again. <br />
* 217926: Duration Analysis in control window doesn't select all "other" cases. <br />
* 217708: It is not possible to make multiselection using radial graph. <br />
* 218043: Issue with AnalysisWindowSize context variable. <br />
* 218058: Profiling Analysis for Case Attributes doesn't work when using numerical case attribute. <br />
* 218035: Switch model from filter: Error processing PA request. Invalid column name 'CA_VALUE_1290462'. <br />
'''Fixed bugs in QPR ProcessAnalyzer Server:'''<br />
* 218024: Add log writing to odbc query.<br />
* 217836: Error when opening filter in customer environment.<br />
* 217995: ImportCaseAttributes command does not import cases properly.<br />
* 218094: PA error text doesn't have information which value have problem.<br />
* 218145: Input String was not in the correct format error when opening customer model.<br />
<br />
== Old Releases ==<br />
See older releases in [[QPR ProcessAnalyzer Release Archive]]<br />
__NOTOC__</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=6394QPR ProcessAnalyzer System Requirements2017-10-13T08:36:55Z<p>TeeLeht: /* Suggested Hardware for QPR ProcessAnalyzer Pro */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
*** Windows Authentication<br />
** '''Application Development''':<br />
*** .Net Extensibility 4.5/4.6<br />
*** ASP.NET 4.5/4.6<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5/4.6 Features''':<br />
*** .Net 4.5/4.6<br />
*** ASP.Net 4.5/4.6<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 or newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
<br />
QPR ProcessAnalyzer has flexible deployment architecture and the load from multiple simultaneous users and multiple geographical locations around the world can balanced by using a distributed sql server cluster, replicated sql server machines and deploying multiple application servers<br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
'''QPR ProcessAnalyzer Pro Client hardware'''<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Mobile Client <br />
* 2 core processor<br />
<br />
'''QPR ProcessAnalyzer Pro Server hardware'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* Minimum<br />
** 32GB Memory<br />
** 4 processor cores<br />
** 200GB Disk<br />
* Recommended minimum for medium size data sets (1+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 4 processor cores<br />
** 300GB Disk<br />
* Recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 128GB Memory<br />
** 8 processor cores<br />
** 400GB Disk<br />
* Recommended minimum for very large data sets (100+ million events, multiple processes) with simultaneous users<br />
** 256GB Memory<br />
** 16 processor cores<br />
** 500GB Disk<br />
<br />
Option B - in-memory not in use - Analysis is done in SQL Server:<br />
* Minimum 4GB Memory 1 core 100 GB disk <br />
* Recommended: 8GB Memory 2 core 200 GB disk<br />
* Recommended for many simultaneous user: 16GB Memory 4 core 200 GB disk<br />
<br />
'''QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* minimum<br />
** 16GB Memory<br />
** 300GB - 1TB available SSD disk for SQL Server temp database<br />
** 500GB - 10TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
<br />
Option B - in-memory not in use - analysis is done in SQL Server:<br />
<br />
* minimum<br />
** 16GB Memory<br />
** 200GB available SSD disk for SQL Server temp database<br />
** 200GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* Recommended minimum for medium size data sets (1+ million events, multiple processes) with simultaneous users<br />
** 32GB Memory<br />
** 300GB available SSD disk for SQL Server temp database<br />
** 400GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 600GB available SSD disk for SQL Server temp database<br />
** 1 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 8 processor cores<br />
* recommended minimum for very large data sets (100+ million events, multiple processes) with many simultaneous users<br />
** 256 GB Memory<br />
** 1 TB available SSD disk for SQL Server temp database<br />
** 10 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 16 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=6393QPR ProcessAnalyzer System Requirements2017-10-13T08:34:43Z<p>TeeLeht: /* Suggested Hardware for QPR ProcessAnalyzer Pro */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
*** Windows Authentication<br />
** '''Application Development''':<br />
*** .Net Extensibility 4.5/4.6<br />
*** ASP.NET 4.5/4.6<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5/4.6 Features''':<br />
*** .Net 4.5/4.6<br />
*** ASP.Net 4.5/4.6<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 or newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
<br />
QPR ProcessAnalyzer has flexible deployment architecture and the load from multiple simultaneous users and multiple geographical locations around the world can balanced by using a distributed sql server cluster, replicated sql server machines and deploying multiple application servers<br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
'''QPR ProcessAnalyzer Pro Client hardware'''<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Mobile Client <br />
* 2 core processor<br />
<br />
'''QPR ProcessAnalyzer Pro Server hardware'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* Minimum<br />
** 32GB Memory<br />
** 4 processor cores<br />
** 200GB Disk<br />
* Recommended minimum for average size data sets (1+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 4 processor cores<br />
** 300GB Disk<br />
* Recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 128GB Memory<br />
** 8 processor cores<br />
** 400GB Disk<br />
* Recommended minimum for BIG DATA data sets (100+ million events, multiple processes) with simultaneous users<br />
** 256GB Memory<br />
** 16 processor cores<br />
** 500GB Disk<br />
<br />
Option B - in-memory not in use - Analysis is done in SQL Server:<br />
* Minimum 4GB Memory 1 core 100 GB disk <br />
* Recommended: 8GB Memory 2 core 200 GB disk<br />
* Recommended for many simultaneous user: 16GB Memory 4 core 200 GB disk<br />
<br />
'''QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* minimum<br />
** 16GB Memory<br />
** 300GB - 1TB available SSD disk for SQL Server temp database<br />
** 500GB - 10TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
<br />
Option B - in-memory not in use - analysis is done in SQL Server:<br />
<br />
* minimum<br />
** 16GB Memory<br />
** 300GB available SSD disk for SQL Server temp database<br />
** 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 600GB available SSD disk for SQL Server temp database<br />
** 1 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 8 processor cores<br />
* recommended minimum for BIG DATA (1+ billion events, multiple processes) with many simultaneous users<br />
** 256 GB Memory<br />
** 1 TB available SSD disk for SQL Server temp database<br />
** 10 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 16 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=6392QPR ProcessAnalyzer System Requirements2017-10-13T08:32:33Z<p>TeeLeht: /* Suggested Hardware for QPR ProcessAnalyzer Pro */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
*** Windows Authentication<br />
** '''Application Development''':<br />
*** .Net Extensibility 4.5/4.6<br />
*** ASP.NET 4.5/4.6<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5/4.6 Features''':<br />
*** .Net 4.5/4.6<br />
*** ASP.Net 4.5/4.6<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 or newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
<br />
QPR ProcessAnalyzer has flexible deployment architecture and the load from multiple simultaneous users and multiple geographical locations around the world can balanced by using a distributed sql server cluster, replicated sql server machines and deploying multiple application servers<br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
'''QPR ProcessAnalyzer Pro Client hardware'''<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Mobile Client <br />
* 2 core processor<br />
<br />
'''QPR ProcessAnalyzer Pro Server hardware'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* Minimum<br />
** 32GB Memory<br />
** 4 processor cores<br />
** 200GB Disk<br />
* Recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 8 processor cores<br />
** 400GB Disk<br />
* Recommended minimum for BIG DATA data sets (100+ million events, multiple processes) with simultaneous users<br />
** 256GB Memory<br />
** 16 processor cores<br />
** 800GB Disk<br />
<br />
Option B - in-memory not in use - Analysis is done in SQL Server:<br />
* Minimum 4GB Memory 1 core 100 GB disk <br />
* Recommended: 8GB Memory 2 core 200 GB disk<br />
* Recommended for many simultaneous user: 16GB Memory 4 core 200 GB disk<br />
<br />
'''QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server'''<br />
<br />
Option A - in-memory usage enabled - analysis is done in Pro Server<br />
* minimum<br />
** 16GB Memory<br />
** 300GB - 1TB available SSD disk for SQL Server temp database<br />
** 500GB - 10TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
<br />
Option B - in-memory not in use - analysis is done in SQL Server:<br />
<br />
* minimum<br />
** 16GB Memory<br />
** 300GB available SSD disk for SQL Server temp database<br />
** 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 600GB available SSD disk for SQL Server temp database<br />
** 1 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 8 processor cores<br />
* recommended minimum for BIG DATA (1+ billion events, multiple processes) with many simultaneous users<br />
** 256 GB Memory<br />
** 1 TB available SSD disk for SQL Server temp database<br />
** 10 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 16 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=6391QPR ProcessAnalyzer System Requirements2017-10-13T08:30:42Z<p>TeeLeht: /* Suggested Hardware for QPR ProcessAnalyzer Pro */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
*** Windows Authentication<br />
** '''Application Development''':<br />
*** .Net Extensibility 4.5/4.6<br />
*** ASP.NET 4.5/4.6<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5/4.6 Features''':<br />
*** .Net 4.5/4.6<br />
*** ASP.Net 4.5/4.6<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 or newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
<br />
QPR ProcessAnalyzer has flexible deployment architecture and the load from multiple simultaneous users and multiple geographical locations around the world can balanced by using a distributed sql server cluster, replicated sql server machines and deploying multiple application servers<br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Pro Client hardware:<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Mobile Client <br />
* 2 core processor<br />
<br />
QPR ProcessAnalyzer Pro Server hardware:<br />
<br />
Option A - in-memory usage enabled:<br />
* Minimum<br />
** 32GB Memory<br />
** 4 processor cores<br />
** 200GB Disk<br />
* Recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 8 processor cores<br />
** 400GB Disk<br />
* Recommended minimum for BIG DATA data sets (100+ million events, multiple processes) with simultaneous users<br />
** 256GB Memory<br />
** 16 processor cores<br />
** 800GB Disk<br />
<br />
Option B - in-memory not in use - Analysis is done in SQL Server machine:<br />
* Minimum 4GB Memory 1 core 100 GB disk <br />
* Recommended: 8GB Memory 2 core 200 GB disk<br />
* Recommended for many simultaneous user: 16GB Memory 4 core 200 GB disk<br />
<br />
QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server<br />
<br />
Option A - in-memory usage enabled - analysis is done in Application server:<br />
* minimum<br />
** 16GB Memory<br />
** 300GB - 1TB available SSD disk for SQL Server temp database<br />
** 500GB - 10TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
<br />
Option B - in-memory not in use - analysis is done in SQL Server:<br />
<br />
* minimum<br />
** 16GB Memory<br />
** 300GB available SSD disk for SQL Server temp database<br />
** 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* recommended minimum for large data sets (10+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 600GB available SSD disk for SQL Server temp database<br />
** 1 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 8 processor cores<br />
* recommended minimum for BIG DATA (1+ billion events, multiple processes) with many simultaneous users<br />
** 256 GB Memory<br />
** 1 TB available SSD disk for SQL Server temp database<br />
** 10 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 16 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=4717QPR ProcessAnalyzer Release Notes2017-05-23T07:51:00Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2017.4 (planned release date 23.5.2017, life cycle phase: Active) ==<br />
Build number: 2017.4.0.36424, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''PAPO Features:'''<br/><br />
- 307022: The Profiling Analysis can now be used in the Control window in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] to select cases for the analysis in the Analysis window.<br><br />
- 307003: The buttons in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object (PAPO)]] were rearranged.<br><br />
- 307057: The Duration, Profiling, Influence, and Variation Analyses in [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] now have generic and some analysis specific settings supported.<br><br />
- 306969: The QPR ProcessAnalyzer Presentation Object now supports the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Influence_Analysis_for_Case_Attributes|Influence Analysis for Case Attributes]] in the grid format.<br><br />
- 307030: [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Duration_Analysis|Duration Analysis]] can now be used in the {{DriverNameForTheDay}} window of the QPR ProcessAnalyzer Presentation Object.<br><br />
'''PA Features:'''<br/><br />
- 403516: Consolidate event names in PA example Excels (SAP_OrderToCash.xlsx, SAP_OrderToCash v2.xlsx and SAP_OrderToCash_Extended.xlsx).<br><br />
'''Fixed bugs:'''<br/><br />
- 217845: Create Filter from CaseAttributeTrends with PA script doesn't work.<br/><br />
- 217830: Tab delimiter is not taken into use when datatable imported.<br/><br />
- 217902: SqlException thrown when opening influence analysis on a filter without any case attributes.<br/><br />
<br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2017.5 (planned release date 4.7.2017) ==<br />
Build number: 2017.5.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- ....<br><br />
'''Fixed bugs:'''<br/><br />
- ....<br/><br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2017.3 (release date 11.04.2017, life cycle phase: Mature) ===<br />
Build number: 2017.3.0.36338 <s>36324</s>, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305862: There now are new StartTime Limit and Maximum Text Length settings to be used with the [[Operation Log]] and the Operation Log Analysis [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command.<br/><br />
- 306983: PAPO - Highlight selected flow label in flowchart: selected flow labels are now clearly visible on the flowchart. Selected objects are highlighted on the flowchart.<br/><br />
- 306986 & 307017: The QPR ProcessAnalyzer Presentation Object (PAPO) now has a new [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Control_Window_and_Analysis_Window|window system]].<br/><br />
- 306987: PAPO - in-memory Variation analysis: Variation analysis is now supported in in-memory mode.<br/><br />
- 307000: The model shown in the QPR ProcessAnalyzer Presentation Object (PAPO) can now be changed via a menu.<br><br />
- 306999: The Start and End symbols in the QPR ProcessAnalyzer Presentation Object (PAPO) flowchart were updated.<br><br />
'''Fixed bugs:'''<br/><br />
- 217679: PA cannot add new case Attribute values to exising case via Excel if CaseId starts with leading zero.<br/><br />
- 217790: Filtering is too slow.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.2 (release date 28.02.2017, life cycle phase: Mature) ===<br />
Build number: 2017.2.0.36218, Model compatibility version: 2, Database version: 56, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306966: Performance optimizations into PA database.<br/><br />
- 306930: Improved messages to SQL Queries.<br/><br />
- 306910: Implement importSalesforceQuery support for TLS 1.1. Note that the support from PA Salesforce Integration service has been discontinued.<br/><br />
- 306964: Make it possible to transfer the contents of a filter efficiently to MobileDashboard.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217605: Operation log throws some exception.<br/><br />
- 217546: Slow access to project by project name. ETL parameter: (SELECT 'ProjectName', 'name').<br/><br />
- 217363: ScriptLauncher should LogOff.<br/><br />
- 217618, 217636: PA Excel Client doesn't connect to PA Server when Windows performance counter is not accessible (part 1 and 2).<br/><br />
- 217650: System.DBNull objects returned from event analysis when IncludeCaseAttributeValues is used.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.1 (release date 16.01.2017, life cycle phase: Mature) ===<br />
Build number: 2017.1.0.36111, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306899: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23SendEmail|SendEmail]] script command now supports sending attachments.<br/><br />
- 306896: A [[Open_R_Setup#Case_Prediction_Example_Script|case prediction Open R example script]] was added to QPR ProcessAnalyzer wiki.<br/><br />
- 306484: There is now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportEventsIncremental|ImportEventsIncremental]] script command for synchronizing event data between a data table that holds event data and the specified model.<br/><br />
- 306906: The [[Script Log]] entries are now written to the database at the same time as the script is being run. There is also a new Script Log Report analysis type for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command for administrators to access script logs.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217526: Log entries written as errors even if they are not.<br/><br />
- 217545: Session expires exceedingly often in a service deployed in AWS behind load balancer.<br/><br />
- 217591: Special characters in PA script parameters cause script to fail and hide the actual root cause of the failure.<br/><br />
<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.7 (release date 2.12.2016, life cycle phase: Mature) ===<br />
Build number: 2016.7.0.35938, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306677: There now is a possibility to remove the [[Filtering#Runtime_Selection|runtime selection]] and reopen the current analysis by selecting "Change > Clear Runtime Selection". <br/><br />
- 306873: In the QPR ProcessAnalyzer Service web.config, there is now a [[Installing_QPR_ProcessAnalyzer_Server#Configure_Response_Polling_Interval_for_QPR_MobileDashboard|ResponsePollingInterval]] setting to be used if QPR ProcessAnalyzer data is to be accessed via QPR MobileDashboard.<br/><br />
- 306860: New [[Flowchart_Analysis#Influence_Flowchart_Analysis|Influence Flowchart Analysis]] allows users to see how the process differs between two sets of cases. <br/><br />
- 306874: There's now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CreateFilter | CreateFilter]] script command available, that enables making QPR ProcessAnalyzer filters in QPR MobileDashboard by calling a QPR ProcessAnalyzer script there.<br/><br />
- 306750: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new 'IncludeSelection' parameter.<br/><br />
- 306342: There now is a new [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|@_CurrentScriptId]] script variable that enables making loops in scripts without hard coding the script id into the script.<br/><br />
- 306891: There are now two new analysis types to be used with the GetAnalysis command [[Analysis Parameters|FilterReport and FilterRuleReport]].<br/><br />
- 306614: Remove Excel client login attempt to global-url.<br/><br />
- 306864: Some performance optimizations were done for QPR ProcessAnalyzer core and [[Installing_QPR_ProcessAnalyzer_Server#Adjust_SQL_Server_Settings|recommendations for some SQL Server settings]] were added.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217430: Insert bulk failed due to a schema change of the target table.<br/><br />
- 217447: Remove LocalDb check if PA Xpress not activated.<br/><br />
- 217446: Possible to import over 1 million events with Xpress standard and after that it is not possible to login to Xpress anymore.<br/><br />
- 217395: Write exception text in progress log and server log file if an exception is caught.<br/><br />
- 217465: Clarification about Open R setup on server side.<br/><br />
- 216370: Stack traces missing in script run logs.<br/><br />
- 217467: Caught unhandled exception. Import invalid pacm file with Pro.<br/><br />
- 217478: Minimum Flow Volume setting changed in an unexpected way.<br/><br />
- 217500: Fix comparison flowchart color algorithm.<br/><br />
- 217356: Improve log writing [Data import fails for timeout (SAP error text missing in ClientSideImport)].<br/><br />
- 217493: Analysis title, benchmark drop down menu not updated properly.<br/><br />
- 217525: EVT_ORDER based index is missing in event cache tables.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.6 (release date 24.10.2016, life cycle phase: Mature) ===<br />
Build number: 2016.6.0.35754, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] is now available for flowchart benchmarking.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: Support for [[Open_R_Setup | Open R]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Mature) ===<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Retired) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Retired) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: End-Of-Life)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: End-Of-Life) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (release date 1.11.2012, life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (release date 18.9.2012, life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (release date 30.8.2012, life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (release date 21.6.2012, life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (release date 15.5.2012, life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (release date 27.4.2012, life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (release date 29.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (release date 7.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (release date 17.2.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (release date 27.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (release date 5.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (release date 19.12.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (release date 25.11.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/><br />
<br />
=== QPR ProcessAnalyzer 2.0 (release date 24.2.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) using Excel Client <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=4716QPR ProcessAnalyzer Release Notes2017-05-23T07:50:05Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2017.4 (planned release date 23.5.2017, life cycle phase: Active) ==<br />
Build number: 2017.4.0.36424, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''PAPO Features:'''<br/><br />
- 307022: The Profiling Analysis can now be used in the Control window in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] to select cases for the analysis in the Analysis window.<br><br />
- 307003: The buttons in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object (PAPO)]] were rearranged.<br><br />
- 307057: The Duration, Profiling, Influence, and Variation Analyses in [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] now have generic and some analysis specific settings supported.<br><br />
- 306969: The QPR ProcessAnalyzer Presentation Object now supports the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Influence_Analysis_for_Case_Attributes|Influence Analysis for Case Attributes]] in the grid format.<br><br />
- 307030: [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Duration_Analysis|Duration Analysis]] can now be used in the {{DriverNameForTheDay}} window of the QPR ProcessAnalyzer Presentation Object.<br><br />
'''PA Features:'''<br/><br />
- 403516: Consolidate event names in PA example Excels (SAP_OrderToCash.xlsx, SAP_OrderToCash v2.xlsx and SAP_OrderToCash_Extended.xlsx).<br><br />
'''Fixed bugs:'''<br/><br />
- 217845: Create Filter from CaseAttributeTrends with PA script doesn't work.<br/><br />
- 217830: Tab delimiter is not taken into use when datatable imported.<br/><br />
- 217902: SqlException thrown when opening influence analysis on a filter without any case attributes.<br/><br />
<br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2017.5 (planned release date 4.7.2017) ==<br />
Build number: 2017.5.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- ....<br><br />
'''Fixed bugs:'''<br/><br />
- ....<br/><br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2017.3 (release date 11.04.2017, life cycle phase: Mature) ===<br />
Build number: 2017.3.0.36338 <s>36324</s>, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305862: There now are new StartTime Limit and Maximum Text Length settings to be used with the [[Operation Log]] and the Operation Log Analysis [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command.<br/><br />
- 306983: PAPO - Highlight selected flow label in flowchart: selected flow labels are now clearly visible on the flowchart. Selected objects are highlighted on the flowchart.<br/><br />
- 306986 & 307017: The QPR ProcessAnalyzer Presentation Object (PAPO) now has a new [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Control_Window_and_Analysis_Window|window system]].<br/><br />
- 306987: PAPO - in-memory Variation analysis: Variation analysis is now supported in in-memory mode.<br/><br />
- 307000: The model shown in the QPR ProcessAnalyzer Presentation Object (PAPO) can now be changed via a menu.<br><br />
- 306999: The Start and End symbols in the QPR ProcessAnalyzer Presentation Object (PAPO) flowchart were updated.<br><br />
'''Fixed bugs:'''<br/><br />
- 217679: PA cannot add new case Attribute values to exising case via Excel if CaseId starts with leading zero.<br/><br />
- 217790: Filtering is too slow.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.2 (release date 28.02.2017, life cycle phase: Mature) ===<br />
Build number: 2017.2.0.36218, Model compatibility version: 2, Database version: 56, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306966: Performance optimizations into PA database.<br/><br />
- 306930: Improved messages to SQL Queries.<br/><br />
- 306910: Implement importSalesforceQuery support for TLS 1.1. Note that the support from PA Salesforce Integration service has been discontinued.<br/><br />
- 306964: Make it possible to transfer the contents of a filter efficiently to MobileDashboard.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217605: Operation log throws some exception.<br/><br />
- 217546: Slow access to project by project name. ETL parameter: (SELECT 'ProjectName', 'name').<br/><br />
- 217363: ScriptLauncher should LogOff.<br/><br />
- 217618, 217636: PA Excel Client doesn't connect to PA Server when Windows performance counter is not accessible (part 1 and 2).<br/><br />
- 217650: System.DBNull objects returned from event analysis when IncludeCaseAttributeValues is used.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.1 (release date 16.01.2017, life cycle phase: Mature) ===<br />
Build number: 2017.1.0.36111, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306899: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23SendEmail|SendEmail]] script command now supports sending attachments.<br/><br />
- 306896: A [[Open_R_Setup#Case_Prediction_Example_Script|case prediction Open R example script]] was added to QPR ProcessAnalyzer wiki.<br/><br />
- 306484: There is now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportEventsIncremental|ImportEventsIncremental]] script command for synchronizing event data between a data table that holds event data and the specified model.<br/><br />
- 306906: The [[Script Log]] entries are now written to the database at the same time as the script is being run. There is also a new Script Log Report analysis type for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command for administrators to access script logs.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217526: Log entries written as errors even if they are not.<br/><br />
- 217545: Session expires exceedingly often in a service deployed in AWS behind load balancer.<br/><br />
- 217591: Special characters in PA script parameters cause script to fail and hide the actual root cause of the failure.<br/><br />
<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.7 (release date 2.12.2016, life cycle phase: Mature) ===<br />
Build number: 2016.7.0.35938, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306677: There now is a possibility to remove the [[Filtering#Runtime_Selection|runtime selection]] and reopen the current analysis by selecting "Change > Clear Runtime Selection". <br/><br />
- 306873: In the QPR ProcessAnalyzer Service web.config, there is now a [[Installing_QPR_ProcessAnalyzer_Server#Configure_Response_Polling_Interval_for_QPR_MobileDashboard|ResponsePollingInterval]] setting to be used if QPR ProcessAnalyzer data is to be accessed via QPR MobileDashboard.<br/><br />
- 306860: New [[Flowchart_Analysis#Influence_Flowchart_Analysis|Influence Flowchart Analysis]] allows users to see how the process differs between two sets of cases. <br/><br />
- 306874: There's now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CreateFilter | CreateFilter]] script command available, that enables making QPR ProcessAnalyzer filters in QPR MobileDashboard by calling a QPR ProcessAnalyzer script there.<br/><br />
- 306750: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new 'IncludeSelection' parameter.<br/><br />
- 306342: There now is a new [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|@_CurrentScriptId]] script variable that enables making loops in scripts without hard coding the script id into the script.<br/><br />
- 306891: There are now two new analysis types to be used with the GetAnalysis command [[Analysis Parameters|FilterReport and FilterRuleReport]].<br/><br />
- 306614: Remove Excel client login attempt to global-url.<br/><br />
- 306864: Some performance optimizations were done for QPR ProcessAnalyzer core and [[Installing_QPR_ProcessAnalyzer_Server#Adjust_SQL_Server_Settings|recommendations for some SQL Server settings]] were added.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217430: Insert bulk failed due to a schema change of the target table.<br/><br />
- 217447: Remove LocalDb check if PA Xpress not activated.<br/><br />
- 217446: Possible to import over 1 million events with Xpress standard and after that it is not possible to login to Xpress anymore.<br/><br />
- 217395: Write exception text in progress log and server log file if an exception is caught.<br/><br />
- 217465: Clarification about Open R setup on server side.<br/><br />
- 216370: Stack traces missing in script run logs.<br/><br />
- 217467: Caught unhandled exception. Import invalid pacm file with Pro.<br/><br />
- 217478: Minimum Flow Volume setting changed in an unexpected way.<br/><br />
- 217500: Fix comparison flowchart color algorithm.<br/><br />
- 217356: Improve log writing [Data import fails for timeout (SAP error text missing in ClientSideImport)].<br/><br />
- 217493: Analysis title, benchmark drop down menu not updated properly.<br/><br />
- 217525: EVT_ORDER based index is missing in event cache tables.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.6 (release date 24.10.2016, life cycle phase: Mature) ===<br />
Build number: 2016.6.0.35754, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] is now available for flowchart benchmarking.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: Support for [[Open_R_Setup | Open R]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Mature) ===<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Retired) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Retired) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: End-Of-Life)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: End-Of-Life) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (release date 1.11.2012, life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (release date 18.9.2012, life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (release date 30.8.2012, life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (release date 21.6.2012, life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (release date 15.5.2012, life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (release date 27.4.2012, life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (release date 29.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (release date 7.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (release date 17.2.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (release date 27.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (release date 5.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (release date 19.12.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (release date 25.11.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/><br />
<br />
=== QPR ProcessAnalyzer 2.0 - (release date 24.2.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) using Excel Client <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=4715QPR ProcessAnalyzer Release Notes2017-05-23T07:43:16Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2017.4 (planned release date 23.5.2017, life cycle phase: Active) ==<br />
Build number: 2017.4.0.36424, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''PAPO Features:'''<br/><br />
- 307022: The Profiling Analysis can now be used in the Control window in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] to select cases for the analysis in the Analysis window.<br><br />
- 307003: The buttons in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object (PAPO)]] were rearranged.<br><br />
- 307057: The Duration, Profiling, Influence, and Variation Analyses in [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] now have generic and some analysis specific settings supported.<br><br />
- 306969: The QPR ProcessAnalyzer Presentation Object now supports the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Influence_Analysis_for_Case_Attributes|Influence Analysis for Case Attributes]] in the grid format.<br><br />
- 307030: [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Duration_Analysis|Duration Analysis]] can now be used in the {{DriverNameForTheDay}} window of the QPR ProcessAnalyzer Presentation Object.<br><br />
'''PA Features:'''<br/><br />
- 403516: Consolidate event names in PA example Excels (SAP_OrderToCash.xlsx, SAP_OrderToCash v2.xlsx and SAP_OrderToCash_Extended.xlsx).<br><br />
'''Fixed bugs:'''<br/><br />
- 217845: Create Filter from CaseAttributeTrends with PA script doesn't work.<br/><br />
- 217830: Tab delimiter is not taken into use when datatable imported.<br/><br />
- 217902: SqlException thrown when opening influence analysis on a filter without any case attributes.<br/><br />
<br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2017.5 (planned release date 4.7.2017) ==<br />
Build number: 2017.5.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- ....<br><br />
'''Fixed bugs:'''<br/><br />
- ....<br/><br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2017.3 (release date 11.04.2017, life cycle phase: Mature) ===<br />
Build number: 2017.3.0.36338 <s>36324</s>, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305862: There now are new StartTime Limit and Maximum Text Length settings to be used with the [[Operation Log]] and the Operation Log Analysis [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command.<br/><br />
- 306983: PAPO - Highlight selected flow label in flowchart: selected flow labels are now clearly visible on the flowchart. Selected objects are highlighted on the flowchart.<br/><br />
- 306986 & 307017: The QPR ProcessAnalyzer Presentation Object (PAPO) now has a new [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Control_Window_and_Analysis_Window|window system]].<br/><br />
- 306987: PAPO - in-memory Variation analysis: Variation analysis is now supported in in-memory mode.<br/><br />
- 307000: The model shown in the QPR ProcessAnalyzer Presentation Object (PAPO) can now be changed via a menu.<br><br />
- 306999: The Start and End symbols in the QPR ProcessAnalyzer Presentation Object (PAPO) flowchart were updated.<br><br />
'''Fixed bugs:'''<br/><br />
- 217679: PA cannot add new case Attribute values to exising case via Excel if CaseId starts with leading zero.<br/><br />
- 217790: Filtering is too slow.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.2 (release date 28.02.2017, life cycle phase: Mature) ===<br />
Build number: 2017.2.0.36218, Model compatibility version: 2, Database version: 56, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306966: Performance optimizations into PA database.<br/><br />
- 306930: Improved messages to SQL Queries.<br/><br />
- 306910: Implement importSalesforceQuery support for TLS 1.1. Note that the support from PA Salesforce Integration service has been discontinued.<br/><br />
- 306964: Make it possible to transfer the contents of a filter efficiently to MobileDashboard.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217605: Operation log throws some exception.<br/><br />
- 217546: Slow access to project by project name. ETL parameter: (SELECT 'ProjectName', 'name').<br/><br />
- 217363: ScriptLauncher should LogOff.<br/><br />
- 217618, 217636: PA Excel Client doesn't connect to PA Server when Windows performance counter is not accessible (part 1 and 2).<br/><br />
- 217650: System.DBNull objects returned from event analysis when IncludeCaseAttributeValues is used.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.1 (release date 16.01.2017, life cycle phase: Mature) ===<br />
Build number: 2017.1.0.36111, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306899: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23SendEmail|SendEmail]] script command now supports sending attachments.<br/><br />
- 306896: A [[Open_R_Setup#Case_Prediction_Example_Script|case prediction Open R example script]] was added to QPR ProcessAnalyzer wiki.<br/><br />
- 306484: There is now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportEventsIncremental|ImportEventsIncremental]] script command for synchronizing event data between a data table that holds event data and the specified model.<br/><br />
- 306906: The [[Script Log]] entries are now written to the database at the same time as the script is being run. There is also a new Script Log Report analysis type for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command for administrators to access script logs.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217526: Log entries written as errors even if they are not.<br/><br />
- 217545: Session expires exceedingly often in a service deployed in AWS behind load balancer.<br/><br />
- 217591: Special characters in PA script parameters cause script to fail and hide the actual root cause of the failure.<br/><br />
<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.7 (release date 2.12.2016, life cycle phase: Mature) ===<br />
Build number: 2016.7.0.35938, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306677: There now is a possibility to remove the [[Filtering#Runtime_Selection|runtime selection]] and reopen the current analysis by selecting "Change > Clear Runtime Selection". <br/><br />
- 306873: In the QPR ProcessAnalyzer Service web.config, there is now a [[Installing_QPR_ProcessAnalyzer_Server#Configure_Response_Polling_Interval_for_QPR_MobileDashboard|ResponsePollingInterval]] setting to be used if QPR ProcessAnalyzer data is to be accessed via QPR MobileDashboard.<br/><br />
- 306860: New [[Flowchart_Analysis#Influence_Flowchart_Analysis|Influence Flowchart Analysis]] allows users to see how the process differs between two sets of cases. <br/><br />
- 306874: There's now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CreateFilter | CreateFilter]] script command available, that enables making QPR ProcessAnalyzer filters in QPR MobileDashboard by calling a QPR ProcessAnalyzer script there.<br/><br />
- 306750: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new 'IncludeSelection' parameter.<br/><br />
- 306342: There now is a new [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|@_CurrentScriptId]] script variable that enables making loops in scripts without hard coding the script id into the script.<br/><br />
- 306891: There are now two new analysis types to be used with the GetAnalysis command [[Analysis Parameters|FilterReport and FilterRuleReport]].<br/><br />
- 306614: Remove Excel client login attempt to global-url.<br/><br />
- 306864: Some performance optimizations were done for QPR ProcessAnalyzer core and [[Installing_QPR_ProcessAnalyzer_Server#Adjust_SQL_Server_Settings|recommendations for some SQL Server settings]] were added.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217430: Insert bulk failed due to a schema change of the target table.<br/><br />
- 217447: Remove LocalDb check if PA Xpress not activated.<br/><br />
- 217446: Possible to import over 1 million events with Xpress standard and after that it is not possible to login to Xpress anymore.<br/><br />
- 217395: Write exception text in progress log and server log file if an exception is caught.<br/><br />
- 217465: Clarification about Open R setup on server side.<br/><br />
- 216370: Stack traces missing in script run logs.<br/><br />
- 217467: Caught unhandled exception. Import invalid pacm file with Pro.<br/><br />
- 217478: Minimum Flow Volume setting changed in an unexpected way.<br/><br />
- 217500: Fix comparison flowchart color algorithm.<br/><br />
- 217356: Improve log writing [Data import fails for timeout (SAP error text missing in ClientSideImport)].<br/><br />
- 217493: Analysis title, benchmark drop down menu not updated properly.<br/><br />
- 217525: EVT_ORDER based index is missing in event cache tables.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.6 (release date 24.10.2016, life cycle phase: Mature) ===<br />
Build number: 2016.6.0.35754, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] is now available for flowchart benchmarking.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: Support for [[Open_R_Setup | Open R]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Mature) ===<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Retired) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Retired) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: End-Of-Life)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: End-Of-Life) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (release date 1.11.2012, life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (release date 18.9.2012, life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (release date 30.8.2012, life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (release date 21.6.2012, life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (release date 15.5.2012, life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (release date 27.4.2012, life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (release date 29.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (release date 7.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (release date 17.2.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (release date 27.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (release date 5.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (release date 19.12.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (release date 25.11.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=4714QPR ProcessAnalyzer Release Notes2017-05-23T07:40:21Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2017.4 (planned release date 23.5.2017, life cycle phase: Active) ==<br />
Build number: 2017.4.0.36424, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''PAPO Features:'''<br/><br />
- 307022: The Profiling Analysis can now be used in the Control window in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] to select cases for the analysis in the Analysis window.<br><br />
- 307003: The buttons in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object (PAPO)]] were rearranged.<br><br />
- 307057: The Duration, Profiling, Influence, and Variation Analyses in [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] now have generic and some analysis specific settings supported.<br><br />
- 306969: The QPR ProcessAnalyzer Presentation Object now supports the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Influence_Analysis_for_Case_Attributes|Influence Analysis for Case Attributes]] in the grid format.<br><br />
- 307030: [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Duration_Analysis|Duration Analysis]] can now be used in the {{DriverNameForTheDay}} window of the QPR ProcessAnalyzer Presentation Object.<br><br />
'''PA Features:'''<br/><br />
- 403516: Consolidate event names in PA example Excels (SAP_OrderToCash.xlsx, SAP_OrderToCash v2.xlsx and SAP_OrderToCash_Extended.xlsx).<br><br />
'''Fixed bugs:'''<br/><br />
- 217845: Create Filter from CaseAttributeTrends with PA script doesn't work.<br/><br />
- 217830: Tab delimiter is not taken into use when datatable imported.<br/><br />
- 217902: SqlException thrown when opening influence analysis on a filter without any case attributes.<br/><br />
<br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2017.5 (planned release date 4.7.2017) ==<br />
Build number: 2017.5.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- ....<br><br />
'''Fixed bugs:'''<br/><br />
- ....<br/><br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2017.3 (release date 11.04.2017, life cycle phase: Mature) ===<br />
Build number: 2017.3.0.36338 <s>36324</s>, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305862: There now are new StartTime Limit and Maximum Text Length settings to be used with the [[Operation Log]] and the Operation Log Analysis [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command.<br/><br />
- 306983: PAPO - Highlight selected flow label in flowchart: selected flow labels are now clearly visible on the flowchart. Selected objects are highlighted on the flowchart.<br/><br />
- 306986 & 307017: The QPR ProcessAnalyzer Presentation Object (PAPO) now has a new [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Control_Window_and_Analysis_Window|window system]].<br/><br />
- 306987: PAPO - in-memory Variation analysis: Variation analysis is now supported in in-memory mode.<br/><br />
- 307000: The model shown in the QPR ProcessAnalyzer Presentation Object (PAPO) can now be changed via a menu.<br><br />
- 306999: The Start and End symbols in the QPR ProcessAnalyzer Presentation Object (PAPO) flowchart were updated.<br><br />
'''Fixed bugs:'''<br/><br />
- 217679: PA cannot add new case Attribute values to exising case via Excel if CaseId starts with leading zero.<br/><br />
- 217790: Filtering is too slow.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.2 (release date 28.02.2017, life cycle phase: Mature) ===<br />
Build number: 2017.2.0.36218, Model compatibility version: 2, Database version: 56, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306966: Performance optimizations into PA database.<br/><br />
- 306930: Improved messages to SQL Queries.<br/><br />
- 306910: Implement importSalesforceQuery support for TLS 1.1. Note that the support from PA Salesforce Integration service has been discontinued.<br/><br />
- 306964: Make it possible to transfer the contents of a filter efficiently to MobileDashboard.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217605: Operation log throws some exception.<br/><br />
- 217546: Slow access to project by project name. ETL parameter: (SELECT 'ProjectName', 'name').<br/><br />
- 217363: ScriptLauncher should LogOff.<br/><br />
- 217618, 217636: PA Excel Client doesn't connect to PA Server when Windows performance counter is not accessible (part 1 and 2).<br/><br />
- 217650: System.DBNull objects returned from event analysis when IncludeCaseAttributeValues is used.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.1 (release date 16.01.2017, life cycle phase: Mature) ===<br />
Build number: 2017.1.0.36111, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306899: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23SendEmail|SendEmail]] script command now supports sending attachments.<br/><br />
- 306896: A [[Open_R_Setup#Case_Prediction_Example_Script|case prediction Open R example script]] was added to QPR ProcessAnalyzer wiki.<br/><br />
- 306484: There is now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportEventsIncremental|ImportEventsIncremental]] script command for synchronizing event data between a data table that holds event data and the specified model.<br/><br />
- 306906: The [[Script Log]] entries are now written to the database at the same time as the script is being run. There is also a new Script Log Report analysis type for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command for administrators to access script logs.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217526: Log entries written as errors even if they are not.<br/><br />
- 217545: Session expires exceedingly often in a service deployed in AWS behind load balancer.<br/><br />
- 217591: Special characters in PA script parameters cause script to fail and hide the actual root cause of the failure.<br/><br />
<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.7 (release date 2.12.2016, life cycle phase: Mature) ===<br />
Build number: 2016.7.0.35938, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306677: There now is a possibility to remove the [[Filtering#Runtime_Selection|runtime selection]] and reopen the current analysis by selecting "Change > Clear Runtime Selection". <br/><br />
- 306873: In the QPR ProcessAnalyzer Service web.config, there is now a [[Installing_QPR_ProcessAnalyzer_Server#Configure_Response_Polling_Interval_for_QPR_MobileDashboard|ResponsePollingInterval]] setting to be used if QPR ProcessAnalyzer data is to be accessed via QPR MobileDashboard.<br/><br />
- 306860: New [[Flowchart_Analysis#Influence_Flowchart_Analysis|Influence Flowchart Analysis]] allows users to see how the process differs between two sets of cases. <br/><br />
- 306874: There's now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CreateFilter | CreateFilter]] script command available, that enables making QPR ProcessAnalyzer filters in QPR MobileDashboard by calling a QPR ProcessAnalyzer script there.<br/><br />
- 306750: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new 'IncludeSelection' parameter.<br/><br />
- 306342: There now is a new [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|@_CurrentScriptId]] script variable that enables making loops in scripts without hard coding the script id into the script.<br/><br />
- 306891: There are now two new analysis types to be used with the GetAnalysis command [[Analysis Parameters|FilterReport and FilterRuleReport]].<br/><br />
- 306614: Remove Excel client login attempt to global-url.<br/><br />
- 306864: Some performance optimizations were done for QPR ProcessAnalyzer core and [[Installing_QPR_ProcessAnalyzer_Server#Adjust_SQL_Server_Settings|recommendations for some SQL Server settings]] were added.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217430: Insert bulk failed due to a schema change of the target table.<br/><br />
- 217447: Remove LocalDb check if PA Xpress not activated.<br/><br />
- 217446: Possible to import over 1 million events with Xpress standard and after that it is not possible to login to Xpress anymore.<br/><br />
- 217395: Write exception text in progress log and server log file if an exception is caught.<br/><br />
- 217465: Clarification about Open R setup on server side.<br/><br />
- 216370: Stack traces missing in script run logs.<br/><br />
- 217467: Caught unhandled exception. Import invalid pacm file with Pro.<br/><br />
- 217478: Minimum Flow Volume setting changed in an unexpected way.<br/><br />
- 217500: Fix comparison flowchart color algorithm.<br/><br />
- 217356: Improve log writing [Data import fails for timeout (SAP error text missing in ClientSideImport)].<br/><br />
- 217493: Analysis title, benchmark drop down menu not updated properly.<br/><br />
- 217525: EVT_ORDER based index is missing in event cache tables.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.6 (release date 24.10.2016, life cycle phase: Mature) ===<br />
Build number: 2016.6.0.35754, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] is now available for flowchart benchmarking.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: Support for [[Open_R_Setup | Open R]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Mature) ===<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Retired) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Retired) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: End-Of-Life)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: End-Of-Life) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (release date 1.11.2012, life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (release date 21.6.2012, life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (release date 15.5.2012, life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (release date 27.4.2012, life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (release date 29.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (release date 7.3.2012, life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (release date 17.2.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (release date 27.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (release date 5.1.2012, life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (release date 19.12.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (release date 25.11.2011, life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=4713QPR ProcessAnalyzer Release Notes2017-05-23T07:31:32Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2017.4 (planned release date 23.5.2017, life cycle phase: Active) ==<br />
Build number: 2017.4.0.36424, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''PAPO Features:'''<br/><br />
- 307022: The Profiling Analysis can now be used in the Control window in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] to select cases for the analysis in the Analysis window.<br><br />
- 307003: The buttons in the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object (PAPO)]] were rearranged.<br><br />
- 307057: The Duration, Profiling, Influence, and Variation Analyses in [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#QPR_ProcessAnalyzer_Presentation_Object_.28PAPO.29|QPR ProcessAnalyzer Presentation Object]] now have generic and some analysis specific settings supported.<br><br />
- 306969: The QPR ProcessAnalyzer Presentation Object now supports the [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Influence_Analysis_for_Case_Attributes|Influence Analysis for Case Attributes]] in the grid format.<br><br />
- 307030: [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Duration_Analysis|Duration Analysis]] can now be used in the {{DriverNameForTheDay}} window of the QPR ProcessAnalyzer Presentation Object.<br><br />
'''PA Features:'''<br/><br />
- 403516: Consolidate event names in PA example Excels (SAP_OrderToCash.xlsx, SAP_OrderToCash v2.xlsx and SAP_OrderToCash_Extended.xlsx).<br><br />
'''Fixed bugs:'''<br/><br />
- 217845: Create Filter from CaseAttributeTrends with PA script doesn't work.<br/><br />
- 217830: Tab delimiter is not taken into use when datatable imported.<br/><br />
- 217902: SqlException thrown when opening influence analysis on a filter without any case attributes.<br/><br />
<br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2017.5 (planned release date 4.7.2017) ==<br />
Build number: 2017.5.0.xxxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- ....<br><br />
'''Fixed bugs:'''<br/><br />
- ....<br/><br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2017.3 (release date 11.04.2017, life cycle phase: Mature) ===<br />
Build number: 2017.3.0.36338 <s>36324</s>, Model compatibility version: 2, Database version: 57, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305862: There now are new StartTime Limit and Maximum Text Length settings to be used with the [[Operation Log]] and the Operation Log Analysis [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command.<br/><br />
- 306983: PAPO - Highlight selected flow label in flowchart: selected flow labels are now clearly visible on the flowchart. Selected objects are highlighted on the flowchart.<br/><br />
- 306986 & 307017: The QPR ProcessAnalyzer Presentation Object (PAPO) now has a new [[QPR_ProcessAnalyzer_in_QPR_MobileDashboard#Control_Window_and_Analysis_Window|window system]].<br/><br />
- 306987: PAPO - in-memory Variation analysis: Variation analysis is now supported in in-memory mode.<br/><br />
- 307000: The model shown in the QPR ProcessAnalyzer Presentation Object (PAPO) can now be changed via a menu.<br><br />
- 306999: The Start and End symbols in the QPR ProcessAnalyzer Presentation Object (PAPO) flowchart were updated.<br><br />
'''Fixed bugs:'''<br/><br />
- 217679: PA cannot add new case Attribute values to exising case via Excel if CaseId starts with leading zero.<br/><br />
- 217790: Filtering is too slow.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.2 (release date 28.02.2017, life cycle phase: Mature) ===<br />
Build number: 2017.2.0.36218, Model compatibility version: 2, Database version: 56, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306966: Performance optimizations into PA database.<br/><br />
- 306930: Improved messages to SQL Queries.<br/><br />
- 306910: Implement importSalesforceQuery support for TLS 1.1. Note that the support from PA Salesforce Integration service has been discontinued.<br/><br />
- 306964: Make it possible to transfer the contents of a filter efficiently to MobileDashboard.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217605: Operation log throws some exception.<br/><br />
- 217546: Slow access to project by project name. ETL parameter: (SELECT 'ProjectName', 'name').<br/><br />
- 217363: ScriptLauncher should LogOff.<br/><br />
- 217618, 217636: PA Excel Client doesn't connect to PA Server when Windows performance counter is not accessible (part 1 and 2).<br/><br />
- 217650: System.DBNull objects returned from event analysis when IncludeCaseAttributeValues is used.<br/><br />
<br />
=== QPR ProcessAnalyzer 2017.1 (release date 16.01.2017, life cycle phase: Mature) ===<br />
Build number: 2017.1.0.36111, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306899: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23SendEmail|SendEmail]] script command now supports sending attachments.<br/><br />
- 306896: A [[Open_R_Setup#Case_Prediction_Example_Script|case prediction Open R example script]] was added to QPR ProcessAnalyzer wiki.<br/><br />
- 306484: There is now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23ImportEventsIncremental|ImportEventsIncremental]] script command for synchronizing event data between a data table that holds event data and the specified model.<br/><br />
- 306906: The [[Script Log]] entries are now written to the database at the same time as the script is being run. There is also a new Script Log Report analysis type for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command for administrators to access script logs.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217526: Log entries written as errors even if they are not.<br/><br />
- 217545: Session expires exceedingly often in a service deployed in AWS behind load balancer.<br/><br />
- 217591: Special characters in PA script parameters cause script to fail and hide the actual root cause of the failure.<br/><br />
<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.7 (release date 2.12.2016, life cycle phase: Mature) ===<br />
Build number: 2016.7.0.35938, Model compatibility version: 2, Database version: 55, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306677: There now is a possibility to remove the [[Filtering#Runtime_Selection|runtime selection]] and reopen the current analysis by selecting "Change > Clear Runtime Selection". <br/><br />
- 306873: In the QPR ProcessAnalyzer Service web.config, there is now a [[Installing_QPR_ProcessAnalyzer_Server#Configure_Response_Polling_Interval_for_QPR_MobileDashboard|ResponsePollingInterval]] setting to be used if QPR ProcessAnalyzer data is to be accessed via QPR MobileDashboard.<br/><br />
- 306860: New [[Flowchart_Analysis#Influence_Flowchart_Analysis|Influence Flowchart Analysis]] allows users to see how the process differs between two sets of cases. <br/><br />
- 306874: There's now a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CreateFilter | CreateFilter]] script command available, that enables making QPR ProcessAnalyzer filters in QPR MobileDashboard by calling a QPR ProcessAnalyzer script there.<br/><br />
- 306750: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new 'IncludeSelection' parameter.<br/><br />
- 306342: There now is a new [[Data_Extraction,_Transformation,_and_Loading#Script_Variables|@_CurrentScriptId]] script variable that enables making loops in scripts without hard coding the script id into the script.<br/><br />
- 306891: There are now two new analysis types to be used with the GetAnalysis command [[Analysis Parameters|FilterReport and FilterRuleReport]].<br/><br />
- 306614: Remove Excel client login attempt to global-url.<br/><br />
- 306864: Some performance optimizations were done for QPR ProcessAnalyzer core and [[Installing_QPR_ProcessAnalyzer_Server#Adjust_SQL_Server_Settings|recommendations for some SQL Server settings]] were added.<br/><br />
'''Fixed bugs:'''<br/><br />
- 217430: Insert bulk failed due to a schema change of the target table.<br/><br />
- 217447: Remove LocalDb check if PA Xpress not activated.<br/><br />
- 217446: Possible to import over 1 million events with Xpress standard and after that it is not possible to login to Xpress anymore.<br/><br />
- 217395: Write exception text in progress log and server log file if an exception is caught.<br/><br />
- 217465: Clarification about Open R setup on server side.<br/><br />
- 216370: Stack traces missing in script run logs.<br/><br />
- 217467: Caught unhandled exception. Import invalid pacm file with Pro.<br/><br />
- 217478: Minimum Flow Volume setting changed in an unexpected way.<br/><br />
- 217500: Fix comparison flowchart color algorithm.<br/><br />
- 217356: Improve log writing [Data import fails for timeout (SAP error text missing in ClientSideImport)].<br/><br />
- 217493: Analysis title, benchmark drop down menu not updated properly.<br/><br />
- 217525: EVT_ORDER based index is missing in event cache tables.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.6 (release date 24.10.2016, life cycle phase: Mature) ===<br />
Build number: 2016.6.0.35754, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] is now available for flowchart benchmarking.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: Support for [[Open_R_Setup | Open R]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Mature) ===<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Retired) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Retired) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Retired) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: End-Of-Life) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: End-Of-Life)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: End-Of-Life) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (release date 1.11.2012, life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (release date 21.6.2012, life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (release date 15.5.2012, life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=3368QPR ProcessAnalyzer System Requirements2016-11-17T06:53:25Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP .NET 3.5 & 4.5<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** .NET Environment 3.5<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Server<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server<br />
* minimum<br />
** 16GB Memory<br />
** 300GB available SSD disk for SQL Server temp database<br />
** 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 4 processor cores<br />
* recommended minimum for large data sets (100+ million events, multiple processes) with simultaneous users<br />
** 64GB Memory<br />
** 600GB available SSD disk for SQL Server temp database<br />
** 1 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 8 processor cores<br />
* recommended minimum for BIG DATA (1+ billion events, multiple processes) with many simultaneous users<br />
** 256 GB Memory<br />
** 1 TB available SSD disk for SQL Server temp database<br />
** 10 TB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
** 16 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=3331QPR ProcessAnalyzer System Requirements2016-11-08T11:39:06Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP .NET 3.5 & 4.5<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** .NET Environment 3.5<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== System Requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server are as follows:<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Pro Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Server<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Pro Database Server - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=3294QPR ProcessAnalyzer Release Notes2016-10-21T08:19:50Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2016.5 (release date 19.8.2016, life cycle phase: Active) ==<br />
Build number: 2016.5.0.35492, Model compatibility version: 2, Database version: 54, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306728: Added support for Microsoft SQL Server 2016 for QPR ProcessAnalyzer Service.<br/><br />
Note: When doing migration to SQL server 2016, the read-only flag for the sandbox database should be switched off. After the migration is done switch the read-only flag back on.<br/><br />
- 306727: The Profiling Analysis now has a new [[Profiling_Analysis#Trend|Trend]] type analysis that shows the amount of cases that have the particular value for the selected case or event attribute for any particular period.<br/><br />
- 306733: In addition to the Case Attribute Influence Analysis that has existed before, there's now a new [[Influence_Analysis#Process_Path_Influence_Analysis_Columns|Influence Analysis - Process Path]] available.<br/><br />
- 306536: Microsoft .NET Framework 4.6.1 has been taken into use.<br/><br />
Note: This component needs to be installed on the machine running PA service.<br/><br />
- 306756: The Profiling Analysis [[Profiling_Analysis#Trend|Trend]] type analysis supports case filtering based on the selected cells in the analysis.<br/><br />
- 306754: [[Common QPR Authentication]] now supports QPR MobileDashboard.<br/><br />
- 306760: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new "ForceAnalysisResultType" parameter to support putting all analysis types into tabular format, so the data can more easily be used in scripting environments and QPR MobileDashboard.<br/><br />
'''Bugs:'''<br/><br />
- 213348: Analysis settings are now persistent in PA Excel Client.<br/><br />
- 216399: Fixed importing script with big script logs.<br/><br />
- 216447: Fixed auto-sizing for the comments field of A1 cell in Excel Client.<br/><br />
- 216748: Improve line numbers in ETL script error log.<br/><br />
- 216863: Improved error message shown when connection to PA service is lost.<br/><br />
- 216934: Transition flow issue when unselecting "Show duration" in Path analysis.<br/><br />
- 216938: Path Analysis: remove event type filtering and simplify case filtering.<br/><br />
- 216952: Improved error message shown when trying to connect to PA service with older version of Script Launcher.<br/><br />
- 216960: Added documentation for DeleteModelsInRecycleBinOnStartup parameter of PA_CONFIGURATION table.<br/><br />
- 216972: The Start Time column formatting in the sample file LoanApproval.xlsx has to be updated.<br/><br />
- 216973: Improved error messages shown when the amount of data exceeds the user quota.<br/><br />
- 217034: Fixed the issue with the wrong number of cases and events shown in Path Analysis with benchmark settings.<br/><br />
- 217213: Fixed the issue in Excel Client when the analysis details text in the header was truncated.<br/><br />
- 217229: Update PA service requirements and support material.<br/><br />
- 217232: Documentation bug: ScriptLauncher fails to load SAP dlls in some environments.<br/><br />
- 217244: Optimized the query for getting all models.<br/><br />
- 217254: Update Influence_Analysis wiki page.<br/><br />
- 217264: Columns lenght too narrow in some analysis.<br/><br />
- 217269: Wrong term used in PA.<br/><br />
- 217275: Multi-select drilldown from flowchart and flow analysis behave inconsistently.<br/><br />
- 216734: Add description for Sample size inheritance when creating filters based on existing ones.<br/><br />
- 217074: Curved flows drawn even if they should be straight.<br/><br />
- 216994: Missing icon in windows - operation aborted.<br/><br />
- 216863: The error message, for broken connection from client side, is not user-friendly.<br/><br />
- 217294: Adding a bookmark in Profiling Analysis fails in Web Client.<br/><br />
- 216447: COMException occurs unexpectedly while using excel client (set_AutoSize).<br/><br />
- 217244: Slow MainService.GetModels query.<br/><br />
- 216399: ScriptDeployer fails to import scripts with big script logs.<br/><br />
- 216952: Unclear error message - ScriptLauncher.<br/><br />
- 216960: DeleteModelsInRecycleBinOnStartup requires support material and API test for verification.<br/><br />
- 217017: PA Manage script icon is not visible in Excel 2007.<br/><br />
- 216973: Improve error messages of amount of data exceeded situations to more specific.<br/><br />
- 217279: Deleting model is slow and requires lots of SQL Server disk space.<br/><br />
- 216910: Case costs can be imported as strings in when case attributes are updated.<br/><br />
- 217309: Runtime filtering from Events - chart analysis works inconsistently.<br/><br />
- 217212: Layout issue when exporting filter.<br/><br />
- 217325: Influence analysis terminology.<br/><br />
<br/><br />
<br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2016.6 (planned release date 25.10.2016) ==<br />
Build number: 2016.6.0.xxxx, Model compatibility version: x, Database version: xx, Stream version: x.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306662: There now is a new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] script command, that makes all script commands that are placed after it be run in background, so that the user can continue using QPR ProcessAnalyzer Excel Client while the script is being run.<br/><br />
- 306314: QPR ProcessAnalyzer Xpress now comes with Microsoft SQL Server 2016 Express LocalDB. Due to this, support for 32-bit operating systems is dropped. Support for 32-bit Microsoft Office Excel remains.<br/><br />
- 403132: Epicor and ServiceNow demo models have been added.<br/><br />
- 305476: Flowchart benchmarking now has a new [[Benchmarking#Benchmarking_with_Comparison_Mode|Comparison Mode]] available.<br/><br />
- 306559: There now is a [[Influence_Analysis#Duration_Influence_Analysis_Columns|Duration Influence Analysis]] that shows which case attributes have the most effect into the durations of cases or the selected flow.<br/><br />
- 306842: [[Open_R_Setup | Open R setup]] and example script for clustering / case prediction.<br/><br />
- 306859: IWA support for [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService | --#CallWebService]].<br/><br />
'''Bugs:'''<br/><br />
- 217341: NaN-double values cause problems in json parsers.<br/><br />
- 216725: PA service stops randomly.<br/><br />
- 217290: Extra error message shown after "Unsupported Operation" error in Excel Client.<br/><br />
- 217037: QPR Tab is disabled in Excel client.<br/><br />
- 217404: Drill-down from duration analysis is slow.<br/><br />
- 217419: Deadlock in SqlCore.SetScript.<br/><br />
- 217435: Update labels in dropdown menu for Duration Analysis.<br/><br />
- 217432: Group By Settings chosen in the Duration Analyses will not be adapted to Influence Analysis/Influence Analysis will not work.<br/><br />
<br />
== Past Releases ==<br />
<br />
=== Hotfix for QPR ProcessAnalyzer 2016.4 (release date 15.6.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35184, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 217233: ScriptLauncher doesn't write anything into log if the script file does not exist.<br/><br />
- 217217: Unclear instruction on how to update PA service installation to new version.<br/><br />
- 217223: Importing events from current sheet - start time should be datetime.<br/><br />
- 217245: User rights query suspended (slow execution).<br/><br />
- 217249: Import filter with eventtype fails.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.4 (release date 30.5.2016, life cycle phase: Mature) ===<br />
Build number: 2016.4.0.35096, Model compatibility version: 2, Database version: 53, Stream version: 7.<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 305509: [[QPR_ProcessAnalyzer_Excel_Add-In|Back -button]] to Excel Client.<br/><br />
- 306666: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a new analysis type: Event Type Trends.<br/><br />
- 306697: The [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|GetAnalysis]] script command now has a the 'ShowAllCases' parameter available for case analyses. The parameter can be used in conjunction with the new [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23RemoveCases|RemoveCases]] command to remove unwanted cases from a model.<br/><br />
- 306695: The Event Type Analysis now as the [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type with selectable analysis settings in the user interface.<br/><br />
- 306698: The Event Type Analysis [[Event_Types#Event_Type_Analysis_in_the_Trends_Mode|Trends]] analysis type supports case filtering based on the selected cells in the analysis.<br/><br />
'''Bugs:'''<br/><br />
- 217116: Fix common authentication for QPR Portal bookmark links.<br/><br />
- 217132: ReloginInterval and ReloginDuration can't be configured from command line.<br/><br />
- 217159: COMException after opening a xlsx-file.<br/><br />
- 217126: Run script manager crash or not start if focus is cell editor.<br/><br />
- 217104: Operation log exception in Excel 2007.<br/><br />
- 216967: KeyNotFoundException: The given key was not present in the dictionary in Common.Core.SqlCore.DoReadOnlyGetModels.<br/><br />
- 217094: Influence results are not sorted correctly when MaximumCount is used when viewing from Mobile dashboard.<br/><br />
- 217156: COMException occurs when running a script with #ShowReport twice with selected activity box.<br/><br />
- 216810: Attempt to write negative values into progress bar in progress status dialog.<br/><br />
- 216813: Connection timeouts are hard coded to all PA database connections.<br/><br />
- 217029: Case attribute dependent filter rules get corrupted when exporting a view to pacm file.<br/><br />
- 217176: Problems running scriptlauncher performance tests.<br/><br />
- 217216: Update QPR PA About box.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.3 (release date 19.4.2016, life cycle phase: Mature) ===<br />
Build number: 2016.3.0.34871, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306647 & 306660: The [[Analysis_Parameters|A1 cell comments]] and the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts|ShowReport and GetAnalysis commands]] now support automatic creation of pivot tables.<br/><br />
- 306439: The [[QPR ProcessAnalyzer ScriptLauncher]] now supports passing configuration settings as command line parameters. It can also do CSV exports of the scripts being run, and it can pass analysis parameters to the scripts being run.<br/><br />
- 306655: QPR ProcessAnalyzer now has new look & feel design for the user interface.<br/><br />
- 306658: Show Script reports in MobileDashboard (and [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23GetAnalysis|run scripts]]).<br/><br />
'''Bugs:'''<br/><br />
- 216554: Selecting a green or red flow from Path analysis and going to Cases shows a empty Cases list.<br/><br />
- 216928: Creating filters from Path Analysis with selected starting/ending transitions doesn't work properly.<br/><br />
- 216927: Selection from Path Analysis doesn't work when there are loops in the flowchart.<br/><br />
- 216948: Timeout period elapsed prior to completion of the operation.<br/><br />
- 216460: Examples with parameters of different GetAnalysis types missing from PA Wiki.<br/><br />
- 217015: EventId's stored to INT cause problem (cause 2G event limit).<br/><br />
- 217026: secureWebHttp endpoint does not work at all in PA service.<br/><br />
- 217023: Sorting order: influence analysis internal sorting should be sorted by contribution.<br/><br />
- 216971: The QPR ProcessAnalyzer home link is broken and leads to nowhere.<br/><br />
- 216933: Ambiguous column name error when clicking on Cases analysis.<br/><br />
- 216991: Open any analysis from Profiling view causes invalid runtime filter if nothing valid is selected.<br/><br />
- 216805: --#GetAnalysis for Model report ('AnalysisType', '21') cannot get "Compatibility Version" information.<br/><br />
- 217001: Error message displayed regarding VSTO during PA installation.<br/><br />
- 216830: Production URL is pointing to a wrong end point in Salesforce integration.<br/><br />
- 217043: API tests stop responding after certain tests have been run.<br/><br />
- 217035: Flowchart analysis headers show incorrect counts while benchmarking.<br/><br />
- 216862: GetAnalysis(6) for event analysis is slow and eventually even crashes (probably consumes lots of memory).<br/><br />
- 216975: ScriptLauncher runScript with Text.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.2 (release date 8.3.2016, life cycle phase: Mature) ===<br />
Build number: 2016.2.0.34637, Model compatibility version: 2, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306619: Refactor event cache table generation<br/><br />
- 306616: The filter definitions are now available for all filter types in the Filter Rule Properties dialog.<br/><br />
- 306617: The [[Analysis Parameters|A1 cell in the analyses]] now has the added information of total processing time of the analysis (query and Excel client processing), Project name, User name, and Filter rules.<br/><br />
- 306367: The [[Excel Log]] is now in use by default. In addition, the implementation now uses log4net which provides log rotation capabilities among other features.<br/><br />
- 306637: SalesforceURL parameter was added to #ImportSalesforceQuery command.<br/><br />
- 306625: The QPR ProcessAnalyzer Service can now be [[Installing_QPR_ProcessAnalyzer_Server#Activating_by_Using_the_QPR.ProcessAnalyzer.ActivationUtility.exe|activated]] manually via email to QPR Customer Care in case the automatic activation is not possible.<br/><br />
- 306634: The [[Influence Analysis]] now has a new setting "Weighted by Case Cost" for adding case-specific weights for individual cases.<br/><br />
'''Bugs:'''<br/><br />
- 216831: Fixed an issue in drilling down from benchmarked Flowchart Analysis.<br/><br />
- 216866: Fixed an error thrown when opening Variation Analysis view from Path Analysis.<br/><br />
- 216871: Fixed an issue with Variation Analysis that gives 0 for event count in the first line.<br/><br />
- 216859: Fixed an issue with initializedb.sql and optimizedb.sql missing from the PA_Deploy.zip file.<br/><br />
- 216440: Changed the error shown when opening bookmarks with invalid benchmark settings.<br/><br />
- 216872: Added a notification that only the sampled cases are copied to a new a model or exported to a .pacm file.<br/><br />
- 216924: Changed the default context for script manager to be "Project" instead of "Model".<br/><br />
<br />
=== Hotfix with version number 2016.1 (release date 10.2.2016, life cycle phase: Mature) ===<br />
Build number: 2016.1.0.34489, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216715: Excel Client go unstable state if session expired when session information dialog is open.<br/><br />
- 216719: Fixed the issue in Excel Client where the number of events was not checked before starting animation.<br/><br />
- 216786: Fixed the issue with corrupted bookmarks.<br/><br />
- 216814: Refactored flow analysis predecessor and successor calculation.<br/><br />
- 216464: Fixed the error message shown when user inputs activation key in an invalid format while activating via email.<br/><br />
- 216847: Fixed an issue with filtering with include only cases, takes a lot of time.<br/><br />
- 216856: Fixed an issue about Duration filter that does not work correctly when used together with event type filters.<br/><br />
- 216848: Fixed an issue TA: Model export is taking too long time.<br/><br />
<br />
=== QPR ProcessAnalyzer 2016.1 (release date 18.1.2016, life cycle phase: Mature) ===<br />
Build number: 2016.1.0.33400, Model compatibility version: 1, Database version: 53, Stream version: 7<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Features:'''<br/><br />
- 306474: QPR ProcessAnalyzer now supports Microsoft Office 2016 suite.<br/><br />
- 306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
- 306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
- 306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
- 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.<br/><br />
- 306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 306581: Case attributes source model functionality has been removed.<br/><br />
- 306597: InstallShield was upgraded to version 2015.<br />
<br/><br />
'''Bugs:'''<br/><br />
- 216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
- 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.<br/><br />
- 216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
- 216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
- 216770: Fixed a performance issue where unnecessary temporary tables were created when there were no runtime filters being used.<br/><br />
- 216763: Fixed Profiling Analysis so that by default it should always be opened for case attributes.<br/><br />
- 216781: Fixed performance issue in Flow analysis with selected Start or End Event attributes.<br/><br />
- 216789: Removed automatic retry mechanism for the case when EndpointNotFoundException was thrown.<br/><br />
- 216792: Fixed an issue in Flow analysis with incorrect values for starter events when event attribute based benchmarking is performed.<br />
<br />
=== Hotfix with version number 2015.5 (release date 7.10.2015, life cycle phase: Mature) ===<br />
Build number: 2015.5.0.33631, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Mature) ===<br />
Build number: 2015.5.0.33554, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
- 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.<br/><br />
- 306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
- 306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
- 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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
<br />
=== Hotfix with version number 2015.5 (release date 26.8.2015, life cycle phase: Mature) ===<br />
Build number: 2015.5.0.33323, Model compatibility version: 0, Database version: 44, Stream version: 6<br/><br />
Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
=== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Retired)===<br />
<br />
Build number: 2015.4.0.33243, Model compatibility version: 0, Database version: 43, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Retired) ===<br />
<br />
Build number: 2015.3.0.32848, Model compatibility version: 0, Database version: 42, Stream version: 6<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Retired) ===<br />
Build number: 2015.2.0.32408, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: End-of-life) ===<br />
Build number: 2015.1.0.32120, Model compatibility version: 0, Database version: 40, Stream version: 6<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: End-of-life) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Category:QPR_ProcessAnalyzer&diff=3063Category:QPR ProcessAnalyzer2016-09-16T12:34:56Z<p>TeeLeht: Created page with "Pages of this QPR ProcessAnalyzer category list functionalities available for QPR ProcessAnalyzer product users."</p>
<hr />
<div>Pages of this QPR ProcessAnalyzer category list functionalities available for QPR ProcessAnalyzer product users.</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Manage_Users_and_Groups&diff=3062Manage Users and Groups2016-09-16T12:33:33Z<p>TeeLeht: </p>
<hr />
<div>The Manage Users dialog is used to create, edit, and delete users and user groups and manage user roles. In addition, you can access the User Rights Report.<br/><br />
<br />
It should be noted that when making changes to your own user's roles or user groups, in order for them to take effect, you should relogin to the product.<br />
<br />
== Viewing and Editing User Properties ==<br />
As a non-administrator user, you can view and edit only your own user properties.<br />
#Select the user name from the list and click the '''Properties''' button.<br />
#In the User Properties dialog that opens, you can change the Login Name, Full Name, E-Mail address, Password, and Description.<br />
#To apply the changes, click '''OK'''.<br />
<br />
To join a group, click '''Join''', input the '''Group Member Join-In Token''', and click '''OK'''.<br />
<br />
== Viewing the User Rights Report ==<br />
As a non-administrator user, you can view only your own User Rights Report.<br />
<br />
The [[User Rights Report]] can be opened by clicking the '''Report''' button. A sheet containing the User Rights is created.<br />
<br />
'''Depending on the role, the following actions are available.'''<br />
<br />
== Creating a User or a User Group ==<br />
#In the left side of the dialog, select either '''Users''' or '''Groups''' according to which one you want to create.<br />
#Click the '''Create''' button and define the properties in the dialog that opens.<br />
#Close the creation dialog by clicking '''OK'''.<br />
<br />
Note that creating a User Group requires that the creator has the Administrator, Model Creator, or Evaluator role for the <All> Project level.<br />
<br />
When creating a new User Group or viewing the properties of a User Group, you can create a '''Join-In Token''' for a regular group member or a hidden group member. By clicking '''Join''' in the User Properties dialog and inputting the token there, the user can join the group for which the token was made.<br />
<br />
== Assigning a User to a User Group ==<br />
#Select the user from the list on the left side of the dialog.<br />
#In the right side of the dialog, select '''Group Memberships'''.<br />
#Select the group from the '''Group''' drop-down menu.<br />
#Click '''Add'''.<br />
<br />
== Assigning a User Role to a User or a User Group ==<br />
#Select the user or the user group from the list on the left side of the dialog.<br />
#Select the specific project to which you want to assign the role from the '''Project''' drop-down list. Selecting "<All>" will apply the role to all projects available.<br />
#Select the Role from the '''Role''' drop-down list.<br />
#Click '''Add'''.<br />
<br />
{{Template:User Rights}}<br />
<br />
== Removing a User Role from a User or a User Group ==<br />
#Select the user or the user group from the list on the left side of the dialog.<br />
#Select the model from the right side of the dialog.<br />
#Click '''Remove'''.<br />
<br />
== Use Cases ==<br />
{{How to Publish Results to Others}}<br />
<br />
<br />
{{About Version}}<br />
<br />
[[Category: QPR ProcessAnalyzer]]<br />
[[Category: User Rights]]<br />
[[Category: Publishing]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Wiki&diff=3061QPR ProcessAnalyzer Wiki2016-09-16T12:30:20Z<p>TeeLeht: </p>
<hr />
<div>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.<br />
<br />
== [[Installing QPR ProcessAnalyzer]] ==<br />
See the [[Quick Installation Instructions]] for the basic steps of installing QPR ProcessAnalyzer. More detailed instructions are given on the [[Installing QPR ProcessAnalyzer]] page.<br />
<br />
== [[Get Started]] ==<br />
Get started with QPR ProcessAnalyzer by following these [[Get Started|first steps]].<br />
<br />
== [[QPR ProcessAnalyzer Excel Add-In | Using QPR ProcessAnalyzer Excel Client]] ==<br />
See the [[QPR ProcessAnalyzer Excel Add-In]] page for information on how to use QPR ProcessAnalyzer Excel Client.<br />
<br/><br />
[[File:Ribbon.png|986px|link=QPR ProcessAnalyzer Excel Add-In]]<br />
<br />
== [[Data Extraction, Transformation, and Loading]] ==<br />
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.<br/><br />
Learn the basics of creating ETL scripts in SQL and using them in QPR ProcessAnalyzer on the [[QPR ProcessAnalyzer ETL Tutorial | ETL Tutorial]] page.<br />
<br />
== [[QPR ProcessAnalyzer in QPR MobileDashboard]] ==<br />
QPR MobileDashboard is the common responsive web user interface for all QPR products.<br />
<br />
== [[Integration Service for Salesforce Cloud]] ==<br />
QPR Software provides an [[Integration Service for Salesforce Cloud|integration service]] for importing data from Salesforce Cloud service.<br />
<br />
== [[QPR Connector for QPR ProcessAnalyzer]] ==<br />
The [[QPR Connector for QPR ProcessAnalyzer]] is a tool for uploading data from an SQL database into a QPR ProcessAnalyzer Service for analysis purposes.<br />
<br />
== [[QPR ProcessAnalyzer Apps]] ==<br />
[[QPR ProcessAnalyzer Apps]] is a page containing small apps that extend the use of QPR ProcessAnalyzer.<br />
<br />
== [[QPR ProcessAnalyzer Certification]] ==<br />
[[QPR ProcessAnalyzer Certification]] page provides information about taking the QPR ProcessAnalyzer certification test.<br />
<br />
== [[Agreements]] ==<br />
[[Agreements]] page contains the end user license and software as a service agreements.<br />
<br />
__NOTOC__</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=StartBackground_Script_Examples&diff=3060StartBackground Script Examples2016-09-14T11:59:56Z<p>TeeLeht: </p>
<hr />
<div>This page contains examples for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23StartBackground|StartBackground]] command.<br />
<br />
The following example will first show a "Starting SAP import" message in the user interface, then run an import from SAP that is executed in client side, then enter the background execution mode and then create a new model based on the extracted data.<br />
<pre><br />
Print 'Starting SAP import'<br />
<br />
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL<br />
(SELECT 'SapSystemNumber', '10') UNION ALL<br />
(SELECT 'SapUser', 'qpr') UNION ALL<br />
(SELECT 'SapPW', 'demo') UNION ALL<br />
(SELECT 'SapRouter', '') UNION ALL<br />
(SELECT 'SapClient', '200') UNION ALL<br />
(SELECT 'SapLanguage', 'EN') UNION ALL<br />
(SELECT 'SapPoolSize', '5') UNION ALL<br />
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL<br />
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL<br />
(SELECT 'ExecuteInClientSide', '1') UNION ALL<br />
(SELECT 'DataTargetName', 'SAPDATA') UNION ALL<br />
(SELECT 'Append', '0') UNION ALL<br />
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL<br />
(SELECT 'SapQueryTable', 'VBAK')<br />
--#ImportSapQuery<br />
<br />
(SELECT 'Enabled', 'TRUE')<br />
--#StartBackground<br />
<br />
<br />
(SELECT 'AnalysisType', '18') UNION ALL <br />
(SELECT 'DataTableName', 'SAPDATA') UNION ALL <br />
(SELECT 'TargetTable', '#SAPDATA') <br />
--#GetAnalysis<br />
<br />
(SELECT 'ModelName', 'NewModel');<br />
(SELECT * from #SAPDATA;<br />
--#ImportEvents<br />
<br />
<br />
</pre><br />
<br />
[[Category:Examples]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=3057QPR ProcessAnalyzer System Requirements2016-09-07T08:17:23Z<p>TeeLeht: /* System Requirements for QPR ProcessAnalyzer ScriptLauncher */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP .NET 3.5 & 4.5<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** .NET Environment 3.5<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=3056QPR ProcessAnalyzer System Requirements2016-09-07T07:58:27Z<p>TeeLeht: /* System Requirements for QPR ProcessAnalyzer ScriptLauncher */</p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
* A 64-bit Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.6.1<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2016 database.<br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft .NET Framework 4.6.1 is installed <br />
* Microsoft SQL Server 2012, 2014, or 2016 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
** '''Performance''':<br />
*** Static Content Compression<br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP .NET 3.5 & 4.5<br />
*** ISAPI Extensions<br />
*** ISAPI Filters<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
*** HTTP Activation<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** .NET Environment 3.5<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== System Requirements for QPR ProcessAnalyzer ScriptLauncher ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer ScriptLauncher tool are:<br />
* 64-bit version of Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 10, or Microsoft Windows Server 2012 R2 operating system<br />
**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.<br />
*Internet connection <br />
*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 [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_ScriptLauncher|instructions]] for installing them.<br />
<br />
The following components are also required:<br />
*Microsoft .NET Framework 4.6.1<br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=Exit_Script_Examples&diff=3004Exit Script Examples2016-08-12T06:47:12Z<p>TeeLeht: </p>
<hr />
<div>This page contains script examples for the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23Exit|Exit]] script command.<br />
<br/><br />
<br/><br />
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.<br />
<pre><br />
(SELECT 'Exit', '0') UNION ALL <br />
(SELECT 'RunScriptId', '12') <br />
--#Exit <br />
</pre><br />
<br />
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.<br />
<pre><br />
(SELECT 'Exit', '1') UNION ALL <br />
(SELECT 'RunScriptId', '12') <br />
--#Exit <br />
</pre><br />
<br />
The following example stops the script execution, gives a message, and runs a script with Id 12.<br />
<pre><br />
(SELECT 'Exit', '1') UNION ALL<br />
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL<br />
(SELECT 'RunScriptId', '12')<br />
--#Exit<br />
</pre><br />
<br />
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.<br />
<pre><br />
DECLARE @ScriptToRun VARCHAR(10)<br />
<br />
IF @_ExceptionOccurred = 1 <br />
SET @ScriptToRun = '2' <br />
ELSE SET @ScriptToRun = <nowiki>''</nowiki><br />
<br />
(SELECT 'Exit', '1') UNION ALL <br />
(SELECT 'RunScriptId', @ScriptToRun) <br />
--#Exit<br />
</pre><br />
<br />
The following example script stops the execution of the current script if the script has been last modified more than 600 seconds ago<br />
<pre><br />
(SELECT 'AnalysisType', '24') UNION ALL<br />
(SELECT 'TargetTable', '#ScriptAnalysis')<br />
--#GetAnalysis<br />
<br />
(SELECT 'Exit', IIF((DATEDIFF(ss,[Last Modified On],GETDATE()) > 600),1,0) FROM #ScriptAnalysis where [Id] = @_ScriptId)<br />
--#Exit <br />
</pre><br />
<br />
<br />
[[Category:Examples]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2618QPR ProcessAnalyzer System Requirements2016-01-13T11:49:31Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2617QPR ProcessAnalyzer System Requirements2016-01-13T11:48:51Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, 2013, or 2016.<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
**** BIT Server Extenstion Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=2567QPR ProcessAnalyzer Release Notes2015-12-09T11:08:53Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==<br />
Build number: 2015.5.0.33554, <br/><br />
'''Features:'''<br/><br />
-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.<br/><br />
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
-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.<br/><br />
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
-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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2016.1 ==<br />
Build number: 2016.1.0.xxxxx, Model conpatibility version: 1, Database version: 50, Stream version: 7 <br />
'''Features:'''<br/><br />
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
-306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
-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.<br/><br />
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br />
<br />
'''Bugs:'''<br/><br />
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
-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.<br/><br />
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
<br />
== Past Releases ==<br />
<br />
== Hotfix with version number 2015.5 (release date 7.10.2015) ==<br />
Build number: 2015.5.0.33631, Internal version: 5 (5.7.0.33631), Database version: 44, Stream version: 6. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
== Hotfix with version number 2015.5 (release date 26.8.2015) ==<br />
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.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==<br />
<br />
Build number: 2015.4.0.33243<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==<br />
<br />
Build number: 2015.3.0.32848<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===<br />
Build number: 2015.2.0.32408<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===<br />
Build number: 2015.1.0.32120<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=2566QPR ProcessAnalyzer Release Notes2015-12-09T11:01:03Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2015.5 (release date 25.9.2015, life cycle phase: Active) ==<br />
Build number: 2015.5.0.33554, <br/><br />
'''Features:'''<br/><br />
-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.<br/><br />
-306453: With the new feature, [[Common QPR Authentication]], it is possible to configure a common authentication system between different QPR Suite product web clients.<br/><br />
-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.<br/><br />
-306471: Scripts now have the [[Supported_QPR_ProcessAnalyzer_Commands_in_Scripts#--.23CallWebService|CallWebService command]] available enabling you to extract data via a Web Service.<br/><br />
-306473: QPR ProcessAnalyzer now supports Windows 10 operating system.<br/><br />
-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.<br/><br />
<br />
'''Bugs:'''<br/><br />
- 216363: Fixed an issue with Web Service requests in which TimeOutExceptions could not be handled in the client side.<br/><br />
- 216465: Fixed a performance issue with Influence Analysis.<br/><br />
- 216498: Fixed an issue where temporary tables got dropped when using the Run command with arguments.<br/><br />
__TOC__<br />
<br />
== Next Release: QPR ProcessAnalyzer 2016.1 ==<br />
Build number: 2016.1.0.xxxxx, Model conpatibility version: 1, Database version: 50, Stream version: 7 <br />
'''Features:'''<br/><br />
-306485: This feature introduces new [[Filters#Filter_Rules|filter rules]] that enable defining which Case and Event Attributes are included or excluded in filtering.<br/><br />
-306508: In this refactorization feature, the internal mechanism for filtering has been changed.<br/><br />
-306509: New [[Filters#Sample_Size|sample size]] functionality is introduced for filters to facilitate finding the optimized sampling size for the analysis.<br/><br />
-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.<br/><br />
-306513: The [[Filters#Filter_Properties|Filter Properties]] dialog has been redesigned to enable access to filter rules directly from this dialog.<br />
<br />
'''Bugs:'''<br/><br />
-216205: Fixed an issue where QPR ProcessAnalyzer Service had the wrong EMS address.<br/><br />
-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.<br/><br />
-216405: Fixed an issue where case attribute import was not showing an error message if no case attribute columns existed.<br/><br />
-216729: Fixed an issue where after importing a big model using a script, a file model import with Excel Client was very slow.<br/><br />
<br />
== Past Releases ==<br />
<br />
== Hotfix with version number 2015.5 (release date 7.10.2015) ==<br />
Build number: 2015.5.0.33631, Database version: 44, Stream version: 6. Contact [mailto:customercare@qpr.com? QPR Customer Care] for more information.<br/><br />
'''Bugs:'''<br/><br />
- 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. <br/><br />
- 216556: Fixed a timeout issue related to memory consumption that occurred when running a script.<br/><br />
- 216566: Fixed an issue where the client-service polling was broken when exporting a model.<br/><br />
<br />
== Hotfix with version number 2015.5 (release date 26.8.2015) ==<br />
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.<br/><br />
'''Bugs:'''<br/><br />
- 216466: Fixed an issue where the ImportSalesforceQuery function failed.<br />
<br />
== QPR ProcessAnalyzer 2015.4 (release date 13.8.2015, life cycle phase: Mature)==<br />
<br />
Build number: 2015.4.0.33243<br/><br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306401: [[Template:Activating_QPR_ProcessAnalyzer#Activation Levels|The product activation limits]] for QPR ProcessAnalyzer Xpress and Xpress Evaluation have been changed.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 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).<br/><br />
- 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.<br/><br />
- 215832: Fixed an issue with the delay after a user cancels an operation in Excel Client.<br/><br />
- 215854: Fixed the inconsistency issue in the operation ID which caused a failure in Excel Client progress bar.<br/><br />
- 215886: Fixed the issue where Excel was not responding when a user tried to open a sample file.<br/><br />
- 215998: Fixed an issue where an Evaluator user was able to create an unlimited amount of models.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 216070: Fixed an issue related to Evaluator user rights.<br/><br />
- 216079: Fixed an issue with Profiling and Influence Analysis failing if the SQL value is of type FLOAT.<br/><br />
- 216084: Fixed an issue where the error text did not show the script name when an error occurred in the running of a script.<br/><br />
- 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.<br/><br />
- 216153: Fixed an issue where old temporary table was not deleted before it was used in [[Data_Extraction,_Transformation,_and_Loading#--.23GetAnalysis|GetAnalysis command]].<br/><br />
- 216183: Fixed an issue in Influence Analysis where the subset of zero values could not be selected for drilldown.<br/><br />
- 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.<br/><br />
- 216192: Fixed an issue with case attribute import in case the first column has the name "Id".<br/><br />
- 216211: Fixed a connection slowness issue in QPR ProcessAnalyzer Xpress after the LocalDB instance was stopped.<br/><br />
- 216215: Fixed the error message in QPR ProcessAnalyzer Web Client when a user tried to open a bookmark of unsupported type.<br/><br />
- 216218: Fixed the error message for a network connection problem.<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216249: Fixed an error that occurred when trying to copy a model multiple times in a row.<br/><br />
- 216255: Fixed an issue where deleted filters were still visible in the list of filters accessible from the Change button in the ribbon.<br/><br />
- 216256: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to relate an idea to a deleted filter.<br/><br />
- 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.<br/><br />
- 216269: Fixed an incorrect label in the Bookmark Properties dialog.<br/><br />
- 216312: Fixed the URL of the link for "Forgot your Product Activation Code?" in the QPR ProcessAnalyzer Activation Utility dialog.<br/><br />
- 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.<br/><br />
- 216338: Fixed an issue where an unhandled timeout exception was thrown when restoring a big model.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 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.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
- 216359: Fixed an error which appeared when user tried to use Excel client newer than the recommended client version in the service.<br/><br />
- 216361: Fixed an issue where the stack trace was not always written to the log file when an error occured.<br/><br />
- 216375: Fixed the QPR ProcessAnalyzer ScriptLauncher to be a 64-bit application instead of 32-bit.<br/><br />
- 216380: Fixed the build errors which appeared in the installer log of QPR ProcessAnalyzer.<br/><br />
- 216422: Fixed an issue in QPR ProcessAnalyzer Excel Client where Run Scripts button in some cases was visible for a user without RunScripts rights.<br/><br />
- 216423: Fixed an issue with an error occurring when trying to open Project Workspace after an expired session in QPR ProcessAnalyzer Xpress.<br/><br />
- 216425: Fixed an issue where QPR ProcessAnalyzer Web Client became unresponsive when user tried to open a deleted bookmark.<br/><br />
- 216432: Fixed a performance issue with GetAnalysis operation.<br/><br />
- 216433: Fixed an issue where case-related data was incorrectly shown in Project Workspace after importing a new model.<br />
<br/><br />
- 216436: Fixed an issue with filters not working in a customer production environment.<br/><br />
<br />
== QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Mature) ==<br />
<br />
Build number: 2015.3.0.32848<br/><br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===<br />
Build number: 2015.2.0.32408<br/><br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===<br />
Build number: 2015.1.0.32120<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===<br />
Build number: 2014.4.0.31422<br/><br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Retired) ===<br />
Build number: 2014.3.0.30795<br/><br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Retired) ===<br />
Build number: 2014.2.0.30286<br/><br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: End-of-life) ===<br />
Build version: 2014.1.0.28965<br/><br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.7.0.28641<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.6.0.28180<br/><br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.5.0.27571<br/><br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.4.0.26819<br/><br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
Build number: 4.3.0.26358<br/><br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_Commands&diff=2565SQL Scripting Commands2015-12-07T08:37:34Z<p>TeeLeht: </p>
<hr />
<div>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.<br/><br />
<br />
=<br/> --#CallWebService =<br />
Extracts data via Web Service. This command takes one SELECT query as parameter.<br />
<br />
== Query ==<br />
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:<br />
; 'Address'<br />
: Defines the URI of the service to call. Mandatory.<br />
; 'Method'<br />
: Defines the HTTP method to use for the call. Must be any of the following: GET (default), POST, PUT, DELETE. Optional.<br />
; 'Body'<br />
: Defines the message body text to send to the service. Default value is empty. Optional.<br />
; 'Encoding'<br />
: 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.<br />
; 'Timeout'<br />
: Number of milliseconds to wait before the request times out. Default value is 60000. Optional.<br />
; 'ExecuteInClientSide'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT.<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
;<nowiki><other parameters></nowiki><br />
: All the rest of the passed parameters not listed above are added as extra headers to the request. Optional.<br />
<br />
== Result ==<br />
<br />
The result of the request is passed to the script following the CallWebService operation in the following variables:<br />
: <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). <br />
: <code>@_ResponseStatusCode</code> The numeric status code received from the remote server. INT. <br />
: <code>@_ResponseSuccess</code> True only if the request returned status code that represents a success. BIT.<br />
<br />
== Example ==<br />
<pre><br />
(SELECT 'Method', 'GET') UNION ALL<br />
(SELECT 'Address', 'http://google.com') UNION ALL<br />
(SELECT 'ContentType', 'application/json') UNION ALL<br />
(SELECT 'Accept', '*/*')<br />
--#CallWebService<br />
PRINT SUBSTRING(@_ResponseText, 1, 50);<br />
</pre><br />
<br />
== Script Log Results ==<br />
When the script is run, entries similar to the following will be shown in the script log:<br />
<br />
<pre><br />
Execution duration: 0,753 seconds<br />
Execution Log:<br />
2015-09-14T13:59:49.2838661+03:00 Notification 85 Script operation: "--#CallWebService" started<br />
2015-09-14T13:59:49.3468813+03:00 Notification 85 Address: http://google.com<br />
Method: GET<br />
ContentType: application/json<br />
Encoding: Unicode (UTF-8)<br />
Body content length: 0<br />
Timeout: 60000<br />
ExecuteInClientSide: 0<br />
Additional headers: Accept(3)<br />
2015-09-14T13:59:49.6579900+03:00 Notification 85 Script operation: "--#CallWebService" completed: Result: OK, text length: 53019, status code: 200<br />
<nowiki><br />
2015-09-14T13:59:49.7230130+03:00 Notification 85 <!doctype html><html itemscope="" itemtype="http:/<br />
</nowiki><br />
</pre><br />
<br />
=<br/> --#Exit =<br />
Stops the execution of the script and gives a message to the user. This command takes one SELECT query as its parameter.<br />
<br />
== Query ==<br />
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:<br/><br />
; 'Exit'<br />
: Defines whether to stop the script execution:<br />
: 1 = stop execution of the current script and call the script defined by the RunScriptId parameter if it is given.<br />
: 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.<br />
; 'MessageText'<br />
: 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.<br />
; 'RunScriptId'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
<br />
== Examples ==<br />
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.<br />
<pre><br />
(SELECT 'Exit', '0') UNION ALL <br />
(SELECT 'RunScriptId', '12') <br />
--#Exit <br />
</pre><br />
<br />
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.<br />
<pre><br />
(SELECT 'Exit', '1') UNION ALL <br />
(SELECT 'RunScriptId', '12') <br />
--#Exit <br />
</pre><br />
<br />
The following example stops the script execution, gives a message, and runs a script with Id 12.<br />
<pre><br />
(SELECT 'Exit', '1') UNION ALL<br />
(SELECT 'MessageText', 'Data from SAP not valid. Script execution will be terminated. Check source data. Running script Id 12.') UNION ALL<br />
(SELECT 'RunScriptId', '12')<br />
--#Exit<br />
</pre><br />
<br />
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.<br />
<pre><br />
DECLARE @ScriptToRun VARCHAR(10)<br />
<br />
IF @_ExceptionOccurred = 1 <br />
SET @ScriptToRun = '2' <br />
ELSE SET @ScriptToRun = <nowiki>''</nowiki><br />
<br />
(SELECT 'Exit', '1') UNION ALL <br />
(SELECT 'RunScriptId', @ScriptToRun) <br />
--#Exit<br />
</pre><br />
<br />
=<br/> --#GetAnalysis =<br />
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.<br />
<br />
== Query ==<br />
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:<br/><br />
; '<Analysis Parameter>'<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Flowchart Analysis (0)<br />
: Variation Analysis in the Chart Mode (1)<br />
: Path Analysis (3)<br />
: Event Type Analysis in the Chart Mode (4)<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis in the Table Mode (7)<br />
: Variation Analysis in the Table Mode (8)<br />
: Duration Analysis (9)<br />
: Profiling Analysis (10)<br />
: User Report (11)<br />
: Operation Log Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Data Table Analysis (18)<br />
: Model Report (21)<br />
: Project Report (22)<br />
: Data Table Report (23)<br />
: Script Report (24)<br />
: 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]]. <br />
; 'TargetTable'<br />
: 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.<br />
: You can define the 'TargetTable' when using the following analysis types:<br />
: - Case Analysis<br />
: - Event Analysis<br />
: - Event Type Analysis<br />
: - Variation Analysis<br />
: - User Permissions<br />
: - Operation Log<br />
: - Flow Analysis<br />
: - Influence Analysis<br />
: - Integration Table <br />
: - Model Report<br />
: - Project Report<br />
: - Data Table Report<br />
: - Script Report<br />
; 'Show'<br />
: Optional. If TRUE or 1, the analysis is opened after the script is run.<br />
; 'Title'<br />
: Optional. The title for the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.<br />
; 'SheetName'<br />
: Optional. The name of the Excel sheet created when Show is TRUE or 1. Default value is the name of the analysis type.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
<br />
== Examples == <br />
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.<br />
<pre><br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'FilterId', '3') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'Show', '1') UNION ALL<br />
(SELECT 'Title', 'Analysis Title') UNION ALL<br />
(SELECT 'SheetName', 'Excel Sheet Name') UNION ALL<br />
(SELECT 'TargetTable', '#ExampleTable')<br />
--#GetAnalysis<br />
</pre><br />
<br />
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]].<br />
<pre><br />
(SELECT 'AnalysisType', '21') UNION ALL<br />
(SELECT 'Show', '1') UNION ALL<br />
(SELECT 'TargetTable', '#ModelResult')<br />
--#GetAnalysis<br />
</pre><br />
<br />
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]].<br />
<pre><br />
(SELECT 'AnalysisType', '22') UNION ALL<br />
(SELECT 'Show', '1') UNION ALL<br />
(SELECT 'TargetTable', '#ProjectResult')<br />
--#GetAnalysis<br />
</pre><br />
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]].<br />
<pre><br />
(SELECT 'AnalysisType', '23') UNION ALL<br />
(SELECT 'Show', '1') UNION ALL<br />
(SELECT 'TargetTable', '#DataTableResult')<br />
--#GetAnalysis<br />
</pre><br />
<br />
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]].<br />
<pre><br />
(SELECT 'AnalysisType', '24') UNION ALL<br />
(SELECT 'Show', '1') UNION ALL<br />
(SELECT 'TargetTable', '#ScriptResult')<br />
--#GetAnalysis<br />
</pre><br />
<br />
=<br/> --#ImportCaseAttributes =<br />
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.<br />
<br />
== First Query ==<br />
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:<br/><br />
; 'ProjectId' or 'ProjectName'<br />
: 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.<br />
; 'ModelId' or 'ModelName'<br />
: 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.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
<br />
== Second Query ==<br />
; <nowiki>'<data>'</nowiki><br />
: 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.<br />
<br />
=<br/> --#ImportDataTable =<br />
Imports data to a Data Table. This command takes two SELECT queries as parameters.<br />
== First Query ==<br />
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:<br/><br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
<br />
== Second Query ==<br />
; <nowiki>'<data>'</nowiki><br />
: 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.<br />
<br />
== Examples ==<br />
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.<br />
<pre><br />
SELECT 'START'<br />
--#WriteLog<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'FilterId', '3') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT 'DataLoaded'<br />
--#WriteLog<br />
<br />
SELECT count(*) from [#AnalysisResult]<br />
--#WriteLog<br />
<br />
(SELECT 'ProjectId', '1') UNION ALL<br />
(SELECT 'DataTableName', 'ExampleTable') UNION ALL<br />
(SELECT 'Append', '1')<br />
(SELECT * FROM [#AnalysisResult])<br />
--#ImportDataTable<br />
</pre><br />
<br />
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.<br />
<pre><br />
(SELECT 'AnalysisType', '18') UNION ALL <br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'DataTableName', 'ExampleTable') UNION ALL <br />
(SELECT 'TargetTable', '#CSV1') <br />
--#GetAnalysis<br />
<br />
(SELECT * FROM #CSV1) <br />
(SELECT 'Title', 'CSV Table') UNION ALL <br />
(SELECT 'MaximumCount', '0')<br />
--#ShowReport<br />
</pre><br />
<br />
=<br/> --#ImportEvents =<br />
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.<br />
== First Query ==<br />
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:<br/><br />
; 'ProjectId' or 'ProjectName'<br />
: 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.<br />
; 'ModelId' or 'ModelName'<br />
: 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.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
<br />
== Second Query ==<br />
; <nowiki>'<data>'</nowiki><br />
: 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.<br />
<br />
=<br/> --#ImportOdbcQuery =<br />
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.<br />
== Query ==<br />
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:<br/><br />
; '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. <br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
<br />
'''ODBC specific parameters'''<br />
; 'OdbcConnectionString'<br />
: 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]].<br />
; 'OdbcQueryString'<br />
: 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.<br />
; 'ExecuteInClientSide'<br />
: 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.<br />
<br />
== Example ==<br />
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.<br />
<pre><br />
(SELECT 'OdbcConnectionString', 'DSN=PA_EXPRESS_40') UNION ALL<br />
(SELECT 'OdbcQueryString', 'SELECT * FROM PA_MODEL') UNION ALL<br />
(SELECT 'TargetTable', '#ImportOdbcTable') UNION ALL<br />
(SELECT 'Append', '1')<br />
--#ImportOdbcQuery<br />
</pre><br />
<br />
=<br/> --#ImportOleDbQuery =<br />
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.<br />
<br />
== Query ==<br />
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:<br/><br />
; 'TargetTable'<br />
: 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.<br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
'''OLE DB Query Parameters'''<br />
; 'OleDbConnectionString'<br />
: 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.<br />
; 'OleDbQueryString'<br />
: 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.<br />
; 'ExecuteInClientSide'<br />
: 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.<br />
<br />
== Examples ==<br />
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.<br />
<pre><br />
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL<br />
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') UNION ALL<br />
(SELECT 'TargetTable', '#TABLE') UNION ALL<br />
(SELECT 'Append', '1')<br />
--#ImportOleDbQuery<br />
<br />
(SELECT * FROM #TABLE) UNION ALL<br />
(SELECT 'MaximumCount', '0')<br />
--#ShowReport<br />
</pre><br />
<br />
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. <br />
<pre><br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL <br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL <br />
(SELECT 'Append', '0') UNION ALL <br />
(SELECT 'OleDbConnectionString', 'Provider=SQLOLEDB;Data Source=(local);Initial Catalog=DB1;Integrated Security=SSPI;') UNION ALL <br />
(SELECT 'OleDbQueryString', 'SELECT * FROM EXAMPLE') <br />
--#ImportOleDbQuery<br />
<br />
(SELECT 'AnalysisType', '18') UNION ALL<br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL <br />
(SELECT 'MaximumCount', '0') UNION ALL <br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL <br />
(SELECT 'TargetTable', '#TABLE') <br />
--#GetAnalysis <br />
<br />
(SELECT * FROM #TABLE) <br />
(SELECT 'MaximumCount', '0') <br />
--#ShowReport <br />
</pre><br />
<br />
=<br/> --#ImportSalesforceQuery =<br />
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!<br />
<br />
This command takes one SELECT query as its parameter.<br />
== Query ==<br />
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:<br/><br />
; 'TargetTable'<br />
: 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.<br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
'''Salesforce Query Parameters'''<br />
; 'SalesforceUser'<br />
: Username for the Salesforce cloud.<br />
; 'SalesforcePW'<br />
: Password for the Salesforce cloud.<br />
; 'SalesforceQueryMode'<br />
: 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()].<br />
; 'SalesforceQuery'<br />
: 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.<br />
; 'SalesforceQueryRetries'<br />
: Optional. Number of retries to attempt if the Salesforce query doesn't succeed. Default value is 3.<br />
; 'SalesforceQueryRetryWait'<br />
: Optional. Number of milliseconds to wait between query retries. Default is 3000 ms.<br />
; 'SalesforceBatchSize'<br />
: 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.<br />
<br />
== Example ==<br />
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.<br />
<pre><br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL<br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL<br />
(SELECT 'Append', '0') UNION ALL<br />
(SELECT 'SalesforceUser', 'example.user@qpr.com') UNION ALL<br />
(SELECT 'SalesforcePW', 'examplepassword') UNION ALL<br />
(SELECT 'SalesforceQuery', 'SELECT CreatedDate FROM Contact')<br />
--#ImportSalesforceQuery<br />
<br />
(SELECT 'AnalysisType', '18') UNION ALL <br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL <br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL <br />
(SELECT 'TargetTable', '#TABLE') <br />
--#GetAnalysis <br />
<br />
(SELECT * FROM #TABLE) <br />
(SELECT 'MaximumCount', '0') <br />
--#ShowReport <br />
</pre><br />
<br />
=<br/> --#ImportSapQuery =<br />
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.<br />
<br />
== Query ==<br />
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:<br/><br />
; 'TargetTable'<br />
: If this parameter is given, store the results into a temporary SQL table in ETL sandbox.<br />
If the TargetTable parameter is not given, use the following destination parameters:<br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
<br />
'''SAP Connection Parameters:'''<br />
; 'SapUser'<br />
: 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.<br />
; 'SapPW'<br />
: 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.<br />
; 'SapClient'<br />
: 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.<br />
; 'SapAppServerHost'<br />
: 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.<br />
; 'SapMessageServerHost'<br />
: 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.<br />
; 'SapSystemNumber'<br />
: 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.<br />
; 'SapSystemID'<br />
: 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.<br />
; 'ExecuteInClientSide'<br />
: 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.<br />
<br />
'''Other SAP Parameters:'''<br />
; 'SapLanguage'<br />
: 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.<br />
; 'SapPoolSize'<br />
: 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.<br />
; 'SapPeakConnectionsLimit'<br />
: 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.<br />
; 'SapConnectionIdleTimeout'<br />
: 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.<br />
; 'SapRouter'<br />
: 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.<br />
; 'SapLogonGroup'<br />
: 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.<br />
; 'SapQueryMode'<br />
: 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.<br />
; 'SapQueryTable'<br />
: 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.<br />
; 'SapRowcount'<br />
: 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.<br />
; 'SapRowskips'<br />
: 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.<br />
; 'SapWhereClause'<br />
: 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.<br />
; 'SapWhereClauseSelect'<br />
: 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.<br/><br />
: See also [[Data_Extraction,_Transformation,_and_Loading#Client_Exception_When_Using_.23ImportSapQuery_Command|Troubleshooting]] for other SAP related limitations.<br />
; 'SapFieldNames'<br />
: 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.<br />
; 'SapFunction'<br />
: 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.<br />
<br />
== Examples ==<br />
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".<br />
<pre><br />
(SELECT 'ProjectName', 'ImportSapQueryExample') UNION ALL<br />
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL<br />
(SELECT 'Append', 'TRUE') UNION ALL<br />
(SELECT 'SapUser', 'exampleuser') UNION ALL<br />
(SELECT 'SapPW', 'examplepassword') UNION ALL<br />
(SELECT 'SapClient', '200') UNION ALL<br />
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL<br />
(SELECT 'SapSystemNumber', '10') UNION ALL<br />
(SELECT 'SapLanguage', 'EN') UNION ALL<br />
(SELECT 'SapPoolSize', '5') UNION ALL<br />
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL<br />
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL<br />
(SELECT 'SapRouter', '/H/127.0.0.1/A/1234/H/') UNION ALL<br />
(SELECT 'SapLogonGroup', 'GROUPXNAME') UNION ALL<br />
(SELECT 'SapQueryMode', '1') UNION ALL<br />
(SELECT 'SapQueryTable', 'VBAK') UNION ALL<br />
(SELECT 'SapDelimiter', '|') UNION ALL<br />
(SELECT 'SapRowcount', '0') UNION ALL<br />
(SELECT 'SapRowskips', '0') UNION ALL<br />
(SELECT 'SapWhereClause', 'VBELN EQ `0060000039`, OR VBELN EQ `0060000040`') UNION ALL<br />
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK')<br />
--#ImportSapQuery<br />
</pre><br />
<br />
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:<br />
<pre><br />
(SELECT 'CatchOperationExceptions', '1') UNION ALL<br />
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL<br />
(SELECT 'SapSystemNumber', '10') UNION ALL<br />
(SELECT 'SapUser', 'qpr') UNION ALL<br />
(SELECT 'SapPW', 'demo') UNION ALL<br />
(SELECT 'SapRouter', '') UNION ALL<br />
(SELECT 'SapClient', '200') UNION ALL<br />
(SELECT 'SapLanguage', 'EN') UNION ALL<br />
(SELECT 'SapPoolSize', '5') UNION ALL<br />
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL<br />
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL<br />
(SELECT 'ExecuteInClientSide', '1') UNION ALL<br />
(SELECT 'TargetTable', '#SAPmode1') UNION ALL<br />
(SELECT 'Append', '0') UNION ALL<br />
(SELECT 'SapWhereClause', 'VBELN BETWEEN `0060000039` AND `0060000041`') UNION ALL<br />
(SELECT 'SapQueryTable', 'VBAK')<br />
--#ImportSapQuery<br />
<br />
DECLARE @_SuccessOrNot as NVARCHAR(MAX);<br />
SET @_SuccessOrNot = CASE @_ExceptionOccurred<br />
WHEN 1 THEN<br />
'Exception(s) occurred!'<br />
ELSE<br />
'SAP import OK.'<br />
END<br />
<br />
SELECT <br />
@_SuccessOrNot as Result,<br />
@_ExceptionOccurred as ExceptionOccurred, <br />
@_ExceptionType as ExceptionType, <br />
@_ExceptionMessage as ExceptionMessage,<br />
@_ExceptionDetails as ExceptionDetails<br />
(SELECT 'SheetName' , 'ExceptionData')<br />
--#ShowReport<br />
<br />
(SELECT * FROM #SAPmode1)<br />
(SELECT 'SheetName' , 'SAPmode1')<br />
--#ShowReport<br />
</pre><br />
<br />
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:<br />
<pre><br />
/* First, create the temporary table that holds the WHERE clause. */<br />
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)<br />
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'VBELN BETWEEN ''0060000039'''</nowiki>, 1<br />
INSERT INTO #SapWhereClauseTable SELECT <nowiki>'AND ''0060000041'''</nowiki>, 2<br />
<br />
/* Specify the target for the data that the script extracts from SAP */<br />
(SELECT 'TargetTable', '#SAPmode1') UNION ALL<br />
(SELECT 'Append', '0') UNION ALL<br />
<br />
/* Define the SAP connection parameters */<br />
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL<br />
(SELECT 'SapSystemNumber', '10') UNION ALL<br />
(SELECT 'SapUser', 'exampleuser') UNION ALL<br />
(SELECT 'SapPW', 'examplepassword') UNION ALL<br />
(SELECT 'SapClient', '200') UNION ALL<br />
(SELECT 'SapLanguage', 'EN') UNION ALL<br />
(SELECT 'SapPoolSize', '5') UNION ALL<br />
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL<br />
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL<br />
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL<br />
<br />
/* Use the WHERE clause defined in the temporary table */<br />
(SELECT 'SapWhereClauseSelect', 'SELECT * from #SapWhereClauseTable ORDER BY order_number') UNION ALL<br />
(SELECT 'SapQueryTable', 'VBAK') <br />
--#ImportSapQuery<br />
<br />
/* Show the results */<br />
(SELECT * FROM #SAPmode1)<br />
(SELECT 'SheetName' , 'SAPmode1')<br />
--#ShowReport<br />
</pre><br />
<br />
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.<br />
<pre><br />
/* First, create the temporary table that holds the WHERE clause.*/ <br />
CREATE TABLE #SapWhereClauseTable (sap_select_string varchar(255), order_number int)<br />
INSERT INTO #SapWhereClauseTable SELECT 'VBELN BETWEEN ''0060000039''', 1<br />
INSERT INTO #SapWhereClauseTable SELECT 'AND ''0060000042''', 2<br />
<br />
/* Define that the command is executed in the client side.*/<br />
(SELECT 'ExecuteInClientSide', 'True') UNION ALL<br />
<br />
/* Specify the data table where the data is imported into.*/<br />
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL<br />
(SELECT 'Append', '0') UNION ALL<br />
<br />
/* Define the SAP connection parameters.*/ <br />
(SELECT 'SapAppServerHost', '127.0.0.1') UNION ALL<br />
(SELECT 'SapSystemNumber', '10') UNION ALL<br />
(SELECT 'SapUser', 'exampleuser') UNION ALL<br />
(SELECT 'SapPW', 'examplepassword') UNION ALL<br />
(SELECT 'SapRouter', '') UNION ALL<br />
(SELECT 'SapClient', '200') UNION ALL<br />
(SELECT 'SapLanguage', 'EN') UNION ALL<br />
(SELECT 'SapPoolSize', '5') UNION ALL<br />
(SELECT 'SapPeakConnectionsLimit', '10') UNION ALL<br />
(SELECT 'SapConnectionIdleTimeout', '600') UNION ALL<br />
(SELECT 'SapFieldNames', 'VBELN,ERDAT,ERZET,ERNAM,NETWR,WAERK') UNION ALL<br />
<br />
/* Use the WHERE clause defined in the temporary table.*/ <br />
(SELECT 'SapWhereClauseSelect', 'SELECT sap_select_string from #SapWhereClauseTable ORDER BY order_number') UNION ALL<br />
(SELECT 'SapQueryTable', 'VBAK')<br />
--#ImportSapQuery<br />
<br />
/* Create an analysis.*/ <br />
(SELECT 'AnalysisType', '18') UNION ALL<br />
(SELECT 'DataTableName', 'SapQueryTableExample') UNION ALL<br />
(SELECT 'TargetTable', '#Result')<br />
--#GetAnalysis<br />
<br />
/* Show the results.*/ <br />
SELECT * FROM #Result<br />
--#ShowReport<br />
</pre><br />
<br />
=<br/> --#ImportSqlQuery =<br />
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.<br />
== Query ==<br />
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:<br/><br />
; 'TargetTable'<br />
: 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.<br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target data table exists.<br />
; 'DataTableId' or 'DataTableName'<br />
: The id or the name of the existing/new target data table.<br />
; 'Append'<br />
: 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.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
'''SQL Query Parameters'''<br />
; 'SqlConnectionString'<br />
: 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.<br />
; 'SqlQueryString'<br />
: 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.<br />
; 'ExecuteInClientSide'<br />
: 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.<br />
<br />
== Examples ==<br />
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.<br />
<pre><br />
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL<br />
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE') UNION ALL<br />
(SELECT 'TargetTable', '#TABLE') UNION ALL<br />
(SELECT 'Append', '1')<br />
--#ImportSqlQuery<br />
<br />
(SELECT * FROM #TABLE) <br />
(SELECT 'MaximumCount', '0') <br />
--#ShowReport <br />
</pre><br />
<br />
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. <br />
<pre><br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL <br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL <br />
(SELECT 'Append', '0') UNION ALL <br />
(SELECT 'SqlConnectionString', 'Data Source=(local);Initial Catalog=DB1;Integrated Security=true') UNION ALL <br />
(SELECT 'SqlQueryString', 'SELECT * FROM EXAMPLE')<br />
--#ImportSqlQuery<br />
<br />
(SELECT 'AnalysisType', '18') UNION ALL <br />
(SELECT 'ProjectName', 'ExampleProject') UNION ALL <br />
(SELECT 'MaximumCount', '0') UNION ALL <br />
(SELECT 'DataTableName', 'ExampleDataTable') UNION ALL <br />
(SELECT 'TargetTable', '#TABLE') <br />
--#GetAnalysis <br />
<br />
(SELECT * FROM #TABLE) <br />
(SELECT 'MaximumCount', '0') <br />
--#ShowReport <br />
</pre><br />
<br />
=<br/> --#RemoveEvents =<br />
Removes all or specified events in the target model, but retains Cases, Event Types, and Variations. This command takes two SELECT queries as parameters.<br />
== First Query ==<br />
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:<br/><br />
; 'ProjectId' or 'ProjectName'<br />
: The id or the name of the project in which the target model exists. Defaults to the current project.<br />
; 'ModelId' or 'ModelName'<br />
: The id or the name of the target model. Defaults to the current model. If ModelId is given, neither ProjectId nor ProjectName are used.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
<br />
== Second Query ==<br />
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.<br />
<br />
== Examples ==<br />
The following example will remove all events in the model with Id "22931" in the project with Id "234".<br />
<pre><br />
(SELECT 'ProjectId', '234') UNION ALL<br />
(SELECT 'ModelId', '22931')<br />
--#RemoveEvents<br />
</pre><br />
<br />
The following example will remove 10 first events from the model by using Event Id's from --#GetAnalysis command.<br />
<pre><br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '10') UNION ALL<br />
(SELECT 'ModelId', '<ModelId>') UNION ALL<br />
(SELECT 'IncludeEventIds', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#Events')<br />
--#GetAnalysis<br />
<br />
(SELECT 'ModelId', '<ModelId>')<br />
(SELECT [Event Id] from [#Events])<br />
--#RemoveEvents<br />
</pre><br />
<br />
== Script Log Results ==<br />
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:<br />
<pre><br />
Remove events for model id=41 started<br />
Number of events in model (before): 641<br />
Number of events to be removed: 100<br />
Number of events removed: 10<br />
Number of events not found: 90<br />
Number of events in model (after): 631<br />
</pre><br />
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.<br />
<br />
In case there are no event Id's specified in the query, the script log will show the following entries:<br />
<pre><br />
Remove events for model id=41 started<br />
Number of events in model (before): 621<br />
Remove all events<br />
Number of events in model (after): 0<br />
</pre><br />
<br />
=<br/> --#Run =<br />
Runs another script with specified parameters. This command can take multiple SELECT queries as parameters.<br />
<br />
== First Query ==<br />
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:<br/><br />
; 'ScriptId'<br />
: Mandatory. The Id of the called script.<br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
: <code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
: <code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
: <code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
: <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.<br />
== Following Queries ==<br />
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.<br />
The possible arguments are as follows:<br />
:* @_Argv - type INT: the number of provided parameters (from 0 to 10)<br />
:* #_Arg1, ... #_Arg10: arguments passed to that script<br />
<br />
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.<br />
<br />
== Examples ==<br />
In the following example, the script gets data from two data tables and passes that data to the script with Id equal to <ScriptId>. <br />
<br />
<pre><br />
(SELECT 'AnalysisType', '18') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'DataTableId', '<DataTableId_1>') UNION ALL<br />
(SELECT 'TargetTable', '#DataTable1')<br />
--#GetAnalysis<br />
<br />
(SELECT 'AnalysisType', '18') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'DataTableId', '<DataTableId_2>') UNION ALL<br />
(SELECT 'TargetTable', '#DataTable2')<br />
--#GetAnalysis<br />
<br />
(SELECT 'ScriptId', '<ScriptId>')<br />
SELECT * FROM #DataTable1;<br />
SELECT * FROM #DataTable2;<br />
--#Run<br />
</pre><br />
<br />
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.<br />
<pre><br />
print 'Number of arguments: ' + cast(@_Argv as varchar(100));<br />
<br />
SELECT * from #_Arg1;<br />
(SELECT 'MaximumCount', '0')<br />
--#ShowReport<br />
<br />
SELECT * from #_Arg2;<br />
(SELECT 'MaximumCount', '0')<br />
--#ShowReport<br />
</pre><br />
<br />
= --#SendEmail =<br />
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. <br />
<br />
== Query ==<br />
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:<br/><br />
; 'CatchOperationExceptions'<br />
: 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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
'''E-mail Parameters'''<br />
; 'EmailFrom'<br />
: Defines the from address for this e-mail message. Mandatory.<br />
; 'EmailTo'<br />
: Defines the recipient(s) for this e-mail message given in a list separated by comma. Mandatory.<br />
; 'EmailSubject'<br />
: Defines the subject of the email. Default value is empty. Optional.<br />
; 'EmailBody'<br />
: Defines the message body. Default value is empty. Optional.<br />
; 'EmailCc'<br />
: Defines the carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.<br />
; 'EmailBcc'<br />
: Defines the blind carbon copy recipient(s) for this e-mail message given in a list separated by comma. Optional.<br />
; 'EmailIsBodyHtml'<br />
: 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.<br />
; 'EmailSender'<br />
: Defines the sender's address for this e-mail message. Default value is empty. Optional.<br />
; 'EmailReplyTo'<br />
: Defines the ReplyTo address(es) for the mail message given in a list separated by comma. Optional.<br />
; 'EmailPriority',<br />
: Defines the priority of this e-mail message. Possible values are "High", "Normal", and "Low". Default value is "Normal". Optional.<br />
; 'EmailDeliveryNotification'<br />
: Defines the delivery notifications for this e-mail message. Possible values are "Delay", "Never", "None", "OnFailure", and "OnSuccess". Default value is "None". Optional.<br />
; 'EmailBodyEncoding'<br />
: 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.<br />
; 'EmailSubjectEncoding'<br />
: 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.<br />
<br />
'''SMTP Server Parameters'''<br />
; 'SmtpServer'<br />
: Defines the hostname or the IP address of the server. Mandatory for the first occurrence of the SendEmail command during script execution.<br />
; 'SmtpPort'<br />
: Defines the port of the SMTP server. Default value is "25". Optional.<br />
; 'SmtpAuthenticationUsername'<br />
: 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.<br />
; 'SmtpAuthenticationPassword'<br />
: 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.<br />
; 'SmtpEnableSSL'<br />
: 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.<br />
<br />
== Example ==<br />
The following example will send an e-mail message to multiple recipients.<br />
<pre><br />
(SELECT 'EmailFrom', 'example.from@address.com') UNION ALL<br />
(SELECT 'EmailTo', 'recipient.one@address.com,recipient.two@address.com,recipient.three@address.com') UNION ALL<br />
(SELECT 'EmailSubject', 'Example E-mail') UNION ALL<br />
(SELECT 'EmailBody', 'QPR ProcessAnalyzer example script started running.') UNION ALL<br />
(SELECT 'SmtpServer', 'localhost')<br />
--#SendEmail<br />
</pre><br />
<br />
See also [[How to Define the SMTP Server Connection in an On-Site Deployment]].<br />
<br />
=<br/> --#ShowReport =<br />
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.<br />
'''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.<br />
<br />
This command takes two SELECT queries as parameters.<br />
== First Query ==<br />
A user specified SQL query to be shown in the configured Excel sheet. <br />
; <nowiki>'<data>'</nowiki><br />
: Mandatory. The database query whose results are to be returned.<br />
<br />
== Second Query ==<br />
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:<br/><br />
; '<Analysis Parameter>'<br />
: Optional. The [[Analysis Parameters]] given for the operation. Some suggested parameters to be used:<br />
:; 'Title'<br />
:: The title of the created report. If not given, "Report" will be used as a default.<br />
:; 'SheetName'<br />
:: The name of the Excel sheet to be created.<br />
:; 'MaximumCount'<br />
:: The maximum number of rows to show (0 = all, default = 1000).<br />
; '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:<br />
: 1 = don't stop execution of the script, continue running the script from the next statement.<br />
: 0 = stop execution of the current script and show the exception.<br />
: The following script variables will be set and are shown in the script log:<br />
:<code>@_ExceptionOccurred</code> If there was an exception, then this value is 1, otherwise 0. INT<br />
:<code>@_ExceptionType</code> If there was an exception, shows the C# class name for the exception, NVARCHAR(MAX), otherwise NULL.<br />
:<code>@_ExceptionMessage</code> If there was an exception, contains a message that would have been displayed, NVARCHAR(MAX), otherwise NULL.<br />
:<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.<br />
<br />
== Example ==<br />
The following example opens the data table identified by data table name "SqlTable" and project name "Test" as a report.<br />
<pre><br />
(SELECT 'AnalysisType', '18') UNION ALL<br />
(SELECT 'ProjectName', 'Test') UNION ALL<br />
(SELECT 'DataTableName', 'SqlTable') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM #AnalysisResult; <br />
(SELECT 'Title', 'Report1') UNION ALL<br />
(SELECT 'SheetName', 'Sheet1') UNION ALL<br />
(SELECT 'MaximumCount', '0') <br />
--#ShowReport <br />
</pre><br />
<br />
=<br/> --#WriteLog =<br />
Adds the first column values from the preceding SQL statements to the log that is shown after the whole script execution is completed.<br />
<br />
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.<br />
<br />
== Examples ==<br />
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.<br />
<pre><br />
SELECT 'Script started'<br />
SELECT 'Example'<br />
--#WriteLog<br />
PRINT 'Print Example'<br />
</pre></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2552QPR ProcessAnalyzer System Requirements2015-11-23T12:33:25Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, or 2013<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Background Intelligent Transfer Service (BIT)''':<br />
***IIS Server Extension <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
**** BIT Server Extenstion Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated to QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2551QPR ProcessAnalyzer System Requirements2015-11-23T12:31:55Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, or 2013<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Background Intelligent Transfer Service (BIT)''':<br />
***IIS Server Extension <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
**** BIT Server Extenstion Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for SQL Server temp database<br />
* minimum 500GB available SSD or RAID disk for data storage on a disk dedicated for QPR ProcessAnalyzer<br />
* minimum 4 processor cores</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2443QPR ProcessAnalyzer System Requirements2015-10-14T05:58:07Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, or 2013<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Background Intelligent Transfer Service (BIT)''':<br />
***IIS Server Extension <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
**** BIT Server Extenstion Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 16GB Memory<br />
* minimum 500GB available SSD disk for temporary data<br />
* minimum 500GB available RAID or SSD disk for data storage<br />
* minimum 4 core processor</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_System_Requirements&diff=2256QPR ProcessAnalyzer System Requirements2015-09-07T13:44:02Z<p>TeeLeht: </p>
<hr />
<div><br />
__TOC__<br />
<br />
== System Requirements for QPR ProcessAnalyzer Excel Client ==<br />
<br />
The System Requirements for QPR ProcessAnalyzer Excel Client are:<br />
*Microsoft Windows Vista, Microsoft Windows 7, Microsoft Windows 8, or Microsoft Windows 10 operating system<br />
**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.<br />
*Microsoft Office 2007, 2010, or 2013<br />
*Internet connection for connecting to QPR ProcessAnalyzer Service<br />
*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.<br />
<br />
The following components are also required and will be installed if not found on your computer:<br />
*Microsoft .NET Framework 4.5.1 or 4.6<br />
*Microsoft Visual Studio Tools for Office Runtime<br />
<br />
=== Requirements for Using the Script Command --#ImportSapQuery ===<br />
<br />
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]].<br />
<br />
== System Requirements for QPR ProcessAnalyzer Xpress ==<br />
<br />
The requirements specific to QPR ProcessAnalyzer Xpress include the following:<br />
* SQL LocalDB 2012 database <br />
* Internet connection in order to connect to the [[Activation|activation]] server<br />
<br />
== System Requirements for QPR ProcessAnalyzer Server ==<br />
<br />
The system requirements for QPR ProcessAnalyzer Server are as follows:<br />
* Microsoft Windows Server 2008 R2 or 2012 operating system<br />
* Sufficiently powerful enough hardware to run the operating system<br />
* Microsoft SQL Server 2012 or 2014 database, with the following features:<br />
** '''Instance Features''':<br />
*** Database Engine Services<br />
**** SQL Server Replication<br />
**** Full-Text and Semantic Extractions for Search<br />
**** Data Quality Services<br />
** '''Shared Features''':<br />
*** Data Quality Client<br />
*** SQL Server Data Tools<br />
*** Client Tools Connectivity<br />
*** Integration Services<br />
*** Client Tools Backwards Compatibility<br />
*** Management Tools - Basic<br />
**** Management Tools - Complete<br />
*** Distributed Replay Controller<br />
*** Distributed Replay Client<br />
*** Master Data Services<br />
* Microsoft Internet Information Services, with the following role services (features) enabled:<br />
** '''Common HTTP Features''':<br />
*** Default Document<br />
*** Directory Browsing<br />
*** HTTP Errors<br />
*** Static Content <br />
*** HTTP Redirection<br />
** '''Health and Diagnostics''':<br />
*** HTTP Logging <br />
*** Logging Tools <br />
*** Request Monitor <br />
*** Tracing <br />
** '''Security''':<br />
*** Request Filtering <br />
** '''Application Development''':<br />
*** .Net Extensibility 3.5 & 4.5<br />
*** ASP <br />
*** ASP .NET 3.5 & 4.5<br />
** '''Management Tools''':<br />
*** IIS 6 Management Console <br />
*** IIS 6 Management Compatibility<br />
**** IIS 6 Management Console<br />
** '''IIS Hostable Web Core'''<br />
<br />
* The following Features need to be enabled:<br />
** '''.Net Framework 3.5 Features''':<br />
*** .Net Framework 3.5<br />
** '''.Net Framework 4.5 Features''':<br />
*** .Net 4.5<br />
*** ASP.Net 4.5<br />
*** WCF Services<br />
**** HTTP Activation <br />
**** TCP Port Sharing <br />
** '''Background Intelligent Transfer Service (BIT)''':<br />
***IIS Server Extension <br />
** '''Remote server Administration Tools''':<br />
*** Feature Administration Tools <br />
**** BIT Server Extenstion Tools <br />
** '''User Interfaces and Infrastructure''':<br />
*** Graphical Management Tools and Infrastructure<br />
*** Server Graphical Shell<br />
** '''Windows Powershell''':<br />
*** Windows Powershell 2.0, 3.0 and newer if available<br />
*** Windows Powershell ISE<br />
** '''Windows Process Activation Service''':<br />
*** Process Model<br />
*** Configuration APIs<br />
** '''WoW64 Support'''<br />
** The [http://www.iis.net/downloads/microsoft/url-rewrite URL rewrite module]<br />
<br />
If IIS is installed after the system setup, the following command must be run after the setup to enable correct operation:<br />
<pre><br />
aspnet_regiis.exe -i -enable<br />
</pre><br />
<br />
== Supported Web Browsers for QPR ProcessAnalyzer Web Client ==<br />
<br />
QPR ProcessAnalyzer Web Client supports the following web browsers: <br />
*Microsoft Internet Explorer 9 or later<br />
*Mozilla Firefox version 17 or later<br />
*Google Chrome version 23 or later<br />
*Apple Safari 5 or later<br />
<br />
'''Note:''' If you are using Microsoft Internet Explorer, do not turn on the compatibility mode.<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Xpress ==<br />
<br />
QPR ProcessAnalyzer Xpress Excel Client<br />
* minimum 8GB Memory<br />
* minimum 32GB available SSD Disk<br />
* minimum 4 core processor<br />
<br />
== Suggested Hardware for QPR ProcessAnalyzer Pro ==<br />
<br />
QPR ProcessAnalyzer Excel Client <br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer Web Client <br />
* minimum 2GB Memory<br />
<br />
QPR ProcessAnalyzer Service<br />
* minimum 4GB Memory<br />
<br />
QPR ProcessAnalyzer - Microsoft SQL Server Database Server<br />
* minimum 64GB Memory<br />
* minimum 500GB available SSD disk for temporary data<br />
* minimum 500GB available RAID or SSD disk for data storage<br />
* minimum 4 core processor</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=1962QPR ProcessAnalyzer Release Notes2015-06-11T13:01:08Z<p>TeeLeht: /* Next Release: QPR ProcessAnalyzer 2015.4 */</p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br/><br />
<br />
For information on the compatibility of different release versions, see [[Version_Compatibility_Matrix|Version Compatibility Matrix]].<br />
<br />
== Latest Release: QPR ProcessAnalyzer 2015.3 (release date 20.5.2015, life cycle phase: Active) ==<br />
<br />
'''Features:'''<br/><br />
- 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.<br/><br />
- 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]].<br/><br />
- 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.<br/><br />
- 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.<br />
<br/><br />
- 306382: There is a new tool called [[QPR ProcessAnalyzer ScriptLauncher]] which enables running scripts on a QPR ProcessAnalyzer Server.<br />
<br />
'''Fixed Bugs:'''<br/><br />
- 215322: Fixed an issue where attribute value selection in Flow Analysis was not working in Web Client.<br/><br />
- 215422: Fixed an error preventing the use of Web Client when clicking hyperlinks while the page is loading.<br/><br />
- 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.<br/> <br />
- 215775: Fixed an issue where having dots in database names was causing an error.<br/><br />
- 216117: Fixed an issue with changing Analysis settings when Excel table filter was applied.<br/><br />
- 216130: It is no longer allowed to delete a filter when there are bookmarks using that filter in benchmark settings.<br/><br />
- 216135: Fixed an issue with Variation Analysis where an Event Type string was shown as empty.<br/><br />
- 216148: Fixed an error which occurred when the model was saved as a new model from Filter Properties.<br/><br />
- 216159: Fixed an issue where the QPR ProcessAnalyzer Activation Utility did not display the options properly.<br/><br />
- 216162: Fixed an error which occurred when opening Case Analysis.<br/><br />
- 216163: Fixed an error which occurred when a user's default filter had been deleted by another user.<br/><br />
- 216175: Fixed an issue with showing the Flowchart when a bookmark was opened in Web Client.<br/><br />
- 216184: Fixed an issue with cancelling logging in when the server for QPR ProcessAnalyzer was not configured properly.<br/><br />
- 216190: Fixed a performance issue related to reading scripts from the server.<br/><br />
<br />
== Next Release: QPR ProcessAnalyzer 2015.4 (planned release date 11.8.2015)==<br />
<br />
'''Features:'''<br/><br />
- 306379: Scripts now have the [[Data_Extraction,_Transformation,_and_Loading#--.23Run|Run command]] available enabling you to run another script with specified parameters.<br/><br />
- 306406: Scripts can now be [[Script Encryption|encrypted]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216238: Fixed an issue where hidden Excel sheets were created every time a user would open Excel.<br/><br />
- 216350: Fixed an issue with slow Variation Analysis in models having lots of variations.<br/><br />
- 216352: Fixed an issue where import of a model caused variations to be updated for all models.<br/><br />
- 216357: Fixed an issue where QPR ProcessAnalyzer Integration Kit failed in case there was no data to be loaded.<br/><br />
<br />
__TOC__<br />
<br />
== Past Releases ==<br />
<br />
=== QPR ProcessAnalyzer 2015.2 (release date 17.3.2015, life cycle phase: Mature) ===<br />
<br />
'''Features''':<br/><br />
- There's a new QueryObjectProperties function available for QPR ProcessAnalyzer [[Web Service API]].<br/><br />
- The [[Influence Analysis]] now supports the [[Filtering#Include / Exclude Filters|Include and Exclude cases filtering]] and [[Filtering#Runtime Selection|Runtime Selection filtering]].<br/><br />
- 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]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 216050: Fixed an issue in Influence Analysis where empty and non-existing attribute values were combined into '(blank)' subset.<br/><br />
- 216051: Fixed an issue in Influence Analysis where whitespace characters were cut at the end of attribute values.<br/><br />
- 216062: Fixed an issue where the Settings pane disappeared from a bookmarked view.<br/><br />
- 216088: Fixed an issue where Excel Add-in for QPR ProcessAnalyzer crashed on Excel start-up.<br/><br />
- 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.<br/><br />
- 216122: Optimized the Workspace opening to take less time.<br />
<br />
=== QPR ProcessAnalyzer 2015.1 (release date 5.2.2015, life cycle phase: Mature) ===<br />
<br />
'''Features''':<br/><br />
- 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.<br/><br />
- The [[Progress Status|Progress Status dialog]] now shows the Excel add-in activity figures for ongoing operations.<br/><br />
- A new CatchOperationExceptions parameter and related script variables are now supported by QPR ProcessAnalyzer [[Data_Extraction,_Transformation,_and_Loading|script commands]].<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 215360: Fixed an issue where the selections on the Settings pane were not updated after running a script.<br/><br />
- 215515: Fixed a performance issue related to selecting several groups or models in Project Workspace.<br/><br />
- 215707: Fixed an issue where the user received an error message when opening a bookmarked view.<br/><br />
- 215818, 215969: Fixed layout related issues when using the 150% font size setting in the operating system.<br/><br />
- 215855: Fixed an issue related to timestamps when importing events.<br/><br />
- 215867: Fixed a memory issue which occurred when using the ExecuteInClientSide function.<br/><br />
- 215959: Fixed a performance issue related to importing events.<br/><br />
- 215960: Fixed a performance issue related to opening Project Workspace.<br/><br />
- 215980: Fixed a layout related issue for drop-down menus in some Analysis views.<br/><br />
- 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.<br/><br />
- 215966: The "Append = 0" parameter not working with ImportOdbcQuery, ImportOleQuery, ImportSapQuery, and ImportSqlQuery when importing data to temporary tables was fixed.<br/><br />
- 215968: Fixed an issue where the number of events in a model that was copied was not correct.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.4 (release date 28.11.2014, life cycle phase: Mature) ===<br />
<br />
'''Features''':<br/><br />
- It is now possible to configure LDAP authentication to be used as [[Authentication Methods|a user authentication method]].<br/><br />
- 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.<br/><br />
- There is a new [[Progress Log]] listing the recent operations and their progress.<br/><br />
- Microsoft .NET 4.5.1 Framework has been taken into use.<br/><br />
- 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.<br/><br />
- The [[Template:Activating QPR ProcessAnalyzer|activation level limits]] have been updated.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213258: Fixed an issue where generating the Operation Log using the "All" option for the maximum row count caused an error.<br/><br />
- 213703: Fixed an issue where list customization was lost when opening an element.<br/><br />
- 215330: Fixed an issue where some unicode characters were not properly handled in equality checks.<br/><br />
- 215381: A warning message is now displayed to the user before the start of copying a large model.<br/><br />
- 215474: The HealthcareData sample file now contains instructions for using the sample data.<br/><br />
- 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.<br/><br />
- 215677: Fixed an issue where illegal characters in an Excel sheet tab name caused the model import to fail.<br/><br />
- 215678: Fixed an issue related to the handling of broken bookmarks.<br/><br />
- 215691: Fixed an issue where no log was written when opening a sample file failed.<br/><br />
- 215695: Fixed an issue where the View setting panel disappeared in Excel Client when a bookmark was opened.<br/><br />
- 215715: Fixed an issue where Event Analysis showed an incorrect number of events in the A1 cell.<br/><br />
- 215741: Fixed an issue where Variation Analysis was not working correctly on Finnish and German Excel.<br/><br />
- 215773: Fixed an issue where sandbox related information was missing from the Excel log.<br/><br />
- 215837: Fixed an issue where running a script with ImportSAPQuery commands failed randomly.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.3 (release date 16.9.2014, life cycle phase: Mature) ===<br />
<br />
'''Features''':<br/><br />
- Activation is now required for running a [[Installing_QPR_ProcessAnalyzer#Installing_QPR_ProcessAnalyzer_Service|QPR ProcessAnalyzer Service]].<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213234: Fixed an issue where an error message occurred after deleting a model.<br/><br />
- 213784: Fixed an issue in which the internal SQL data type was not supported by Excel for showing in the report.<br/><br />
- 213785: Fixed an issue where an overflow of text data in a single cell occurred.<br/><br />
- 213811: Fixed an issue where opening the Path analysis of some models hanged the Excel client.<br/><br />
- 214106: Fixed a script import issue by removing the support for .pasql import.<br/><br />
- 214612: Fixed an issue where a violation of unique key constraint occurred due to duplicate global ID's.<br/><br />
- 215017: Fixed an issue where cancelling an open Workspace dialog caused an exception.<br/><br />
- 215026: Fixed an issue where trying to import a Data Table via SQL query as an administrator resulted in an error message.<br/><br />
- 215044: Fixed an issue with client version mismatch dialog.<br/><br />
- 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.<br/><br />
- 215183: In the Activation Utility, 'Next' is now the default button instead of 'Back'.<br/><br />
- 215230: Fixed an issue where the first cell of a column in the Excel client was in a different format than the others.<br/><br />
- 215276: Fixed an issue where an error occurred when an ETL script tried to create a table that already existed in the sandbox database.<br/><br />
- 215331: Fixed an issue where you couldn't log in to another database after the current database was deleted.<br/><br />
- 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.<br/><br />
- 215449: Fixed an issue where the official sample file, SAP_OrderToCash, could not be opened from the Excel client.<br/><br />
- 215453: Fixed an issue where an error occurred when trying to import event data to a model as a case attribute.<br/><br />
- 215472: Fixed an issue where deleted filters were not removed completely from a model.<br/><br />
- 215473: Fixed an issue where an empty Flowchart view caused the View title also to disappear from the current view.<br/><br />
- 215482: Fixed an issue where copying a model failed if the attribute type was GUI.<br/><br />
- 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.<br/><br />
- 215498: Fixed an issue where an error occurred when the database connection to QPR ProcessAnalyzer was lost.<br/><br />
- 215506: Fixed an issue where the analysis drawing duration in Excel was missing.<br/><br />
- 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.<br/><br />
- 215515: Fixed an issue where selecting a group of models/projects in Project Workspace caused slowness.<br/><br />
- 215630: Logs were added for checking the sandbox connection when QPR ProcessAnalyzer Xpress is connected to LocalDB.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.2 (release date 18.6.2014, life cycle phase: Mature) ===<br />
<br />
'''Features''':<br/><br />
- 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]]). <br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 214783: Fixed an issue where animation did not work correctly when using Flowchart benchmarking view.<br/><br />
- 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.<br/><br />
- 215160: Fixed an issue where animation did not work for cases with empty attribute values in benchmark settings.<br/><br />
<br />
=== QPR ProcessAnalyzer 2014.1 (release date 23.1.2014, life cycle phase: Retired) ===<br />
'''Features''':<br/><br />
- The [[Operation Log|Operation Log]] now shows the Last Polling Time related to the new asynchronous web service interface in QPR ProcessAnalyzer.<br/><br />
- Version numbering scheme in QPR ProcessAnalyzer was updated.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
- 214640: Fixed an issue where opening the Workspace dialog as an Administrator user took long.<br/><br />
- 215003: Fixed an issue where opening the Workspace dialog took a long time when there were many Data Tables containing a lot of rows.<br/><br />
- 214661: Fixed an issue where variation string was incorrect in Case Analysis if Event Types had been filtered.<br/><br />
- 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.<br/><br />
- 214995: Fixed an issue where importing a large .csv file into a single Data Table in a project created multiple projects and Data Tables.<br/><br />
- 215006: Fixed an issue where the "Append = 0" parameter didn't work when importing data into Data Tables.<br />
<br />
=== QPR ProcessAnalyzer 4.7 (release date 20.11.2013, life cycle phase: End-of-life) ===<br />
'''Features''':<br/><br />
- 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.<br/><br />
- The Flowchart Analysis can now be made to show the progress of each case as an [[Flowchart Animation|animation]].<br />
<br />
=== QPR ProcessAnalyzer 4.6 (release date 9.10.2013, life cycle phase: End-of-life) ===<br />
'''Features''':<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- 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.<br/><br />
- Scripts now have a [[Data_Extraction,_Transformation,_and_Loading#--.23SendEmail|SendEmail]] command available for use with notification purposes.<br/><br />
<br />
'''Fixed Bugs''':<br/><br />
<br />
- 214286: Fixed an issue where in some cases it was impossible to log in to the PA service.<br/><br />
- 214354: Fixed an issue where an exception was thrown when a large CSV file was imported to a data table.<br/><br />
- 214393: Fixed an issue where bookmarks didn't remember excluded cases.<br/><br />
- 214404: Fixed an issue where an error occurred after a project was deleted.<br/><br />
- 214422: Running an empty script caused ProcessAnalyzer Excel client to hang. Now it doesn't.<br/><br />
- 214437: Fixed an issue where importing case attributes or events from a large CSV file created multiple models.<br/><br />
- 214441: Fixed an issue where the @_FilterId variable was not updated properly.<br/><br />
- 214455: Fixed an upgrade issue in QPR ProcessAnalyzer installer.<br/><br />
- 214458: Fixed an issue where an exception was thrown when Manage Scripts button was clicked after the session had expired.<br/><br />
- 214407: QPR ProcessAnalyzer now remembers the SQL Import Connection String and SQL Query values during the login session.<br/><br />
- 214254: Increased the size of the drop-down selection list of import target models so that longer names can be shown.<br/><br />
- 214271: Added some descriptions for the [[Filters#Filters|Filter Rules]].<br/><br />
<br />
=== QPR ProcessAnalyzer 4.5 (release date 28.8.2013, life cycle phase: End-of-life) ===<br />
'''Features''':<br/><br />
- [[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.<br/><br />
- 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.<br/><br />
- There are now [[Script Management#Script Manager|Script Manager]] and [[Script Management#Script Properties|Script Properties]] dialogs available for managing and developing scripts.<br/><br />
- It is now possible to define the target model for the ImportEvents, ImportCaseAttributes (formerly "ImportCaseData"), and RemoveEvents [[Data Extraction, Transformation, and Loading|script]] commands.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213970: The import functionality was refactored.<br/><br />
- 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.<br/><br />
- 213965: Fixed an issue where a "ButtonClick" error was given when the Cancel button was clicked on login after the session had expired.<br/><br />
- 214134: Fixed an issue where the QPR ProcessAnalyzer installer didn't install sample files when installing to Microsoft Office 2013.<br/><br />
- 214015: Added a note to QPR ProcessAnalyzer Wiki, that in some scenarios when installing QPR ProcessAnalyzer, the computer may reboot without prompting the user.<br/><br />
- 213871: Fixed an issue where some QPR ProcessAnalyzer Service users were not visible to even Administrator users.<br/><br />
- 213966: Fixed an issue where an error message was given when filter properties of a deleted model were opened.<br/><br />
- 213903: Fixed an issue where the user was thrown out of QPR ProcessAnalyzer Service after a failed import operation.<br/><br />
- 211971: Fixed an issue where Path Analysis event boxes were incorrectly named when a long name was given to them.<br/><br />
- 214181: Added troubleshooting instructions for dealing with "Invalid Object Name" exception when running a script with #GetAnalysis and #ImportEvents commands.<br/><br />
- 214053: Added notes to QPR ProcessAnalyzer installer and Wiki, that Microsoft Excel should not be running or started during installation.<br/><br />
- 214040: Fixed an issue where the copied model and the source model were not identical.<br/><br />
- 214052: Fixed an issue where the selected filter name was not updated in the Benchmark Filter menu.<br/><br />
- 214249: Some terminology changes were made: "Script Text" -> "Script Code", "ViewId" -> "FilterId", "ViewName" -> "FilterName", and "@_ViewId" -> "@_FilterId".<br/><br />
- 213686: The Flow Analysis performance was optimized a bit.<br/><br />
- 213841: The Include Only and Exclude buttons are now enabled in Path Analysis.<br/><br />
- 214115: Fixed an issue where exporting a deleted model caused an error.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.4 (release date 10.6.2013, life cycle phase: End-of-life) ===<br />
'''Features''':<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ShowReport|ShowReport]] command providing customized reporting.<br/><br />
- Importing data to [[Data Table|Data Tables]] using the Excel Client.<br/><br />
- Support for Windows 8 and Microsoft Office 2013.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23Exit|Exit]] command for stopping script execution.<br/><br />
- [[Data Extraction, Transformation, and Loading#--.23ImportDataTable|ImportDataTable]] command for importing data into [[Data Table|Data Tables]] using a script.<br />
<br />
'''Fixed Bugs''':<br/><br />
- 213486: Querying event attribute values in Case Analysis is now faster.<br/><br />
- 213565: Fixed the issue where the progress indicator moves back and forth between 100% and 90% when copying or importing large models.<br/><br />
- 213780: Fixed the wrong date format in 64-bit Excel Operation Log.<br/><br />
- 213736: It is no longer possible to try login to the QPR ProcessAnalyzer Web Client unless both Login name and Password have been given.<br/><br />
- 213832: Added scrollbar for the QPR ProcessAnalyzer Web Client Bookmark view's Navigator pane.<br/><br />
- 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.<br/><br />
- 213540: Fixed the formatting of Duration Days values to include only two decimals in QPR ProcessAnalyzer Excel Client Case Analysis.<br/><br />
- 213946: Fixed an issue where model export didn't work in QPR ProcessAnalyzer Excel Client.<br/><br />
- 213993: Improved performance of Flowchart Analysis when benchmarking by both start and event attributes.<br/><br />
<br />
=== QPR ProcessAnalyzer 4.3 (release date 23.4.2013, life cycle phase: End-of-life) ===<br />
- [[Data Extraction, Transformation, and Loading|ETL]] capabilities within QPR ProcessAnalyzer for script based transformations, data validations, and extended analysis using load scripts<br/><br />
- [[Duration Analysis]] - added grouping by Week, Quarter, and Year for easier analysis<br/><br />
- Variation Ids in [[Cases|Case Analysis]] for allowing benchmarking by process variation<br/><br />
- Enhanced [[User Rights Report]] for easier user administration and access rights settings<br/><br />
- 32-bit and 64-bit versions available from one installer package for easier delivery<br/><br />
- New [[Start]] button and Login window allow automatic login and now also support logout<br/><br />
- [[Full Screen Mode|Web Client Full Screen Mode]] for maximixing screen space for large graphs and allowing browser based zoom<br/><br />
- Web Client - improved [[Variation Analysis (Web Client)|Variation Analysis]] visualization for showing the variations in a graphical format<br/><br />
- Updated product names: As an existing user, sign-up normally by choosing the Pro option. More options to be released soon...<br/><br />
<br />
=== QPR ProcessAnalyzer 4.0 - Collaboration Release (life cycle phase: End-of-life) ===<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
=== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release (life cycle phase: End-of-life) ===<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
=== QPR ProcessAnalyzer 3.10 - Maintenance Release (life cycle phase: End-of-life) ===<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release (life cycle phase: End-of-life) ===<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
=== QPR ProcessAnalyzer 3.8 - the User Group Management Release (life cycle phase: End-of-life) ===<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
=== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release (life cycle phase: End-of-life) ===<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.5 - the Reporting Release (life cycle phase: End-of-life) ===<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
=== QPR ProcessAnalyzer 3.4 - the Salesforce Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
=== QPR ProcessAnalyzer 3.3 - the Benchmarking Release (life cycle phase: End-of-life) ===<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
=== QPR ProcessAnalyzer 3.2 - the Analysis Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
=== QPR ProcessAnalyzer 3.1 - the Navigation Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
=== QPR ProcessAnalyzer 3.0 - the Cloud Release (life cycle phase: End-of-life) ===<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=917SQL Scripting for ETL2013-04-15T19:46:39Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and switch the ABPD dimension from original EventType to Event Attribute 'Organization' ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult] => Import the event by selecting the column [Organization] as the Event Type. Note: CHANGE this column to the desired dimension for ABPD analysis <br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and combine some event types to a new event type ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], 'COMBINED', [Start Time] FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
=> Select those event type that should be combined and use the new EventType name for them<br/><br />
=> This example replaces 'Sales Order' and 'Shipment' with new EventType name 'COMBINED'<br/><br />
* UNION ALL => Use this statement to build the events from several sub queries<br />
* SELECT [Case], [Event Type], [Start Time] FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
=> Select all other Event Types and include them as they are, ie. no change to these events<br/><br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], 'COMBINED', [Start Time], * FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
UNION ALL<br />
SELECT [Case], [Event Type], [Start Time], * FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and define new event types based on old event types and an event attribute ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], convert(varchar(255),[Event Type]) + '_' + convert(varchar(255),[SAP_User]), [Start Time], * FROM [#AnalysisResult]<br />
=> Create the new EventType by combining original Event Type, a string '_' and event attribute SAP_User<br/><br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], convert(varchar(255),[Event Type]) + '_' + convert(varchar(255),[SAP_User]), [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: calculate the amount of events within same case with same timestamp ==<br />
The following Load Script will:<br/><br />
1.. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
2. Calculate the amount of events within same case with same timestamp<br />
SELECT count(*) FROM [#AnalysisResult] AS AR1, [#AnalysisResult] AS AR2 <br />
=> Return the count(*) as the result of the query<br />
WHERE AR1.[Case] = AR2.[Case] AND AR1.[Event Type] <> AR2.[Event Type] AND AR1.[Start Time] = AR2.[Start Time]<br />
=> Case & Start Time are same in both events, Event Type is different<br />
--#WriteLog<br />
=> show the result to user<br />
<br />
<pre><br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '10') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT count(*) FROM [#AnalysisResult] AS AR1, [#AnalysisResult] AS AR2 <br />
WHERE AR1.[Case] = AR2.[Case] AND AR1.[Event Type] <> AR2.[Event Type] AND AR1.[Start Time] = AR2.[Start Time]<br />
--#WriteLog<br />
<br />
</pre><br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=916SQL Scripting for ETL2013-04-15T19:26:05Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and switch the ABPD dimension from original EventType to Event Attribute 'Organization' ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult] => Import the event by selecting the column [Organization] as the Event Type. Note: CHANGE this column to the desired dimension for ABPD analysis <br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and combine some event types to a new event type ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], 'COMBINED', [Start Time] FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
=> Select those event type that should be combined and use the new EventType name for them<br/><br />
=> This example replaces 'Sales Order' and 'Shipment' with new EventType name 'COMBINED'<br/><br />
* UNION ALL => Use this statement to build the events from several sub queries<br />
* SELECT [Case], [Event Type], [Start Time] FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
=> Select all other Event Types and include them as they are, ie. no change to these events<br/><br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], 'COMBINED', [Start Time], * FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
UNION ALL<br />
SELECT [Case], [Event Type], [Start Time], * FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and define new event types based on old event types and an event attribute ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], convert(varchar(255),[Event Type]) + '_' + convert(varchar(255),[SAP_User]), [Start Time], * FROM [#AnalysisResult]<br />
=> Create the new EventType by combining original Event Type, a string '_' and event attribute SAP_User<br/><br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], convert(varchar(255),[Event Type]) + '_' + convert(varchar(255),[SAP_User]), [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=915SQL Scripting for ETL2013-04-15T19:09:45Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and switch the ABPD dimension from original EventType to Event Attribute 'Organization' ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult] => Import the event by selecting the column [Organization] as the Event Type. Note: CHANGE this column to the desired dimension for ABPD analysis <br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and combine some event types to a new event type ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], 'COMBINED', [Start Time] FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
=> Select those event type that should be combined and use the new EventType name for them<br/><br />
=> This example replaces 'Sales Order' and 'Shipment' with new EventType name 'COMBINED'<br/><br />
* UNION ALL => Use this statement to build the events from several sub queries<br />
* SELECT [Case], [Event Type], [Start Time] FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
=> Select all other Event Types and include them as they are, ie. no change to these events<br/><br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], 'COMBINED', [Start Time] FROM [#AnalysisResult] WHERE [Event Type] IN ('Sales Order', 'Shipment')<br />
UNION ALL<br />
SELECT [Case], [Event Type], [Start Time] FROM [#AnalysisResult] WHERE [Event Type] NOT IN ( 'Sales Order', 'Shipment')<br />
--#ImportEvents<br />
</pre><br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=914SQL Scripting for ETL2013-04-15T18:54:51Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a copy of events and switch the ABPD dimension from original EventType to Event Attribute 'Organization' ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
* SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult] => Import the event by selecting the column [Organization] as the Event Type. Note: CHANGE this column to the desired dimension for ABPD analysis <br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT [Case], [Organization], [Start Time], * FROM [#AnalysisResult]<br />
--#ImportEvents<br />
</pre><br />
<br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=913SQL Scripting for ETL2013-04-15T18:37:57Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult] )<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create an extended copy of existing model with new case attributes ==<br />
This scripts extends the simple model copying script by creating new case attributes from Case Table report<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* SelectedActivityCounts * => Get the counts for all EventTypes<br />
* SelectedEventAttributes * => Get the values for all EventAttributes consolidated to Case level<br />
* ShowDurations 255 => Retrieve all duration columns<br />
* ShowStarts 7 => Retrieve all Starts columns<br />
* ShowEnds 7 => Retrieve all Starts columns<br />
* ShowVariationIds => Retrive the Variation ID for each case<br />
* ShowVariationPaths => Retrieve the ordered list of Event Type Strings for each case<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult] )<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'SelectedActivityCounts', '*') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'ShowDurations', '255') UNION ALL<br />
(SELECT 'ShowStarts', '7') UNION ALL<br />
(SELECT 'ShowEnds', '7') UNION ALL<br />
(SELECT 'ShowVariationIds', 'True') UNION ALL<br />
(SELECT 'ShowVariationPaths', 'True') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=912SQL Scripting for ETL2013-04-15T18:31:18Z<p>TeeLeht: </p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a copy of existing model ==<br />
The following Load Script will:<br/><br />
1. Clear the current contents of the model<br/><br />
2. Select all events from another model defined with ViewId = 1234567. (note: change this Id to be an Id from the default Filter (previously called View) of the source model:<br/><br />
* AnalysisType 6 => Event Table<br />
* MaximumCount 0 => Retrieve all events from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to make a copy<br />
* SelectedEventAttributes * => Get all Event Attributes<br />
* TargetTable #AnalysisResult => Store the result into a temporary SQL table named #AnalysisResult<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
3. Import all events to the current model (#ImportEvents)<br />
<br />
4. Select all case attributes from the source model (defined with ViewId = 1234567)<br />
* AnalysisType 5 => Case Table<br />
* MaximumCount 0 => Retrieve all cases from the model<br />
* ViewId 1234567 => CHANGE THIS to be the Filter ID / ViewId of the source model from which you want to copy case attributes<br />
* SelectedCaseAttributes * => Get all Case Attributes<br />
* TargetTable #AnalysisResult2 => Store the result into a new temporary SQL table named #AnalysisResult2<br />
* #GetAnalysis => Execute the query (stores the result into #AnalysisResult)<br />
<br />
5. Import all case attributes to the current model (#ImportCaseData)<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '6') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedEventAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult] )<br />
--#ImportEvents<br />
<br />
(SELECT 'AnalysisType', '5') UNION ALL<br />
(SELECT 'MaximumCount', '0') UNION ALL<br />
(SELECT 'ViewId', '1234567') UNION ALL<br />
(SELECT 'SelectedCaseAttributes', '*') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult2')<br />
--#GetAnalysis<br />
<br />
SELECT * FROM [#AnalysisResult2]<br />
--#ImportCaseData<br />
</pre><br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=SQL_Scripting_for_ETL&diff=911SQL Scripting for ETL2013-04-15T17:48:08Z<p>TeeLeht: /* Example Load Script */</p>
<hr />
<div>It is possible to load raw data into QPR ProcessAnalyzer and do the data transformation and loading into QPR ProcessAnalyzer Service via '''Load Scripts''' using temporary database tables, so that the resulting transformed data can be used for analyses in QPR ProcessAnalyzer.<br />
<br />
A user with the ManageIntegrations and RunScripts permissions can define a '''Load Script''' in the [[Model Properties]] dialog. The Load Script consists of SQL statements and QPR ProcessAnalyzer commands that take the preceding SQL statements as parameters.<br />
<br />
== Supported QPR ProcessAnalyzer Commands in Load Scripts ==<br />
'''--#GetAnalysis'''<br/><br />
: Creates an analysis from the data which the preceding SQL statements given as parameters provide. The analysis parameters have to be defined in the SQL SELECT statements as follows:<br/><br />
<br />
: <code>SELECT '<Analysis Parameter>', '<Value>'</code><br/><br />
<br />
: See [[Analysis Parameters]] for a list of supported analysis parameters in QPR ProcessAnalyzer.<br />
<br />
: The --#GetAnalysis command supports the following analysis types:<br />
: Case Analysis (5)<br />
: Event Analysis (6)<br />
: Event Type Analysis (7) Note: analysis is in table format only.<br />
: Variation Analysis (8) Note: analysis is in table format only.<br />
: User Report (11)<br />
: OperationLog Analysis (12)<br />
: Flow Analysis (13)<br />
: Influence Analysis (14)<br />
: Integration Table Analysis (18)<br />
<br />
'''--#ImportEvents'''<br/><br />
: Loads Events from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#ImportCaseData'''<br/><br />
: Loads Case Attributes from the data which the preceding SQL statements given as parameters provide.<br />
<br />
'''--#RemoveEvents'''<br/><br />
: Removes all events in the model, but retains Cases, Event Types, and Variations.<br />
<br />
'''--#WriteLog'''<br/><br />
: Displays a log after the script execution is completed.<br />
<br />
== SQL Command Support ==<br />
When transforming data, 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.<br />
<br />
== Terminating Load Scripts ==<br />
A Load Script can be terminated by the following ways:<br />
*The user running the script can click the '''Cancel''' button when the script is running.<br />
*A QPR ProcessAnalyzer Administrator user can terminate the script via the Operations Log.<br />
*The SQL Server System Administrator can kill the session using the script by using e.g. SQL Server Management Studio.<br />
*The Internet Information Services Administrator can recycle the application pool if the Load 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.<br />
*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.<br />
<br />
'''NOTE!'''<br/><br />
Terminating the Load Script will not revert any changes the script has already done in the database before the Cancel button is clicked.<br />
<br />
== Example Load Script: Create a new model from operation log ==<br />
The following Load Script will read the operation log of QPR ProcessAnalyzer and create process model based on those log entries.<br />
Comments:<br />
- AnalysisType 12 => Operation Log<br />
- MaximumCount 10000 => Retrieve only the 10000 most recent operations<br />
<br />
<pre><br />
--#RemoveEvents<br />
<br />
(SELECT 'AnalysisType', '12') UNION ALL<br />
(SELECT 'MaximumCount', '10000') UNION ALL<br />
(SELECT 'TargetTable', '#AnalysisResult')<br />
--#GetAnalysis<br />
<br />
(<br />
SELECT <br />
[Session Id], 'InitializeConnection', DATEADD(ms, 3, [Start Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SqlCore.InitializeConnection'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'InitializeSessionManager', [Start Time], [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type:%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] IN (<br />
'SingletonSessionManager.InitializeSessionManager'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'Start:' + [Name], [Start Time], [Model Id], [Model Name], NULL AS [Error], NULL AS [Message], [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
UNION ALL<br />
(<br />
SELECT <br />
[Session Id], 'End:' + [Name], DATEADD(ms, 3, [End Time]), [Model Id], [Model Name],<br />
(CASE WHEN ([Message] LIKE 'Exception of type%') THEN<br />
'Exception'<br />
ELSE<br />
NULL<br />
END) AS [Error], <br />
[Message], NULL AS [Additional Data]<br />
FROM <br />
#AnalysisResult<br />
WHERE<br />
[End Time] IS NOT NULL<br />
AND [Name] NOT IN (<br />
'SingletonSessionManager.InitializeSessionManager',<br />
'SqlCore.InitializeConnection',<br />
'SqlCore.Dispose'<br />
)<br />
)<br />
--#ImportEvents<br />
<br />
SELECT <br />
[Session Id], [User Id], [User Name]<br />
FROM <br />
#AnalysisResult<br />
GROUP BY<br />
[Session Id], [User Id], [User Name]<br />
HAVING<br />
[User Id] <> 0<br />
--#ImportCaseData<br />
</pre><br />
<br />
[[Category:ETL]]<br />
[[Category:API]]</div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=643QPR ProcessAnalyzer Release Notes2012-11-06T11:27:18Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br />
<br />
== QPR ProcessAnalyzer 4.0 - Collaboration Release ==<br />
- '''Web User Interface''' – Interactive Process Discovery & Analysis with web browser <br/><br />
- '''Collaboration''' – Share analysis results, comments and ideas within the project group <br/><br />
- '''Project Workspace''' – Process models are grouped to projects <br/><br />
<br />
== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release ==<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
== QPR ProcessAnalyzer 3.10 - Maintenance Release ==<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release ==<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
== QPR ProcessAnalyzer 3.8 - the User Group Management Release ==<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release ==<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release ==<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.5 - the Reporting Release ==<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
== QPR ProcessAnalyzer 3.4 - the Salesforce Release ==<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
== QPR ProcessAnalyzer 3.3 - the Benchmarking Release ==<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
== QPR ProcessAnalyzer 3.2 - the Analysis Release ==<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.1 - the Navigation Release ==<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
== QPR ProcessAnalyzer 3.0 - the Cloud Release ==<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLehthttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Release_Notes&diff=446QPR ProcessAnalyzer Release Notes2012-09-18T13:49:41Z<p>TeeLeht: </p>
<hr />
<div>This page introduces each new QPR ProcessAnalyzer release.<br />
<br />
== QPR ProcessAnalyzer 3.11 - Web Portal ‘BETA’ Release ==<br />
- '''BETA version''' of the new '''Web User Interface''' for QPR ProcessAnalyzer <br/><br />
- '''Salesforce Lead process''' supported by Integration Service for Salesforce Cloud <br/><br />
<br />
== QPR ProcessAnalyzer 3.10 - Maintenance Release ==<br />
- Improved '''Security''' <br/><br />
- Improved '''Performance''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.9 - the Real-Time Analysis Release ==<br />
- '''Real-Time analysis''' of continuous event streams using '''Automatic Recalculation''' <br/><br />
- Keep track of 'include/exclude' actions with '''View Filters''' <br/><br />
- '''Improved performance''' utilizing new algorithms and SQL Server 2012 <br/><br />
<br />
== QPR ProcessAnalyzer 3.8 - the User Group Management Release ==<br />
- Enhanced [[User Manager|User Management]] includes '''creation of new User Accounts and Groups''' <br/><br />
- '''[[Influence Analysis]]''' for '''continuous values''' using subsets <br/><br />
- '''[[Use Cases#Filtering Example|Clear filter for Event Types]]''' only – keeps other filters active <br/><br />
<br />
== QPR ProcessAnalyzer 3.7 - the Influence Analysis Release ==<br />
- New '''[[Influence Analysis]]''' reveals '''reasons''' for process variations <br/><br />
- '''User Groups''' for easier access rights settings <br/><br />
- More informative '''Model, View & Report Managers''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.6 - the Attribute Analysis Release ==<br />
<br />
- Show '''Case Attributes''' in Process Analysis <br/><br />
- Show '''Event Attributes''' in Process Analysis <br/><br />
- Profiling for '''Event Attributes''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.5 - the Reporting Release ==<br />
<br />
- Save Analysis views as [[Report|'''Interactive Reports''']] for easy distribution <br/><br />
- '''On-line product documentation''' available in QPR ProcessAnalyzer Wiki at http://devnet.qpr.com/pawiki/ <br/><br />
- '''64-bit version''' for 64-bit Microsoft Excel users <br/><br />
<br />
== QPR ProcessAnalyzer 3.4 - the Salesforce Release ==<br />
<br />
- [[Flows|'''Flow Analysis''']] for benchmarking duration and amount differences in flow level <br/><br />
- [[Benchmarking|'''Benchmarking''']] for process analysis view <br/><br />
- [[Integration Service for Salesforce Cloud|'''Integration Service for Salesforce Cloud''']] – Automated analysis of sales process <br/><br />
<br />
== QPR ProcessAnalyzer 3.3 - the Benchmarking Release ==<br />
<br />
- [[Benchmarking|'''Benchmarking''']] based on '''Case Attributes''' in Path Analysis <br/><br />
- [[Benchmarking|'''Benchmarking''']] for different views in Path Analysis <br/><br />
- [[QPR Connector for QPR ProcessAnalyzer|'''QPR Connector for QPR ProcessAnalyzer''']] product launch for integrating on-premise IT systems <br/><br />
<br />
== QPR ProcessAnalyzer 3.2 - the Analysis Release ==<br />
<br />
- '''Event Type Chart''' showing the order of activities as a Gantt chart <br/><br />
- '''Process Cost Analysis''' with '''Weighted Durations''' <br/><br />
- Improved filtering for '''Path Analysis''' <br/><br />
<br />
== QPR ProcessAnalyzer 3.1 - the Navigation Release ==<br />
<br />
- '''Easy navigation''' between filtered views <br/><br />
- '''Graphical variation''' charts <br/><br />
- '''Event attributes''' available in Cases list <br/><br />
<br />
== QPR ProcessAnalyzer 3.0 - the Cloud Release ==<br />
<br />
- '''Automated Business Process Discovery''' (ABPD) from Cloud <br/><br />
- Support for '''large databases''' <br/><br />
- Integration to '''SAP''' <br/></div>TeeLeht