QPR ProcessAnalyzer Release Notes - Revision history

Ollvihe: /* Fixed issues */

2026-06-30T23:47:08Z

Fixed issues

← Older revision		Revision as of 23:47, 30 June 2026
Line 24:		Line 24:

	===Fixed issues===		===Fixed issues===
	* Added decimals selection for numeric and period selection for date type of ~~case/event attribute~~ filter rules, and selected values in filter rules are presented based on these selections. (D-14867)		* Added decimals selection for numeric case/event attribute filter rules and period selection for date type of filter rules, and selected values in filter rules are presented based on these selections. (D-14867)
	* Older datatables having null value as json configuration broke modification operations for all datatables in the same project. (D-14887)		* Older datatables having null value as json configuration broke modification operations for all datatables in the same project. (D-14887)
	* Fixed an HTTP header related issue in MCP OAuth authentication with Microsoft Copilot agents. (D-14893)		* Fixed an HTTP header related issue in MCP OAuth authentication with Microsoft Copilot agents. (D-14893)

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T21:10:17Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 21:10, 24 June 2026
Line 6:		Line 6:

	<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">		<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
	~~'''~~Known issue:~~'''~~ QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.		Known issue: QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.

	To fix the issue for this release, run the following SQL command to convert values to strings:		To fix the issue for this release, run the following SQL command to convert values to strings:

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T12:00:10Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 12:00, 24 June 2026
Line 8:		Line 8:
	'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.		'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.

	To fix the issue, run the following SQL command to convert values to strings:		To fix the issue for this release, run the following SQL command to convert values to strings:
	<pre>		<pre>
	UPDATE [PA_CONFIGURATION]		UPDATE [PA_CONFIGURATION]

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T11:59:21Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 11:59, 24 June 2026
Line 8:		Line 8:
	'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.		'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.

	To ~~prevent or~~ fix the issue, ~~follow these steps:~~		To fix the issue, run the following SQL command to convert values to strings:

	~~'''1.''' Run~~ the following SQL ~~query against the database~~ to ~~identify any setting values that are non-textual:~~
	~~<pre>~~
	~~SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType~~
	~~FROM [PA_CONFIGURATION]~~
	~~WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')~~
	~~</pre>~~

	~~'''2.''' If the query returns any rows,~~ convert ~~the non-textual~~ values to ~~a textual data type by running the following SQL before updating to this release~~:
	<pre>		<pre>
	UPDATE [PA_CONFIGURATION]		UPDATE [PA_CONFIGURATION]
	SET [CFG_VALUE] = CAST([CFG_VALUE] AS NVARCHAR(4000))		SET [CFG_VALUE] = CAST([CFG_VALUE] AS NVARCHAR(4000))
	~~WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')~~
	</pre>		</pre>
	</div>		</div>

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T11:55:51Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 11:55, 24 June 2026
Line 6:		Line 6:

	<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">		<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
	'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration ~~error. The~~ issue ~~occurs~~ when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types.		'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration issue, occurring when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types. This issue will be fixed in the next release.

	To prevent or fix the issue, follow these steps:		To prevent or fix the issue, follow these steps:

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T08:45:36Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 08:45, 24 June 2026
Line 11:		Line 11:

	'''1.''' Run the following SQL query against the database to identify any setting values that are non-textual:		'''1.''' Run the following SQL query against the database to identify any setting values that are non-textual:

	<pre>		<pre>
	SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType		SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType
Line 18:		Line 17:
	</pre>		</pre>

	'''2.''' If the query returns any rows, convert the non-textual values to a textual data type by running the following SQL ''before'' updating to this release:		'''2.''' If the query returns any rows, convert the non-textual values to a textual data type by running the following SQL before updating to this release:

	<pre>		<pre>
	UPDATE [PA_CONFIGURATION]		UPDATE [PA_CONFIGURATION]
Line 25:		Line 23:
	WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')		WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')
	</pre>		</pre>

	~~If you have already updated and ProcessAnalyzer fails to start, run the conversion query above and then retry the database migration.~~
	</div>		</div>

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T08:43:47Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 08:43, 24 June 2026
Line 6:		Line 6:

	<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">		<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
	Known issue: QPR ProcessAnalyzer might ~~not~~ start after updating to this release, due to ~~the~~ database migration ~~failing~~. To fix the issue, the ~~PA_CONFIGURATION table needs~~ to ~~be changed as follows~~:		'''Known issue:''' QPR ProcessAnalyzer might fail to start after updating to this release due to a database migration error. The issue occurs when the <code>PA_CONFIGURATION</code> table contains setting values (<code>CFG_VALUE</code>) stored in non-textual data types.

			To prevent or fix the issue, follow these steps:

			'''1.''' Run the following SQL query against the database to identify any setting values that are non-textual:

	~~Run the following SQL query to the database (returning possible setting values that are non-textual):~~
	<pre>		<pre>
	SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType		SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType
Line 15:		Line 18:
	</pre>		</pre>

	If ~~there are~~ any non-textual ~~setting~~ values ~~(CFG_VALUE), the values need~~ to ~~be converted into~~ textual before updating to this release~~. Use the following SQL to convert values to textual~~:		'''2.''' If the query returns any rows, convert the non-textual values to a textual data type by running the following SQL ''before'' updating to this release:

	<pre>		<pre>
	UPDATE [PA_CONFIGURATION]		UPDATE [PA_CONFIGURATION]
Line 21:		Line 25:
	WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')		WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')
	</pre>		</pre>

			If you have already updated and ProcessAnalyzer fails to start, run the conversion query above and then retry the database migration.
	</div>		</div>

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T08:39:36Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 08:39, 24 June 2026
Line 6:		Line 6:

	<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">		<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
	Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to ~~a failing~~ database migration. To fix the issue, the PA_CONFIGURATION table needs to be changed as follows:		Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to the database migration failing. To fix the issue, the PA_CONFIGURATION table needs to be changed as follows:

	~~(1)~~ Run the following SQL query to the database (returning possible setting values that are non-textual):		Run the following SQL query to the database (returning possible setting values that are non-textual):
	<pre>		<pre>
	SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType		SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType
Line 21:		Line 21:
	WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')		WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')
	</pre>		</pre>

	~~(2) Make sure that there are no duplicate setting names (CFG_KEY) in the database. All duplicate rows must be removed before updating to this release.~~
	</div>		</div>

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-24T00:09:06Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 00:09, 24 June 2026
Line 8:		Line 8:
	Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to a failing database migration. To fix the issue, the PA_CONFIGURATION table needs to be changed as follows:		Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to a failing database migration. To fix the issue, the PA_CONFIGURATION table needs to be changed as follows:

	(1) Run the following SQL query to the database:		(1) Run the following SQL query to the database (returning possible setting values that are non-textual):
	<pre>		<pre>
	SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType		SELECT [CFG_KEY], [CFG_VALUE], SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') AS BaseType
Line 14:		Line 14:
	WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')		WHERE SQL_VARIANT_PROPERTY([CFG_VALUE], 'BaseType') NOT IN ('varchar', 'nvarchar')
	</pre>		</pre>
	~~It returns possible setting values (CFG_VALUE) that are not textual. If there are any, the values need to be converted into textual before updating to this release.~~

	Use the following SQL to convert values to textual:		If there are any non-textual setting values (CFG_VALUE), the values need to be converted into textual before updating to this release. Use the following SQL to convert values to textual:
	<pre>		<pre>
	UPDATE [PA_CONFIGURATION]		UPDATE [PA_CONFIGURATION]

Ollvihe: /* Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026) */

2026-06-23T23:39:21Z

Current Release: QPR ProcessAnalyzer 2026.5 (build 10981) (released 23.6.2026)

← Older revision		Revision as of 23:39, 23 June 2026
Line 6:		Line 6:

	<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">		<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
	Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to a failing database migration. To ~~avoid~~ the issue, the PA_CONFIGURATION table ~~might need~~ to be changed as follows:		Known issue: QPR ProcessAnalyzer might not start after updating to this release, due to a failing database migration. To fix the issue, the PA_CONFIGURATION table needs to be changed as follows:

	(1) Run the following SQL query to the database:		(1) Run the following SQL query to the database: