QPR ProcessAnalyzer Wiki - Recent changes [en]

Create Object-centric Model from Relational Schema

Ollvihe — Fri, 17 Apr 2026 11:40:11 GMT

Create object-centric model datatables

← Older revision		Revision as of 11:40, 17 April 2026
(One intermediate revision by the same user not shown)
Line 121:		Line 121:
	let objectTypeNames = modelObject.Configuration.OcelDataSource.ObjectTypes.Keys;		let objectTypeNames = modelObject.Configuration.OcelDataSource.ObjectTypes.Keys;
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	let objectsDatatableName = modelObject.~~Configuration.OcelDataSource.ObjectTypes[~~objectTypeNames[i]];		let objectsDatatableName = modelObject.OcelObjectTypeConfiguration(objectTypeNames[i]).Datatable;
	let objectsDatatable = Project.DatatableByName(objectsDatatableName);		let objectsDatatable = Project.DatatableByName(objectsDatatableName);
	if (Count(objectsDatatable.Columns.Where(Name == COLUMN_OBJECT_TYPES_OBJECT_ID)) == 0) {		if (Count(objectsDatatable.Columns.Where(Name == COLUMN_OBJECT_TYPES_OBJECT_ID)) == 0) {
Line 139:		Line 139:
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	let objectTypeName = objectTypeNames[i];		let objectTypeName = objectTypeNames[i];
	let objectsDatatableName = modelObject.~~Configuration~~.~~OcelDataSource.ObjectTypes[objectTypeName]~~;		let objectsDatatableName = modelObject.OcelObjectTypeConfiguration(objectTypeName).Datatable;
	let objectsDatatable = Project.DatatableByName(objectsDatatableName);		let objectsDatatable = Project.DatatableByName(objectsDatatableName);
	let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;		let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;
Line 184:		Line 184:
	let sourceColumn = foreignKeys[j].Columns[0].Source;		let sourceColumn = foreignKeys[j].Columns[0].Source;
	let targetColumn = foreignKeys[j].Columns[0].Target;		let targetColumn = foreignKeys[j].Columns[0].Target;
	let objectsDatatableNames = modelObject.~~Configuration.OcelDataSource.ObjectTypes~~.~~Values~~;		let objectsDatatableNames = objectTypeNames.{
			let objectTypeName = _;
			modelObject.OcelObjectTypeConfiguration(objectTypeName).Datatable;
			};
	if (!objectsTable.In(objectsDatatableNames)) {		if (!objectsTable.In(objectsDatatableNames)) {
	throw "Foreign key in the EventTypes datatable \"" + eventsDatatableName + "\" is not referring to an object type table.";		throw "Foreign key in the EventTypes datatable \"" + eventsDatatableName + "\" is not referring to an object type table.";
Line 201:		Line 204:
	let objectTypeName;		let objectTypeName;
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	if (modelObject.~~Configuration.OcelDataSource.ObjectTypes.Get~~(objectTypeNames[i]) == objectsTable) {		if (modelObject.OcelObjectTypeConfiguration(objectTypeNames[i]).Datatable == objectsTable) {
	objectTypeName = objectTypeNames[i];		objectTypeName = objectTypeNames[i];
	break;		break;
Line 274:		Line 277:
	WriteLog("Add object attributes as common event attributes");		WriteLog("Add object attributes as common event attributes");
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	let objectsDatatableName = modelObject.~~Configuration.OcelDataSource.ObjectTypes[~~objectTypeNames[i]];		let objectsDatatableName = modelObject.OcelObjectTypeConfiguration(objectTypeNames[i]).Datatable;
	let objectsDatatable = Project.DatatableByName(objectsDatatableName);		let objectsDatatable = Project.DatatableByName(objectsDatatableName);
	let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;		let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;
Line 320:		Line 323:
	WriteLog("Add data to Event-to-Object table from ObjectTypes tables");		WriteLog("Add data to Event-to-Object table from ObjectTypes tables");
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	let objectsDatatableName = modelObject.~~Configuration.OcelDataSource.ObjectTypes[~~objectTypeNames[i]];		let objectsDatatableName = modelObject.OcelObjectTypeConfiguration(objectTypeNames[i]).Datatable;
	let objectsDatatable = Project.DatatableByName(objectsDatatableName);		let objectsDatatable = Project.DatatableByName(objectsDatatableName);
	let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;		let dateColumns = objectsDatatable.Columns.Where(DataType == "DateTime").Name;
Line 360:		Line 363:
	let TARGET_COLUMN_PREFIX = "Target";		let TARGET_COLUMN_PREFIX = "Target";
	for (let i = 0; i < Count(objectTypeNames); i++) {		for (let i = 0; i < Count(objectTypeNames); i++) {
	let objectsDatatableName = modelObject.~~Configuration.OcelDataSource.ObjectTypes[~~objectTypeNames[i]];		let objectsDatatableName = modelObject.OcelObjectTypeConfiguration(objectTypeNames[i]).Datatable;
	let objectsDatatable = Project.DatatableByName(objectsDatatableName);		let objectsDatatable = Project.DatatableByName(objectsDatatableName);
	let foreignKeys = objectsDatatable.ForeignKeys;		let foreignKeys = objectsDatatable.ForeignKeys;

MCP Tool Examples

Ollvihe — Fri, 17 Apr 2026 00:40:02 GMT

@@ Line 1: / Line 1: @@
-This page contains example scripts that can be used as MCP tools.
+This page contains example scripts intended for use as MCP tools. When developing MCP tool scripts, make sure they return a string value, as this is required for the MCP client's LLM to interpret the output correctly.
 == List of Models ==
 <syntaxhighlight lang="typescript" line>
+let result = Query(#{
 </syntaxhighlight>

QPR ProcessAnalyzer Wiki

Ollvihe — Fri, 17 Apr 2026 00:23:24 GMT

Data Integrations and Connectors

← Older revision		Revision as of 00:23, 17 April 2026
Line 118:		Line 118:
	* [[QPR ProcessAnalyzer API\|QPR ProcessAnalyzer REST API]]		* [[QPR ProcessAnalyzer API\|QPR ProcessAnalyzer REST API]]
	* [[Sample Eventlog Files\|Sample Eventlogs]]		* [[Sample Eventlog Files\|Sample Eventlogs]]
			* [[MCP_Tool_Examples\|MCP Tool Examples]]
	</div>		</div>
	</div>		</div>

MCP Tool Examples

Ollvihe — Fri, 17 Apr 2026 00:23:01 GMT

Created page with "This page contains example scripts that can be used as MCP tools. Make sure to create the MCP tool scripts in a way that they return a string value. == List of Models == <syntaxhighlight lang="typescript" line> </syntaxhighlight>"

New page

This page contains example scripts that can be used as MCP tools.

Make sure to create the MCP tool scripts in a way that they return a string value.

== List of Models ==

<syntaxhighlight lang="typescript" line>

</syntaxhighlight>

QPR ProcessAnalyzer as MCP Server

Ollvihe — Fri, 17 Apr 2026 00:19:54 GMT

← Older revision		Revision as of 00:19, 17 April 2026
(One intermediate revision by the same user not shown)
Line 120:		Line 120:

	</pre>		</pre>

	~~[[Category: QPR ProcessAnalyzer]]~~
	~~[[Category: MCP]]~~

Data Schema Dialog

TeeHiet — Thu, 16 Apr 2026 13:35:18 GMT

TK-63602

← Older revision		Revision as of 13:35, 16 April 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	The Data Schema dialog ~~in QPR ProcessAnalyzer~~ provides a visual way to manage your project's Snowflake datatables and the relationships (foreign keys) between them.<br>		The Data Schema dialog provides a visual way to manage your project's Snowflake datatables and the relationships (foreign keys) between them.<br>

	~~Note: Datatables stored in SQL Server or those used in an object-centric model (Objects, Events, EventToObject, ObjectToObject) are not displayed in this dialog.~~

	~~== Overview ==~~

	The Data Schema dialog displays an entity-relationship (ER) diagram of your datatables and their relations. The ER diagram automatically arranges the datatables and relations for a clear overview. You cannot manually change the position of items.		The Data Schema dialog displays an entity-relationship (ER) diagram of your datatables and their relations. The ER diagram automatically arranges the datatables and relations for a clear overview. You cannot manually change the position of items.

	You can zoom in and out, and pan across the diagram to explore your data schema. The view is constrained to keep the diagram visible.		You can zoom in and out, and pan across the diagram to explore your data schema. The view is constrained to keep the diagram visible. Clicking on a datatable or a relation in the diagram will select it and open a corresponding details panel on the side, allowing you to view and edit its properties. Clicking on an empty area of the diagram will unselect any item and close the panel.<br>
			If your project has no datatables to display, a message "Start by adding a datatable" will appear.

	~~Interaction: Clicking on a datatable~~ or ~~a relation~~ in ~~the diagram will select it and open a corresponding details panel on the side~~, ~~allowing you to view and edit its properties. Clicking on an empty area of the diagram will unselect any item and close the panel.~~		Note that datatables stored in SQL Server or those used in an object-centric model (Objects, Events, EventToObject, ObjectToObject) are not displayed in this dialog.
	~~Initial State: If your project has no datatables to display~~, ~~a message "Start by adding a datatable" will appear~~.

	== Column Display ==		== Column Display ==

Data Schema Dialog

TeeHiet — Thu, 16 Apr 2026 13:24:18 GMT

TK-63602

New page

The Data Schema dialog in QPR ProcessAnalyzer provides a visual way to manage your project's Snowflake datatables and the relationships (foreign keys) between them. 

Note: Datatables stored in SQL Server or those used in an object-centric model (Objects, Events, EventToObject, ObjectToObject) are not displayed in this dialog.

== Overview ==

The Data Schema dialog displays an entity-relationship (ER) diagram of your datatables and their relations. The ER diagram automatically arranges the datatables and relations for a clear overview. You cannot manually change the position of items.

You can zoom in and out, and pan across the diagram to explore your data schema. The view is constrained to keep the diagram visible.

Interaction: Clicking on a datatable or a relation in the diagram will select it and open a corresponding details panel on the side, allowing you to view and edit its properties. Clicking on an empty area of the diagram will unselect any item and close the panel.
Initial State: If your project has no datatables to display, a message "Start by adding a datatable" will appear.

== Column Display ==
A dropdown menu allows you to control the level of detail shown for columns in the datatables. The following selections are available:
* '''Don't show columns''': Hides all columns for a clean, high-level view.
* '''Show key and relation columns''': Displays only primary keys, foreign keys, and the columns they target.
* '''Show all columns''': Shows every column for all datatables in the diagram.

== Permissions ==
Your ability to make changes is determined by your project permissions. If you lack GenericWrite permissions, all fields will be read-only, and buttons for creating new items will be hidden. Deleting datatables requires the DeleteModel permission.

== Handling Invalid Relations ==
When the dialog opens, it checks for invalid relations (e.g., a relation pointing to a non-existent datatable or column). If any are found, an error message will appear with a Delete invalid relations button to remove them.

== Creating a New Datatable ==
# Click the New datatable button to open the "New datatable" side panel.
# Enter a unique name for your datatable in the Datatable name field.
# Click Save.
The new datatable will be created and will appear selected in the diagram, automatically opening the "Datatable details" panel for further configuration. 
The Save button is disabled if the chosen name is already in use by another datatable in the project.

== Datatable Details ==
To edit an existing datatable, select it in the diagram to open the Datatable details panel. This panel has three tabs: Properties, Columns, and Data location.

=== Properties Tab ===
This tab displays key information about the datatable. The Properties tab has the following editable Fields:
* '''Datatable name''': The name of the datatable. Must be unique within the project.
* '''Description''': An optional, multi-line text field for notes.

The Properties tab has the following read-only fields:
* '''Datatable ID''': The system-assigned numeric ID.
* '''Snowflake object type''': Shows if the datatable is a Table or a View in Snowflake.
* '''Row count''': The number of rows in the datatable.
* '''Column count''': The number of columns in the datatable.
* '''Data changed''': Timestamp of the last data load performed via QPR ProcessAnalyzer.
* '''Data changed by''': The user who performed the last data load.
* '''Properties changed''': Timestamp of the last change to the datatable's properties (e.g., name, columns).
* '''Properties changed by''': The user who last changed the properties.
* '''Created''': Timestamp of the datatable's creation.
* '''Created by''': The user who created the datatable.

Click '''Save''' to apply any changes made to the name or description.

=== Columns Tab ===
This tab shows a table of all columns in the datatable, allowing you to add, edit, reorder, and delete them.

==== Editing a Column ====
* To rename a column, simply edit the text in the Column name field. The change is saved automatically when you click outside the textbox. Duplicate column names are not allowed.
* Use the Key checkbox to designate a column as part of the datatable's primary key.
Note that the Data type of an existing column cannot be changed.

==== Adding a New Column ====
# Click on the "Add column" row at the bottom of the table.
# Enter a Column name.
# Select the Data type from the dropdown: Text (default), Decimal, Integer, Date, or Boolean.
# Check the Key box if it's a primary key column.
# Click the save button on that row to create the column. The button is only active when a valid column name is entered.

==== Reordering and Deleting Columns ====
* Drag and drop rows using the handle to reorder columns.
* Click the trashcan icon at the end of a row to delete a column.

=== Data Location Tab ===
This tab specifies where the datatable's data is stored in Snowflake. You can link a datatable to an existing Snowflake table or let the system manage it. The following fields are available:
* '''Snowflake database''': The database name. Leave empty to use the default from the connection string.
* '''Snowflake schema''': The schema name. Leave empty to use the default.
* '''Snowflake table''': The table or view name. Leave empty to use a system-defined table.
Note: Table names cannot start with "pa_dt" or "qprpa_dt" as these are reserved prefixes.
 
If you specify a database, you must also specify the schema and table for the changes to be saved.

=== Deleting a Datatable ===
To delete a datatable, click the '''Delete''' button. This button is hidden if you do not have the DeleteModel permission.

== Managing Relations (Foreign Keys) ==
Relations define how your datatables are linked. You can create and manage these from the Data Schema diagram.

=== Creating a New Relation ===
# Click the '''New relation''' button to open the "New relation" side panel.
# Define the relation by selecting the source and target datatables and columns:
#* Source datatable: The table containing the foreign key.
#* Target datatable: The table the foreign key points to.
#* Source column: The column in the source table.
#* Target column: The column in the target table.
#Click Create.
The new relation will appear as a line connecting the two datatables in the diagram.

=== Editing a Relation ===
To edit an existing relation, select it in the diagram to open the '''Relation details''' panel.

==== Defining Column Pairs ====
* A relation is defined by at least one pair of columns. Use the '''Source datatable''', '''Target datatable''', '''Source column''', and '''Target column''' dropdowns to define the link.
* Only columns with Text or Integer data types can be used in a relation.
* You can add more column pairs for composite keys by clicking the "Add column pair" button.
* Each additional column pair can be deleted by clicking its delete button.

'''Searching''': All dropdown lists include a search field to help you quickly find datatables or columns by name. The search is case-insensitive. 
'''Saving Changes''': Click the Save button to apply your changes. The button is disabled if any dropdown is empty or if the same column is used in multiple pairs within the same relation. 
'''Automatic Closing''': The panel will close without saving if you select another item or click on an empty space in the diagram. 

==== Deleting a Relation ====
To delete a relation, click the '''Delete''' button in the '''Relation details''' panel. A confirmation dialog will appear.

QPR ProcessAnalyzer Project Workspace

TeeHiet — Thu, 16 Apr 2026 12:36:31 GMT

TK-63602

← Older revision		Revision as of 12:36, 16 April 2026
Line 348:		Line 348:
	# Select the datatable to be duplicated.		# Select the datatable to be duplicated.
	# Click the '''Duplicate''' button. A duplicate of the datatable is created.		# Click the '''Duplicate''' button. A duplicate of the datatable is created.

			== Data Schema ==
			See [[Data Schema Dialog]].

	== Bin ==		== Bin ==

QPR ProcessAnalyzer Wiki

Ollvihe — Tue, 14 Apr 2026 13:08:38 GMT

Installing and Configuring

← Older revision		Revision as of 13:08, 14 April 2026
Line 141:		Line 141:
	* [[Snowflake_Connection_Configuration\|Connect to Snowflake]]		* [[Snowflake_Connection_Configuration\|Connect to Snowflake]]
	* [[SAML_2.0_Federated_Authentication\|SAML 2.0 Authentication]]		* [[SAML_2.0_Federated_Authentication\|SAML 2.0 Authentication]]
			* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]]
	* [[QPR ProcessAnalyzer Security Hardening\|Security Hardening]]		* [[QPR ProcessAnalyzer Security Hardening\|Security Hardening]]
	* [[Setting_up_Scripting_Sandbox\|Setting up SQL Scripting Sandbox]]		* [[Setting_up_Scripting_Sandbox\|Setting up SQL Scripting Sandbox]]

Datatable in Expression Language

Ollvihe — Tue, 14 Apr 2026 13:03:19 GMT

Datatable Properties

← Older revision		Revision as of 13:03, 14 April 2026
Line 131:		Line 131:
	\|\|NRows (Integer)		\|\|NRows (Integer)
	\|\|Number of data rows in the datatable.		\|\|Number of data rows in the datatable.
			\|-
			\|\|PrimaryKey (String*)
			\|\|Array of column names that belong to the datatable primary key.
	\|-		\|-
	\|\|Project (Project)		\|\|Project (Project)

QPR MEA Integration

Ollvihe — Tue, 14 Apr 2026 11:51:55 GMT

← Older revision		Revision as of 11:51, 14 April 2026
(3 intermediate revisions by the same user not shown)
Line 44:		Line 44:
	.QueryObjects(		.QueryObjects(
	"[PG.1374444994].Subprocess",		"[PG.1374444994].Subprocess",
	"name, typename",		"name, typename, isBpmnDiagram",
	`Find("Account", Name)`,		`Find("Account", Name)`,
	"name",		"name",
Line 58:		Line 58:
	* '''Object type name''' (String): Defines type of the new object.		* '''Object type name''' (String): Defines type of the new object.
	* '''Name''' (String): Defines name for the new object.		* '''Name''' (String): Defines name for the new object.
	* '''Parent IDs''' (String or String*): MEA ID of parent object. If array is given, every array element specifies one ID.		* '''Parent IDs''' (String or String array): MEA ID of parent object. If array is given, every array element specifies one ID.
	* '''Attributes''' (Dictionary): Key/value pairs of <attribute>/<attribute value> to be set for the created object.		* '''Attributes''' (Dictionary): Key/value pairs of <attribute>/<attribute value> to be set for the created object.
	* '''Options''' (String): Optional options for the operation. See https://kb.qpr.com/qpr2025-1/parameters_and_options.html?anchor=options.		* '''Options''' (String): Optional options for the operation. See https://kb.qpr.com/qpr2025-1/parameters_and_options.html?anchor=options.
Line 73:		Line 73:

	Parameters:		Parameters:
	* '''Object IDs''' (String or String*): One or more MEA IDs of objects to be deleted. If array is given, every array element specifies one ID of object to be deleted.		* '''Object IDs''' (String or String array): One or more MEA IDs of objects to be deleted. If array is given, every array element specifies one ID of object to be deleted.
	* '''Options''' (String): Optional options for the query. See https://kb.qpr.com/qpr2025-1/parameters_and_options.html?anchor=options.		* '''Options''' (String): Optional options for the query. See https://kb.qpr.com/qpr2025-1/parameters_and_options.html?anchor=options.

Line 98:		Line 98:
	"[PG.785401983.683494101]",		"[PG.785401983.683494101]",
	"name"		"name"
			);
			</pre>

			Example: Read BPMN XML 2.0 diagram from QPR ProcessDesigner.
			<pre>
			ProjectByName("TestProject")
			.CreateMeaConnection(#{"ConnectionStringKey": "MeaConnection"})
			.GetAttribute(
			"[PG.123.456]",
			"bpmnxml"
	);		);
	</pre>		</pre>
Line 105:		Line 115:

	Parameters:		Parameters:
	* '''Object IDs''' (String or String*): MEA ID of an object from which the attribute is fetched. If array is given, every array element specifies one ID.		* '''Object IDs''' (String or String array): MEA ID of an object from which the attribute is fetched. If array is given, every array element specifies one ID.
	* '''Attribute''' (String): Name of the attribute that is queried. See https://kb.qpr.com/qpr2025-1/supported_parameters.html.		* '''Attribute''' (String): Name of the attribute that is queried. See https://kb.qpr.com/qpr2025-1/supported_parameters.html.
	* '''Value''' (String): Value to be set for given attribute.		* '''Value''' (String): Value to be set for given attribute.
Line 118:		Line 128:
	"name",		"name",
	"ChangedUser"		"ChangedUser"
			);
			</pre>

			Example: Save BPMN XML 2.0 diagram as the QPR ProcessDesigner diagram.
			<pre>
			ProjectByName("TestProject")
			.CreateMeaConnection(#{"ConnectionStringKey": "MeaConnection"})
			.SetAttribute(
			"[PG.123.456]",
			"bpmnxml",
			"<?xml version='1.0' encoding='UTF-8'?>..."
	);		);
	</pre>		</pre>

QPR ProcessAnalyzer Release Notes

Ollvihe — Mon, 13 Apr 2026 14:50:38 GMT

← Older revision		Revision as of 14:50, 13 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	This page lists all new features and fixed issues for each QPR ProcessAnalyzer release.		This page lists all new features and fixed issues for each QPR ProcessAnalyzer release.

			==NextRelease: QPR ProcessAnalyzer 2026.4==
	[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]		[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]

	==~~Latest~~ Release: QPR ProcessAnalyzer 2026.3 (build 10933) (released date 13.04.2026)==		==Current Release: QPR ProcessAnalyzer 2026.3 (build 10933) (released date 13.04.2026)==
	New features presentation: [https://files.qpr.com/releases/QPR_ProcessAnalyzer_2026_3.pdf QPR_ProcessAnalyzer_2026_3.pdf]		New features presentation: [https://files.qpr.com/releases/QPR_ProcessAnalyzer_2026_3.pdf QPR_ProcessAnalyzer_2026_3.pdf]

QPR ProcessAnalyzer Downloads

Ramwisu — Mon, 13 Apr 2026 12:59:39 GMT

← Older revision		Revision as of 12:59, 13 April 2026
Line 5:		Line 5:
	==QPR ProcessAnalyzer ScriptLauncher==		==QPR ProcessAnalyzer ScriptLauncher==
	[[QPR_ProcessAnalyzer_ScriptLauncher#Installing_ScriptLauncher\|Installation instructions]] for QPR ProcessAnalyzer ScriptLauncher.		[[QPR_ProcessAnalyzer_ScriptLauncher#Installing_ScriptLauncher\|Installation instructions]] for QPR ProcessAnalyzer ScriptLauncher.
			* QPR ProcessAnalyzer ScriptLauncher 2026.3 (build 10933): https://files.qpr.com/releases/QPRProcessAnalyzerScriptLauncher_10933.zip
	* QPR ProcessAnalyzer ScriptLauncher 2026.2 (build 10910): https://files.qpr.com/releases/QPRProcessAnalyzerScriptLauncher_10910.zip		* QPR ProcessAnalyzer ScriptLauncher 2026.2 (build 10910): https://files.qpr.com/releases/QPRProcessAnalyzerScriptLauncher_10910.zip
	* QPR ProcessAnalyzer ScriptLauncher 2026.1 (build 10870): https://files.qpr.com/releases/QPRProcessAnalyzerScriptLauncher_10870.zip		* QPR ProcessAnalyzer ScriptLauncher 2026.1 (build 10870): https://files.qpr.com/releases/QPRProcessAnalyzerScriptLauncher_10870.zip
Line 14:		Line 15:
	==QPR ProcessAnalyzer Server (on Windows)==		==QPR ProcessAnalyzer Server (on Windows)==
	[[Installing_QPR_ProcessAnalyzer_Server_on_Windows\|Windows installation instructions]] for QPR ProcessAnalyzer Server.		[[Installing_QPR_ProcessAnalyzer_Server_on_Windows\|Windows installation instructions]] for QPR ProcessAnalyzer Server.
			* QPR ProcessAnalyzer Server 2026.3 (build 10933): https://files.qpr.com/releases/QPRProcessAnalyzerServer_10933.zip
	* QPR ProcessAnalyzer Server 2026.2 (build 10910): https://files.qpr.com/releases/QPRProcessAnalyzerServer_10910.zip		* QPR ProcessAnalyzer Server 2026.2 (build 10910): https://files.qpr.com/releases/QPRProcessAnalyzerServer_10910.zip
	* QPR ProcessAnalyzer Server 2026.1 (build 10870): https://files.qpr.com/releases/QPRProcessAnalyzerServer_10870.zip		* QPR ProcessAnalyzer Server 2026.1 (build 10870): https://files.qpr.com/releases/QPRProcessAnalyzerServer_10870.zip

QPR ProcessAnalyzer Release Notes

Ramwisu — Mon, 13 Apr 2026 12:58:37 GMT

← Older revision		Revision as of 12:58, 13 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	This page lists all new features and fixed issues for each QPR ProcessAnalyzer release.		This page lists all new features and fixed issues for each QPR ProcessAnalyzer release.

	~~==Next Release: QPR ProcessAnalyzer 2026.3 (planned release during week of April 6th)==~~
	[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]		[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]

			==Latest Release: QPR ProcessAnalyzer 2026.3 (build 10933) (released date 13.04.2026)==
	New features presentation: [https://files.qpr.com/releases/QPR_ProcessAnalyzer_2026_3.pdf QPR_ProcessAnalyzer_2026_3.pdf]		New features presentation: [https://files.qpr.com/releases/QPR_ProcessAnalyzer_2026_3.pdf QPR_ProcessAnalyzer_2026_3.pdf]

Line 25:		Line 25:
	* Better error message is shown when invalid value is specified to dashboard aspect ratio flex, chart margin, dashboard margin, external content border width, or external content border corner radius. (D-14805)		* Better error message is shown when invalid value is specified to dashboard aspect ratio flex, chart margin, dashboard margin, external content border width, or external content border corner radius. (D-14805)
	* Improved error message when object-centric model perspective doesn't have the object type correctly defined. (D-14795)		* Improved error message when object-centric model perspective doesn't have the object type correctly defined. (D-14795)
			* Reduced project properties dialog minimum height to fit for smaller screens. (D-14834)
			* Updated NLTK to version 3.9.3. (D-14829)

	===Other improvements===		===Other improvements===
Line 30:		Line 32:
	* Backend components have been updated. (B-09027)		* Backend components have been updated. (B-09027)

	==~~Current Release:~~ Additional release for QPR ProcessAnalyzer 2026.2 (build 10910) (released date 16.3.2026)==		==Additional release for QPR ProcessAnalyzer 2026.2 (build 10910) (released date 16.3.2026)==

	===New features===		===New features===

Next Release Roadmap

Ollvihe — Mon, 13 Apr 2026 12:36:26 GMT

← Older revision		Revision as of 12:36, 13 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	<!--~~10931~~-->		<!--10933-->
	This page contains preliminary information about new features and fixed issues in the next release.		This page contains preliminary information about new features and fixed issues in the next release.

	~~==New features in next release==~~
	* Units can be specified for object counts for each object types in object-centric models. (''B-08992'')

	==Features under work==		==Features under work==
	* Data models with datatables and relations can be visualized and modified with ER diagrams. (''B-09023'')		* Data models with datatables and relations can be visualized and modified with ER diagrams. (''B-09023'')
			* Open and save BPMN diagrams stored in QPR ProcessDesigner. (''B-09041'')

	Note: Features and fixes currently under work are not necessarily targeting to the next release.		Note: Features and fixes currently under work are not necessarily targeting to the next release.
	__NOTOC__		__NOTOC__

QPR ProcessAnalyzer Release Notes

Ramwisu — Mon, 13 Apr 2026 11:13:47 GMT

← Older revision		Revision as of 11:13, 13 April 2026
(One intermediate revision by the same user not shown)
Line 3:		Line 3:
	==Next Release: QPR ProcessAnalyzer 2026.3 (planned release during week of April 6th)==		==Next Release: QPR ProcessAnalyzer 2026.3 (planned release during week of April 6th)==
	[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]		[[Next_Release_Roadmap\|See roadmap for next release features and fixes]]

			New features presentation: [https://files.qpr.com/releases/QPR_ProcessAnalyzer_2026_3.pdf QPR_ProcessAnalyzer_2026_3.pdf]

	===New features===		===New features===

QPR MEA Integration

Ollvihe — Mon, 13 Apr 2026 10:40:17 GMT

MEA Connection String

← Older revision		Revision as of 10:40, 13 April 2026
Line 13:		Line 13:
	* '''logOnName''': Log on name of the user who will access the QPR MEA Web Service.		* '''logOnName''': Log on name of the user who will access the QPR MEA Web Service.
	* '''password''': User's password in QPR MEA.		* '''password''': User's password in QPR MEA.

			All QPR ProcessAnalyzer users who have access to the project where the connection string is stored, can use the MEA connection. The MEA user permissions in the connection string determine what operations can be done in the MEA side. For security reasons, if the intention is only to fetch data, the read-only permissions are sufficient for the MEA user.

	Example connection string:		Example connection string:
Line 19:		Line 21:
	</pre>		</pre>

	Example to store secret:		Example to store the connection string as a secret:
	<pre>		<pre>
	ProjectById(1).SetSecret("QprMea", "MeaConnection", `{ "url": "https://<hostname>/QPR/Portal/QPR.Isapi.dll/wsforward/MainService.svc/webHttp", "logOnName": "MyUser", "password": "MyPassword" }`);		ProjectById(1).SetSecret("QprMea", "MeaConnection", `{ "url": "https://<hostname>/QPR/Portal/QPR.Isapi.dll/wsforward/MainService.svc/webHttp", "logOnName": "MyUser", "password": "MyPassword" }`);

← Older revision		Revision as of 13:08, 14 April 2026
Line 141:		Line 141:
	* [[Snowflake_Connection_Configuration\|Connect to Snowflake]]		* [[Snowflake_Connection_Configuration\|Connect to Snowflake]]
	* [[SAML_2.0_Federated_Authentication\|SAML 2.0 Authentication]]		* [[SAML_2.0_Federated_Authentication\|SAML 2.0 Authentication]]
			* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]]
	* [[QPR ProcessAnalyzer Security Hardening\|Security Hardening]]		* [[QPR ProcessAnalyzer Security Hardening\|Security Hardening]]
	* [[Setting_up_Scripting_Sandbox\|Setting up SQL Scripting Sandbox]]		* [[Setting_up_Scripting_Sandbox\|Setting up SQL Scripting Sandbox]]

← Older revision		Revision as of 13:03, 14 April 2026
Line 131:		Line 131:
	\|\|NRows (Integer)		\|\|NRows (Integer)
	\|\|Number of data rows in the datatable.		\|\|Number of data rows in the datatable.
			\|-
			\|\|PrimaryKey (String*)
			\|\|Array of column names that belong to the datatable primary key.
	\|-		\|-
	\|\|Project (Project)		\|\|Project (Project)