Navigation Menu: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
No edit summary
 
(166 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Installation Instructions ==
The navigation menu can be opened by clicking the dashboard or view name in the header. In the beginning of the menu, for a quick access there is a list of all dashboards in the project, where the selected model is located. Also the following functionalities are available in the navigation menu:
# Prerequisite: [[Web.config_file_in_QPR_ProcessAnalyzer|In-Memory processing]] must be in use in the QPR ProcessAnalyzer Server.
# Download [https://files.qpr.com/releases/PADeploymentPackage/QPRPADeploymentPackageV003.zip QPR ProcessAnalyzer Deployment Package] and extract the contents in the package to a temporary folder.
# Log in to QPR UI.
# Switch to '''My Workspace''' and delete possible previous versions of the deployment package views.
# Import the views from the temporary folder into your QPR UI.
# Publish at least the '''QPR ProcessAnalyzer Frontpage''' view.


== QPR ProcessAnalyzer - Frontpage ==
=== Home ===
This view contains links to all the other views in the deployment package. It's advisable to publish this view, so all users have access to it.
The Home view is opened by default when login in QPR ProcessAnalyzer, and it has quick access buttons to the most common functionalities.


The menu buttons act as links to the different views in the QPR ProcessAnalyzer Deployment Package. The menu options are configured using JSON, which can easily be changed to add new menu items or remove existing. By default, the following JSON is used.
=== 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|flowchart]] on the left shows the process drawn as a conventional process flowchart.


<pre>
=== Conformance Checking ===
var menuItems = [
[[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.
  {"label": "Process Discovery", "viewIdentifier": "QPRProcessAnalyzer"},
  {"label": "Conformance View", "viewIdentifier": "QPRProcessAnalyzerConformanceView"},
  {"label": "Process Benchmarking", "viewIdentifier": "QPRProcessAnalyzerProcessBenchmarking"},
  {"label": "ChartView", "viewIdentifier": "QPRProcessAnalyzerChartView"},
  {"label": "Data Import", "viewIdentifier": "QPRProcessAnalyzerDataImport"},
  {"label": "Change Password", "viewIdentifier": "QPRProcessAnalyzerChangePassword"},
  {"label": "KPI Analysis Tester", "viewIdentifier": "QPRProcessAnalyzerKPIAnalysisTester"},
  {"label": "Model Manager", "viewIdentifier": "qprprocessanalyzermanagemodels"}
];
</pre>


== QPR ProcessAnalyzer - Process Discovery ==
=== Clustering Analysis ===
This is a plain [[QPR_ProcessAnalyzer_Presentation_Object_(PAPO)|QPR ProcessAnalyzer]] view for process discovery.
[[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.


== QPR ProcessAnalyzer - Conformance View ==
=== Enhanced BPMN ===
This view incorporates the [[Conformance Checking in QPR ProcessAnalyzer]] capability of QPR ProcessAnalyzer.
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.


== QPR ProcessAnalyzer - ChartView ==
=== Workspace ===
The ChartView allows the creation of customized charts to answer specific business needs, with measures and dimensions the user has selected. If you edit this view, make sure that the ChartView panel is placed on top of the QPR ProcessAnalyzer panel (you can do this by having the ChartView panel the last panel that you have moved), so that the BPMN editor is shown correctly.
[[QPR_ProcessAnalyzer_Project_Workspace|Project workspace]] is for managing projects, dashboards, datatables and scripts.


== QPR ProcessAnalyzer - KPI Analysis Tester ==
=== Manage Users ===
This view is an example of the [[HTML_Presentation_Object:_QPR_ProcessAnalyzer_KPI_Analysis_Tester|KPI Analysis Tester]].
[[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.


== QPR ProcessAnalyzer - Change Password ==
=== System Reports ===
This view allows the user to change his/her QPR ProcessAnalyzer password.
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.


== QPR ProcessAnalyzer - Data Import ==
=== Benchmark Performance ===
This view is used to import data into the QPR ProcessAnalyzer service (direct database import is not supported). Note that you need to have sufficient rights to import data to the QPR ProcessAnalyzer service in order to use this view.
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.  


=== Import File ===
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.
You can choose whether to import:
* '''cases''' or '''case attributes'''
* '''events''' or '''event attributes'''
* '''.xes''' or '''.pacm''' file.
With cases or case attributes and events or event attributes, the data needs to be imported from .csv files. A .xes or a .pacm file will contain both case and event data.<br>


=== File Format ===
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.
When importing from a csv file, here you can define in what format the data is in the file:
* '''Column delimiter''': Column delimiter is the character that separates data cells in a row. Usually the column delimiter is a semicolon or tab. It's possible to define any character by selecting the "other" option.
* '''Date format''': Date format is used to interpret date values in the csv file. Default format is: "yyyy-MM-dd HH:mm:ss,fff", where dd = zero-padded day of the month, from 01 through 31; MM = zero-padded month, from 01 through 12; yyyy = year as a four-digit number; HH = zero padded hour, using a 24-hour clock from 00 to 23; mm = zero-padded minute, from 00 through 59; ss = second, from 00 through 59; fff = millisecond. More information about formatting: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.
* '''Text qualifier''': Text qualifier is the character used to enclose text (string) values. Sometimes csv files don't contain text qualifiers at all.
* '''Header row number''': The row number (staring from 1) in the file that contains the headers of the data. Usually the first row contains the headers, but the file may start with rows that need to be skipped.


=== Import Destination ===
Notes:
There are following ways to import data:
* 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.
* '''New model to an existing project''': You need to select an existing project to which the new model is to be created. You also need to define name for the new model.
* Presets are run in a random order to reduce random variation in the results.
* '''New model to a new project''': You need to define the name of the new project and new model. Note that you can't define different names for the new project and the new model.
* '''Existing model''': You need to select the project and model to which the data is to be created. You can click the '''Open''' button to check the model that is currently selected.


== QPR ProcessAnalyzer - ModelManager ==
=== Query Designer ===
This view is intended for use by an administrator. Using this view requires that the QPR UI installation and the QPR ProcessAnalyzer service it uses reside in the same domain. The view enables the administrator to control which QPR ProcessAnalyzer models are loaded in memory for in-memory processing at the service. It is advisable not to publish this view.
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]].


[[Category: QPR UI Solutions]]
=== 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_Settings|User Settings]] ===
 
=== 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]]

Latest revision as of 10:34, 20 September 2024

The navigation menu can be opened by clicking the dashboard or view name in the header. In the beginning of the menu, for a quick access there is a list of all dashboards in the project, where the selected model is located. Also the following functionalities are available in the navigation menu:

Home

The Home view is opened by default when login in QPR ProcessAnalyzer, and it has quick access buttons to the most common functionalities.

Process Discovery

The Process Discovery is a starting point for an analysis to discover and visualize processes. The 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 flowchart on the left shows the process drawn as a conventional process flowchart.

Conformance Checking

Conformance Analysis incorporates the 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 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.

Workspace

Project workspace is for managing projects, dashboards, datatables and scripts.

Manage Users

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 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 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 Settings

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.

Retrieved from "https://wiki.onqpr.com/pa/index.php?title=Navigation_Menu&oldid=25136"