QPR ProcessAnalyzer Wiki - Recent changes [en]

Datatable in Expression Language

Ollvihe — Fri, 14 Aug 2026 18:38:18 GMT

Datatable Properties

← Older revision		Revision as of 18:38, 14 August 2026
Line 66:		Line 66:
	\|\|DataSourceObjectType (String)		\|\|DataSourceObjectType (String)
	\|\|		\|\|
	Returns '''~~table~~''' if the source data ~~comes~~ from a database table, and '''~~view~~''' if the data ~~comes~~ from a database view. When datasource type is ''~~view~~'', any operations to modify the datatable data are not possible. When a datatable with the datasource type ''~~view~~'' is deleted, the underlying database view is not deleted, because the views are managed by users directly in the Snowflake. When a datatable with the datasource type ''~~table~~'' is deleted, the underlying database table is deleted, because the tables are managed by QPR ProcessAnalyzer automatically.		Returns '''Table''' if the source data originates from a database table, and '''View''' if the data originates from a database view. When datasource type is ''View'', any operations to modify the datatable data are not possible. When a datatable with the datasource type ''View'' is deleted, the underlying database view is not deleted, because the views are managed by users directly in the Snowflake. When a datatable with the datasource type ''Table'' is deleted, the underlying database table is deleted, because the tables are managed by QPR ProcessAnalyzer automatically.
	\|-		\|-
	\|\|DataSourceType (String)		\|\|DataSourceType (String)

Next Release Roadmap

Ollvihe — Fri, 14 Aug 2026 09:56:20 GMT

← Older revision		Revision as of 09:56, 14 August 2026
(One intermediate revision by the same user not shown)
Line 24:		Line 24:
	* DatetimeTruncation didn't work for Attribute filter rule when filtering events. (''D-14886'')		* DatetimeTruncation didn't work for Attribute filter rule when filtering events. (''D-14886'')
	* "Design diagrams" appeared twice in the Analyzed entities list in chart settings. (''D-14936'')		* "Design diagrams" appeared twice in the Analyzed entities list in chart settings. (''D-14936'')
			* Event type mapping setting didn't work with expression filter rules. (''D-14898'')
			* Chart export created file with only an underscore as name if chart title only contained a space. (''D-14930'')

	==Features under work==		==Features under work==
Line 35:		Line 37:
	* Fixed issue where setting dashboard level perspective didn't update chart to use the perspective. (''D-14814'')		* Fixed issue where setting dashboard level perspective didn't update chart to use the perspective. (''D-14814'')
	* Sorting failed in AI root causes presets when sorting by contributor. (''D-14884'')		* Sorting failed in AI root causes presets when sorting by contributor. (''D-14884'')
	* Event type mapping setting didn't work with expression filter rules. (''D-14898'')
	* Chart export created file with only an underscore as name if chart title only contained a space. (''D-14930'')

	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__

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 21:46:53 GMT

Get Model Details

← Older revision		Revision as of 21:46, 13 August 2026
(7 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
			This feature is available in the QPR ProcessAnalyzer 2026.6 release.
			</div>

	QPR ProcessAnalyzer ships with the following built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.		QPR ProcessAnalyzer ships with the following built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.

Line 10:		Line 14:
	A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (datatables, columns, object types), and finally use several calls for the '''Generic Query''' to perform analyses from different viewpoints to answer to the questions of interest.		A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (datatables, columns, object types), and finally use several calls for the '''Generic Query''' to perform analyses from different viewpoints to answer to the questions of interest.

	== Tools==		== Built-in Tools==
	=== List Available Process Models ===		=== List Available Process Models ===
	Lists all QPR ProcessAnalyzer models in the server where the user has permissions. For each model it returns basic metadata such as the model ID, name, and description, and whether it is object-centric or case-centric. This tool is read-only.		Lists all QPR ProcessAnalyzer models in the server where the user has permissions. For each model it returns basic metadata such as the model ID, name, and description, and whether it is object-centric or case-centric. This tool is read-only.
Line 25:		Line 29:
	'''Outputs.''' The tool returns an object describing the model. It contains the same identity and audit fields as a model object from '''List Available Process Models''' (id, name, description, isObjectCentric, createdDate, createdBy, modifiedDate, and modifiedBy). In addition, it includes a configuration object holding the model's configuration (for object-centric models this includes the OcelDataSource block with the available object types), and a usedDataTables array describing the data tables used by the model.		'''Outputs.''' The tool returns an object describing the model. It contains the same identity and audit fields as a model object from '''List Available Process Models''' (id, name, description, isObjectCentric, createdDate, createdBy, modifiedDate, and modifiedBy). In addition, it includes a configuration object holding the model's configuration (for object-centric models this includes the OcelDataSource block with the available object types), and a usedDataTables array describing the data tables used by the model.

	Each datatable entry includes its ID, name and description, its audit fields (~~createdDate~~, ~~createdBy~~, ~~modifiedDate~~, ~~modifiedBy~~), and its configuration. It also reports the ~~dataSourceType~~ (Snowflake or SQL Server), the ~~dataSourceObjectType~~ (Table or View), and ~~nRows,~~ the number of rows in the underlying data source table (nullable). Each ~~data table~~ further contains a columns ~~array~~ and ~~a foreignKeys array~~.		Each datatable entry includes its ID, name and description, its audit fields (created fate, created by, modified date, modified by), and its configuration. It also reports the data source type (Snowflake or SQL Server), the data source object type (Table or View), and the number of rows in the underlying data source table (nullable). Each datatable further contains columns and foreign keys.

	Every column reports its Name, its Data type (one of Any, String, Boolean, Integer, Float, DateTime~~, or Duration~~)~~, the corresponding DataTypeInDataSource~~, and a ~~PrimaryKey~~ flag that is true only when the column is a primary key of the ~~data table~~. Each foreign key defines a TargetDatatable (the referenced datatable) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.		Every column reports its Name, its Data type (one of Any, String, Boolean, Integer, Float, or DateTime), and a Primary key flag that is true only when the column is a primary key of the datatable. Each foreign key defines a TargetDatatable (the referenced datatable) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.

	=== Generic Query ===		=== Run Generic Query ===
	Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. The tool supports both case-centric models and object-centric (OCPM) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.		Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. The tool supports both case-centric models and object-centric (OCPM) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.

	'''Inputs.''' The tool takes a single required object parameter, query configuration, which describes the query using the QPR ProcessAnalyzer standard query syntax and expression language. It identifies the model to query, the root dataset to operate on~~, the processing method and execution context~~, an optional ~~pre-~~filter, and the dimensions and values that shape the output~~. The detailed format of this configuration follows the standard ProcessAnalyzer query syntax and is not described further here~~.		'''Inputs.''' The tool takes a single required object parameter, [[Web_API:_Expression/query\|query configuration]], which describes the query using the QPR ProcessAnalyzer standard query syntax and expression language. It identifies the model to query, the root dataset to operate on, an optional filter, and the dimensions and values that shape the output.

	'''Outputs.''' The result is ~~returned as~~ a ~~data frame~~ consisting of ~~a Columns array and a Rows array. Each entry in Columns describes one result column with a Name~~ and ~~a DataType (the column's value type). Each entry in Rows is a data row holding one value per column~~.		'''Outputs.''' The result is a tabular dataset consisting of rows and named columns.

QPR ProcessAnalyzer Wiki

Ollvihe — Thu, 13 Aug 2026 21:40:20 GMT

Installing and Configuring

← Older revision		Revision as of 21:40, 13 August 2026
Line 143:		Line 143:
	* [[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]] ([[Built-in_MCP_Tools\|Built-in MCP ~~tools~~]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])		* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]] ([[Built-in_MCP_Tools\|Built-in MCP Tools]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])
	* [[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]]

PA Configuration database table

Ollvihe — Thu, 13 Aug 2026 21:39:56 GMT

MCP and OAuth Server Settings

← Older revision		Revision as of 21:39, 13 August 2026
Line 167:		Line 167:
	Note that when using OAuth 2.0 authentication the BuiltInOAuthServerConfiguration (see below) needs to be defined with an AcceptedAudiences value other than the default.		Note that when using OAuth 2.0 authentication the BuiltInOAuthServerConfiguration (see below) needs to be defined with an AcceptedAudiences value other than the default.
	* '''ApiRateLimitForSingleUser''' (integer): Maximum number of requests permitted for a user in a minute for the /api/mcp endpoint. Default value is 60. Value zero disables the rate limiter.		* '''ApiRateLimitForSingleUser''' (integer): Maximum number of requests permitted for a user in a minute for the /api/mcp endpoint. Default value is 60. Value zero disables the rate limiter.
	* '''EnabledPrimitives''' (array of strings): List of enabled built-in MCP tools. When set to an empty array ''[]'', all built-in MCP tools are disabled. The default value is ''null'', i.e., all tools are enabled. This setting can be used to temporarily disable ~~incorrectly behaving~~ tools, and for example replace them with custom tools implemented ~~with~~ scripts.		* '''EnabledPrimitives''' (array of strings): List of enabled built-in MCP tools. When set to an empty array ''[]'', all the built-in MCP tools are disabled. The default value is ''null'', i.e., all the MCP tools are enabled. This setting can be used to temporarily disable tools, and for example replace them with custom MCP tools implemented using scripts.
	* '''ServerInstructions''' (string): Optional human-readable instructions delivered to MCP clients in the initialization handshake describing the purpose and capabilities of this MCP server. When not defined, the following default description is used:		* '''ServerInstructions''' (string): Optional human-readable instructions delivered to MCP clients in the initialization handshake describing the purpose and capabilities of this MCP server. When not defined, the following default description is used:
	<pre>		<pre>

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 21:38:53 GMT

Next Release Roadmap

Ollvihe — Thu, 13 Aug 2026 13:00:39 GMT

← Older revision		Revision as of 13:00, 13 August 2026
(2 intermediate revisions by the same user not shown)
Line 27:		Line 27:
	==Features under work==		==Features under work==
	* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')		* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')
	* Workspace ~~usability improvements~~ for ~~managing~~ MCP content. (''B-09112'')		* Workspace has been improved for working with MCP server content. (''B-09112'')
	* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')		* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')
	* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')		* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')
Line 33:		Line 33:

	==Fixes under work==		==Fixes under work==
	* ~~Setting~~ dashboard level perspective ~~does not~~ update chart to use ~~that~~ perspective. (''D-14814'')		* Fixed issue where setting dashboard level perspective didn't update chart to use the perspective. (''D-14814'')
	* Sorting failed in AI root causes presets when sorting by contributor. (''D-14884'')		* Sorting failed in AI root causes presets when sorting by contributor. (''D-14884'')
	* Event type mapping ~~doesn~~'t work with expression filter rules. (''D-14898'')		* Event type mapping setting didn't work with expression filter rules. (''D-14898'')
	* Chart export created file with only an underscore as name if chart title only contained a space. (''D-14930'')		* Chart export created file with only an underscore as name if chart title only contained a space. (''D-14930'')

	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__

Create MCP Tools

Ollvihe — Thu, 13 Aug 2026 12:56:56 GMT

← Older revision		Revision as of 12:56, 13 August 2026
Line 1:		Line 1:
			Users can implement their own custom MCP tools using scripts where all the analytics and expression language features are available. In addition to the custom tools, QPR ProcessAnalyzer comes with [[Built-in_MCP_Tools\|built-in MCP tools]].

	== Creating MCP Tools ==		== Creating MCP Tools ==
	MCP tools are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP tool when the '''MCP tool''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP tool option. Also, only system administrators can modify scripts that are MCP tools, because any changes to the MCP interface is restricted to system administrators for security reasons.		MCP tools are implemented using [[Managing_Scripts\|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP tool when the '''MCP tool''' option is selected in the [[Managing_Scripts#Script_Properties\|Script Properties]]. Only system administrator users can enable the MCP tool option. Also, only system administrators can modify scripts that are MCP tools, because any changes to the MCP interface is restricted to system administrators for security reasons.

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 12:53:11 GMT

Overview

@@ Line 1: / Line 1: @@
-QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools|custom MCP tools]] can be implemented using scripts.
+QPR ProcessAnalyzer ships with the followin built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.
 It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives|EnabledPrimitives]] setting if they are undesired.
@@ Line 5: / Line 8: @@
 The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer|Expression Designer]].
-== List Available Process Models ==
+A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (data tables, columns, object types), and finally use '''Generic Query''' to compute results.
-== Get Model Details ==
+'''Inputs.''' The tool takes a single required object parameter, queryConfiguration, which describes the query using the QPR ProcessAnalyzer standard query syntax and expression language. It identifies the model to query, the root dataset to operate on, the processing method and execution context, an optional pre-filter, and the dimensions and values that shape the output. The detailed format of this configuration follows the standard ProcessAnalyzer query syntax and is not described further here.
-== Generic Query ==
+'''Outputs.''' The result is returned as a data frame consisting of a Columns array and a Rows array. Each entry in Columns describes one result column with a Name and a DataType (the column's value type). Each entry in Rows is a data row holding one value per column.

Generic Properties in Expression Language

Ollvihe — Thu, 13 Aug 2026 12:43:19 GMT

Configuration data properties

← Older revision		Revision as of 12:43, 13 August 2026
(One intermediate revision by the same user not shown)
Line 98:		Line 98:
	\|-		\|-
	\|\|SystemProjects (Project*)		\|\|SystemProjects (Project*)
	\|\|Returns all the built-in system projects. System projects are used by the [[~~Built~~-in_MCP_Tools\|Built-in MCP tools]].		\|\|Returns all the built-in system projects. System projects are used by the [[built-in_MCP_Tools\|Built-in MCP tools]].

	System projects are always available read-only projects, and they have negative ID's. System projects can contain other system objects, such as system scripts. System projects are only stored in memory and not written to the database. System projects are not shown in the UI.		System projects are always available read-only projects, and they have negative ID's. System projects can contain other system objects, such as system scripts. System projects are only stored in memory and not written to the database. System projects are not shown in the UI.
	\|-		\|-
	\|\|SystemScripts (Script*)		\|\|SystemScripts (Script*)
	\|\|Returns all the built-in system scripts. System scripts are used by the [[~~Built~~-in_MCP_Tools\|Built-in MCP tools]]~~. System scripts can be run by any user~~.		\|\|Returns all the built-in system scripts. System scripts are used by the [[built-in_MCP_Tools\|Built-in MCP tools]].

	System scripts are are always available read-only scripts, and they have negative ID's. System scripts located in a system project. System scripts are only stored in memory and are not written to the database. System scripts are not shown in the UI.		System scripts are are always available read-only scripts, and they have negative ID's. System scripts located in a system project. System scripts are only stored in memory and are not written to the database. System scripts are not shown in the UI. System scripts can be run by any user.
	\|-		\|-
	\|\|UserGroups (User*)		\|\|UserGroups (User*)

QPR ProcessAnalyzer Objects in Expression Language

Ollvihe — Thu, 13 Aug 2026 12:42:23 GMT

← Older revision		Revision as of 12:42, 13 August 2026
(One intermediate revision by the same user not shown)
Line 570:		Line 570:
	\|-		\|-
	\|\|IsSystemProject (boolean)		\|\|IsSystemProject (boolean)
	\|\|Returns ''true'' if the project is a system project; otherwise returns ''false''.		\|\|Returns ''true'' if the project is a system project; otherwise returns ''false''. For more information, see [[Generic_Properties_in_Expression_Language#:~:text=SystemProjects\|SystemProjects]].
	\|-		\|-
	\|\|LastModifiedBy (User)		\|\|LastModifiedBy (User)
Line 1,020:		Line 1,020:
	\|-		\|-
	\|\|IsSystemScript (boolean)		\|\|IsSystemScript (boolean)
	\|\|Returns ''true'' if the script is a system script; otherwise returns ''false''.		\|\|Returns ''true'' if the script is a system script; otherwise returns ''false''. For more information, see [[Generic_Properties_in_Expression_Language#:~:text=SystemScripts\|SystemScripts]].
	\|-		\|-
	\|\|Language (String)		\|\|Language (String)

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 12:39:45 GMT

← Older revision		Revision as of 12:39, 13 August 2026
(One intermediate revision by the same user not shown)
Line 3:		Line 3:
	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]].
	~~<pre>~~
	~~Flatten(SystemProjects~~.~~Scripts)~~
	~~</pre>~~

	== List Available Process Models ==		== List Available Process Models ==

Generic Properties in Expression Language

Ollvihe — Thu, 13 Aug 2026 12:38:34 GMT

← Older revision		Revision as of 12:38, 13 August 2026
Line 100:		Line 100:
	\|\|Returns all the built-in system projects. System projects are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]].		\|\|Returns all the built-in system projects. System projects are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]].

	System projects are always available read-only projects, and they have negative ID's. System projects can contain other system objects, such as system scripts. System projects are only stored in memory and not written to the database.		System projects are always available read-only projects, and they have negative ID's. System projects can contain other system objects, such as system scripts. System projects are only stored in memory and not written to the database. System projects are not shown in the UI.
	\|-		\|-
	\|\|SystemScripts (Script*)		\|\|SystemScripts (Script*)
	\|\|Returns all the built-in system scripts. System scripts are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]]. System scripts can be run by any user.		\|\|Returns all the built-in system scripts. System scripts are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]]. System scripts can be run by any user.

	System scripts are are always available read-only scripts, and they have negative ID's. System scripts located in a system project. System scripts are only stored in memory and are not written to the database.		System scripts are are always available read-only scripts, and they have negative ID's. System scripts located in a system project. System scripts are only stored in memory and are not written to the database. System scripts are not shown in the UI.
	\|-		\|-
	\|\|UserGroups (User*)		\|\|UserGroups (User*)

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 12:36:30 GMT

← Older revision		Revision as of 12:36, 13 August 2026
Line 3:		Line 3:
	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language:		The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language in [[Navigation_Menu#Expression_Designer\|Expression Designer]]:
	<pre>		<pre>
	SystemProjects.Scripts~~.Name~~		Flatten(SystemProjects.Scripts)
	</pre>		</pre>

Generic Properties in Expression Language

Ollvihe — Thu, 13 Aug 2026 12:33:27 GMT

Configuration data properties

← Older revision		Revision as of 12:33, 13 August 2026
Line 98:		Line 98:
	\|-		\|-
	\|\|SystemProjects (Project*)		\|\|SystemProjects (Project*)
	\|\|Returns all the built-in system projects.		\|\|Returns all the built-in system projects. System projects are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]].

	* System projects are always available read-only projects.		System projects are always available read-only projects, and they have negative ID's. System projects can contain other system objects, such as system scripts. System projects are only stored in memory and not written to the database.
	* System projects have negative ID's.
	* System projects are only stored in memory and not written to the database.
	* System projects can contain other system objects, such as system scripts.
	\|-		\|-
	\|\|SystemScripts (Script*)		\|\|SystemScripts (Script*)
	\|\|Returns all the built-in system scripts.		\|\|Returns all the built-in system scripts. System scripts are used by the [[Built-in_MCP_Tools\|Built-in MCP tools]]. System scripts can be run by any user.

	* System scripts are are always available read-only scripts.		System scripts are are always available read-only scripts, and they have negative ID's. System scripts located in a system project. System scripts are only stored in memory and are not written to the database.
	* System scripts have negative ID's.
	* System scripts are only stored in memory and are not written to the database.
	* System scripts located in a system project.
	* System scripts can be run by any user.
	\|-		\|-
	\|\|UserGroups (User*)		\|\|UserGroups (User*)

Next Release Roadmap

Ollvihe — Thu, 13 Aug 2026 11:50:57 GMT

← Older revision		Revision as of 11:50, 13 August 2026
Line 10:		Line 10:
	* Backend components have been updated. (''B-09128'')		* Backend components have been updated. (''B-09128'')
	* Model data can be customized in filter rules by specifying source data expression for cases and events. (''B-09127'')		* Model data can be customized in filter rules by specifying source data expression for cases and events. (''B-09127'')
			* Added in-built MCP tools which are always available: List Process Models, Get Model Details, and Generic Query. (''B-09136'')

	==Issues fixed in next release==		==Issues fixed in next release==
Line 22:		Line 23:
	* Fixed issue where database migration for configuration table key failed in specific scenario. (''D-14902'')		* Fixed issue where database migration for configuration table key failed in specific scenario. (''D-14902'')
	* DatetimeTruncation didn't work for Attribute filter rule when filtering events. (''D-14886'')		* DatetimeTruncation didn't work for Attribute filter rule when filtering events. (''D-14886'')
			* "Design diagrams" appeared twice in the Analyzed entities list in chart settings. (''D-14936'')

	==Features under work==		==Features under work==
	* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')		* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')
			* Workspace usability improvements for managing MCP content. (''B-09112'')
	* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')		* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')
	* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')		* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')
	* Added in-built MCP tools which are always available: List Process Models, Get Model Details, and Generic Query. (''B-09136'')
	* Added button to export chart to file, and added "Export available in preview mode" setting to disallow exporting from viewers. (''B-09151'')		* Added button to export chart to file, and added "Export available in preview mode" setting to disallow exporting from viewers. (''B-09151'')

	==Fixes under work==		==Fixes under work==
	* In-~~memory sorting fails~~ in AI root causes presets when sorting by contributor~~: Failed to compare two elements in the array~~. (''D-14884'')		* Setting dashboard level perspective does not update chart to use that perspective. (''D-14814'')
			* Sorting failed in AI root causes presets when sorting by contributor. (''D-14884'')
	* Event type mapping doesn't work with expression filter rules. (''D-14898'')		* Event type mapping doesn't work with expression filter rules. (''D-14898'')
	* ~~"Design diagrams" appeared twice in the Analyzed entities list in~~ chart ~~settings~~. (''D-~~14936~~'')		* Chart export created file with only an underscore as name if chart title only contained a space. (''D-14930'')

	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__

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 10:40:56 GMT

← Older revision		Revision as of 10:40, 13 August 2026
Line 2:		Line 2:

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

			The built-in MCP tools are internally available as system projects containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language:
			<pre>
			SystemProjects.Scripts.Name
			</pre>

	== List Available Process Models ==		== List Available Process Models ==

QPR ProcessAnalyzer Wiki

Ollvihe — Thu, 13 Aug 2026 10:37:18 GMT

Installing and Configuring

← Older revision		Revision as of 10:37, 13 August 2026
Line 143:		Line 143:
	* [[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]] ([[Create_MCP_Tools\|MCP Tools]], [[Create_MCP_Resources\|MCP Resources]], [[Create_MCP_Prompts\|MCP Prompts]])		* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]] ([[Built-in_MCP_Tools\|Built-in MCP tools]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])
	* [[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]]

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 10:36:09 GMT

← Older revision		Revision as of 10:36, 13 August 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.		QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools\|custom MCP tools]] can be implemented using scripts.

	It's possible to temporarily disable the built-in MCP ~~tool~~ if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	== List Available Process Models ==		== List Available Process Models ==

Built-in MCP Tools

Ollvihe — Thu, 13 Aug 2026 10:34:23 GMT

Created page with "QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, custom MCP tools can be implemented using scripts. It's possible to temporarily disable the built-in MCP tool if they are undesired. == List Available Process Models == == Get Model Details == == Generic Query =="

New page

QPR ProcessAnalyzer has the built-in MCP tools described in this page. The built-in tools are always available in the MCP interface. In addition, [[Create_MCP_Tools|custom MCP tools]] can be implemented using scripts.

It's possible to temporarily disable the built-in MCP tool if they are undesired.

== List Available Process Models ==

== Get Model Details ==

== Generic Query ==

QPR ProcessAnalyzer Objects in Expression Language

Ollvihe — Wed, 12 Aug 2026 23:30:52 GMT

Project

← Older revision		Revision as of 23:30, 12 August 2026
(One intermediate revision by the same user not shown)
Line 568:		Line 568:
	\|\|Id (Integer)		\|\|Id (Integer)
	\|\|Id of the Project.		\|\|Id of the Project.
			\|-
			\|\|IsSystemProject (boolean)
			\|\|Returns ''true'' if the project is a system project; otherwise returns ''false''.
	\|-		\|-
	\|\|LastModifiedBy (User)		\|\|LastModifiedBy (User)
Line 1,015:		Line 1,018:
	\|\|Id (Integer)		\|\|Id (Integer)
	\|\|Id of the Script.		\|\|Id of the Script.
			\|-
			\|\|IsSystemScript (boolean)
			\|\|Returns ''true'' if the script is a system script; otherwise returns ''false''.
	\|-		\|-
	\|\|Language (String)		\|\|Language (String)

Generic Properties in Expression Language

Ollvihe — Wed, 12 Aug 2026 23:28:10 GMT

Configuration data properties

@@ Line 96: / Line 96: @@
 The global secrets are available in all projects and scripts in the system. Note that the actual secret value cannot be fetched using the expression language.
 |-
 ||UserGroups (User*)

PA Configuration database table

Ollvihe — Wed, 12 Aug 2026 23:17:29 GMT

MCP and OAuth Server Settings

← Older revision		Revision as of 23:17, 12 August 2026
(One intermediate revision by the same user not shown)
Line 156:		Line 156:
	\|-		\|-
	\|\|McpServerConfiguration		\|\|McpServerConfiguration
	\|\|Used to configure the MCP ~~server built-in to ProcessAnalyzer~~ server. If not set, MCP server functionality is disabled ~~and MCP clients can't access to this server using MCP~~. If set, contains ~~a string representation of~~ a JSON object that supports the following properties:		\|\|Used to configure the QPR ProcessAnalyzer's MCP server. If not set, MCP server functionality is disabled. If set, contains a JSON object that supports the following properties:
	* '''McpApiKey''' (string): ~~If defined and not empty, defines the~~ API key that can be used to connect to QPR ProcessAnalyzer MCP server without any other authentication. Default value is empty.~~<br>~~		* '''McpApiKey''' (string): API key that can be used to connect to QPR ProcessAnalyzer MCP server without any other authentication. Default value is empty. Example:
	Example ~~value when using API Key authentication~~:
	<pre>		<pre>
	{ "McpApiKey": "xnTqr@Hd87JcuCmQZbjUHfwD@" }		{ "McpApiKey": "xnTqr@Hd87JcuCmQZbjUHfwD@" }
Line 167:		Line 166:
	</pre>		</pre>
	Note that when using OAuth 2.0 authentication the BuiltInOAuthServerConfiguration (see below) needs to be defined with an AcceptedAudiences value other than the default.		Note that when using OAuth 2.0 authentication the BuiltInOAuthServerConfiguration (see below) needs to be defined with an AcceptedAudiences value other than the default.
			* '''ApiRateLimitForSingleUser''' (integer): Maximum number of requests permitted for a user in a minute for the /api/mcp endpoint. Default value is 60. Value zero disables the rate limiter.
			* '''EnabledPrimitives''' (array of strings): List of enabled built-in MCP tools. When set to an empty array ''[]'', all built-in MCP tools are disabled. The default value is ''null'', i.e., all tools are enabled. This setting can be used to temporarily disable incorrectly behaving tools, and for example replace them with custom tools implemented with scripts.
			* '''ServerInstructions''' (string): Optional human-readable instructions delivered to MCP clients in the initialization handshake describing the purpose and capabilities of this MCP server. When not defined, the following default description is used:
			<pre>
			This is a QPR ProcessAnalyzer MCP server. It exposes its capabilities as MCP primitives (tools, prompts, and resources). These include built-in primitives mainly used for Process Mining-related tasks, such as analyzing both object-centric and case-centric models and managing the related data. In addition, users can create and publish custom primitives that may cover a wide range of tasks beyond Process Mining, including aggregating and deriving data from various data sources, performing ETL operations, modifying data, running analyses, and retrieving insights from process mining projects.
			</pre>
	\|-		\|-
	\|\|BuiltInOAuthServerConfiguration		\|\|BuiltInOAuthServerConfiguration

Next Release Roadmap

Ollvihe — Wed, 12 Aug 2026 10:28:39 GMT

← Older revision		Revision as of 10:28, 12 August 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	* Added "About" dialog containing QPR patent information, and "User Settings" dialog redesigned to "User Profile" dialog. (''B-09015'')		* Added "About" dialog containing QPR patent information, and "User Settings" dialog redesigned to "User Profile" dialog. (''B-09015'')
	* Dropdown lists show case/event attribute value numbers and dates in ascending order. (''B-09125'')		* Dropdown lists show case/event attribute value numbers and dates in ascending order. (''B-09125'')
			* Updated to Angular 22 and Highcharts 13. (''B-09122'')
			* Backend components have been updated. (''B-09128'')
			* Model data can be customized in filter rules by specifying source data expression for cases and events. (''B-09127'')

	==Issues fixed in next release==		==Issues fixed in next release==
Line 17:		Line 20:
	* When going away from unsaved dashboard but selecting cancel, the unsaved changes dialog didn't appear again. (''D-14859'')		* When going away from unsaved dashboard but selecting cancel, the unsaved changes dialog didn't appear again. (''D-14859'')
	* Improved object-centric model validation when object type datatable is not defined. (''D-14864'')		* Improved object-centric model validation when object type datatable is not defined. (''D-14864'')
			* Fixed issue where database migration for configuration table key failed in specific scenario. (''D-14902'')
			* DatetimeTruncation didn't work for Attribute filter rule when filtering events. (''D-14886'')

	==Features under work==		==Features under work==
	* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')		* Label component changing dashboard variables supports any variable data types, and changing model with ModelId doesn't automatically use model default filter. (''B-09029'')
	* Updated to Angular 22 and Highcharts 13. (''B-09122'')
	* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')		* Dropdown list selector component makes query only when the list is opened to improve performance. (''B-09126'')
	* Model data can be customized in filter rules by specifying source data expression for cases and events. (''B-09127'')
	* Backend component update for release 2026.6. (''B-09128'')
	* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')		* Object-centric model perspective can define from which object types events are counted using EventSourceObjectTypes setting. (''B-09133'')
	* Added in-built MCP tools which are always available: List Process Models, Get Model Details, and Generic Query. (''B-09136'')		* Added in-built MCP tools which are always available: List Process Models, Get Model Details, and Generic Query. (''B-09136'')
	* Added button to export chart to file, and "Export available in preview mode" setting to disallow exporting from viewers. (''B-09151'')		* Added button to export chart to file, and added "Export available in preview mode" setting to disallow exporting from viewers. (''B-09151'')

	==Fixes under work==		==Fixes under work==
	* ~~DatetimeTruncation didn't work for Attribute filter rule~~ when ~~filtering events~~. (''D-~~14886~~'')		* In-memory sorting fails in AI root causes presets when sorting by contributor: Failed to compare two elements in the array. (''D-14884'')
	* Event type mapping doesn't work with expression filter rules. (''D-14898'')		* Event type mapping doesn't work with expression filter rules. (''D-14898'')
	* ~~Fixed issue where database migration for configuration table key failed~~ in ~~specific scenario~~. (''D-~~14902~~'')		* "Design diagrams" appeared twice in the Analyzed entities list in chart settings. (''D-14936'')

	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 Chart

Ollvihe — Tue, 11 Aug 2026 23:08:48 GMT

Exporting charts

← Older revision		Revision as of 23:08, 11 August 2026
(One intermediate revision by the same user not shown)
Line 180:		Line 180:

	== Exporting charts ==		== Exporting charts ==
	~~Charts~~ and ~~flowcharts~~ can be exported to ~~files~~. Available export formats depend on the visualization. The following ~~exports~~ are available:		Chart and flowchart can be exported to a file. Available export file formats depend on the visualization. The following file formats are available:
	* Table:		* Table:
	** Microsoft Excel (XLSX)		** Microsoft Excel (XLSX)
	** CSV file (see below)		** CSV file (see below)
	* Pivot table		* Pivot table
	** Microsoft Excel		** Microsoft Excel (XLSX)
	** PDF document		** PDF document
	** CSV file (see below)		** CSV file (see below)
Line 201:		Line 201:

	When exporting data to a CSV file, the export dialog provides the following configurable settings. Adjust these options to control which data is exported and how it is formatted in the resulting file.		When exporting data to a CSV file, the export dialog provides the following configurable settings. Adjust these options to control which data is exported and how it is formatted in the resulting file.
	* ''Start at row'': The row number at which the export begins. Use this setting to skip a number of rows from the top of the data ~~set~~. For example, entering 1 starts the export from the very first row, while entering 10 skips the first nine rows and begins at the tenth. This is useful when you need to export the data in smaller slices.		* '''Start at row''': The row number at which the export begins. Use this setting to skip a number of rows from the top of the data. For example, entering 1 starts the export from the very first row, while entering 10 skips the first nine rows and begins at the tenth. This is useful when you need to export the data in smaller slices.
	* ''Rows to export'': The total number of rows to include in the export, counted from the Start at row position. For example, if Start at row is 10 and Rows to export is 50, the file will contain rows 10 through 59. Use an empty value to export all available rows.		* '''Rows to export''': The total number of rows to include in the export, counted from the "Start at row" position. For example, if Start at row is 10 and Rows to export is 50, the file will contain rows 10 through 59. Use an empty value to export all available rows.
	* ''Column delimiter'': The character placed between individual data values (cells) within each row to separate one column from the next. Select the delimiter that matches the requirements of the application that will read the file. Note that some regional settings expect a semicolon rather than a comma, especially when the decimal delimiter is also a comma.		* '''Column delimiter''': The character placed between individual data values (cells) within each row to separate one column from the next. Select the delimiter that matches the requirements of the application that will read the file. Note that some regional settings expect a semicolon rather than a comma, especially when the decimal delimiter is also a comma.
	* ''Date format'': The pattern used to format date and time values in the exported file. The format is defined using standard date/time pattern letters, where each letter represents a component of the date or time. For example, the pattern yyyy-MM-dd HH:mm:ss.fff produces a value such as 2026-08-12 14:30:45.123. See the [[Importing_Data_to_Datatable_from_CSV_File#Date_Formats\|supported format parts]].		* '''Date format''': The pattern used to format date and time values in the exported file. The format is defined using standard date/time pattern letters, where each letter represents a component of the date or time. For example, the pattern yyyy-MM-dd HH:mm:ss.fff produces a value such as 2026-08-12 14:30:45.123. See the [[Importing_Data_to_Datatable_from_CSV_File#Date_Formats\|supported date format parts]].
	* ''Decimal delimiter'' — The character used to separate the whole-number (integer) part of a number from its decimal (fractional) part. Typical choices are a period (.) or a comma (,), depending on regional conventions.		* '''Decimal delimiter''': The character used to separate the whole-number (integer) part of a number from its decimal (fractional) part. Typical choices are a period (.) or a comma (,), depending on regional conventions.

	== [[Chart_On-screen_Settings\|On-screen settings]] ==		== [[Chart_On-screen_Settings\|On-screen settings]] ==

← Older revision		Revision as of 21:40, 13 August 2026
Line 143:		Line 143:
	* [[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]] ([[Built-in_MCP_Tools\|Built-in MCP ~~tools~~]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])		* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]] ([[Built-in_MCP_Tools\|Built-in MCP Tools]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])
	* [[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 10:37, 13 August 2026
Line 143:		Line 143:
	* [[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]] ([[Create_MCP_Tools\|MCP Tools]], [[Create_MCP_Resources\|MCP Resources]], [[Create_MCP_Prompts\|MCP Prompts]])		* [[QPR_ProcessAnalyzer_as_MCP_Server\|Configure MCP Server]] ([[Built-in_MCP_Tools\|Built-in MCP tools]], [[Create_MCP_Tools\|Custom MCP Tools]], [[Create_MCP_Resources\|Custom MCP Resources]], [[Create_MCP_Prompts\|Custom MCP Prompts]])
	* [[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 23:30, 12 August 2026
(One intermediate revision by the same user not shown)
Line 568:		Line 568:
	\|\|Id (Integer)		\|\|Id (Integer)
	\|\|Id of the Project.		\|\|Id of the Project.
			\|-
			\|\|IsSystemProject (boolean)
			\|\|Returns ''true'' if the project is a system project; otherwise returns ''false''.
	\|-		\|-
	\|\|LastModifiedBy (User)		\|\|LastModifiedBy (User)
Line 1,015:		Line 1,018:
	\|\|Id (Integer)		\|\|Id (Integer)
	\|\|Id of the Script.		\|\|Id of the Script.
			\|-
			\|\|IsSystemScript (boolean)
			\|\|Returns ''true'' if the script is a system script; otherwise returns ''false''.
	\|-		\|-
	\|\|Language (String)		\|\|Language (String)

← Older revision		Revision as of 21:38, 13 August 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	QPR ProcessAnalyzer ships with the ~~followin~~ built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.		QPR ProcessAnalyzer ships with the following built-in MCP tools that allow an MCP client to explore process models and run analytical queries against them.

	== Overview==		== Overview==
	The built-in tools are ~~always~~ available in the MCP interface. All ~~three~~ tools are read-only: they only retrieve data and never modify models, ~~data tables~~, or any other server-side state. In MCP ~~terms, each tool is annotated with readOnlyHint: true and destructiveHint: false. In addition~~, [[Create_MCP_Tools\|custom MCP tools]] ~~can be implemented~~ using scripts.		The built-in tools are by default available in the MCP interface. All the tools are read-only, so they only retrieve data and never modify models, datatables, or any other server-side state. In addition to the built-in MCP tools, users can implement [[Create_MCP_Tools\|custom MCP tools]] using scripts.

	It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.		It's possible to temporarily disable the built-in MCP tools using the [[PA_Configuration_database_table#:~:text=EnabledPrimitives\|EnabledPrimitives]] setting if they are undesired.

	The built-in MCP tools are ~~internally available as~~ system ~~projects~~ containing system scripts. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in [[Navigation_Menu#Expression_Designer\|Expression Designer]].		The built-in MCP tools are exposed in a ''system project'' (named ''_System'') containing ''system scripts'', one for each built-in MCP tool. System projects and scripts are content that cannot be modified and are not shown in the user interface. The built-in MCP tools can be listed using the expression language by querying '''SystemScripts''' in the [[Navigation_Menu#Expression_Designer\|Expression Designer]].

	A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (~~data tables~~, columns, object types), and finally use '''Generic Query''' to ~~compute results~~.		A typical workflow is to first call '''List Available Process Models''' to find a model of interest, then call '''Get Model Details''' to inspect its structure (datatables, columns, object types), and finally use several calls for the '''Generic Query''' to perform analyses from different viewpoints to answer to the questions of interest.

	== Tools==		== Tools==
	=== List Available Process Models ===		=== List Available Process Models ===
	Lists all ~~process~~ models ~~that are available on~~ the server. For each model it ~~reports~~ basic metadata such as the model ID, name, and description~~, whether the model uses in-memory processing~~, and whether it is object-centric ~~(OCPM/OCEL)~~ or case-centric. This tool is read-only.		Lists all QPR ProcessAnalyzer models in the server where the user has permissions. For each model it returns basic metadata such as the model ID, name, and description, and whether it is object-centric or case-centric. This tool is read-only.

	'''Inputs.''' This tool takes no input parameters ~~(the input schema is an empty object)~~.		'''Inputs.''' This tool takes no input parameters.

	'''Outputs.''' The tool returns an object with a single models property, which is an array of model objects. Each model object contains a unique id (integer), a name and description (strings)~~, an isInMemoryModel flag that is true only when the model uses in-memory processing~~, and an isObjectCentric flag that is true for object-centric (OCPM~~/OCEL~~) models and false for case-centric ones. Each object also includes audit information: createdDate and modifiedDate (ISO date-time strings) together with createdBy and modifiedBy (the names of the users who created and last modified the model). Only models that pass a validity check are included in the result.		'''Outputs.''' The tool returns an object with a single models property, which is an array of model objects. Each model object contains a unique ID (integer), a name and description (strings), and an isObjectCentric flag that is true for object-centric (OCPM) models and false for case-centric ones. Each object also includes audit information: createdDate and modifiedDate (ISO date-time strings) together with createdBy and modifiedBy (the names of the users who created and last modified the model). Only models that pass a validity check are included in the result.

	=== Get Model Details ===		=== Get Model Details ===
	Returns detailed information about a single model, identified by its ID. In addition to the basic metadata also returned by ~~'''~~List Available Process Models~~'''~~, this tool exposes the model's configuration and the ~~data tables~~ it uses, including their columns, data types, primary keys, and foreign keys. This is the recommended way to discover the exact table and column names needed to build a query. This tool is read-only.		Returns detailed information about a single model, identified by its ID. In addition to the basic metadata also returned by the List Available Process Models tool, this tool exposes the model's configuration and the datatables it uses, including their columns, data types, primary keys, and foreign keys. This is the recommended way to discover the exact table and column names needed to build a query. This tool is read-only.

	'''Inputs.''' The tool takes one required parameter, ~~modelId~~ (integer), the identifier of the model to retrieve details for.		'''Inputs.''' The tool takes one required parameter, model ID (integer), the identifier of the model to retrieve details for.

	'''Outputs.''' The tool returns an object describing the model. It contains the same identity and audit fields as a model object from '''List Available Process Models''' (id, name, description~~, isInMemoryModel~~, isObjectCentric, createdDate, createdBy, modifiedDate, and modifiedBy). In addition, it includes a configuration object holding the model's configuration (for object-centric models this includes the OcelDataSource block with the available object types), and a usedDataTables array describing the data tables used by the model.		'''Outputs.''' The tool returns an object describing the model. It contains the same identity and audit fields as a model object from '''List Available Process Models''' (id, name, description, isObjectCentric, createdDate, createdBy, modifiedDate, and modifiedBy). In addition, it includes a configuration object holding the model's configuration (for object-centric models this includes the OcelDataSource block with the available object types), and a usedDataTables array describing the data tables used by the model.

	Each ~~data table~~ entry includes its id, name and description, its audit fields (createdDate, createdBy, modifiedDate, modifiedBy), and its configuration. It also reports the dataSourceType (~~one of Local, Redshift,~~ Snowflake~~, Spark,~~ or ~~SqlServer~~), the dataSourceObjectType (Table or View), and nRows, the number of rows in the underlying data source table (nullable). Each data table further contains a columns array and a foreignKeys array.		Each datatable entry includes its ID, name and description, its audit fields (createdDate, createdBy, modifiedDate, modifiedBy), and its configuration. It also reports the dataSourceType (Snowflake or SQL Server), the dataSourceObjectType (Table or View), and nRows, the number of rows in the underlying data source table (nullable). Each data table further contains a columns array and a foreignKeys array.

	Every column reports its Name, its ~~ProcessAnalyzer DataType~~ (one of Any, String, Boolean, Integer, Float, DateTime, Duration~~, ShortString, or Variant~~), the corresponding DataTypeInDataSource, and a PrimaryKey flag that is true only when the column is a primary key of the data table. Each foreign key defines a TargetDatatable (the referenced ~~data table~~) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.		Every column reports its Name, its Data type (one of Any, String, Boolean, Integer, Float, DateTime, or Duration), the corresponding DataTypeInDataSource, and a PrimaryKey flag that is true only when the column is a primary key of the data table. Each foreign key defines a TargetDatatable (the referenced datatable) and a Columns list of source-to-target column mappings, each mapping a Source column name to a Target column name.

	=== Generic Query ===		=== Generic Query ===
	Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. When the processing method is DataFrame (the default and recommended mode), the calculation is executed directly in the data source (Snowflake or SQL Server), and a tabular result with dimension and value columns is returned. The tool supports both case-centric models and object-centric (OCPM~~/OCEL~~) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.		Runs a generic analytical query against a QPR ProcessAnalyzer model. Queries are written using the QPR ProcessAnalyzer standard query syntax and expression language, which lets you select a root dataset (such as cases, events, variations, or flows), group it into dimensions, and compute aggregated values. The tool supports both case-centric models and object-centric (OCPM) models. Despite its analytical power, this tool is read-only: it only reads and aggregates existing data and never modifies it.

	'''Inputs.''' The tool takes a single required object parameter, ~~queryConfiguration~~, which describes the query using the QPR ProcessAnalyzer standard query syntax and expression language. It identifies the model to query, the root dataset to operate on, the processing method and execution context, an optional pre-filter, and the dimensions and values that shape the output. The detailed format of this configuration follows the standard ProcessAnalyzer query syntax and is not described further here.		'''Inputs.''' The tool takes a single required object parameter, query configuration, which describes the query using the QPR ProcessAnalyzer standard query syntax and expression language. It identifies the model to query, the root dataset to operate on, the processing method and execution context, an optional pre-filter, and the dimensions and values that shape the output. The detailed format of this configuration follows the standard ProcessAnalyzer query syntax and is not described further here.

	'''Outputs.''' The result is returned as a data frame consisting of a Columns array and a Rows array. Each entry in Columns describes one result column with a Name and a DataType (the column's value type). Each entry in Rows is a data row holding one value per column.		'''Outputs.''' The result is returned as a data frame consisting of a Columns array and a Rows array. Each entry in Columns describes one result column with a Name and a DataType (the column's value type). Each entry in Rows is a data row holding one value per column.