The navigation menu can be opened by clicking the dashboard or view name in the header. The menu displays projects and dashboards in its left column. To ensure a focused view, only projects that contain dashboards, or have child projects containing dashboards, are listed. When you click on a project name, the menu displays the dashboards within that project. Clicking the project name again navigates you back to the main project list, allowing you to select a different project. To open a dashboard, simply click on its name. The right column of the navigation menu has the following functionalities available:

== Ready-made dashboards ==
=== Starting Dashboard ===
If the user has a [[User_Profile#Starting_dashboard|starting dashboard]], this item is shown in the navigation menu. With this button, the starting dashboard is opened which is usually a custom main page or navigation page.

=== Process Discovery ===
The Process Discovery is a starting point for an analysis to discover and visualize processes. The [[QPR ProcessAnalyzer Chart|Chart]] on the right side allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. The [[Process Flowchart|Process Flowchart]] or [[Object-Centric_Flowchart|Object-Centric Flowchart]] on the left shows the process drawn as a conventional process flowchart or object-centric flowchart.

=== Conformance Checking ===
[[Conformance Analysis]] incorporates the [[Conformance Checking|Conformance Checking]] capability of QPR ProcessAnalyzer. There are two dashboards that belong to the conformance analysis: the nonconformance reasons and the possible root causes for the nonconformance.

=== Clustering Analysis ===
[[Clustering Analysis]] analyzes through the process mining data, and divides cases into similar groups based on case attributes and occurred types of events. Use it to get a deep understanding of the analyzed process mining data and also to validate the data.

=== Enhanced BPMN ===
The [[QPR_ProcessAnalyzer_BPMN_Editor|Enhanced BPMN]] dashboard is for designing BPMN diagrams and visualizing process mining KPI's in BPMN diagrams. Also filtering based on conformance and process flow in the BPMN diagram can be created.

== System functionality ==
=== Workspace ===
[[QPR_ProcessAnalyzer_Project_Workspace|Project workspace]] is for managing projects, dashboards, datatables and scripts.

=== Manage Users ===
[[Manage_Users_and_Groups|Manage Users dialog]] is for administrators to manage users, groups, roles and permissions in the system. It's also possible to view the effective permissions for audit purposes.

=== System Reports ===
System reports dialog is available for administrators, showing system information, such as recent tasks, running tasks, task statistics, dashboard usage, and listings of different kind of objects in the system. The reports can be modified by changing settings, but the settings cannot be saved.

=== Benchmark Performance ===
Benchmark Performance dialog tests how long it takes to run each preset (i.e. get the preset opened), and based on that creates a report of the performance of the system. The performance benchmark is done for the currently open model and filter, so before opening the Benchmark Performance dialog, change a suitable model and filter (usually benchmarking is done for ''All cases''). The benchmark run is started by clicking the '''Start Run''' button. When the benchmark run starts, a table appears showing presets as rows and benchmarking measures as columns. You can monitor the progress of the run, because results are filled to the table as soon as they are available.

You can choose which presets to run (by default all) and how many times each preset is run (by default three times). For example, you can choose not to run certain presets to make the benchmarking complete quicker, or if for some reason, certain presets give error, they can be excluded. Running each preset more times give more predictable result, but on the other hand, the run takes longer.

When the benchmark run is completed, you can click the '''Export Results''' button to download a report (provided as a text file). The report contains the run results and also basic information about the system and the used model. The results show for each preset the average, median, minimum (fastest), maximum (slowest), standard deviation of the results, and a list of each individual run duration. In addition the footer shows sum of the measures for all run presets. You can stop the benchmarking run while in progress by clicking the '''Stop Run''' button and still export a report of already run presets. Note also that the table can be exported to Excel by right clicking it to open a context menu.

Notes:
* Load to the system by other users may affect the benchmark results, so to get the most accurate results, check from the [[QPR_ProcessAnalyzer_Logs#Task_Log|Task log]] that there are currently no other users in the system.
* Presets are run in a random order to reduce random variation in the results.

=== Query Designer ===
Query Designer is for testing QPR ProcessAnalyzer KPI language queries that contain
* root expression to select objects to be analysed
* dimension expressions to slice the analyzed object into slices
* measure expressions to calculate KPI's and other measures from each of the slices
* data can also be sorted and number of rows limited

The expressions are written in the left side using a JSON format. When the '''Run Query''' button is clicked, the defined query is run and results appear to a table in the right side. Details of the JSON format can be found in [[Web_API:_Expression/query|QPR ProcessAnalyzer Expression Analysis]].

=== Expression Designer ===
Expression Designer is used to run expressions in a generic context. Write the expressions in the upper box and the results appear in the lower box. When clicking the '''Run All''' button, all expressions in the upper box are run. It's also possible to select parts of the expression and click the '''Run Selection''' button to only run the selected parts. If there are errors in the run, cursor is automatically moved to the point where the error occurred.

=== [[User_Profile|User Profile]] ===

=== About ===
The About dialog displays technical information about the QPR ProcessAnalyzer environment:
* Software build
* Build timestamp
* Database version
* Features enabled
* System default language
* System default date format
* System default first day of week
* System default clock format
* QPR ProcessAnalyzer memory usage
* Available / total physical memory

=== Sign out ===
The user session can be signed out, which also clears all cached information in the browser side. When using a personal computer, signing out is normally not needed from the security point of view, but if there are other users in the same computer, it's important to sign out after using the system.

When using QPR ProcessAnalyzer as Snowflake Native App, also the Snowflake session is logged out when pressing the ''Sign out''.

__NOTOC__

[[Category: QPR ProcessAnalyzer]]

The navigation menu can be opened by clicking the dashboard or view name in the header. The menu displays projects and dashboards in its left column. To ensure a focused view, only projects that contain dashboards, or have child projects containing dashboards, are listed. When you click on a project name, the menu displays the dashboards within that project. Clicking the project name again navigates you back to the main project list, allowing you to select a different project. To open a dashboard, simply click on its name. The right column of the navigation menu has the following functionalities available:

== Ready-made dashboards ==
=== Starting Dashboard ===
If the user has a [[User_Settings#Starting_dashboard|starting dashboard]], this item is shown in the navigation menu. With this button, the starting dashboard is opened which is usually a custom main page or navigation page.

=== Process Discovery ===
The Process Discovery is a starting point for an analysis to discover and visualize processes. The [[QPR ProcessAnalyzer Chart|Chart]] on the right side allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. The [[Process Flowchart|Process Flowchart]] or [[Object-Centric_Flowchart|Object-Centric Flowchart]] on the left shows the process drawn as a conventional process flowchart or object-centric flowchart.

=== Conformance Checking ===
[[Conformance Analysis]] incorporates the [[Conformance Checking|Conformance Checking]] capability of QPR ProcessAnalyzer. There are two dashboards that belong to the conformance analysis: the nonconformance reasons and the possible root causes for the nonconformance.

=== Clustering Analysis ===
[[Clustering Analysis]] analyzes through the process mining data, and divides cases into similar groups based on case attributes and occurred types of events. Use it to get a deep understanding of the analyzed process mining data and also to validate the data.

=== Enhanced BPMN ===
The [[QPR_ProcessAnalyzer_BPMN_Editor|Enhanced BPMN]] dashboard is for designing BPMN diagrams and visualizing process mining KPI's in BPMN diagrams. Also filtering based on conformance and process flow in the BPMN diagram can be created.

== System functionality ==
=== Workspace ===
[[QPR_ProcessAnalyzer_Project_Workspace|Project workspace]] is for managing projects, dashboards, datatables and scripts.

=== Manage Users ===
[[Manage_Users_and_Groups|Manage Users dialog]] is for administrators to manage users, groups, roles and permissions in the system. It's also possible to view the effective permissions for audit purposes.

=== System Reports ===
System reports dialog is available for administrators, showing system information, such as recent tasks, running tasks, task statistics, dashboard usage, and listings of different kind of objects in the system. The reports can be modified by changing settings, but the settings cannot be saved.

=== Benchmark Performance ===
Benchmark Performance dialog tests how long it takes to run each preset (i.e. get the preset opened), and based on that creates a report of the performance of the system. The performance benchmark is done for the currently open model and filter, so before opening the Benchmark Performance dialog, change a suitable model and filter (usually benchmarking is done for ''All cases''). The benchmark run is started by clicking the '''Start Run''' button. When the benchmark run starts, a table appears showing presets as rows and benchmarking measures as columns. You can monitor the progress of the run, because results are filled to the table as soon as they are available.

You can choose which presets to run (by default all) and how many times each preset is run (by default three times). For example, you can choose not to run certain presets to make the benchmarking complete quicker, or if for some reason, certain presets give error, they can be excluded. Running each preset more times give more predictable result, but on the other hand, the run takes longer.

When the benchmark run is completed, you can click the '''Export Results''' button to download a report (provided as a text file). The report contains the run results and also basic information about the system and the used model. The results show for each preset the average, median, minimum (fastest), maximum (slowest), standard deviation of the results, and a list of each individual run duration. In addition the footer shows sum of the measures for all run presets. You can stop the benchmarking run while in progress by clicking the '''Stop Run''' button and still export a report of already run presets. Note also that the table can be exported to Excel by right clicking it to open a context menu.

Notes:
* Load to the system by other users may affect the benchmark results, so to get the most accurate results, check from the [[QPR_ProcessAnalyzer_Logs#Task_Log|Task log]] that there are currently no other users in the system.
* Presets are run in a random order to reduce random variation in the results.

=== Query Designer ===
Query Designer is for testing QPR ProcessAnalyzer KPI language queries that contain
* root expression to select objects to be analysed
* dimension expressions to slice the analyzed object into slices
* measure expressions to calculate KPI's and other measures from each of the slices
* data can also be sorted and number of rows limited

The expressions are written in the left side using a JSON format. When the '''Run Query''' button is clicked, the defined query is run and results appear to a table in the right side. Details of the JSON format can be found in [[Web_API:_Expression/query|QPR ProcessAnalyzer Expression Analysis]].

=== Expression Designer ===
Expression Designer is used to run expressions in a generic context. Write the expressions in the upper box and the results appear in the lower box. When clicking the '''Run All''' button, all expressions in the upper box are run. It's also possible to select parts of the expression and click the '''Run Selection''' button to only run the selected parts. If there are errors in the run, cursor is automatically moved to the point where the error occurred.

=== [[User_Profile|User Profile]] ===

=== About ===
The About dialog displays technical information about the QPR ProcessAnalyzer environment:
* Software build
* Build timestamp
* Database version
* Features enabled
* System default language
* System default date format
* System default first day of week
* System default clock format
* QPR ProcessAnalyzer memory usage
* Available / total physical memory

=== Sign out ===
The user session can be signed out, which also clears all cached information in the browser side. When using a personal computer, signing out is normally not needed from the security point of view, but if there are other users in the same computer, it's important to sign out after using the system.

When using QPR ProcessAnalyzer as Snowflake Native App, also the Snowflake session is logged out when pressing the ''Sign out''.

__NOTOC__

[[Category: QPR ProcessAnalyzer]]

QPR ProcessAnalyzer Wiki

2026-06-17T13:25:18Z

TeeHiet: TK-63420

<div class="downloadButton" style="width:190px;float:right;margin: 3px 12px 0px 15px;">[[Online_Learning_Platform|Online Learning<br />Platform]]</div>

Welcome to QPR ProcessAnalyzer Wiki! QPR ProcessAnalyzer is a software for turning event and transactional data into visual process analysis and intelligence. Topics in this documentation are divided based on user roles for process analysts, developers and administrators.

<div style="height:5px;"></div>
== For Process Analysts ==
This section contains information how to get started with QPR ProcessAnalyzer and how to create your first dashboards! This section also describes how to use filters and how to make different kinds of analyses with QPR ProcessAnalyzer.

<div style="display: flex;flex-wrap: wrap;">
<div style="flex: 1 0 210px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">
=== Getting Started ===
* [[Getting Started with QPR ProcessAnalyzer]]
* [[Log_in_QPR_ProcessAnalyzer|Log in QPR ProcessAnalyzer]]
* [[QPR_ProcessAnalyzer_Native_App_in_Snowflake|Snowflake Native App]]
* [[Introduction to Process Mining|Introduction to Process Mining]]
* [[Process_Mining_Concepts|Process Mining Concepts]]
* [[Navigation_Menu|Navigation Menu]]
* [[User Profile|User Profile]] and [[Languages and Localization|Language Settings]]
* [[QPR Task Recorder for Web Apps|QPR Task Recorder for Web Apps]]
</div>

<div style="flex: 1 0 210px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Working with Dashboards ===
* [[QPR_ProcessAnalyzer_Project_Workspace|Project Workspace]]: [[QPR_ProcessAnalyzer_Project_Workspace#Projects|Projects]], [[QPR_ProcessAnalyzer_Project_Workspace#Dashboards|Dashboards]], [[QPR_ProcessAnalyzer_Project_Workspace#Models|Models]], [[QPR_ProcessAnalyzer_Project_Workspace#Datatables|Datatables]], [[Managing_Scripts|Scripts]], [[QPR_ProcessAnalyzer_Project_Workspace#Recycle_Bin|Recycle Bin]]
* [[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]
* [[QPR ProcessAnalyzer Dashboard Designer|Creating Dashboards]]
* [[AI Assistant for QPR ProcessAnalyzer|AI Assistant]] (powered by OpenAI GPT)
* [[Dashboard Variables|Dynamic Variables in Dashboards]]
* [[Business Calendar|Business Calendar to Calculate Durations]]
* [[Best Practices for Designing Dashboards|Best Practices for Designing Dashboards]]
</div>

<div style="flex: 1 0 370px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Analyses and Visualizations ===
<div style="float:left; width:50%;">
* [[Process Flowchart|Case-Centric Flowchart]]
* [[Object-Centric_Flowchart|Object-Centric Flowchart]]
* [[QPR ProcessAnalyzer Chart|Chart]] / [[Snowflake Chart|Snowflake Chart]]
** [[QPR ProcessAnalyzer Graph Charts|Graph charts]]
** [[QPR_ProcessAnalyzer_Table|Table]]
** [[QPR_ProcessAnalyzer_Pivot_Table|Pivot Table]]
** [[QPR_ProcessAnalyzer_KPI_Card|KPI Card]]
** [[Gantt_Chart|Gantt Chart]]
** [[Sankey_Chart|Sankey Chart]]
** [[Measure,_Dimension_and_Column_Settings|Measure Settings]]
** [[Chart_On-screen_Settings|On-screen Settings]]
** [[Chart_Linked_Settings|Linked Settings]]
** [[Actions_to_Run_Script_in_Table|Run Script Actions]]
</div>
<div style="float:left; width:50%;">
* [[AI_Agent|AI Agent]]
* [[AI Root Causes|AI Root Causes Analysis]] / [[Root Causes|Classic Root Causes Analysis]]
* [[Clustering Analysis|Clustering Analysis]]
* [[Conformance Analysis|Conformance Analysis]]
* [[Design Diagram|Design Diagram]] / [[QPR ProcessAnalyzer BPMN Editor|BPMN Editor]]
* [[Label and Link]]
* [[Image|Image]]
* [[Range_Filter|Range Filter Selector]] (for dates and numbers)
* [[Filter_Selectors|Dimension Filter Selectors]]
* [[Dropdown_List_Selector|Dropdown List Selector]]
* [[External_Content|Embedded webpage]]
</div>
</div>

</div>

== For Citizen Developers ==
This section describes how to build ETL scripts that transform the source data into process mining models. There is also a detailed description how the process mining models can be configured so that they are optimal for the desired analyses. Finally, there is reference documentation for all expression language related functionality, that can be used both when writing custom KPI's in dashboards and in the ETL scripts.

<div style="display: flex;flex-wrap: wrap;">
<div style="flex: 1 0 370px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">
=== Expression Language Reference ===
* [[SQL_Expressions|SQL Expressions for Snowflake]]
* In-memory expressions: [[QPR_ProcessAnalyzer_Expressions|Basic Syntax and Operations]] / [[Generic Functions in QPR ProcessAnalyzer|Generic Functions]]
* [[Generic_Objects_in_Expression_Language|Generic types]] ([[Generic_Properties_in_Expression_Language|Generic Properties]], [[Generic_Objects_in_Expression_Language#Array|Array]], [[Generic_Objects_in_Expression_Language#DateTime|DateTime]], [[Generic_Objects_in_Expression_Language#String|String]], [[Generic_Objects_in_Expression_Language#Timespan|Timespan]], [[Generic_Objects_in_Expression_Language#Dictionary|Dictionary]])
* [[Process_Mining_Objects_in_Expression_Language|In-memory models API]] ([[Process_Mining_Objects_in_Expression_Language#AttributeType|AttributeType]], [[Process_Mining_Objects_in_Expression_Language#Case|Case]], [[Process_Mining_Objects_in_Expression_Language#Event|Event]], [[Process_Mining_Objects_in_Expression_Language#EventLog|EventLog]], [[Process_Mining_Objects_in_Expression_Language#EventType|EventType]], [[Process_Mining_Objects_in_Expression_Language#Flow|Flow]], [[Process_Mining_Objects_in_Expression_Language#FlowOccurrence|FlowOccurrence]], [[Process_Mining_Objects_in_Expression_Language#Variation|Variation]])
* Configuration objects ([[Dashboard_in_Expression_Language|Dashboard]], [[Datatable_in_Expression_Language|Datatable]], [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Model|Model]], [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Filter|Filter]], [[Diagram_in_Expression_Language|Diagram]], [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Script|Script]], [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#Project|Project]], [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#User.2FGroup|User/Group]])
* Tabular data ([[DataFrame in Expression Language|DataFrame]], [[SqlDataFrame in Expression Language|SqlDataFrame]], [[DataFlow_in_Expression_Language|DataFlow]])
* [[Machine_Learning_Functions_in_Expression_Language|Machine Learning API]] / [[Conformance_Checking|Conformance Checking]] / [[QPR_MEA_Integration|QPR MEA Integration]]
* [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filter Rules JSON]]
* [[System Library]]
</div>

<div style="flex: 1 0 250px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Create Process Mining Models ===
* [[Creating Process Mining Model|Walkthrough: Creating Process Mining Model]]
* [[Exporting_and_Importing_Data_in_QPR_ProcessAnalyzer|Importing Data from CSV, XES and PACM files]]
* [[Object-centric_Process_Mining_Model|Object-centric Process Mining (OCPM)]]
* [[Create_Object-centric_Model_from_Relational_Schema|Create OCPM Model from Relational Schema]]
* [[Event Ordering for Identical Timestamps|Event Ordering for Identical Timestamps]]
* [[Managing Time Zones and Local Time|Time Zones and Local Time]]
* [[Best_Practices_for_Designing_Models|Best Practices for Designing Models]]
* [[Decide_Case_ID_Data_Type|Decide Case ID Data Type]]
* [[Create_Predicted_Eventlog|Create Predicted Eventlog]]
* [[Create Simulated Eventlog]]
==== For In-memory Models ====
* [[Calculated Attributes in QPR ProcessAnalyzer|Calculated Case and Event Attributes]]
* [[Email Notifications|Email Notifications]]
* [[QPR ProcessAnalyzer Model Datasources|Model datasources]] ([[QPR ProcessAnalyzer Model Datasources#Loading Data from Datatables|Datatable]], [[QPR ProcessAnalyzer Model Datasources#Loading Script|Loading Script]], [[QPR ProcessAnalyzer Model Datasources#ODBC_Datasource|ODBC]])
* [[Case Level Permissions|Case Level Permissions]]
* [[Automatic Model Loading on Server Startup|Keeping Models Always Available]]
</div>

<div style="flex: 1 0 250px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Data Integrations and Connectors ===
* [[Managing Scripts|Managing Scripts in Workspace]]
* [[Datatable_Properties_Dialog|Managing Datatables in Workspace]]
* [[SQL Scripting for ETL|Writing SQL Scripts]]
* [[SQL Scripting Commands|SQL Scripting Commands Reference]]
* [[Storing Secrets for Scripts|Storing Secrets]]
* [[QPR ProcessAnalyzer ScriptLauncher|Installing and using QPR ScriptLauncher]]
* [[Importing_Data_from_SAP|How to Import Data from SAP]]
* [[Anonymize data|Anonymize data]]
* [[Expression Script Examples|Expression Script Examples]]
* [[QPR ProcessAnalyzer API|QPR ProcessAnalyzer REST API]]
* [[Sample Eventlog Files|Sample Eventlogs]]
* [[Connecting_to_QPR_ProcessAnalyzer_MCP_Server|Connecting to MCP Server]]
* [[MCP_Tool_Examples|MCP Tool Examples]]
</div>
</div>

== For System Administrators ==
This section starts with the planning of QPR ProcessAnalyzer installation. After all requirements have been fulfilled, you can continue with the installation and configuration of QPR ProcessAnalyzer. Finally, learn how to manage users and perform other administrative tasks.

<div style="display: flex;flex-wrap: wrap;">
<div style="flex: 1 0 290px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">
=== Planning Installation ===
* [[QPR ProcessAnalyzer System Requirements|System Requirements]]
* [[QPR ProcessAnalyzer System Architecture|System Architecture]]
* [[User Session Management|User Session Management]]
* [[QPR_ProcessAnalyzer_Downloads|Downloads Page]]
* [[QPR ProcessAnalyzer Release Notes|QPR ProcessAnalyzer Release Notes]]
</div>

<div style="flex: 1 0 290px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Installing and Configuring ===
* [[Deploy_QPR_ProcessAnalyzer_from_Container|Container Deployment]]
* [[Installing QPR ProcessAnalyzer Server on Windows|Install on Windows]] (or [[Updating_QPR_ProcessAnalyzer_Server|Update]])
* [[Snowflake_Connection_Configuration|Connect to Snowflake]]
* [[SAML_2.0_Federated_Authentication|SAML 2.0 Authentication]]
* [[QPR_ProcessAnalyzer_as_MCP_Server|Configure MCP Server]] / [[Create_MCP_Tools|Create MCP Tools]]
* [[QPR ProcessAnalyzer Security Hardening|Security Hardening]]
* [[Setting_up_Scripting_Sandbox|Setting up SQL Scripting Sandbox]]
* [[Activate_QPR_ProcessAnalyzer_using_ActivationUtility|Activation without Internet Connection]]
</div>

<div style="flex: 1 0 290px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;">

=== Administrating System ===
* [[Roles and Permissions|User Roles and Permissions]]
* [[Manage Users and Groups|Managing Users]]
* [[PA_Configuration_database_table|Configurations in database]]
* [[Server_settings_in_appsettings.json|Configurations in appsettings.json file]]
* [[Server_settings_in_log4net.config|Configurations in log4net.config file]]
* [[QPR ProcessAnalyzer Logs|Logs for Audit and Troubleshooting]]
* [[Embed_to_Website|Embed to Website]]
* [[In-memory_Models_Management|In-memory Models Management]]
</div>
</div>

== Agreements ==
See the [[QPR General Terms and Conditions]] and [[QPR SaaS Terms and Conditions]].

__NOTOC__

User Settings

2026-06-17T13:21:31Z

TeeHiet: TeeHiet moved page User Settings to User Profile: TK-63420

#REDIRECT [[User Profile]]

User Profile

2026-06-17T13:21:31Z

TeeHiet: TeeHiet moved page User Settings to User Profile: TK-63420

== User information ==
User Settings dialog shows following information for the currently logged in user:
* '''User name''': Login name used when user logs in.
* '''Full name''': Person full name (for example first name and last name).
* '''Email''': User's email address.
* '''Groups''': Groups the user belongs to. The user gets permissions from the groups.
* '''Global roles''': List of global roles the user has. There is one or several permissions in each role and user gets permissions from the roles.
* '''Global permissions''': List of global permissions the user has. The permissions determine what actions the user has in the system.

The '''Authenticated using''' field describes which authentication method was used to log in to QPR ProcessAnalyzer. There are following options:
* QPR ProcessAnalyzer password
* External identity provider through SAML 2.0
* Snowflake (available in Snowflake Native App)

== Localization settings ==
User can set the user's own language, content language, date format, first day of week and whether the 12-hour clock is used. See [[Languages_and_Localization#Date_Format_Settings|more information]].

== Change password ==
User can change user own password. When changing the password, you need to provide your current password and also confirm the new password. Note that when authenticated using the SSO (SAML 2.0 identity provided) or Snowflake, the password changing in QPR ProcessAnalyzer is not available.

When running QPR ProcessAnalyzer as Snowflake Native App, there is also '''Login as other user''' button to log out QPR ProcessAnalyzer session and go the login screen, so that a different QPR ProcessAnalyzer user can be used. The Snowflake session is not logged out when pressing this button.

== Starting dashboard ==
Starting dashboard (a.k.a. default dashboard) can be defined that is opened when a user logs in. The starting dashboard can be a navigation page containing links to other dashboards in the process mining application.

The starting dashboard is defined for a group, allowing to define different starting dashboards for users of different groups. All users belonging to a group with a starting dashboard will define that as the starting dashboard for all the users in that group. If a user belongs to multiple groups with each having a starting dashboard, the user's starting dashboard will be taken from a group having alphabetically the first name. Thus, it's possible to define a starting dashboard for a narrower group that overrides a larger group, if the narrower group is alphabetically before the larger group.

See how to [[Manage_Users_and_Groups#Editing_Group_Information|configure starting dashboards]].

== Technical information ==

'''QPR ProcessAnalyzer version''' can be seen. When pressing the '''(details)''' link, a dialog with following system related technical information is shown:
* Database major version
* Database minor version
* PACM file version
* System default language
* System default date format
* System default first day of week
* System default use of 12-hour clock
* Server build
* Client build
* Client revision
* Build timestamp
* Database initialized for version
* QPR ProcessAnalyzer memory usage
* Available / total physical memory

Create MCP Prompts

2026-06-11T08:57:55Z

TeeHiet:

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

To enable a script as an MCP Prompt:
# Log in to QPR ProcessAnalyzer as a System Administrator.
# Open or create the script.
# For the script to be used as an MCP prompt, give it a name. This name is then used as the MCP prompt name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover prompts with invalid names. The maximum length of the name is 50 characters.
# Open the properties of the script.
# Switch to the '''MCP''' tab and select the '''MCP prompt''' option.
# Switch to the '''Description''' tab and provide a description. The description is added to the context of the client.

== MCP Prompt Settings ==
The prompt description is a concise metadata field that gives an AI agent instructions on how to achieve complex tasks. When a prompt is called, the associated script is executed and the result is returned as a prompt message.

Every script can define its own prompt configuration as JSON. Supported values are same as [https://modelcontextprotocol.io/specification/2025-11-25/server/prompts#prompt here], except for the name which is always generated automatically and can't be overridden. Defining the prompt configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the prompt.

In addition to the name of the prompt, MCP prompts provide the following information to the MCP client:
* '''title''': Title of the prompt. Uses the script's title by default.
* '''description''': Description of the prompt. Uses the script's description by default.
* '''arguments''': Following arguments are available to indicate about the MCP prompt:
** '''name'' (required, string): The argument name.
** '''description''' (optional, string): A human-readable description of the argument.
** '''required''' (optional, boolean): Whether the argument must be provided.
* '''icons''': Same as icons for [[Create_MCP_Tools#MCP_Icons|MCP tools]].
* '''meta''': Metadata about the prompt.

'''Example''': a full MCP prompt configuration:<syntaxhighlight lang="json">
{
"title": "Text Summarizer",
"description": "Generates a concise summary of the provided text",
"arguments": [
{
"name": "text",
"description": "The text content to summarize",
"required": true
},
{
"name": "maxLength",
"description": "Maximum length of the summary in characters",
"required": false
}
],
"icons": [
{
"src": "https://example.com/icons/summarize.svg",
"mimeType": "image/svg+xml",
"sizes": ["any"],
"theme": "light"
}
],
"meta": {
"category": "text-processing"
}
}
</syntaxhighlight>

'''Example''': a prompt script that takes modelId as parameter:<pre>
`
Based on the model ${modelId}, create a report having the following structure:

=== Metadata ===
- Name
- Description
- Configuration and used data tables

=== Model data ===
- Model statistics such as number of cases, events, event types, flows, variations etc.

=== Model structure ===
- Analysis based on event types, flows, variations and BPMN model.
`
</pre>

Create MCP Resources

2026-06-11T08:55:27Z

TeeHiet:

== Creating MCP Resources ==
MCP resources are implemented using [[Managing_Scripts|scripts]] written in QPR ProcessAnalyzer expression language. A script will be added as the MCP resource when the '''MCP resource''' option is selected in the [[Managing_Scripts#Script_Properties|Script Properties]]. Only system administrator users can enable the MCP resource option. Also, only system administrators can modify scripts that are MCP resources, because any changes to the MCP interface is restricted to system administrators for security reasons. An MCP Resource script that returns binary data has to return the resource as Base64 encoded string.

To enable a script as an MCP Resource:
# Log in to QPR ProcessAnalyzer as a System Administrator.
# Open or create the script.
# For the script to be used as an MCP resource, give it a name. This name is then used as the MCP resource name. It is important to ensure that every script intended for MCP use has a non-empty, valid name, as clients may fail to discover resources with invalid names. The maximum length of the name is 50 characters.
# Open the properties of the script.
# Switch to the '''MCP''' tab and select the '''MCP resource''' option.
# Switch to the '''Description''' tab and provide a description. The description is added to the context of the client.

== MCP Resource Settings ==
The MCP resource is a read-only data entity that provides AI models with external context, files, or background knowledge. When a resource is read, the associated script is executed and the result is returned as text resource contents.

Every script can define its own resource configuration as JSON. Supported values are same as [https://modelcontextprotocol.io/specification/2025-11-25/server/resources#resource here], except for the name which is always generated automatically and can't be overridden. Defining the resource configuration will override any default configurations generated for scripts automatically by QPR ProcessAnalyzer. For example, specifying the value for "title" here will override the default functionality of using script's name as title of the resource.

In addition to the name of the resource, MCP resources provide the following information to the MCP client:
* '''title''': Title of the resource. Uses the script's title by default.
* '''description''': Description of the resource. Uses the script's description by default.
* '''uri''': "script:///{scriptId}" where scriptId is the script's database identifier. This value can't be modified.
* '''mimeType''': Mime type of the resource. Defaults to "text/plain".
* '''annotations''': Metadata for filtering and prioritization of the resource content.
** '''audience''' (optional, array of roles): The intended audience for this content. Supported values are: "user" and "assistant".
** '''priority''' (optional, number): How important this data is, as a decimal number between "0" (lowest) and "1" (highest).
** '''lastModified''' (optional, string): When the resource was last modified, as an ISO 8601 date-time string (e.g. "2025-01-12T15:00:58Z").
* '''size''' (integer): Size in bytes.
* '''icons''': Same as icons for [[Create_MCP_Tools#MCP_Icons|MCP tools]].
* '''meta''': Metadata about the resource.

'''Example''': a full MCP resource configuration:<syntaxhighlight lang="json">
{
"title": "Process Mining Data Export",
"description": "Exports process mining analysis results as JSON",
"mimeType": "application/json",
"size": 102400,
"annotations": {
"audience": ["user", "assistant"],
"priority": 0.8,
"lastModified": "2025-06-25T10:30:00Z"
},
"icons": [
{
"src": "https://example.com/icons/export.png",
"mimeType": "image/png",
"sizes": ["48x48"]
}
],
"meta": {
"refreshInterval": "300",
"dataSource": "process-mining"
}
}
</syntaxhighlight>

'''Example''': a resource script that returns binary data:<pre>
CallWebService(#{
"Address": "https://www.qpr.com/hs-fs/hubfs/main/global-content/qpr-software-color-header%2Blogo.png?width=150&…
})["Response"]
</pre>

Create MCP Resources

2026-06-11T08:51:04Z

TeeHiet: /* Creating MCP Resources */

Server settings in appsettings.json

2026-05-28T13:39:43Z

TeeHiet: TK-64813

The appsettings.json file is the main settings file for the QPR ProcessAnalyzer Server application.

{| class="wikitable" style="text-align: left"
!Setting
!Description
|-
|SqlDatabaseConnectionString
|Connection string to configuration database in SQL Server. Check whether you are using the SQL Server default instance or a named instance, and whether the SQL Server authentication or Windows authentication is used.

Connect to SQL Server default instance using SQL Server authentication:
<pre>
Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;
</pre>

Connect to SQL Server default instance using Windows authentication:
<pre>
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;
</pre>

Connect to SQL Server named instance using SQL Server authentication:
<pre>
Server=myServerName\\myInstanceName;Database=myDataBase;User Id=myUsername;Password=myPassword;
</pre>

Connect to SQL Server named instance using Windows authentication:
<pre>
Server=myServerName\\myInstanceName;Database=myDataBase;Trusted_Connection=True;
</pre>

More information about connections strings: https://www.connectionstrings.com/sqlconnection.
|-
|LogFilePath
|Location of the QPR ProcessAnalyzer Server log file, defined as the full path including the file name. For example: ''C:\\ProgramData\\QPR Software\\QPR ProcessAnalyzer\\Logs\\PA.log'' (json escapings are included).
|-
|CorsOrigins
|Defines how QPR ProcessAnalyzer Server responds to the CORS preflight requests. By default, this setting is empty, meaning that CORS is not allowed. To allow CORS from all origins, specify '''*''' (note that this is the least secure option). If CORS need to be enabled for a specific site(s), they are defined as a comma separated list to this setting. More about CORS: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS.
|-
|UseXForwardedForAsClientIp
|If QPR ProcessAnalyzer Server is running behind a web traffic load balancer (e.g. in Amazon Web Services), the following setting needs to be set to ''True''. In that case, the client ip address is fetched from http request ''X-Forwarded-For'' (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) field instead of the source of the ip packet. Client ip address is needed for logging and as a security confirmation in addition to the session id. When there is no load balancer and thus X-Forwarded-For is not set, it's important to have this setting as ''False''.
|}

Following settings are used by in-memory models (so these settings are not effective for Snowflake models):
{| class="wikitable" style="text-align: left"
!Setting
!Description
|-
|ModelLoadOnStartup
|Whether in-memory models having setting ''LoadOnStartup'' as '''true''' are loaded automatically during the server startup. By default, this setting should be set to '''True'''. This setting can be used to temporarily disable automatic model loading for all models when for example automatic model loading causes issues.
|-
|DropUnusedFiltersAfter
|
Specifies duration after which filters are dropped from the memory if they have not been used during that time. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). When a calculation uses a filter, the filter's last used time is updated (also model's last used time is updated). This setting can be overridden for each model in the [[In-memory_Models_Management|model settings]].
|-
|DropUnusedAnalysisResultsAfter
|
Specifies duration after which query results (analysis results) are dropped from the memory if they have not been used during that time. Defined in format ''HH:mm:ss'' or ''d.HH:mm:ss'', for example 01:00:00 (one hour), 00:30:00 (30 minutes) or 1.00:00:00 (24 hours). Default value is 00:30:00 (30 minutes).
|}

Following settings are for the product activation:
{| class="wikitable" style="text-align: left"
!Setting
!Description
|-
|ProductActivationCode
|QPR ProcessAnalyzer Server product license activation code. Ask your organization license activation code from [mailto:customercare@qpr.com customercare@qpr.com].

QPR ProcessAnalyzer Server automatically activates itself if the code is specified and there is an internet connection in the server computer. If there is no internet access, the activation need to be done manually by using the [[Activate_QPR_ProcessAnalyzer_using_ActivationUtility|Activation Utility]].
|-
|FirstName
|Customer contact person first name.
|-
|LastName
|Customer contact person last name.
|-
|Email
|Customer contact person email address.
|-
|LicenseFilePath
|QPR ProcessAnalyzer Server license file path including the file name. For example ''C:\\ProgramData\\QPR Software\\QPR ProcessAnalyzer\\pa_service.lf'' (json escapings are included). The license file is created when the QPR ProcessAnalyzer Server is activated. If changing the activation code, this file needs to be deleted manually to enable reactivation.
|-
|EMSAddress
|Activation server address ''<nowiki>https://activation.qpr.com</nowiki>'' that is contacted when the QPR ProcessAnalyzer Server is activated. Do not change this setting.
|-
|UseProxyServer
|If needed, define the proxy server for QPR ProcessAnalyzer Server activation.
|-
|ProxyAddress
|If needed, define the proxy server for QPR ProcessAnalyzer Server activation.
|-
|Country
|Customer country.
|-
|JobTitle
|Customer contact person job title.
|-
|PhoneNumber
|Customer contact person phone number.
|-
|Address
|Customer address.
|-
|PostalCode
|Customer postal code.
|-
|Region
|Customer region.
|-
|Organization
|Customer organization.
|}

Following settings are used by HTTP request and response logging:
{| class="wikitable" style="text-align: left"
!Setting
!Description
|-
|HttpLogging
|When this section is defined as a top-level property in appsettings.json, the HTTP request and response logging is enabled. The following properties can be configured (see [https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.httplogging.httploggingoptions?view=aspnetcore-10.0 component documentation] for more information):
* LoggingFields: Specifies which parts of the HTTP request and response are logged (e.g., "RequestPropertiesAndHeaders", "ResponseStatusCode", "All"). Default value is "All".
* RequestBodyLogLimit: The maximum number of bytes of the request body to log. Default value is "4096".
* ResponseBodyLogLimit: The maximum number of bytes of the response body to log. Default value is "4096".
* CombineLogs: Boolean value that defines whether to combine request and response logs into a single log entry. Default value is "true".
* MediaTypeOptions:|An array of media type strings to log when body logging is enabled.
An example configuration:<syntaxhighlight lang="json">
"HttpLogging": {
"LoggingFields": "RequestPropertiesAndHeaders, ResponseStatusCode",
"RequestBodyLogLimit": 4096,
"ResponseBodyLogLimit": 4096,
"CombineLogs": true
}
</syntaxhighlight>
|}
<div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;">
The appsettings.json needs to be a correctly formatted json file, and thus the backslashes and quotation marks in string values need to be escaped as follows: \ → \\ and " → \".
</div>

2026-05-13T11:57:31Z

TeeHiet: /* 5. Customer’s Use of the SaaS Services */

These QPR SaaS Terms and Conditions, together with the QPR General Terms and Conditions, shall apply to the delivery of the Software described in detail in the Purchase Order between QPR and the Customer, which are delivered to the Customer via information networks (“SaaS Services”) and the Support Services for such SaaS Services.

Any definition used in these QPR SaaS Terms and Conditions, but not defined herein, has the meaning set forth in the QPR General Terms and Conditions.

== 1. SaaS Services ==

1.1 QPR shall deliver the SaaS Services identified in the Purchase Order to the Customer substantially as set out in the Agreement. The SaaS Services shall contain the required hardware and software platform, including the server hardware, network connectivity from the server hardware to the internet, and backups of the data in the environment.

1.2 QPR constantly develops its service offering and reserves the right to make changes to the SaaS Services, at any time, provided that such change does not have a material adverse effect on the agreed functionality of the SaaS Services or the agreed service levels. QPR will inform the Customer of changes and where reasonably possible with fourteen (14) days prior notice before the change takes effect.

== 2. Use Rights ==

2.1 During the License Term and subject to the terms and conditions of the Agreement, QPR hereby grants to the Customer a non-exclusive and non-transferable license to use the SaaS Services solely for the Customer’s internal business operations.

2.2 The use of the SaaS Services is limited to the User Licenses or any other license metrics set out in the Purchase Order.

2.3 The Customer may not license, sublicense, rent, resell, lease, market, commercialize or otherwise assign, transfer, disclose or make available the SaaS Services in any form or manner to any person other than the Customer’s employees and third-party service providers without the written consent of QPR. The Customer’s third-party service providers shall not be permitted to use the SaaS Services for the benefit of any entities other than the Customer. The Customer shall itself monitor its use of the SaaS Services and report any use in excess of the agreed User Licenses to QPR. QPR may also monitor the use of the SaaS Services by the Customer to verify the Customer’s compliance with the Agreement and agreed User Licenses.

== 3. Support Services ==

3.1 QPR shall provide the Customer with Support Services during the License Term substantially as set out in the Agreement. The Support Services are described in detail in [the Purchase Order and the Service Description / the prevailing QPR Customer Care Program published by QPR [insert link]. QPR reserves the right to make changes to the [Support Services / QPR Customer Care Program] at any time.

3.2 QPR agrees to provide all Support Services with due care, skill, and diligence. QPR may at its own discretion subcontract any or all of the Support Services to its authorized resellers, subcontractors, or representatives.

3.3 The Support Services concern the use of the SaaS Services only. The following matters will not be covered by the Support Services:

<ol style="list-style-type:lower-alpha">
<li>Assistance relating to Third Party Software, integrations or any software, products or services other than the SaaS Services.</li>
<li>Assistance with a problem resulting from the misuse, improper use, unauthorized alteration or modification, or damage caused by misuse, of the SaaS Services.</li>
<li>Assistance with a problem resulting from the combination of the SaaS Services with other software, applications, systems or equipment to the extent such combination has not been approved by QPR.</li>
<li>Assistance with installing, configuring, using, and integrating any third-party product that the Customer has purchased separately, including but not limited to database systems, operating systems, web servers, browsers, network equipment, and firewall systems.</li>
<li>Assistance relating to integrations or interfaces with other software components or product versions that are not explicitly designated by QPR as compatible with the SaaS Services in use.</li>
<li>Assistance concerning product versions of the SaaS Services other than the most recent official release.</li>
</ol>

3.4 The Customer will be responsible for paying QPR’s standard fees as applicable from time to time for time and other resources provided by QPR to diagnose or attempt to correct any matter not covered by the Support Services as defined above.

3.5 Due to obsoleting of technologies of vendors, QPR will not provide Support Services for the SaaS Services in a runtime environment where components or products are no longer fully supported by vendors, even if the SaaS Services would have been supported in such runtime environment at the time of signing the Purchase Order.

== 4. Service Levels ==

4.1 QPR will use commercially reasonable efforts to ensure that the SaaS Services are available to use during any given time, except during maintenance windows, updates, and repair. Operation of the SaaS Services may require short breaks in the service outside maintenance windows.

4.2 QPR will perform maintenance in hosting servers and environments in pre-scheduled maintenance windows. The standard maintenance windows will be communicated separately. In case of emergency maintenance requirements, QPR will use its commercially reasonable efforts to inform Customers of such maintenance needs at least 24 hours in advance.

4.3 QPR cannot guarantee network availability between the Customer and the hosted environment, as network availability can involve numerous third parties and is beyond the control of QPR. QPR will not be liable for any downtime that the Customer experiences as a result of the Customer’s own network connectivity issues.

4.4 QPR is obligated to start resolving any service outage or other problem with the SaaS Services within one (1) hour after receiving notification from the Customer during opening hours of QPR Customer Care. QPR will make efforts to determine whether the outage or other problem is within QPR's reasonable control. If QPR determines that the issue is attributable to QPR, the Customer will be credited an amount equal to the Fees paid for the SaaS Services for one (1) day for every 4 hours of downtime that the Customer experiences after QPR has received notification from the Customer. QPR will have no other liability to the Customer for failure to provide availability of the SaaS Services.

== 5. Customer’s Use of the SaaS Services ==

5.1 The Customer’s use of the SaaS Services must comply with all applicable laws, regulations, and ordinances, including any laws regarding the export of data or software. The Customer agrees to comply with reasonable instructions and specifications of QPR, including any guidance in or design of the SaaS Services. The Customer shall be solely responsible for ensuring that any use of the SaaS Services by the Customer’s employees is in accordance with the Agreement and the instructions and specifications of QPR.

5.2 The Customer may use the SaaS Services solely for its internal business purposes. The Customer is not entitled to resell or in any other way distribute (including merger, consolidation or similar transaction) the SaaS Services to any third parties without the written consent of QPR.

5.3 The Customer acknowledges that the SaaS Services are delivered utilizing Amazon Web Services (“AWS”) and Snowflake's services. Third party services are exclusively governed by their respective terms and conditions.

5.4 QPR products contain powerful features, under which the Customer can perform mass operations involving complex structures and large amounts of data and processing. As many operations can be executed in parallel by different concurrent users, it is quite possible to exhaust the capacity of the underlying resources, like CPU, central memory, storage system, and network interfaces. The capacity and performance limits of the computing environment can eventually be reached even with a single user, by increasing the amount and complexity of data and performing big enough operations. QPR will never guarantee that an arbitrary end user scenario would not exhaust the resources of the computing environment. The Customer is responsible for dimensioning the computing environment and using QPR products in a sensible way.

== 6. Information Security, Storage, and Backup ==

6.1 The Customer shall be responsible for its devices, systems, applications, connections, and software as well as their functionality. The Customer shall be responsible for the protection of the Customer’s data communications and data systems and costs for communications and other comparable costs related to the use of the SaaS Services.

6.2 The Customer Material is stored in a database file on hosted servers and it is backed up in accordance with the Service Description and QPR’s standard practices applicable from time to time.

6.3 QPR asserts no ownership or other rights to Customer Material. The Customer is solely responsible for having all required rights to use the Customer Material in the manner required by the SaaS Services or applicable laws, including but not limited to transferring the data to an information system maintained by a third party. Customer agrees not to transfer any illegal or infringing material to the SaaS Services.

6.4 QPR may store the Customer Material at any geographical location within the European Economic Area (EEA) using any third-party storage providers it deems suitable. Should there be limitations as to where Customer Material can be stored geographically, the Customer is obliged to inform QPR before transferring any of such data to the SaaS Services.

6.5 QPR personnel shall not access the Customer Material, except as necessary for resolving any technical problems of the SaaS Services, performing maintenance tasks, or performing agreed services agreed with the Customer, such as Support Services.

6.6 QPR will use commercially reasonable efforts to provide and maintain a secure environment for and retain sufficient backups of all Customer Material. In the unlikely event of a security breach or unrecoverable loss of Customer Material caused by QPR, the exclusive remedy of the Customer will be limited to a refund of a maximum of the total amount paid by the Customer for the SaaS Services over the six (6) months preceding the event. The Customer agrees to assume the risk of any such security breach or data loss and agrees to hold QPR harmless thereof.

== 7. Term and Termination ==

7.1 The Agreement shall enter into force on the date it has been duly signed by each party and shall continue for the License Term set out in the Purchase Order. After the License Term, the Agreement shall automatically renew for additional twelve (12) month renewal periods, unless terminated by either party with written notice to the other party at least three (3) months prior to the end of the License Term or the then-current renewal period.

7.2 Either party may terminate the Agreement in accordance with the QPR General Terms and Conditions.

__NOTOC__

[[Category: QPR ProcessAnalyzer]]

Create MCP Tools

2026-05-13T04:39:32Z

TeeHiet: TK-64611