https://wiki.onqpr.com/pa/api.php?action=feedcontributions&user=Lasuusi&feedformat=atomQPR ProcessAnalyzer Wiki - User contributions [en]2024-03-28T17:16:04ZUser contributionsMediaWiki 1.39.1https://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Model_Datasources&diff=18203QPR ProcessAnalyzer Model Datasources2021-05-11T06:46:53Z<p>Lasuusi: </p>
<hr />
<div>Data into QPR Processanalyzer models can be loaded from several datasources. The following datasource types can be used:<br />
* [[#Loading Data from Datatables|Datatables]]: Data can be loaded from QPR ProcessAnalyzer [[QPR_ProcessAnalyzer_Project_Workspace#Managing_Datatables|datatables]].<br />
* [[#Loading Data using Loading Script|Loading Script]]: Data can be loaded using a loading script written in QPR ProcessAnalyzer [[QPR_ProcessAnalyzer_Expressions|expression language]]. The loading script can extract the data and perform needed transformations to the suitable eventlog format. The loading script is started when the model needs to be loaded into memory (pull principle). With the expression language, it's also possible to fetch data from other QPR ProcessAnalyzer models.<br />
* [[#Loading Data from ODBC Datasource|ODBC datasources]]: Data can be loaded from any ODBC compliant source system, such as database systems, SAP HANA, ServiceNow, Excel files and CSV files.<br />
<br />
== Model Datasource Settings ==<br />
Datasource needs to be defined for cases and another datasource for events. Model datasource settings are in the ''Model Properties'' dialog in '''Cases datasource''' and '''Events datasource''' tabs. It's possible that cases and events are loaded from different types of datasources, e.g. cases from an ODBC datasource and events from a datatable. Events datasource is optional and cases datasource is mandatory.<br />
<br />
Following settings are available:<br />
* '''Datasource''': The datasource can be ''Datatable'' (stored in QPR ProcessAnalyzer database), ''ODBC'' (data is fetched by executing an ODBC query to an OCBC datasource) or ''Loading Script'' (data is created by running an expression language query which can access e.g. datatables and ODBC datasources).<br />
* '''Datatable''': When ''datasource'' is a ''datatable'', this settings defines the datatable to use.<br />
* '''Case ID''': Defines column containing case id. This mapping needs to be done for both the cases and events data. The column datatype can be either string or number.<br />
* '''Event Type''': Defines column containing event type name. This mapping needs to be done for the events data. This column datatype must be string.<br />
* '''Event Time''': Defines column containing event timestamp. This mapping needs to be done for the events data. The column datatype must be date.<br />
* '''Connection String''': ODBC datasources connection string to use to fetch the cases/events data. Connection string depends on the data source type and can be found e.g. in https://www.connectionstrings.com.<br />
* '''Connection String Key''': [[Secure Strings|Secure string key]] of the ODBC connection string to use to fetch the cases/events data. Alternative to the OdbcConnectionString property.<br />
* '''ODBC Query''': ODBC query to run to the ODBC datasource to fetch the cases/events data. Query syntax depends on the source system where the data is fetched.<br />
* '''Loading Script''': Expression language script that provides the cases/events data. For more information, see the examples.<br />
<br />
Note that when changing datasource settings, the model is dropped from the memory, so that it can be reloaded using the changed settings.<br />
<br />
== Datatable Models ==<br />
When the ''DataSource'' is ''Datatable'', data is loaded from a QPR ProcessAnalyzer [[QPR_ProcessAnalyzer_Project_Workspace#Managing_Datatables|datatable]]. Datatables can be created by importing data to them from CSV files, or as a result of an [[Data_Extraction,_Transformation,_and_Loading|ETL script]].<br />
<br />
When a model using datatables as a datasource, is moved to another project, also the linked datatables are moved with the model. Note that there may be several models using a same datatable, and in that case the linkages to other models may be broken when moving a model to other project. Note also that if another datatable with the same name already exist in the target project, the datatable cannot be moved, because there cannot be two datatables having the same name in the same project.<br />
<br />
== Loading Script ==<br />
Data loaded to a QPR ProcessAnalyzer model can be defined using a loading script, which is written in the QPR ProcessAnalyzer expression language. The loading script produces a DataFrame containing the cases or events data. In addition, mappings from the DataFrame column names defining which column is case id, event type name and timestamp needs to be defined.<br />
<br />
The loading script is run in a security context where there are [[Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|GenericRead and GenericWrite]] permissions for the project, where the loaded model is located. This means that the loading script has access to all the data in the same project, and also a write access e.g. to the datatables. User permissions are not used by the loading script, so that the user who initiated the loading, wouldn't affect the result. In addition, the model may be loaded [[Automatic Model Loading on Server Startup|automatically on server startup]], and in that case there is no user who initiated the loading.<br />
<br />
When loading data from an ODBC datasource, note also the [[PA_Configuration_database_table_in_QPR_ProcessAnalyzer|AllowExternalDatasources setting]], which may prevent the loading.<br />
<br />
=== Examples ===<br />
<br />
Loading script for events that takes the eventlog from another model:<br />
<pre><br />
ToDataFrame(<br />
EventLogById(1).Events.[Case.Name, TypeName, Timestamp],<br />
["CaseId", "EventType", "Timestamp"]<br />
)<br />
</pre><br />
<br />
Loading script for events:<br />
<pre><br />
let maxEventsPerModel = 1000;<br />
let ms = ["SAP_OrderToCash", "BPIC13_incidents"].(<br />
Let("modelName", _), Models.Where(Name == modelName))[0]);<br />
Let("eventAttributes", ToDictionary());<br />
ms.EventAttributes.(<br />
Let("ea", _), eventAttributes.Set(ea.Name, ea));<br />
Let("orderedEventAttributes", OrderByValue(eventAttributes.Keys));<br />
ConcatTop([[Flatten(<br />
["Case", "EventType", "TimeStamp", orderedEventAttributes])],<br />
ConcatTop(ms.EventLog.Events[NumberRange(0, Min(CountTop(_), maxEventsPerModel) - 1)].Flatten(<br />
[Case.Name, Type.Name, TimeStamp, (Let("evt", _), orderedEventAttributes.(<br />
Let("att", _), evt.Attribute(att)<br />
)<br />
)]<br />
)<br />
)]<br />
)<br />
</pre><br />
<br />
Loading script for cases:<br />
<pre><br />
Let("maxEventsPerModel", 1000);Let("ms", ["SAP_OrderToCash", "BPIC13_incidents"].(Let("modelName", _), Models.Where(Name == modelName))[0]);Let("caseAttributes", ToDictionary());ms.CaseAttributes.(Let("ca", _), caseAttributes.Set(ca.Name, ca));Let("orderedCaseAttributes", OrderByValue(caseAttributes.Keys));Let("cases", ToDictionary());ms.EventLog.Events[NumberRange(0, Min(CountTop(_), maxEventsPerModel) - 1)].Case.(Let("c", _), cases.Set(c, true));ConcatTop([[Flatten(["Case", "Model", orderedCaseAttributes])],cases.Keys.Flatten([Name, EventLog.Name, (Let("c", _), orderedCaseAttributes.(Let("att", _), c.Attribute(att)))])])<br />
</pre><br />
<br />
Create a model with eventlog data embedded into the expression.<br />
<pre><br />
ToDataFrame([["a", "et1", DateTime(2019,1)],["a", "et2", DateTime(2019,2)],["a", "et3", DateTime(2019,3)],["b", "et1", DateTime(2019,2)],["c", "et3", DateTime(2019,2)],["c", "et2", DateTime(2019,3)],["c", "et2", DateTime(2019,4)],["c", "et3", DateTime(2019,5)],["c", "et4", DateTime(2019,6)]], ["Case","Timestamp","EventType"])<br />
</pre><br />
<br />
This loading script loads events using several odbc queries (each event type separately).<br />
<pre><br />
let eventTypes = ["Invoice Created", "Requested Delivery", "Inventory Date", "Invoice Payment", "Actual Delivery"];<br />
let data = eventTypes.(<br />
ImportODBC(<br />
"Driver={ODBC Driver 17 for SQL Server};Server=SERVER\\MSSQLSERVER2017;DataBase=Process Mining Data;Uid=user1;Pwd=pw1;",<br />
"SELECT [Case] AS \"CaseId\", Event_Type AS \"EventType\", Start_Time AS TimeStamp, Cost, Variable_cost, booleanAttribute1 FROM [OtC Model events] Where [Event_Type]=\'" + _ +"\'"<br />
)<br />
);<br />
let combinedData = data[0];<br />
For("i", 1, i < CountTop(data), i + 1,<br />
let("combinedData",<br />
combinedData.Append(data[i])<br />
)<br />
);<br />
combinedData;<br />
</pre><br />
<br />
== ODBC Datasource ==<br />
When ''Datasource'' is ''ODBC'', data is loaded directly from an ODBC datasource when the model is loaded, and the data is not stored permanently in QPR ProcessAnalyzer. There needs to be a suitable ODBC driver installed in QPR ProcessAnalyzer server, and ''ODBC connection string'' and ''ODBC query'' needs to be defined (examples below). Note that when model datasource is ODBC, it's not possible to import data to the model in QPR ProcessAnalyzer UI (data needs to be imported where it is originally stored).<br />
<br />
[[PA_Configuration_database_table_in_QPR_ProcessAnalyzer|AllowExternalDatasources]] setting needs to be set to ''True'' to use the ODBC datasource.<br />
<br />
=== ODBC Driver Installation ===<br />
''Microsoft Access Database Engine 2016 Redistributable'' is a recommended software package containing ODBC drivers for<br />
* Microsoft SQL Server<br />
* Microsoft Access (*.mdb and *.accdb) files<br />
* Microsoft Excel (*.xls, *.xlsx, and *.xlsb) files<br />
* CSV text files<br />
<br />
The package is installed in the computer where the QPR ProcessAnalyzer Server is running. Installation instructions:<br />
# Go to https://www.microsoft.com/en-us/download/details.aspx?id=54920 and click Download.<br />
# Select whether to use the 32bit or 64bit (x64) version (usually it's the 64bit version).<br />
# Double-click the executable file on your hard disk to start the setup program.<br />
# Follow the instructions on the screen to complete the installation.<br />
<br />
=== Read data from CSV file ===<br />
Data can be loaded from CSV files located in the file system using ''Microsoft Access Text Driver (*.txt, *.csv)'' driver. The following example loads files C:\ProcessMiningData\ModelCaseAttributes.csv and C:\ProcessMiningData\ModelEventData.csv.<br />
* Cases: Connection String: Driver={Microsoft Access Text Driver (*.txt, *.csv)};DefaultDir=C:\\ProcessMiningData\\;Extensions=asc,csv,tab,txt<br />
* Cases: ODBC Query: SELECT * FROM [ModelCaseAttributes.csv]<br />
* Events: Connection String: Driver={Microsoft Access Text Driver (*.txt, *.csv)};DefaultDir=C:\\ProcessMiningData\\;Extensions=asc,csv,tab,txt<br />
* Events: ODBC Query: SELECT * FROM [ModelEventData.csv]<br />
<br />
When reading from CSV files, you may need to set the CSV file format for the ODBC driver using the '''Schema.ini''' file (more information: https://docs.microsoft.com/en-us/sql/odbc/microsoft/schema-ini-file-text-file-driver?view=sql-server-2017). ODBC text driver may guess column data type and return null values in case when guessed column type not match. Guessing based top rows of data. ODBC text driver support only one data type per column mixed data types is not supported.<br />
<br />
=== Read data from Excel file ===<br />
In this example, data is loaded from a Excel file that is accessible in the file system. In this example, the loaded file is C:\ProcessMiningData\ModelData.xlsx and cases are in sheet ''MyCases'' and events in sheet ''MyEvents''.<br />
<br />
* Cases: Connection String: Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=C:\\ProcessMiningData\\ModelData.xlsx<br />
* Cases: ODBC Query: SELECT * FROM [MyCases$]<br />
* Events: Connection String: Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=C:\\ProcessMiningData\\ModelData.xlsx<br />
* Events: ODBC Query: SELECT * FROM [MyEvents$]<br />
<br />
=== Read data from SQL Server ===<br />
Recommended driver: https://www.microsoft.com/en-us/download/details.aspx?id=56567<br />
<br />
In this example, data is loaded from an SQL Server table. SQL Server hostname is ''myServerName'', instance name is ''myInstanceName'' and database name is ''MyDatabase''. The ''Trusted_Connection'' is for Windows authentication.<br />
* Cases: Connection String: Driver={ODBC Driver 17 for SQL Server};Server=myServerName\\myInstanceName;DataBase=MyDatabase;Trusted_Connection=Yes;<br />
* Cases: ODBC Query: SELECT CASENAME, COST, COUNTRY, PRODUCT FROM CASES_TABLE<br />
* Events: Connection String: Driver={ODBC Driver 17 for SQL Server};Server=myServerName\\myInstanceName;DataBase=MyDatabase;Trusted_Connection=Yes;<br />
* Events: ODBC Query: SELECT CASENAME, CREATED_DATE, CREATED_BY FROM EVENTS_TABLE<br />
<br />
If SQL Server authentication is used, the connection string is Driver={ODBC Driver 17 for SQL Server};Server=myServerName\myInstanceName;DataBase=MyDatabase;Trusted_Connection=No;Uid=myUsername;PWD=myPassword;<br />
<br />
More about SQL Server connection strings: https://www.connectionstrings.com/sql-server/<br />
<br />
=== Troubleshooting for ODBC Loading ===<br />
<br />
The following error message may be encountered: ''System.Data.Odbc.OdbcException (0x80131937): ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''. Probable reason is that the ODBC driver is missing or driver name is not correct. To solve the issue:<br />
* Check ODBC drivers is installed by running '''C:\Windows\System32\odbcad32.exe'''.<br />
* Check the connection string.<br />
<br />
The following error message may be encountered: '''ERROR [HY024] [Microsoft][ODBC Text Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.'''.<br />
Example error when specified directory is missing:<br />
<br />
Error when CSV file is missing: '''System.Data.Odbc.OdbcException (0x80131937): ERROR [42S02] [Microsoft][ODBC Text Driver] The Microsoft Access database engine could not find the object 'CaseAttributes.csv'. Make sure the object exists and that you spell its name and the path name correctly. If 'CaseAttributes.csv' is not a local object, check your network connection or contact the server administrator.'''<br />
<br />
Error codes for troubleshooting: [https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/appendix-a-odbc-error-codes?view=sql-server-2017| ODBC Error Codes].<br />
<br />
If the error message mention about Case or Event attributes named as ''F<column number>'' (e.g. F10), the data might be inconsistent, as there might be different amount of columns in different rows.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=18039QPR ProcessAnalyzer Chart2021-04-20T12:29:50Z<p>Lasuusi: </p>
<hr />
<div>Chart allows to create versatile and visually appealing charts with flexible KPI definitions to answer many business needs. Chart allows to calculate KPI's from the process mining objects, such as cases, events, event types and flows. The data can be sliced into freely selectable dimensions and KPIs calculated for each dimension to visualize comparisons, benchmarks and trends. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette. In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the entire screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Process Discovery''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Visual Settings ==<br />
[[File:Chartsettingsgeneral.png|right|300px]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of chart types, table, pivot chart and a KPI card available (see more in [[#Available_Visualizations|next chapter]]. Depending on the visualization, different mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, the measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When enabled and number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
* '''[[#On-screen Settings|On-screen Settings]]'''<br />
* '''Custom Layout''': Using the Custom Layout, advanced visual settings for the chart and table can be defined using JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be specified. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
* '''Export''': Tables, pivot tables and charts can be exported into several formats available in the dropdown list.<br />
<br />
=== Available Visualizations ===<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Graphs|Graph]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
<br />
== Analyzed Data ==<br />
When creating a chart, the first thing to decide, are which items to be analyze. Settings that determine the analyzed data are:<br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. Still, for cases it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|700px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
* '''Analyzed objects sample size''': Sampling randomly removes some of the items leaving only the sample size of items left to the analyzed objects. If sample size is not defined, sampling is not used. The purpose of sampling is to improve performance, as there will be less items in the dimension and measure calculation. The intention is that the calculation from the sampled dataset would provide close enough results in statistically high enough probability. Sampling cannot be used in some calculations, because it affects the calculation results.<br />
* '''Model''': Select a process mining model that is shown by this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used by the chart. This setting allows to create dashboards, where the dashboard at the same time fetches and visualizes data from different models.<br />
<br />
== Selecting Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right|300px]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
=== Measure, Dimension and Column Settings ===<br />
[[File:Chartsettingsmeasuresettings.png|right|650px]]<br />
<br />
When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column settings. The following settings are available for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels shown for example as chart axis titles or table column names (depending on the visualization). Use the custom label to define your own label which replaces the automatic label. If you want to hide the label, you can use a space as the custom title.<br />
* '''Color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is shown with each measure/dimension/column value. In some expressions, units are determined automatically, e.g. for durations.<br />
* '''Unit position''': Determines how units are shown with the value. Units can be shown before or after the value, and there can be a space between or not. Unit can also be hidden.<br />
* '''Date format''': Date type of data is presented with this date format. For example: dd.MM.yyyy HH:mm:ss, M/d/yyyy HH:mm.<br />
* '''Hidden''': For tables, measures/dimensions/columns can be hidden using this checkbox. For example, conditional formatting can use data from the hidden columns.<br />
* '''Web link''': When defined (works in tables only), the measure/dimension/column will be a clickable web link opening the target web site to a new tab. Only the text in the table cell is clickable, so filtering is possible when clicking next to the text. To refer to the data in the same row, web links can contain tags (e.g. '''${dimension:1}'''), which are replaced with the data. You can also refer to the clicked value with '''${this}'''. If the web link only consists of a single tag, the tag value is not encoded (because the tag is assumed to contain a full url). If the web link contains static text in addition to the tags, the tag values are encoded using encodeUriComponent (because tags are assumed to be used as url parameters). If the link does not start with http:// or https://, the link is interpreted as a relative link, and it's added to the end of the QPR ProcessAnalyzer url. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://devnet.onqpr.com/pawiki/index.php?search=${this}</nowiki>''<br />
* '''Show for null value''': When an expression provides a null value, the text defined in this field is shown in the visualization. By default empty text.<br />
* '''Show for empty string''': When an expression provides an empty string value, the text defined in this field is shown in the visualization. By default ''(empty)''.<br />
* '''Show for boolean true''': When an expression provides a boolean type of value ''true'', the text defined in this field is shown in the visualization. By default ''Yes''.<br />
* '''Show for boolean false''': When an expression provides a boolean type of value ''false'', the text defined in this field is shown in the visualization. By default ''No''.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual data type of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are important for the visualization to show correctly, e.g. charts mostly require numerical data. Data type list also has ''Auto detect'' which analyzes the calculated data and chooses the data type based on the most common data type in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''. This setting is only available for measures.<br />
* '''Variable name''': Name of the variable containing this measure or column value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined. This setting is not available for dimensions.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right|300px]]<br />
<br />
In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
* '''Find Root Causes''': Rules that are used by the root causes analyses, which are finding root causes for the phenomena pointed by those rules.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right|300px]]<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted. You can copy chart settings and use them in another chart as follows: Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
* '''[[#Linked settings|Linked settings]]'''<br />
* '''[[#Variable mappings|Variable mappings]]'''<br />
* '''[[#Benchmark performance|Benchmark performance]]'''<br />
* '''Show in Query Designer''': For testing and development purposes, clicking this button starts editing the current expression in the [[QPR_ProcessAnalyzer_Features_Overview#Query_Designer|Query Designer]] view.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Background color''': Chart area background color affecting the Highcharts-based charts, KPI cards, tables (excluding the grey header), and root causes visualization.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Shows tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown, the chart title is not shown (titles are still shown for tables).<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Component settings (without data)''': Chart uses Highcharts library to draw charts and Syncfusion library to draw tables and pivots. With this options you can see the actual configuration that is used by the visualization component. The visualized data is part of the configuration, but it's removed.<br />
* '''Component settings (with data)''': This is similar option as the previous, except the visualized data is also included.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Chart comparison''': Similar to the Chart filter, except showing the currently selected comparison.<br />
<br />
<br />
<br />
== On-screen Settings ==<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are visible above the chart in the dashboard for quick access. On-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
== Variable mappings ==<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
* '''variable''': Name of the bound dashboard variable.<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter to bind to.<br />
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
== Linked settings ==<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
* '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter.<br />
* '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<br />
Example:<br />
<br />
[[File:Linkedsettings.png|center|500px]]<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Start event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Start event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "End event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "End event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Time unit"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Time unit"<br />
}<br />
]<br />
]<br />
</pre><br />
<br />
== Benchmark performance ==<br />
Clicking the '''Benchmark performance''' buttons starts a performance benchmark run for the chart, which measures the time taken for the server to calculate and return the required data for the chart. Benchmarking is useful when for example creating custom expressions and finding the most optimal way of writing them. The benchmark runs the calculation multiple times to reduce effect of random variation in the measurement. When the benchmark run is completed, the following information is shown:<br />
* Benchmark result (shown as bolded) (calculated as a median time of the individual measurements)<br />
* Variation in the benchmark measurement (calculated as a standard deviation of the individual measurements divided by the benchmark result)<br />
* Difference to the previous benchmark result<br />
* List of all individual measurements (abandoned are greyed out)<br />
<br />
The highest individual measurements (approximately 40%) are abandoned from the calculation and shown as greyed out, because the highest measurements are usually result of the random variation.<br />
<br />
The history of benchmark runs done for the chart are preserved until the dashboard is closed.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Chartsettingsmeasuresettings.png&diff=18037File:Chartsettingsmeasuresettings.png2021-04-20T12:20:57Z<p>Lasuusi: Lasuusi uploaded a new version of File:Chartsettingsmeasuresettings.png</p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Chartsettingsmeasures.png&diff=18036File:Chartsettingsmeasures.png2021-04-20T12:20:13Z<p>Lasuusi: Lasuusi uploaded a new version of File:Chartsettingsmeasures.png</p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Chartsettingsgeneral.png&diff=18035File:Chartsettingsgeneral.png2021-04-20T12:19:23Z<p>Lasuusi: Lasuusi uploaded a new version of File:Chartsettingsgeneral.png</p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Graphs&diff=17860QPR ProcessAnalyzer Graphs2021-03-15T07:42:21Z<p>Lasuusi: </p>
<hr />
<div>Graphs are general term for column, bar, line, area, etc. charts.<br />
<br />
== Graph Colors ==<br />
In graphs, colors can be defined for '''series''' (i.e. all data points of the series) and individual '''data points'''. Data point colors will have priority over the series colors.<br />
<br />
Series colors can be defined using the following settings:<br />
* By default, series colors come from a '''default color palette'''.<br />
* '''Custom color palette''' can be defined overriding the default color palette.<br />
* Series color can be set for individual measures/dimensions in the measure/dimension settings (overriding the palette color).<br />
<br />
If defined, the data point colors override series color for individual data points. Data point colors can be defined using following rules:<br />
* For entire graph, data point colors can be defined using a measure/dimension that is mapped to a '''data point color''' (available in the measure/dimension settings).<br />
* For individual series, '''[[QPR_ProcessAnalyzer_Chart#Measure.2C_Dimension_and_Column_Settings|color mappings]]''' can be used to define a specific color to specific measure/dimension value. This will override the previous one.<br />
* For individual series, '''[[#Conditional_Formatting|conditional formatting]]''' can be used to define rules for data point colors (in the measure/dimension settings). This will override the previous ones.<br />
<br />
== Conditional Formatting ==<br />
<br />
Conditional formatting can be used to define colors for each data point (i.e. color for column, bar, circle etc. depending on chart type). The conditional formatting is defined in the settings of the measure/dimension that is mapped to the y-axis.<br />
<br />
Conditional formatting example:<br />
<pre><br />
{<br />
"color": {<br />
"rules": [<br />
{<br />
"value": 100,<br />
"comparison": ">",<br />
"color": "#36d475"<br />
},<br />
{<br />
"color": "#EF5254"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
See more examples from the [[QPR_ProcessAnalyzer_Table#Conditional_Formatting|table conditional formatting]] how to define conditional formatting for graphs. Note that graphs only support the '''color''' property in the top level in the JSON.<br />
<br />
==Customization Examples==<br />
Example for hiding legend.<br />
<pre><br />
{<br />
"legend": {<br />
"enabled": false<br />
}<br />
}<br />
</pre><br />
<br />
Example for forcing a minimum and maximum value for the first (left side) Y-axis.<br />
<pre><br />
{<br />
"yAxis": [<br />
{<br />
"min": 0,<br />
"max": 100<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example for forcing a minimum and maximum value for the second (right side) Y-axis.<br />
<pre><br />
{<br />
"yAxis": [<br />
{},<br />
{<br />
"min": 0,<br />
"max": 100<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example for forcing a minimum value for two Y-axes (left and right side).<br />
<pre><br />
{<br />
"yAxis": [<br />
{<br />
"min": 0,<br />
"max": 100<br />
},<br />
{<br />
"min": 0,<br />
"max": 10000<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example for forcing a minimum and maximum value for the second (right side) Y-axis without forcing a maximum value on the first (left side) Y-axis and giving custom titles for the two Y-axes.<br />
<pre><br />
{<br />
"yAxis": [<br />
{<br />
"min": 0,<br />
"title": {<br />
"text": "Left Y-axis"<br />
}<br />
},<br />
{<br />
"min": 0,<br />
"max": 100,<br />
"title": {<br />
"text": "Right Y-axis"<br />
}<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example for hiding the second Y-axis.<br />
<pre><br />
{<br />
"yAxis": [<br />
{<br />
"visible": true<br />
},<br />
{<br />
"visible": false<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
Example for forcing a minimum value for the X-axis.<br />
<pre><br />
{<br />
"xAxis": {<br />
"min": 0,<br />
"max": 10<br />
}<br />
}<br />
</pre><br />
<br />
Example for reversing order for the Y-axis.<br />
<pre><br />
{<br />
"yAxis": [<br />
{<br />
"reversed": true<br />
}<br />
]<br />
}<br />
</pre><br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=17495QPR ProcessAnalyzer Chart2021-01-13T08:13:37Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|700px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format.<br />
* '''Web link''': When defined (works in tables only), the measure/dimension/column will be a clickable web link opening the target web site to a new tab. Only the text in the table cell is clickable, so filtering is possible when clicking next to the text. To refer to the data in the same row, web links can contain tags (e.g. '''${dimension:1}'''), which are replaced with the data. You can also refer to the clicked value with '''${this}'''. If the link does not start with http:// or https://, the link is interpreted as a relative link, and it's added to the end of the QPR ProcessAnalyzer url. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://devnet.onqpr.com/pawiki/index.php?search=${this}</nowiki>''<br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Background color''': Chart area background color affecting the Highcharts-based charts, KPI cards, tables (excluding the grey header), and root causes visualization.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
=== On-screen Settings ===<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
=== Custom Layout ===<br />
Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
<br />
=== Variable mappings ===<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
* '''variable''': Name of the bound dashboard variable.<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter to bind to.<br />
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
=== Linked settings ===<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
* '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter.<br />
* '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<br />
Example:<br />
<br />
[[File:Linkedsettings.png|center|500px]]<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Start event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Start event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "End event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "End event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Time unit"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Time unit"<br />
}<br />
]<br />
]<br />
</pre><br />
<br />
=== Benchmark performance ===<br />
Clicking the '''Benchmark performance''' buttons starts a performance benchmark run for the chart, which measures the time taken for the server to calculate and return the required data for the chart. Benchmarking is useful when for example creating custom expressions and finding the most optimal way of writing them. The benchmark runs the calculation multiple times to reduce effect of random variation in the measurement. When the benchmark run is completed, the following information is shown:<br />
* Benchmark result (shown as bolded) (calculated as a median time of the individual measurements)<br />
* Variation in the benchmark measurement (calculated as a standard deviation of the individual measurements divided by the benchmark result)<br />
* Difference to the previous benchmark result<br />
* List of all individual measurements (abandoned are greyed out)<br />
<br />
The highest individual measurements (approximately 40%) are abandoned from the calculation and shown as greyed out, because the highest measurements are usually result of the random variation.<br />
<br />
The history of benchmark runs done for the chart are preserved until the dashboard is closed.<br />
<br />
=== Go to Query Designer ===<br />
For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=17494QPR ProcessAnalyzer Chart2021-01-13T08:10:17Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|500px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format.<br />
* '''Web link''': When defined (works in tables only), the measure/dimension/column will be a clickable web link opening the target web site to a new tab. Only the text in the table cell is clickable, so filtering is possible when clicking next to the text. To refer to the data in the same row, web links can contain tags (e.g. '''${dimension:1}'''), which are replaced with the data. You can also refer to the clicked value with '''${this}'''. If the link does not start with http:// or https://, the link is interpreted as a relative link, and it's added to the end of the QPR ProcessAnalyzer url. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://devnet.onqpr.com/pawiki/index.php?search=${this}</nowiki>''<br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Background color''': Chart area background color affecting the Highcharts-based charts, KPI cards, tables (excluding the grey header), and root causes visualization.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
=== On-screen Settings ===<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
=== Custom Layout ===<br />
Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
<br />
=== Variable mappings ===<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
* '''variable''': Name of the bound dashboard variable.<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter to bind to.<br />
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
=== Linked settings ===<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
* '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter.<br />
* '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<br />
Example:<br />
<br />
[[File:Linkedsettings.png|center|500px]]<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Start event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Start event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "End event"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "End event"<br />
}<br />
],<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Time unit"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Time unit"<br />
}<br />
]<br />
]<br />
</pre><br />
<br />
=== Benchmark performance ===<br />
Clicking the '''Benchmark performance''' buttons starts a performance benchmark run for the chart, which measures the time taken for the server to calculate and return the required data for the chart. Benchmarking is useful when for example creating custom expressions and finding the most optimal way of writing them. The benchmark runs the calculation multiple times to reduce effect of random variation in the measurement. When the benchmark run is completed, the following information is shown:<br />
* Benchmark result (shown as bolded) (calculated as a median time of the individual measurements)<br />
* Variation in the benchmark measurement (calculated as a standard deviation of the individual measurements divided by the benchmark result)<br />
* Difference to the previous benchmark result<br />
* List of all individual measurements (abandoned are greyed out)<br />
<br />
The highest individual measurements (approximately 40%) are abandoned from the calculation and shown as greyed out, because the highest measurements are usually result of the random variation.<br />
<br />
The history of benchmark runs done for the chart are preserved until the dashboard is closed.<br />
<br />
=== Go to Query Designer ===<br />
For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Linkedsettings.png&diff=17493File:Linkedsettings.png2021-01-13T08:03:46Z<p>Lasuusi: </p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=17173Filtering in QPR ProcessAnalyzer2020-11-05T08:36:10Z<p>Lasuusi: /* Filter actions */</p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removing them.<br />
<br />
[[File:Filterruledisableing.png]]<br />
<br />
== Filter actions ==<br />
Users with [https://devnet.onqpr.com/pawiki/index.php/Roles_and_Permissions_in_QPR_ProcessAnalyzer at least the Analyzer user rights] can modify and delete the saved filters of a model. You can do this by opening the Filters list, hovering your mouse over a saved filter and clicking on the three dots that appear on the right edge.<br />
<br />
[[File:Filteroptions.png|500px]]<br />
<br />
When you go to the "Actions" tab you have the following options:<br />
* '''Delete''': Delete this filter permanently.<br />
* '''Duplicate''': Create a copy of this filter.<br />
* '''Replace''': Replace this filter's rules with the selected rules in the header.<br />
* '''Export''': Export this filter's rules to a file.<br />
* '''Import''': Replace this filter's rules by importing new rules from a file.<br />
<br />
[[File:Filteractions.png|500px]]<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=17172Filtering in QPR ProcessAnalyzer2020-11-05T08:32:54Z<p>Lasuusi: </p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removing them.<br />
<br />
[[File:Filterruledisableing.png]]<br />
<br />
== Filter actions ==<br />
Users with [https://devnet.onqpr.com/pawiki/index.php/Roles_and_Permissions_in_QPR_ProcessAnalyzer at least the Analyzer user rights] can modify and delete the saved filters of a model. You can do this by opening the saved filter list, hovering your mouse over a saved filter and clicking on the three dots that appear on the right edge.<br />
<br />
[[File:Filteroptions.png|500px]]<br />
<br />
When you go to the "Actions" tab you have the following options:<br />
* '''Delete''': Delete this filter permanently.<br />
* '''Duplicate''': Create a copy of this filter.<br />
* '''Replace''': Replace this filter's rules with the selected rules in the header.<br />
* '''Export''': Export this filter's rules to a file.<br />
* '''Import''': Replace this filter's rules by importing new rules from a file.<br />
<br />
[[File:Filteractions.png|500px]]<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=17171Filtering in QPR ProcessAnalyzer2020-11-05T08:30:52Z<p>Lasuusi: </p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removing them.<br />
<br />
[[File:Filterruledisableing.png]]<br />
<br />
== Filter actions ==<br />
Users with [https://devnet.onqpr.com/pawiki/index.php/Roles_and_Permissions_in_QPR_ProcessAnalyzer at least the Analyzer user rights] can modify and delete the saved filters of a model. You can do this by opening the saved filter list, hovering your mouse over a saved filter and clicking on the three dots that appear on the right edge.<br />
<br />
[[File:Filteroptions.png]]<br />
<br />
When you go to the "Actions" tab you have the following options:<br />
* '''Delete''': Delete this filter permanently.<br />
* '''Duplicate''': Create a copy of this filter.<br />
* '''Replace''': Replace this filter's rules with the selected rules in the header.<br />
* '''Export''': Export this filter's rules to a file.<br />
* '''Import''': Replace this filter's rules by importing new rules from a file.<br />
<br />
[[File:Filteractions.png]]<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=17170Filtering in QPR ProcessAnalyzer2020-11-05T08:25:31Z<p>Lasuusi: </p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
== Filter actions ==<br />
Users with [https://devnet.onqpr.com/pawiki/index.php/Roles_and_Permissions_in_QPR_ProcessAnalyzer at least the Analyzer user rights] can modify and delete the saved filters of a model. You can do this by opening the saved filter list, hovering your mouse over a saved filter and clicking on the three dots that appear on the right edge.<br />
<br />
[[File:Filteroptions.png]]<br />
<br />
When you go to the "Actions" tab you have the following options:<br />
* '''Delete''': Delete this filter permanently.<br />
* '''Duplicate''': Create a copy of this filter.<br />
* '''Replace''': Replace this filter's rules with the selected rules in the header.<br />
* '''Export''': Export this filter's rules to a file.<br />
* '''Import''': Replace this filter's rules by importing new rules from a file.<br />
<br />
[[File:Filteractions.png]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removing them.<br />
<br />
[[File:Filterruledisableing.png]]<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Table&diff=17091QPR ProcessAnalyzer Table2020-10-27T08:46:44Z<p>Lasuusi: </p>
<hr />
<div>Table conditional formatting can be used to define table cell background colors, text colors, colored icons and databar, where all depend on the data in the table.<br />
<br />
== Table Functionalities ==<br />
<br />
<br />
==Conditional Formatting==<br />
Conditional formatting is defined in the measure/dimension/column settings as a JSON object with following allowed properties:<br />
* '''backgroundColor'''<br />
** '''rules''': Rules are checked in the defined order and the first matching determines the color.<br />
*** '''color''': color to use when the rule matches.<br />
*** '''value''': Value to compare against.<br />
*** '''comparison''': One of the following: <, >, <=, >=, ==, !=<br />
** '''scale'''<br />
*** '''color''': Color that corresponds with the value.<br />
*** '''value''': Value that corresponds with the color.<br />
** '''color''': Fixed color that is used when no rules/scale is defined or there are no matching rules.<br />
* '''textColor''': Same settings can be used as in the backgroundColor.<br />
* '''databar'''<br />
** '''min''': Value that represents the databar minimum position (i.e. when databar is not visible).<br />
** '''max''': Value that represents the databar maximum position (i.e. databar fills the whole cell).<br />
** '''color''': Color of the databar. Default color is #4bc3ff.<br />
* '''icon'''<br />
** '''rules''': Similar syntax can be used as in the color rules, except instead of "color" there is "icon" attribute to define the icon. All Google Material Icons are available: https://material.io/resources/icons/.<br />
** '''color''': Color of the icon. Default color is #333333.<br />
<br />
Rule value property and scale minimum and maximum can be defined:<br />
* fixed value, e.g. 5<br />
* aggregate of the same column data, e.g. { "aggregate": "max" }<br />
* aggregate of another column data, e.g. { "type": "measure", "index": 1, "aggregate": "max" }<br />
* refer to a cell value in other column in the same row, e.g. {"type": "measure", "index": 1 }<br />
<br />
Available aggregations are: min, max, sum, average, median, first, last.<br />
<br />
===Templates===<br />
Below are listed the examples used in dashboards with their respective use cases and Conditional formatting expressions. The recommended colors and their color codes are as follows:<br />
<br />
* Green: #68DD8F (Positively correlating KPIs)<br />
* Red: #EF5254 (Negatively correlating KPIs)<br />
* Blue: #4BC3FF (Case/Event counts)<br />
* Dark blue: #0F55A5 (Automation)<br />
* Orange: #FEA88A (Durations)<br />
* Yellow: #FFD851 (Value/Cost)<br />
====Traffic lights====<br />
Use case: KPIs based on traffic light signaling<br />
<br />
[[File:Trafficlightconiditionalformatting.png|200px]]<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"rules": [<br />
{<br />
"color": "#EF5254",<br />
"value": 10,<br />
"comparison": ">="<br />
},<br />
{<br />
"color": "#FFD851",<br />
"value": 6.5,<br />
"comparison": ">="<br />
},<br />
{<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
====Green databar====<br />
Use case: KPIs where 100% is a desired value, eg. On-Time Delivery<br />
<br />
[[File:Greendatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
<br />
</pre><br />
====Red databar====<br />
Use case: KPIs where 0% is the desired value and you want to highlight the worst performers of this metric, eg. Material shortages<br />
<br />
[[File:Reddatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#EF5254"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
====Blue databar====<br />
Use cases: Case/event counts<br />
<br />
[[File:Bluedatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#4BC3FF"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
====Dark blue databar====<br />
Use case: Automation rate and similar metrics that scale 0-100%<br />
<br />
[[File:Darkbluedatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#7588C4"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
====Yellow databar====<br />
Usecase: Monetary KPIs such as cost/value<br />
<br />
[[File:Yellowdatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
====Orange scale====<br />
Use case: Durations<br />
<br />
[[File:Orangescale.png|200px]]<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": {"aggregate": "max" },<br />
"color": "#fea88a"<br />
},<br />
{<br />
"value": {"aggregate": "min" },<br />
"color": "#FBE8E6"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
===Other examples===<br />
Background color is based on a color scale where column minimum value zero gets color #FFFFFF and maximum value #FFD851. Color is scaled linearly between these colors.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
Similar to previous example, except minimum and maximum values come from another column (measure number 1).<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": { "type":"measure", "index": 1, "aggregate": "min" },<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "type":"measure", "index": 1, "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
The following setting defines a fixed background color for a column.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"color": "#FFD851"<br />
}<br />
}<br />
</pre><br />
<br />
Background color code is taken from column measure 1 from the same row.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"color": { "type":"measure", "index": 1 }<br />
}<br />
}<br />
</pre><br />
Text color is #FF0000 if value is lower than 20, otherwise #00FF00.<br />
<pre><br />
{<br />
"textColor": {<br />
"rules": [<br />
{<br />
"color": "#FF0000",<br />
"value": 20,<br />
"comparison": "<"<br />
},<br />
{<br />
"color": "#00FF00"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
Creates a red-white-green color scale where the minimum value is red, the nominal value (eg. a target value) of 50 is white and maximum value is green.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": { "aggregate": "min" },<br />
"color": "#EF5254"<br />
},<br />
{<br />
"value": 50,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
Adds an icon left of the value (icon sentiment_satisfied_alt if value is over 100 and otherwise sentiment_very_dissatisfied). Also icons have different colors.<br />
<pre><br />
{<br />
"icon": {<br />
"rules": [<br />
{<br />
"icon": "sentiment_satisfied_alt",<br />
"value": 100,<br />
"comparison": ">"<br />
}<br />
],<br />
"icon": "sentiment_very_dissatisfied",<br />
"color": {<br />
"rules": [<br />
{<br />
"color": "#36d475",<br />
"value": 100,<br />
"comparison": ">"<br />
},<br />
{<br />
"color": "#EF5254"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=17037Getting Started with QPR ProcessAnalyzer2020-10-19T14:59:03Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Flowchart Analysis]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Process Discovery Chart tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
==== Exercises ====<br />
*[https://qpr-my.sharepoint.com/:b:/p/lassi_uusitalo/EadmyqBQqKtLjef6ALdxu3UBunI5y3fXBa8zR8IoDv8bmQ?e=FE3Nl9 Process Discovery Exercises]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
**Presets<br />
**General settings<br />
**Measure settings<br />
**Dimension settings<br />
**Duplicating charts<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
**Creating dashboards<br />
**Dashboard management views<br />
**Dashboard duplication<br />
**How to use dashboard links<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
==== Exercises ====<br />
*[https://qpr-my.sharepoint.com/:b:/p/lassi_uusitalo/EXD4_HFY525EhNtEY7wF1LgBbZlIz0U3CUlnHLeqqN8txg?e=kEgO1e Dashboard Exercises]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=17036Getting Started with QPR ProcessAnalyzer2020-10-19T13:55:40Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Flowchart Analysis]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Process Discovery Chart tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
==== Exercises ====<br />
*[https://qpr-my.sharepoint.com/:b:/p/lassi_uusitalo/EadmyqBQqKtLjef6ALdxu3UBunI5y3fXBa8zR8IoDv8bmQ?e=FE3Nl9 Process Discovery Exercises]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
**Presets<br />
**General settings<br />
**Measure settings<br />
**Dimension settings<br />
**Duplicating charts<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
**Creating dashboards<br />
**Dashboard management views<br />
**Dashboard duplication<br />
**How to use dashboard links<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16988Getting Started with QPR ProcessAnalyzer2020-10-12T14:55:44Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Flowchart Analysis]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Process Discovery Chart tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
**Presets<br />
**General settings<br />
**Measure settings<br />
**Dimension settings<br />
**Duplicating charts<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
**Creating dashboards<br />
**Dashboard management views<br />
**Dashboard duplication<br />
**How to use dashboard links<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16987Getting Started with QPR ProcessAnalyzer2020-10-12T14:47:27Z<p>Lasuusi: /* Chart settings */</p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
**Presets<br />
**General settings<br />
**Measure settings<br />
**Dimension settings<br />
**Duplicating charts<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
**Creating dashboards<br />
**Dashboard management views<br />
**Dashboard duplication<br />
**How to use dashboard links<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16986Getting Started with QPR ProcessAnalyzer2020-10-12T14:39:59Z<p>Lasuusi: /* Designing Dashboards */</p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
**Creating dashboards<br />
**Dashboard management views<br />
**Dashboard duplication<br />
**How to use dashboard links<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16985Getting Started with QPR ProcessAnalyzer2020-10-12T14:38:56Z<p>Lasuusi: /* Filtering */</p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
**Creating filters<br />
**Saving filters<br />
**Chart specific filters<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
<br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16984Getting Started with QPR ProcessAnalyzer2020-10-12T14:34:30Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=HJ6e_LeiZO0 Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16983Getting Started with QPR ProcessAnalyzer2020-10-12T14:19:22Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=KovhqaVv5to Introduction video to dashboard creation]<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=XrFtLHCab7o Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16979Getting Started with QPR ProcessAnalyzer2020-10-12T10:03:36Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[https://www.youtube.com/watch?v=fwW207eCjFM Introduction video to dashboard creation]<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[https://www.youtube.com/watch?v=XrFtLHCab7o Instruction video to Data Import]<br />
*[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings Custom date and time format strings]<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=16976Filtering in QPR ProcessAnalyzer2020-10-07T11:02:15Z<p>Lasuusi: /* Turning off Filter Rules */</p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removing them.<br />
<br />
[[File:Filterruledisableing.png]]<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16917Getting Started with QPR ProcessAnalyzer2020-10-01T13:52:12Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
*[[Model Creation in QPR ProcessAnalyzer]]<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Model_Creation_in_QPR_ProcessAnalyzer&diff=16912Model Creation in QPR ProcessAnalyzer2020-10-01T12:45:05Z<p>Lasuusi: </p>
<hr />
<div>== Model Creation ==<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16911QPR ProcessAnalyzer Chart2020-10-01T11:06:44Z<p>Lasuusi: /* Linked settings */</p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|500px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
=== On-screen Settings ===<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
=== Custom Layout ===<br />
Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
<br />
=== Variable mappings ===<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
* '''variable''': Name of the bound dashboard variable.<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter to bind to.<br />
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
=== Linked settings ===<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
* '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter.<br />
* '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
<br />
=== Go to Query Designer ===<br />
For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16910QPR ProcessAnalyzer Chart2020-10-01T11:06:23Z<p>Lasuusi: /* Variable mappings */</p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|500px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
=== On-screen Settings ===<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
=== Custom Layout ===<br />
Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
<br />
=== Variable mappings ===<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
* '''variable''': Name of the bound dashboard variable.<br />
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
* '''parameter''': Name of the chart setting or parameter to bind to.<br />
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
=== Linked settings ===<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
** '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter.<br />
** '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
=== Go to Query Designer ===<br />
For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16909QPR ProcessAnalyzer Chart2020-10-01T11:05:09Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|500px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
=== On-screen Settings ===<br />
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
* '''index''': Index of the measure, dimension or column starting from zero.<br />
* '''parameter''': Name of the parameter.<br />
* '''label''': Custom label for the setting.<br />
* '''maxWidth''': Maximum width of the shown setting in pixels.<br />
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
=== Custom Layout ===<br />
Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
<br />
=== Variable mappings ===<br />
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
** '''variable''': Name of the bound dashboard variable.<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
** '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter to bind to.<br />
** '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
** '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
** '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
<br />
=== Linked settings ===<br />
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
** '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter.<br />
** '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
=== Go to Query Designer ===<br />
For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Chart_Basics&diff=16831Chart Basics2020-09-24T12:32:13Z<p>Lasuusi: </p>
<hr />
<div>There are four ways to use Charts in QPR ProcessAnalyzer Process Discovery and Dashboards:<br />
*Using default analysis elements in Process Discovery<br />
*Using presets<br />
*Creating your own ChartView analysis elements<br />
*Creating custom KPIs with ExpressionLanguage<br />
<br />
= Default analysis elements in Process Discovery =<br />
In Process Discovery you can use the default analysis elements by browsing the header tabs on top of the ChartView. You can see more options by clicking on the left and right arrows. Each type of analysis is explained below.<br />
<br />
[[File:ProcessDiscoveryAnalysisView1.png|450px]]<br />
== Cases ==<br />
<br />
[[File:Tabs 1cases.png|600px]]<br />
<br />
Case analysis shows each individual case within the (filtered) dataset in their own rows:<br />
*'''Case ID:''' The individual identifier assigned to a case.<br />
*'''Case start:''' Time stamp of the first event of the case.<br />
*'''Case end:''' Time stamp of the last event of the case.<br />
*'''Case duration:''' End-to-end duration from the first event of the case to the last event of the case.<br />
*'''Latest event:''' Last event in the chain of events of the case.<br />
*'''Events:''' Count of event occurrences in the case.<br />
*'''Event types:''' Count of event types in the case.<br />
<br />
<br />
<br />
== Events ==<br />
<br />
[[File:Tabs 2events.png|600px]]<br />
<br />
Events analysis shows each individual event within the (filtered) dataset in their own rows:<br />
*'''Case ID:''' The individual identifier assigned to a case.<br />
*'''Event type:''' Name of the event.<br />
*'''Event time:''' Time stamp of the event.<br />
*'''Duration from case start:''' Duration between the event and the first event of the case.<br />
*'''Duration from previous event:''' Duration between the event and the event preceeding it.<br />
*'''Event order number:''' Sequence/index number of the event within the case.<br />
<br />
== Event Types ==<br />
<br />
[[File:Tabs 3eventtypes.png|600px]]<br />
<br />
Event types analysis shows each individual event type within the (filtered) dataset in their own rows with their respective aggregated information:<br />
*'''Event type:''' Name of the event.<br />
*'''Cases:''' Count of cases containing the event type.<br />
*'''Events occured:''' Event count of the event type in all (filtered) cases.<br />
*'''Incoming flows:''' Number of event types directly preceeding the event type within the selected cases.<br />
*'''Outgoing flows:''' Number of event types directly following the event type within the selected cases.<br />
*'''Events per case:''' Calculation rule: ''Events occurred / Cases''.<br />
<br />
== Case Attribute profiling ==<br />
<br />
[[File:Tabs 4caseattributes.png|600px]]<br />
<br />
Case Attribute profiling visualizes the break down of the case count according to Case Attribute values. You can choose different Case Attributes to analyze by toggling the dropdown menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.<br />
<br />
== Event Attribute Profiling ==<br />
<br />
[[File:Tabs 5eventattributes.png|600px]]<br />
<br />
Event Attribute profiling visualizes the break down of the event count according to Event Attribute values. You can choose different Event Attributes to analyze by toggling the dropdown menu. The Visualization defaults to bar chart which you can change from the "General" tab of the Chart Settings.<br />
== Case duration analysis ==<br />
<br />
[[File:Tabs 6caseduration.png|600px]]<br />
<br />
Case duration analysis breaks down the case count according to the duration of the cases within the (filtered) dataset. You can choose the granularity of the case durations from the dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.<br />
<br />
== Event duration analysis ==<br />
<br />
[[File:Tabs 7eventduration.png|600px]]<br />
<br />
Event duration analysis breaks down the flow duration between two selected events. You can choose the analysis target by either:<br />
*Selecting a flow from the flowchart.<br />
*Toggling the "Start" and "End" dropdown menus and selecting the desired events.<br />
<br />
You can choose the granularity of the event durations from the "Time unit" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.<br />
== Case counts ==<br />
<br />
[[File:Tabs 8casecounts.png|600px]]<br />
<br />
Case Counts analysis breaks down the Case Count based on the starting time of the (filtered) Cases in the data. You can choose the granularity of the time periods from the "Period" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.<br />
== Event counts ==<br />
[[File:Tabs 9eventcounts.png|600px]]<br />
<br />
Event Counts analysis breaks down the Event Count based on the starting time of the (filtered) Events in the data. You can choose the granularity of the time periods from the "Period" dropdown menu. The Visualization defaults to column chart which you can change from the "General" tab of the Chart Settings.<br />
== Variations ==<br />
[[File:Tabs 10variations.png|600px]]<br />
<br />
Variations analysis aggregates Case Counts of identical process flows and sorts them in a descending order of Case Count. When Events in case > Event types in case, there is rework and/or looping in the process.<br />
*'''Cases:''' Count of cases containing the specific process flow variation<br />
*'''Average duration:''' Average duration of the specific process flow variation<br />
*'''Events in case:''' Count of occurred events in the process flow variation<br />
*'''Event types in case:''' Count of event types in the process flow variation<br />
== Flows ==<br />
[[File:Tabs 11flows.png|600px]]<br />
<br />
Flows analysis aggregates all start event to end event flows and sorts them in a descending order of Average duration of the flows:<br />
*'''Start:''' Name of the start event of the flow.<br />
*'''End:''' Name of the end event of the flow.<br />
*'''Average duration:''' Average duration of the flow.<br />
*'''Median duration:''' Median duration of the flow.<br />
*'''Cases:''' Count of cases which contain the flow.<br />
*'''Occurrences:''' Count of flow occurrences.<br />
*'''Looping:''' Looping percentage (repetition per case count). Calculation rule: ''(Occurrences / Cases - 1) * 100''.<br />
*'''St.dev.:''' Standard deviation of the duration of the flow.<br />
== Root causes ==<br />
[[File:Tabs 12rootcauses2.png|600px]]<br />
<br />
The idea of Root-cause analysis is to see whether some Subsets of data (=Case Attributes) correlate with any selected process behavior. Moreover, to provide insights where to focus business initiatives to maximize or minimize the selected process behavior.<br />
<br />
'''For example:''' Order Price Change ratio is on average 17%. Is it 17% through all the case attributes such as Purchasing Country or is the Order Price Change ratio potentially 2% in Country X and 9% in Country Z. -> Best practices from Country X to be rolled into Country Z operations.<br />
<br />
* '''Header:''' Average of the analyzed feature in whole data model. Used as a benchmark for all the data subsets e.g. dimensioning with all case attribute values and seeing whether there are any subsets of data which have a higher or lower average. <br />
* '''2nd Column:''' Subset of data: Case Attribute + Concerned Case Attribute value e.g. Case Attribute: SO: Customer Country: United Kingdom<br />
* '''3rd Column:''' Case count within the Subset of data (see column #2), 24 700 cases<br />
* '''4th Column:''' Percentage of the cases having the analyzed feature in the concerned subset of data e.g. Case Attribute Value SO: Customer country: United Kingdom has 7.8% of orders having the analyzed features (Order Price Changes). Note. Clearly lower than global average 17%.<br />
* '''1st Column:''' Because the subset of data (e.g. concerned case attribute value for example SO: Customer country: United Kingdom) has a lower or a higher percentage of cases having the concerned feature compared to global average, it is responsible for X% of the whole featured effect. In other words, how many cases too many/too little there are in this Data subset compared to global average. Finally, this number of cases is divided by the total number of cases having the analyzed feature to make it a “contribution percentage”. This means that global average is now 15% lower than it would be if United Kingdom was on a global average level 17% (contracts to 7.8% what it currently has).<br />
<br />
== Clustering ==<br />
[[File:Tabs 13clustering.png|600px]]<br />
<br />
* '''Feature''' and '''Value''': These two columns list the case attribute and other values that are common to the cases in the cluster.<br />
* '''Cluster Density %''': Share of cases having this feature value within the cluster (i.e. the number of cases having the value shown on the row in this particular cluster divided by the number of cases in the cluster * 100).<br />
* '''Total Density %''': Share of cases having this feature value in the whole data set (i.e. the total number of cases having the value shown on the row divided by the total number of cases * 100).<br />
* '''Contribution %''': Amount of cases that can be explained to belong to this cluster because of this feature value. The scale is such that 0% means that the feature value isn't specific to this cluster and 100% means that all cases belonging to this cluster can be explained by this feature value.<br />
<br />
= Using presets =<br />
[[File:ProcessDiscoveryAnalysisView2.png|right|450px]]You can expand your selection of analyses to 50+ pre-made presets. To open the presets you need to:<br />
*Click on the ChartView area<br />
*Click on the cog on the top-right corner to open the Chart Settings<br />
*Select you preferred analysis from the use cases in the "Presets" tab<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
= Creating your own ChartView analysis elements =<br />
To create your own customized analysis views you can toggle the values directly in Chart Settings. Most of the time you can understand "Dimensions" as the X-axis of the chart and "Measures" as the Y-axis of the chart. To get started please see [[QPR ProcessAnalyzer Chart]] or reach out to QPR staff for advice. In order to avoid any unexpected errors it is adviced to start from a blank ChartView by clicking "Create New" under the "Presets" tab.<br />
= Creating custom KPIs with ExpressionLanguage =<br />
For more complicated calculations which cannot be done with standard configuration options you need to use ExpressionLanguage code. ExpressionLanguage is a JSON based QPR language that is used for building KPIs in QPR ProcessAnalyzer. To get started please see [[QPR ProcessAnalyzer Expressions]] or reach out to QPR staff for advice.</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16828Getting Started with QPR ProcessAnalyzer2020-09-23T09:11:57Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[https://www.youtube.com/watch?v=zbQVZ1gtGGM Introduction video to chart settings]<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Filtering_in_QPR_ProcessAnalyzer&diff=16822Filtering in QPR ProcessAnalyzer2020-09-21T11:25:05Z<p>Lasuusi: </p>
<hr />
<div>'''Filters''' define a subset of cases and events in the process analysis model. This subset of data is used for all analysis. A filter consist of a list of '''filter rules''', which are applied in the defined order. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (AND type of logic, instead of OR logic).<br />
<br />
== Saving filters ==<br />
You can save your filter selection by hovering your mouse over the filter dropdown menu (without clicking) and choosing "Save new filter" from below.<br />
<br />
[[File:Savingfilters.png]]<br />
<br />
<br />
This will propmt a pop-up window where you can name your filter and confirm your selection by clicking "Save". You can also define whether to set the filter to be published only to you (Private), everybody (Public), or if the filter is the default filter for the model (Default Public).<br />
<br />
[[File:Filterprivacymode.png|500px]]<br />
<br />
== Turning off Filter Rules ==<br />
It's possible to turn off (disable) individual filter rules in a filter. When a filter rule is turned off, it's not applied, i.e. it doesn't have any effect on the calculation. The turned off filter rule is still preserved as part of the filter, and it's thus easy to turn the filter rule on again. This way, filter rules can be toggled on and off without removed them.<br />
<br />
== Operations in Filter Properties ==<br />
Clicking the '''Export...''' button gives you the option of exporting the filter to a '''.pacm''' file or the events to an Excel sheet. Note that when exporting a filter, only visible cases, events and attributes are included in the destination. That is, if the filter has any filter rules, then only cases, events and attributes visible for that filter will be exported.<br />
<br />
Clicking the '''Save As New Model''' button will save the filtered data as a new model. Only the filtered cases, events and attributes are included to the new model.<br />
<br />
== Filter Rule Types ==<br />
Following filter rule types are available:<br />
* '''Include/exclude cases based on case attribute values''': For example, include only those cases where case attribute "Account Manager" is "Patricia White" or "Mary Wilson".<br />
* '''Include/exclude cases having certain event type(s)''': For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).<br />
* '''Include/exclude cases having certain flow(s)''': For example, include cases that have a flow from "Outbound Delivery" to "Handling unit". To match, there must not be other events between those two events.<br />
* '''Include/exclude cases based on case duration''': For example, include cases the case duration is over 50 days. Case duration is the last event timestamp minus the first event timestamp.<br />
* '''Include/exclude cases based on flow duration''': For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.<br />
* '''Include/exclude cases belonging to certain variation(s) (sequence of events)''': For example, include cases belonging to variation "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude cases having certain event attribute value(s)''': For example, include cases having event(s) with event attribute "Organization" is "Finance".<br />
* '''Include/exclude cases having certain part of variation''': For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".<br />
* '''Include/exclude event types''': For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".<br />
<br />
There are two kinds of filter rules: case filter rules and event type filter rule. Case filter rules filter out cases, and the number of cases decreases. The event type filters filter out events, so the number of cases doesn't decrease but the process flow in individual cases may change as event types are left out. Note that event type filter rules may filter out all events of a case, which results in cases that don't have events at all. It's not possible to show those cases in flowcharts or calculated durations for them.<br />
<br />
A case has a '''Flow''' between events A and B means that the case has both events A and B and there are no other events between them. A case may have the same flow multiple times. '''Flow duration''' is the event B timestamp minus A timestamp. Note also that flows always has a direction: flow from A to B is different than flow from B to A.<br />
<br />
'''Variation''' means a sequence of events that a case goes through. A case always belongs to a certain variation. If another case has different events or they are in different order, the case belongs to a different variation. Duration between events doesn't matter in terms of which variation a case belongs.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Savingfilters.png&diff=16820File:Savingfilters.png2020-09-21T11:17:12Z<p>Lasuusi: </p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Model_Creation_in_QPR_ProcessAnalyzer&diff=16819Model Creation in QPR ProcessAnalyzer2020-09-21T08:41:31Z<p>Lasuusi: </p>
<hr />
<div>== Model Creation ==<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
<br />
== Data Import via QPR ProcessAnalyzer UI ==<br />
Typical scenario for using<br />
<br />
An organization has some ETL platform (potentially with access to multiple IT system / data lakes) in use which provides CSV file as output<br />
<br />
*Employee uploads CSV files via web browser to QPR ProcessAnalyzer<br />
*New process mining model is created in couple of minutes!<br />
*Limitations:<br />
**CSV data must be in the Process Mining data format as no data editor available<br />
**CSV size max. 230mb<br />
<br />
[[File:ImportingdatatoQPRProcessAnalyzer1.png]]<br />
<br />
== QPR ProcessAnalyzer MS Excel add-on ==<br />
Typical scenario for using<br />
<br />
QPR ProcessAnalyzer user has MS Excel add-on installed and wishes to do some data manipulation with MS Excel standard functionality<br />
<br />
Guided wizard to help user on the steps to create new model<br />
<br />
New process mining model is created in a couple of minutes<br />
<br />
No SQL knowhow needed and easy data transformation/manipulation<br />
<br />
Limitations:<br />
<br />
CSV data must be in the Process Mining data format<br />
<br />
== QPR Integration platform ==<br />
Typical scenario for using<br />
<br />
An organization would like to dynamically connect with IT systems to schedule frequent data queries<br />
<br />
Developer uses QPR’s readily available standard connectors to query data from IT system & create process mining model<br />
<br />
The standard connectors may to customized fully for the specific needs e.g. new case attributes or process steps <br />
<br />
<br />
<br />
Limitations:<br />
<br />
No limits regarding data format or size<br />
<br />
Requires SQL knowledge<br />
<br />
== Direct ODBC connection to database ==<br />
Typical scenario for using<br />
<br />
An organization has S/4 Hana (or similar) advanced data repository with very high computing power <br />
<br />
Developer uses QPR’s readily available standard connectors to query data from IT system<br />
<br />
The standard connectors may to customized fully for the specific needs e.g. new case attributes or process steps <br />
<br />
Always up-to-date process mining model and no separate scheduling required because data is retrieved from the source system once the model is opened from QPR ProcessAnalyzer<br />
<br />
<br />
<br />
Limitations:<br />
<br />
All the data must be queried with single ODBC query. This means that a single query might be extremely long and complex to be managed.<br />
<br />
Requires SQL knowledge<br />
Max 1 million rows (Excel constraint)<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Model_Creation_in_QPR_ProcessAnalyzer&diff=16818Model Creation in QPR ProcessAnalyzer2020-09-21T08:40:59Z<p>Lasuusi: Created page with "== Model Creation == In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following informati..."</p>
<hr />
<div>== Model Creation ==<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
<br />
== Data Import via QPR ProcessAnalyzer UI ==<br />
Typical scenario for using<br />
<br />
An organization has some ETL platform (potentially with access to multiple IT system / data lakes) in use which provides CSV file as output<br />
<br />
*Employee uploads CSV files via web browser to QPR ProcessAnalyzer<br />
*New process mining model is created in couple of minutes!<br />
*Limitations:<br />
**CSV data must be in the Process Mining data format as no data editor available<br />
**CSV size max. 230mb<br />
<br />
[[File:ImportingdatatoQPRProcessAnalyzer1.png]]<br />
<br />
== QPR ProcessAnalyzer MS Excel add-on ==<br />
Typical scenario for using<br />
<br />
QPR ProcessAnalyzer user has MS Excel add-on installed and wishes to do some data manipulation with MS Excel standard functionality<br />
<br />
Guided wizard to help user on the steps to create new model<br />
<br />
New process mining model is created in a couple of minutes<br />
<br />
No SQL knowhow needed and easy data transformation/manipulation<br />
<br />
Limitations:<br />
<br />
CSV data must be in the Process Mining data format<br />
<br />
== QPR Integration platform ==<br />
Typical scenario for using<br />
<br />
An organization would like to dynamically connect with IT systems to schedule frequent data queries<br />
<br />
Developer uses QPR’s readily available standard connectors to query data from IT system & create process mining model<br />
<br />
The standard connectors may to customized fully for the specific needs e.g. new case attributes or process steps <br />
<br />
<br />
<br />
Limitations:<br />
<br />
No limits regarding data format or size<br />
<br />
Requires SQL knowledge<br />
<br />
== Direct ODBC connection to database ==<br />
Typical scenario for using<br />
<br />
An organization has S/4 Hana (or similar) advanced data repository with very high computing power <br />
<br />
Developer uses QPR’s readily available standard connectors to query data from IT system<br />
<br />
The standard connectors may to customized fully for the specific needs e.g. new case attributes or process steps <br />
<br />
Always up-to-date process mining model and no separate scheduling required because data is retrieved from the source system once the model is opened from QPR ProcessAnalyzer<br />
<br />
<br />
<br />
Limitations:<br />
<br />
All the data must be queried with single ODBC query. This means that a single query might be extremely long and complex to be managed.<br />
<br />
Requires SQL knowledge<br />
Max 1 million rows (Excel constraint)</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16811QPR ProcessAnalyzer Chart2020-09-18T09:48:49Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
Example:<br />
[[File:Advancedsortingexample.png|center|500px]]<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"direction": "descending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"direction": "ascending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
* '''On-screen Settings''': Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
** '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
** '''index''': Index of the measure, dimension or column starting from zero.<br />
** '''parameter''': Name of the parameter.<br />
** '''label''': Custom label for the setting.<br />
** '''maxWidth''': Maximum width of the shown setting in pixels.<br />
** '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
** '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
** '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
** '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
** '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
** '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
** '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
** '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
** '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
** '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
** '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center|850px]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
* '''Custom Layout''': Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
* '''Variable mappings''': Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
** '''variable''': Name of the bound dashboard variable.<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
** '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter to bind to.<br />
** '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
** '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
** '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
* '''Linked settings''': Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
** '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter.<br />
** '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
* '''Go to Query Designer''': For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Advancedsortingexample.png&diff=16810File:Advancedsortingexample.png2020-09-18T09:41:12Z<p>Lasuusi: </p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16808Getting Started with QPR ProcessAnalyzer2020-09-17T11:38:23Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters and discover insights hidden in the data. The basics of filtering in QPR ProcessAnalyzer are explained in the first 5 minutes of the video linked below. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16807Getting Started with QPR ProcessAnalyzer2020-09-17T11:21:46Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
[https://www.youtube.com/watch?v=0G0bRh8P8yI Here you can find the 4 minute instruction video for how to find your way around QPR ProcessAnalyzer when logging in for the first time]. To start familiarizing yourself with QPR ProcessAnalyzer it is recommended to have a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). Feel free to experiment with different filters (see the related video) and discover insights hidden in the data. To support your learning journey we have made the following resources publicly available for self-study.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16801QPR ProcessAnalyzer Chart2020-09-17T06:45:13Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object (see an example below):<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 2,<br />
"direction": "ascending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"direction": "descending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
* '''On-screen Settings''': Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
** '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
** '''index''': Index of the measure, dimension or column starting from zero.<br />
** '''parameter''': Name of the parameter.<br />
** '''label''': Custom label for the setting.<br />
** '''maxWidth''': Maximum width of the shown setting in pixels.<br />
** '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
** '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
** '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
** '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
** '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
** '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
** '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
** '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
** '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
** '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
** '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
Example:<br />
<br />
[[File:Onscreensettingsexample.png|center]]<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
* '''Custom Layout''': Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
* '''Variable mappings''': Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
** '''variable''': Name of the bound dashboard variable.<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
** '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter to bind to.<br />
** '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
** '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
** '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
* '''Linked settings''': Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
** '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter.<br />
** '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
* '''Go to Query Designer''': For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Onscreensettingsexample.png&diff=16800File:Onscreensettingsexample.png2020-09-17T06:38:13Z<p>Lasuusi: </p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Chart&diff=16784QPR ProcessAnalyzer Chart2020-09-14T11:07:46Z<p>Lasuusi: </p>
<hr />
<div>Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.<br />
<br />
== Introduction ==<br />
Chart is available as the first item in the tool palette which can be seen when editing is started.<br />
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.<br />
<br />
The basic flow of using the chart is the following:<br />
# Choose objects to visualize, e.g. cases, events, event types or variations.<br />
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).<br />
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.<br />
# Choose the best visualization for the data, such as column charts, donut charts or tables.<br />
<br />
Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.<br />
<br />
Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.<br />
<br />
== Data Selection Settings ==<br />
When creating a chart, the first thing to decide, are which items to be analyze.<br />
<br />
Settings that determine which data is <br />
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.<br />
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.<br />
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object (see an example below):<br />
** '''type''': either '''measure''' or '''dimension'''<br />
** '''index''': measure or dimension order number (starts from 0)<br />
** '''direction''': Either '''ascending''' or '''descending'''<br />
<br />
<pre><br />
[<br />
{<br />
"type": "measure",<br />
"index": 2,<br />
"direction": "ascending"<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"direction": "descending"<br />
}<br />
]<br />
</pre><br />
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.<br />
<br />
== Visualization Settings ==<br />
[[File:Chartsettingsgeneral.png|right]]<br />
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.<br />
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.<br />
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.<br />
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.<br />
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.<br />
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.<br />
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.<br />
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Available Visualizations ==<br />
Chart provides variety of visualization. Here are mentioned some of those:<br />
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.<br />
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.<br />
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.<br />
* '''[[QPR ProcessAnalyzer Graphs|Area Range Chart, Area Spline Range Chart, Column Range Chart, Error Bar Chart]]''': These chart types use ''low'' and ''high'' mappings.<br />
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.<br />
* '''Case Attribute Filter''': Instead of visualizing, the chart works as a case attribute value selector for filtering. When choosing this setting, also a case attribute needs to be selected. There is a dropdown list showing all case attribute values and multiple values can be selected. This filtering functionality is linked to the dashboard filters, and the same filter can be edited both in this chart and in the header.<br />
<br />
== Measures, Dimensions and Columns ==<br />
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).<br />
<br />
When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.<br />
<br />
When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.<br />
<br />
When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.<br />
<br />
Each measure, dimension and column contain the following buttons when hovering:<br />
* '''Measure/dimension/column detailed settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).<br />
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.<br />
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).<br />
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).<br />
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.<br />
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.<br />
<br />
<br />
== Measure, Dimension and Column Specific Settings ==<br />
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:<br />
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.<br />
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.<br />
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.<br />
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.<br />
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.<br />
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.<br />
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.<br />
* '''Date format''': Date type of data is presented with this date format. <br />
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.<br />
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:<br />
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.<br />
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.<br />
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.<br />
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.<br />
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.<br />
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.<br />
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.<br />
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.<br />
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.<br />
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.<br />
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.<br />
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.<br />
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.<br />
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.<br />
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.<br />
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.<br />
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.<br />
** '''Add by''': Adds the specified number to all the measure/dimension/column values.<br />
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.<br />
** '''Divide by''': Divides all measure/dimension/column values by the specified number.<br />
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.<br />
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.<br />
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.<br />
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.<br />
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.<br />
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example: <br />
<pre><br />
"colorMappings": {<br />
"Robert Miller": "#36d475",<br />
"Patricia White": "#ef5254",<br />
"Mary Wilson": "#b9bdc1"<br />
}<br />
</pre><br />
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.<br />
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.<br />
<br />
In addtion, measures have the following settings:<br />
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.<br />
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.<br />
<br />
== Filtering Settings ==<br />
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:<br />
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.<br />
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.<br />
<br />
Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:<br />
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.<br />
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.<br />
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.<br />
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.<br />
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.<br />
<br />
Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.<br />
<br />
<br />
<br />
== Visualize KPI Targets with Colors==<br />
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).<br />
<br />
Target values can be shown in the charts as follows:<br />
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)<br />
# Select your KPI as the first measure.<br />
# For the measure, select ''Variable for other measures'' in the measure settings.<br />
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.<br />
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.<br />
# When using charts, usually a dimension is selected as well.<br />
<br />
Now the KPI targets are visualized as colored columns.<br />
<br />
== Advanced Settings ==<br />
[[File:Chartsettingsadvancedsettings.png|right]]<br />
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.<br />
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.<br />
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.<br />
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.<br />
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.<br />
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.<br />
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).<br />
* '''On-screen Settings''': Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:<br />
** '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions. <br />
** '''index''': Index of the measure, dimension or column starting from zero.<br />
** '''parameter''': Name of the parameter.<br />
** '''label''': Custom label for the setting.<br />
** '''maxWidth''': Maximum width of the shown setting in pixels.<br />
** '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.<br />
** '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.<br />
** '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.<br />
** '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.<br />
** '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.<br />
** '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.<br />
** '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).<br />
** '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.<br />
** '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.<br />
** '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.<br />
** '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.<br />
Example:<br />
<pre><br />
[<br />
{<br />
"type": "dimension",<br />
"index": 0,<br />
"parameter": "Attribute",<br />
"maxWidth": 500<br />
},<br />
{<br />
"type": "dimension",<br />
"index": 1,<br />
"parameter": "Period",<br />
"label": "Time"<br />
}<br />
]<br />
</pre><br />
* '''Custom Layout''': Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].<br />
* '''Variable mappings''': Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:<br />
** '''variable''': Name of the bound dashboard variable.<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).<br />
** '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter to bind to.<br />
** '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.<br />
** '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.<br />
** '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.<br />
<pre><br />
[<br />
{<br />
"variable": "CaseAttributeVariable",<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Attribute"<br />
},<br />
{<br />
"variable": "EventTypes",<br />
"type": "filter",<br />
"filterType": "IncludeEventTypes",<br />
"ruleType": "EventType"<br />
}<br />
]<br />
</pre><br />
* '''Linked settings''': Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:<br />
** '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.<br />
** '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).<br />
** '''parameter''': Name of the chart setting or parameter.<br />
** '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.<br />
<pre><br />
[<br />
[<br />
{<br />
"type": "measure",<br />
"index": 0,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "measure",<br />
"index": 1,<br />
"parameter": "Period"<br />
},<br />
{<br />
"type": "tag",<br />
"tagName": "AutomationAttribute"<br />
}<br />
]<br />
]<br />
</pre><br />
* '''Go to Query Designer''': For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.<br />
<br />
== Show Technical Information ==<br />
In the ''Advanced'' tab, there is a dropdown list on the bottom for showing different kind of technical information for advanced usage:<br />
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.<br />
* '''Expressions''': This option shows expressions that are processed by the server to produce the information shown in the chart. Expression syntax is described in the [[QPR_ProcessAnalyzer_Expression_Analysis|Expression Analysis]].<br />
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.<br />
* '''Query as key-value pairs''': This option shows the entire query that is sent to the server for calculation as a key-value pairs. This format is the one that the http request of the API uses.<br />
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.<br />
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].<br />
* '''Visualization component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.<br />
* '''Visualization component settings (with data)''': This is similar option as the previous, except the data is also included.<br />
<br />
== Copy Chart Settings from Another Chart ==<br />
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.<br />
<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16778Getting Started with QPR ProcessAnalyzer2020-09-10T12:51:44Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
If you are new to QPR ProcessAnalyzer, the easiest way to get started is by having a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). You can find your project specific dashboards by clicking "Home" on the top-left corner. This will display a drop-down menu with a list of pre-made dashboards you can choose from. To support your further learning you can use the following resources to learn about the main themes of using the QPR ProcessAnalyzer.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16776Getting Started with QPR ProcessAnalyzer2020-09-10T11:53:05Z<p>Lasuusi: </p>
<hr />
<div>== Getting started ==<br />
If you are new to QPR ProcessAnalyzer, the easiest way to get started is by having a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). You can find your project specific dashboards by clicking "Home" on the top-left corner. This will display a drop-down menu with a list of pre-made dashboards you can choose from. To support your further learning you can use the following resources to learn about the main themes of using the QPR ProcessAnalyzer.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16774Getting Started with QPR ProcessAnalyzer2020-09-09T13:37:06Z<p>Lasuusi: </p>
<hr />
<div>== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
== Getting started ==<br />
If you are new to QPR ProcessAnalyzer, the easiest way to get started is by having a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). You can find your project specific dashboards by clicking "Home" on the top-left corner. This will display a drop-down menu with a list of pre-made dashboards you can choose from. To support your further learning you can use the following resources to learn about the main themes of using the QPR ProcessAnalyzer.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Getting_Started_with_QPR_ProcessAnalyzer&diff=16773Getting Started with QPR ProcessAnalyzer2020-09-09T12:57:08Z<p>Lasuusi: </p>
<hr />
<div>== Logging in ==<br />
1. Open your web browser (Google Chrome and Mozilla Firefox are the preferred options)<br />
<br />
2. Go to https://[yourdomain].onqpr.com/ or https://processanalyzer.onqpr.com/<br />
<br />
3. Log in using the credentials QPR has provided to you in your e-mail.<br />
== Navigating in QPR ProcessAnalyzer ==<br />
[[File:QPRPAfrontpage.png|600px|right|QPR ProcessAnalyzer frontpage]]After a successful log-in you are presented with the following options:<br />
<br />
*Process Discovery<br />
*[[Conformance Analysis|Conformance Checking]]<br />
*[[Clustering Analysis]]<br />
*[[Enhanced BPMN]]<br />
*[[Importing_Data_to_QPR_ProcessAnalyzer|Data Import]]<br />
*[[QPR ProcessAnalyzer Features Overview#Model_Manager|Model Manager]]<br />
*[[QPR ProcessAnalyzer Project Workspace|Project Workspace]]<br />
<br />
<br />
[[File:QPRPAnavigationmenu.png|200px|right|QPR ProcessAnalyzer navigation menu]]You can navigate in QPR ProcessAnalyzer by either clicking the respective elements on the frontpage or by clicking on the navigation menu on the top left. When choosing the navigation menu you will see the following elements:<br />
<br />
1. Navigation menu drop-down<br />
<br />
2. Existing dashboards within the active project<br />
<br />
3. QPR ProcessAnalyzer elements<br />
<br />
4. Projects and Models<br />
<br />
5. Link to Workspace<br />
<br />
<br />
<br />
<br />
<br />
== Getting started ==<br />
If you are new to QPR ProcessAnalyzer, the easiest way to get started is by having a look at the pre-made dashboards created by the QPR staff for pre-existing applications, eg. Purchase-to-Pay (PtP). You can find your project specific dashboards by clicking "Home" on the top-left corner. This will display a drop-down menu with a list of pre-made dashboards you can choose from. To support your further learning you can use the following resources to learn about the main themes of using the QPR ProcessAnalyzer.<br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Process Discovery ===<br />
==== Flowchart ====<br />
*[https://www.youtube.com/watch?v=lIid7z0qYdw Instruction video for using the Flowchart]<br />
*[[Flowchart_Analysis|Process Flowchart]]<br />
==== Chart ====<br />
*[[Chart_Basics#Default_analysis_elements_in_Process_Discovery|Tabs]]<br />
*[[Chart_Basics#Using_presets|Presets]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Filtering ===<br />
*[https://www.youtube.com/watch?v=gf81AKwC9eI Instruction video for filtering]<br />
*[[Filtering_in_QPR_ProcessAnalyzer|Using Filters]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Chart settings ===<br />
*[[QPR ProcessAnalyzer Chart]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Designing Dashboards ===<br />
*[[QPR ProcessAnalyzer Dashboard Designer]]<br />
</div><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Conformance Analysis ===<br />
*[https://www.youtube.com/watch?v=g304TNwtGlc Instruction video for Conformance Analysis]<br />
*[https://www.youtube.com/watch?v=mpxzHM-fQQU How to automatically create a design model for Conformance Analysis]<br />
*[[Conformance Analysis]]<br />
</div><br />
</div><br />
<div style="display: flex;flex-wrap: wrap;"><br />
<div style="flex: 1 0 270px;border:1px solid #dfdfdf;padding:0 1em 1em 1.5em;background-color:#F7FAFC;margin:10px 0px 0px 10px;"><br />
=== Model Creation ===<br />
In order to create functioning data models for Process Mining the minimum requirement is that you have an event log which contains the following information:<br />
*Case ID - An unique identifier which connects the series of events together, eg. Purchase Order number, invoice number etc.<br />
*Event name - The name of different process steps, eg. Delivery: Goods Issue, Invoice Receipt, SO Item Created etc.<br />
*Timestamp - A registered time of the occurrence of an event<br />
*Attributes - Any additional information attached to a Case ID, eg. Company Code, Customer information, Order status information etc. Attributes are not mandatory for creating functioning models but the more attributes there are in the model the higher quality analysis can be done.<br />
<br />
Based on this information QPR ProcessAnalyzer creates a flowchart which with combination of other available tools lays the foundation for the start of Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are [[Importing_Data_to_QPR_ProcessAnalyzer|using the webUI to import data]] and more advanced techniques such as SQL [[QPR_ProcessAnalyzer_Model_Datasources|to import data directly from various data sources]].<br />
</div><br />
</div><br />
==Changing your password==<br />
[[File:passwordchange.png|200px|right|Changing your password]]<br />
To change your password do the following:<br />
<br />
1. Click '''Home'''<br />
<br />
2. Scroll down and choose '''User Account'''<br />
<br />
3. Enter your current password<br />
<br />
4. Enter your new password<br />
<br />
5. Confirm your new password<br />
<br />
6. Click '''Change Password'''</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Clustering_Analysis&diff=16772Clustering Analysis2020-09-09T12:51:22Z<p>Lasuusi: </p>
<hr />
<div>The Clustering Analysis view groups cases in the model in a way that the cases inside a group are similar to each other (e.g. cases have the same case attribute values are in the same group). Clustering is based on advanced Machine Learning and Artificial Intelligence algorithms. By default Clustering Analysis uses in-memory built-in kmodes algorithm with categorized values for Event Type occurrences and Case Attribute values. The algorithm does not guarantee convergence to the global optimum which means that subsequent Clustering Analysis runs may result in slightly different clustering results. See this [https://en.wikipedia.org/wiki/Cluster_analysis Wikipedia article] for more about the idea behind clustering.<br />
<br />
You can use the Clustering Analysis View, for example, to check data integrity. That is, the Clustering Analysis might reveal that the model actually contains data from two different processes.<br />
<br />
<br />
[[File:Clusteringanalysis.png|800px]]<br />
<br />
== Left Panel ==<br />
You can use the left panel to filter cases. Note that you are not bound to using just the Flowchart analysis, as you can change the analysis by right-clicking the analysis and selecting a different type of analysis shown on the panel.<br />
<br />
== Right Panel ==<br />
The right panel contains the clustering analysis. The table shows the clusters, how many cases are in each cluster, and the following details for each cluster:<br />
* '''Feature''' and '''Value''': These two columns list the case attribute and other values that are common to the cases in the cluster.<br />
* '''Cluster Density %''': Share of cases having this feature value within the cluster (i.e. the number of cases having the value shown on the row in this particular cluster divided by the number of cases in the cluster * 100).<br />
* '''Total Density %''': Share of cases having this feature value in the whole data set (i.e. the total number of cases having the value shown on the row divided by the total number of cases * 100).<br />
* '''Contribution %''': Amount of cases that can be explained to belong to this cluster because of this feature value. The scale is such that 0% means that the feature value isn't specific to this cluster and 100% means that all cases belonging to this cluster can be explained by this feature value.<br />
<br />
[[Category: QPR ProcessAnalyzer]]</div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=File:Clusteringanalysis.png&diff=16771File:Clusteringanalysis.png2020-09-09T12:49:30Z<p>Lasuusi: </p>
<hr />
<div></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=QPR_ProcessAnalyzer_Table&diff=16769QPR ProcessAnalyzer Table2020-09-09T10:23:27Z<p>Lasuusi: </p>
<hr />
<div>Table conditional formatting can be used to define table cell background colors, text colors, colored icons and databar, where all depend on the data in the table.<br />
<br />
== Table Functionalities ==<br />
<br />
<br />
==Conditional Formatting==<br />
Conditional formatting is defined in the measure/dimension/column settings as a JSON object with following allowed properties:<br />
* '''backgroundColor'''<br />
** '''rules''': Rules are checked in the defined order and the first matching determines the color.<br />
*** '''color''': color to use when the rule matches.<br />
*** '''value''': Value to compare against.<br />
*** '''comparison''': One of the following: <, >, <=, >=, ==, !=<br />
** '''scale'''<br />
*** '''color''': Color that corresponds with the value.<br />
*** '''value''': Value that corresponds with the color.<br />
** '''color''': Fixed color that is used when no rules/scale is defined or there are no matching rules.<br />
* '''textColor''': Same settings can be used as in the backgroundColor.<br />
* '''databar'''<br />
** '''min''': Value that represents the databar minimum position (i.e. when databar is not visible).<br />
** '''max''': Value that represents the databar maximum position (i.e. databar fills the whole cell).<br />
** '''color''': Color of the databar. Default color is #4bc3ff.<br />
* '''icon'''<br />
** '''rules''': Similar syntax can be used as in the color rules, except instead of "color" there is "icon" attribute to define the icon. All Google Material Icons are available: https://material.io/resources/icons/.<br />
** '''color''': Color of the icon. Default color is #333333.<br />
<br />
Rule value property and scale minimum and maximum can be defined:<br />
* fixed value, e.g. 5<br />
* aggregate of the same column data, e.g. { "aggregate": "max" }<br />
* aggregate of another column data, e.g. { "type": "measure", "index": 1, "aggregate": "max" }<br />
* refer to a cell value in other column in the same row, e.g. {"type": "measure", "index": 1 }<br />
<br />
Available aggregations are: min, max, sum, average, median, first, last.<br />
<br />
===Templates===<br />
Below are listed the examples used in dashboards with their respective use cases and Conditional formatting expressions. The recommended colors and their color codes are as follows:<br />
<br />
* Green: #68DD8F (Positively correlating KPIs)<br />
* Red: #EF5254 (Negatively correlating KPIs)<br />
* Blue: #4BC3FF (Case/Event counts)<br />
* Dark blue: #0F55A5 (Automation)<br />
* Orange: #FEA88A (Durations)<br />
* Yellow: #FFD851 (Value/Cost)<br />
====Traffic lights====<br />
Use case: KPIs based on traffic light signaling<br />
<br />
[[File:Trafficlightconiditionalformatting.png|200px]]<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"rules": [<br />
{<br />
"color": "#EF5254",<br />
"value": 10,<br />
"comparison": ">="<br />
},<br />
{<br />
"color": "#FFD851",<br />
"value": 6.5,<br />
"comparison": ">="<br />
},<br />
{<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
====Green databar====<br />
Use case: KPIs where 100% is a desired value, eg. On-Time Delivery<br />
<br />
[[File:Greendatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
<br />
</pre><br />
====Red databar====<br />
Use case: KPIs where 0% is the desired value and you want to highlight the worst performers of this metric, eg. Material shortages<br />
<br />
[[File:Reddatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#EF5254"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
====Blue databar====<br />
Use cases: Case/event counts<br />
<br />
[[File:Bluedatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#4BC3FF"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
====Dark blue databar====<br />
Use case: Automation rate and similar metrics that scale 0-100%<br />
<br />
[[File:Darkbluedatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#7588C4"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
====Yellow databar====<br />
Usecase: Monetary KPIs such as cost/value<br />
<br />
[[File:Yellowdatabar.png|200px]]<br />
<pre><br />
{<br />
"databar": {<br />
"min": 0,<br />
"max": { "aggregate": "max" },<br />
"color": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre><br />
<br />
====Orange scale====<br />
Use case: Durations<br />
<br />
[[File:Orangescale.png|200px]]<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": {"aggregate": "max" },<br />
"color": "#fea88a"<br />
},<br />
{<br />
"value": {"aggregate": "min" },<br />
"color": "#FFFFFF"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
===Other examples===<br />
Background color is based on a color scale where column minimum value zero gets color #FFFFFF and maximum value #FFD851. Color is scaled linearly between these colors.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": 0,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
Similar to previous example, except minimum and maximum values come from another column (measure number 1).<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": { "type":"measure", "index": 1, "aggregate": "min" },<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "type":"measure", "index": 1, "aggregate": "max" },<br />
"color": "#FFD851"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
The following setting defines a fixed background color for a column.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"color": "#FFD851"<br />
}<br />
}<br />
</pre><br />
<br />
Background color code is taken from column measure 1 from the same row.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"color": { "type":"measure", "index": 1 }<br />
}<br />
}<br />
</pre><br />
Text color is #FF0000 if value is lower than 20, otherwise #00FF00.<br />
<pre><br />
{<br />
"textColor": {<br />
"rules": [<br />
{<br />
"color": "#FF0000",<br />
"value": 20,<br />
"comparison": "<"<br />
},<br />
{<br />
"color": "#00FF00"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
Creates a red-white-green color scale where the minimum value is red, the nominal value (eg. a target value) of 50 is white and maximum value is green.<br />
<pre><br />
{<br />
"backgroundColor": {<br />
"scale": [<br />
{<br />
"value": { "aggregate": "min" },<br />
"color": "#EF5254"<br />
},<br />
{<br />
"value": 50,<br />
"color": "#FFFFFF"<br />
},<br />
{<br />
"value": { "aggregate": "max" },<br />
"color": "#68DD8F"<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
Adds an icon left of the value (icon sentiment_satisfied_alt if value is over 100 and otherwise sentiment_very_dissatisfied). Also icons have different colors.<br />
<pre><br />
{<br />
"icon": {<br />
"rules": [<br />
{<br />
"icon": "sentiment_satisfied_alt",<br />
"value": 100,<br />
"comparison": ">"<br />
}<br />
],<br />
"icon": "sentiment_very_dissatisfied",<br />
"color": {<br />
"rules": [<br />
{<br />
"color": "#36d475",<br />
"value": 100,<br />
"comparison": ">"<br />
},<br />
{<br />
"color": "#EF5254"<br />
}<br />
]<br />
}<br />
}<br />
}<br />
</pre></div>Lasuusihttps://wiki.onqpr.com/pa/index.php?title=Process_Flowchart&diff=16746Process Flowchart2020-09-07T13:42:40Z<p>Lasuusi: </p>
<hr />
<div>Flowchart Analysis draws the process flow as a flowchart, where the boxes represent the event types (activities) and the arrows are flows (transitions between consecutive events). The flowchart also visualizes case/event counts, durations and costs for the events and flows. The visibility settings of the Flowchart Analysis help to show only the most important event types and flows, and the ones which occur less often can be hidden.<br />
<br />
[[File:FlowchartAnalysis.png|450px]] <br />
<br />
== Flowchart Visibility Settings and Count Indicators ==<br />
Using the event types and flows visibility settings in the bottom left of the screen, you can define control, how many event types and flows are shown in the flowchart. The steppers work as follows:<br />
* The upper plus button is used to show one more event type in the flowchart, and the upper minus button is used to hide one event type. The lower plus button is used to show one more flow in the flowchart, and the lower minus button is used to hide one flow.<br />
* The event types and flows are shown from the most important one, i.e. the one which has occurred the most often.<br />
* The percentage number shows, how many percentage of event types or flows in the model are currently visible.<br />
* Instead of clicking the plus and minus buttons, you can click the number and specify a new percentage. The flowchart will show the closest amount of event types and the percentage number will adjust to the corresponding number.<br />
* When hovering the percentage number, a tooltip appears showing the number of shown event types and total number of event types in the model.<br />
<br />
Notes regarding visibility settings:<br />
* If there are several event types or flow which have equal amount of occurrences, they are shown or hidden at the same time. Thus it's possible that several event types or flow appear or disappear when clicking plus and minus buttons. This is of course quite uncommon, if the case and event volumes are large.<br />
* In the flowchart, for each event type there is at least one incoming and outgoing flow. This is to make the flowchart presentation to look more like consistent process, despite some event types and flows have been hidden as less important.<br />
<br />
The case and event count indicators are located in the left side of the Flowchart Analysis. The upper indicator shows case counts. The percentage number shows how many percentage of cases are in the currently open filter out of the total number of cases in the model. When hovering the indicator, it shows the absolute count of cases in the filter and in the model. The lower indicator shows the same information for the amount of events.<br />
<br />
Clicking an event type or a flow selects it. To select multiple event types and/or flows, hold down the '''Ctrl''' key on the keyboard and click on event types and flows. Pressing '''Ctrl + A''' selects all event types and flows in the flowchart. Note that with the Radial graph layout, only the event type that is in the center of the graph can be selected and the popup menu opened for that event type.<br />
<br />
== Zooming and Filtering in the Flowchart ==<br />
Filters can be created in the flowchart by selecting event types and/or flows and right clicking to open the popup menu. When selecting only event types, you can create filters for including/excluding cases containing all the selected event types and including/excluding event types. When selecting only flow or also flows, you can create filter to include cases containing the selected flows and event types.<br />
<br />
Click and drag the flowchart to move it (panning). Use the mouse wheel to zoom in and out. You can also use the + and - buttons on the bottom right corner to zoom. On touch devices, use the pinch gesture.<br />
<br />
The following keyboard shortcuts are available:<br />
* '''Ctrl+0''' sets the zoom to 100%.<br />
* '''Shift+Z''' fits the flowchart into view.<br />
* '''+'''' and '''-''' zoom the flowchart in and out.<br />
* '''Cursor keys''' scroll the flowchart.<br />
* '''PageUp''' and '''PageDown''' keys scroll the flowchart vertically up and down.<br />
<br />
== Flowchart Settings ==<br />
In the '''Settings''' page, you can define which information is shown in the flowchart:<br />
* '''Case Count KPI'''<br />
** '''Show on Event Types''': When enabled, the flowchart displays in the event type boxes the event occurrence count information both as a percentage out of all the cases in the model and also as an absolute count.<br />
** '''Show on Flows''': When enabled, the flowchart displays in the flow arrows, the occurrence information both as a percentage out of all the cases in the model and also as an absolute count.<br />
* '''Duration KPI'''<br />
** '''Show on Flows''': Makes the flowchart display the duration for flows below the shown cost for all the flows. When enabled, allows selecting duration mode among the following choices:<br />
*** '''Median''': Median durations are shown.<br />
*** '''Average''': Average durations are shown.<br />
*** '''Average Weighted by Cost''': As the average duration but in addition the calculation will be weighted by the costs of the event type or flow.<br />
* '''Cost KPI'''<br />
** '''Show on Event Types''': When enabled, the flowchart displays the cost for event types above the event type name for all the event types.<br />
** '''Show on Flows''': When enabled, the flowchart displays cost for flows below the amounts for all the flows.<br />
*** '''Total''': The costs are shown as total costs (sum of costs).<br />
*** '''Average''': The costs are shown as average costs.<br />
* '''Transition Type'''<br />
** '''Unique Only''': When enabled, data will be displayed in the ''Unique Only'' mode, i.e. only one occurrence per each case is counted, so that the generic flow of the process is shown, as well as the amount of occurrences of each event type. When disabled, all occurrences are counted, thus revealing if a certain step or a flow in the process is repeated several times impacting the process performance. This setting affects the values in both event types and flows.<br />
* '''Graph Layout'''<br />
** Layout to use in the flowchart. Options are '''Grid''', '''Tree''', '''Force Directed''', '''Layered Digraph''' (default), '''Circular''' and '''Radial'''. Note that when the '''Radial''' layout is used, only a single flow can be selected in the flowchart (no multiselect is possible).<br />
** '''Horizontal''': Defines whether to use horizontal (from left to right) or vertical (from top to bottom) direction for layouts. Only the ''Tree'' and ''Layered Digraph'' layouts are affected by this setting.<br />
** '''Radial Layers''': Number of layers to display when the ''Radial'' layout is used.<br />
<br />
== Root Causes in Flowchart ==<br />
The flowchart is also able to show root causes that are explained by occurrence of specific types of events and flows. The flowchart shows root causes when any criteria for finding root causes has been set.<br />
<br />
If the percentage of selected cases that go through a certain event type or flow is higher comparing to other cases, event type box or flow array is colored red. If it's lower, event type box or flow array is colored blue. There is a constant color scale between the red and blue extremes visualized. The center between the red and blue is colored as white. The width of flows is calculated based on the average of case counts of the merged flows.<br />
<br />
[[File:PAPOInfluenceAnalysis2.png|450px]]<br />
<br />
'''Example1:''' "''Shipment sent''" event type is selected. <BR/><br />
From the cases which go through "''Shipment sent''" event type<br />
* 3% of the cases have "''Returned with Notification''" event type.<br />
From the comparison group (the cases which '''do not''' go through "''Shipment sent''" event type)<br />
* 10% of the cases have "''Returned with Notification''" event type.<br />
<br />
'''Example2:''' "''Shipment sent''" event type is selected.<BR/><br />
From the cases which go through "Shipment sent" event type<br />
* 71% of the cases go directly from "''Invoice Created''" event type to "''Payment Received''" event type.<br />
From the comparison group (the cases which '''do not''' go through "''Shipment sent''" event type)<br />
* 58% of the cases go directly from "''Invoice Created''" event type to "''Payment Received''" event type.<br />
<br />
__NOTOC__</div>Lasuusi