Filtering in QPR ProcessAnalyzer: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
(306313)
 
(83 intermediate revisions by 4 users not shown)
Line 1: Line 1:
There are two types of filtering available in QPR ProcessAnalyzer: [[Filtering#Runtime Selection|Runtime Selection]] and [[Filtering#Include / Exclude Filters|Include / Exclude Filters]].
'''Filters''' define a subset of cases and events in the model, e.g., certain region or time period. Filter consists of a list of filter rules, that are criteria defining which cases/events are included and which are excluded from the resulting dataset. Filters are very powerful feature in QPR ProcessAnalyzer, because any filter can be applied to any analysis and chart.


== Runtime Selection ==
Filter consists of one or several '''filter rules''', which are applied in the defined order starting from the leftmost. The evaluation order matters in some rules, because the rule is evaluated to the eventlog that is the result of the previous rule evaluation. For example, if excluding event types, number of events in cases change, and thus subsequent filter rules may match do different cases.
A runtime selection filter is applied when event types, transitions, cases, or attributes are selected and you click on any other analysis button on the ribbon except the Flowchart button. The data on the view that is opened will then be filtered based on what was selected. The runtime selection is not a persistent filter, so it is not added to the [[Filters#Filter History|Filter History]]. In addition, opening the Flowchart analysis will clear the runtime selection.


== Include / Exclude Filters ==
Filter excludes a case/event, if there is a single filter rule that excludes the case/event (i.e., there is an AND type of logic between the filter rules). Filtering functionality is described in more detail in the [[Process_Mining_Concepts|concepts section]].


Using the '''Include Only''' and '''Exclude''' buttons, it is possible to filter the data. Depending on the active view, the buttons do the following:
== Saving filters ==
You can save the set of filter rules that are in the header, so that they can be retrieved easily. Filter are saved to the model that is currently open. Saving is done by hovering the mouse over the filter dropdown menu (without clicking) and choosing '''Save as new filter'''. There must be at least one filter rule available to be able to save the filter. This will prompt a pop-up window where you can name your filter.


=== Flowchart Analysis View with 1..n Event Types Selected, 1..m Transitions selected ===
[[File:Savingfilters.png|1100px]]
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.


=== Flowchart Animation View with 1..n Cases Selected ===
You can also set the '''Privacy mode''' as follows:
* '''Private''': Filter is available only for you.
* '''Public''': Filter is available for all users that can use the model. The creator and model administrators can change the public filter.
* '''Default Public''': Filter is public and in addition the default filter of the model. The default filter is set active for all users automatically when the model is opened. Only one filter can be the default filter pf the model, and when setting a filter as default, the previous default filter is changed to public.


*Include Only
== Turning off filter rules ==
: '''Cases''': Creates a new view containing only the selected cases.
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.


*Exclude
[[File:DisabledFilterRules.png|800px]]
: '''Cases''': Creates a new view excluding the selected cases.


=== Duration Analysis with 1..n Rows Selected ===
== Filter actions ==
*Include Only
Users with [[Roles_and_Permissions#Roles_and_Their_Permissions|Analyzer]] role for the project can save and modify filters. You can do this by opening the filters list, hovering your mouse over a filter and clicking on the three dots. There are following actions available:
: Creates a new view containing only the cases with the selected duration(s).
* '''Properties''': Open filter properties dialog, where the filter name, privacy mode and filter rules can be modified.
*Exclude
* '''Duplicate''': Create a copy of this filter.
: Creates a new view excluding the cases with the selected duration(s).
* '''Delete''': Delete the filter permanently.
* '''Replace''': Replace the rules of this filter with the currently selected rules in the header.
* '''Create model''': Creates a new model containing cases and events that are in this filter. New model and cases/events datatables are created to the same project. This action is available for Snowflake models.
* '''Export''': Export the rules of this filter to a file (in JSON format).
* '''Import''': Replace the rules of this filter with rules imported from a file (in JSON format).


=== Profiling Analysis with 1..n Rows Selected ===
== Filter rule types ==
*Include Only
When creating a new filter the following filter rule types are available:
: Creates a new view containing only the cases with the selected duration(s).
* '''Cases by Case Attribute''': Select cases having specific case attribute values.
*Exclude
* '''Cases by Event Attribute''': Select cases having one or several events with specific event attribute values.
: Creates a new view excluding the cases with the selected duration(s).
* '''Cases with Specific Events''': Select cases having one or several specific types of events.
* '''Cases Flowing Through''': Select cases having specific flow (i.e., direct transition between specific types of events).
* '''First Event in Case''': Select cases starting with specific event.
* '''Last Event in Case''': Select cases ending to specific event.
* '''Case IDs''': Select cases with specific case ID's.
* '''Variations''': Select cases belonging the specific variations.
* '''Events by Attribute''': Select events having specific events attribute values. This filter rule type is available in Snowflake.
* '''Events by Type''': Select events having specific events types.


=== Path Analysis with 1..n Event Types Selected, 1..m Transitions selected ===
Filter rules can be created for the dashboard (i.e., applied to all charts in the dashboard) by clicking the blue plus button in the header, or to specific charts in the chart settings in the '''Filter''' tab. When running the root causes analysis, the root causes criteria is also selected similar to filter rules.
*Include Only
: '''Cases''': Creates a new view containing only the cases that go through all the selected event types and transitions.
: '''Event Types''': Creates a new view containing only the event types of the selected event types.
*Exclude
: '''Cases''': Creates a new view excluding the cases that go through the selected event types and transitions.
: '''Event Types''': Creates a new view excluding the event types of the selected event types.
 
=== Influence Analysis with Row(s) or Parts of Row(s) Selected ===
*Include Only
: '''Cases''': Creates a new view containing only the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).
:* If the selected case attribute(s) are the same that were used to open the Influence Analysis, the new filter will contain only the new selected value(s) for the case attribute(s).
:* If the selected case attribute(s) are not the same that were used to open the Influence Analysis, the original case selection that was used when opening the Influence Analysis isn't used.
*Exclude
: '''Cases''': Creates a new view excluding the cases that have the particular value for the particular case attribute in the selected row(s) or parts of row(s).
 
Note: Only one case attribute can be selected for the Include/Exclude filters in the Influence Analysis.
 
=== List of Cases with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the selected case(s).
*Exclude
: Creates a new view excluding the selected case(s).
 
=== List of Variations with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the cases that belong to selected variation(s).
* Exclude
: Creates a new view excluding the cases that belong to selected variation(s).
 
=== List of Event Types with 1..n Rows Selected ===
*Include Only
: Creates a new view containing only the event types that are selected.
*Exclude
: Creates a new view excluding the event types that are selected.
 
The filtered view that is created will be available in the [[Views#View Manager|Filter Manager]].
 
Note that if you use attribute values with exponents so that the value is bigger than 1E15 (that is, 1 times 10 to the power of 15) or smaller than 1E-15, the filtering does not work correctly. For example, if you have such cost as 2,31176835E+21 and 9,43E-15 and you select these attribute values for filtering, they will give incorrect results.
 
{{Filtering Example}}
 
 
{{About Version}}
 
[[Category: Filtering]]

Latest revision as of 20:25, 21 December 2023

Filters define a subset of cases and events in the model, e.g., certain region or time period. Filter consists of a list of filter rules, that are criteria defining which cases/events are included and which are excluded from the resulting dataset. Filters are very powerful feature in QPR ProcessAnalyzer, because any filter can be applied to any analysis and chart.

Filter consists of one or several filter rules, which are applied in the defined order starting from the leftmost. The evaluation order matters in some rules, because the rule is evaluated to the eventlog that is the result of the previous rule evaluation. For example, if excluding event types, number of events in cases change, and thus subsequent filter rules may match do different cases.

Filter excludes a case/event, if there is a single filter rule that excludes the case/event (i.e., there is an AND type of logic between the filter rules). Filtering functionality is described in more detail in the concepts section.

Saving filters

You can save the set of filter rules that are in the header, so that they can be retrieved easily. Filter are saved to the model that is currently open. Saving is done by hovering the mouse over the filter dropdown menu (without clicking) and choosing Save as new filter. There must be at least one filter rule available to be able to save the filter. This will prompt a pop-up window where you can name your filter.

Savingfilters.png

You can also set the Privacy mode as follows:

  • Private: Filter is available only for you.
  • Public: Filter is available for all users that can use the model. The creator and model administrators can change the public filter.
  • Default Public: Filter is public and in addition the default filter of the model. The default filter is set active for all users automatically when the model is opened. Only one filter can be the default filter pf the model, and when setting a filter as default, the previous default filter is changed to public.

Turning off filter rules

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.

DisabledFilterRules.png

Filter actions

Users with Analyzer role for the project can save and modify filters. You can do this by opening the filters list, hovering your mouse over a filter and clicking on the three dots. There are following actions available:

  • Properties: Open filter properties dialog, where the filter name, privacy mode and filter rules can be modified.
  • Duplicate: Create a copy of this filter.
  • Delete: Delete the filter permanently.
  • Replace: Replace the rules of this filter with the currently selected rules in the header.
  • Create model: Creates a new model containing cases and events that are in this filter. New model and cases/events datatables are created to the same project. This action is available for Snowflake models.
  • Export: Export the rules of this filter to a file (in JSON format).
  • Import: Replace the rules of this filter with rules imported from a file (in JSON format).

Filter rule types

When creating a new filter the following filter rule types are available:

  • Cases by Case Attribute: Select cases having specific case attribute values.
  • Cases by Event Attribute: Select cases having one or several events with specific event attribute values.
  • Cases with Specific Events: Select cases having one or several specific types of events.
  • Cases Flowing Through: Select cases having specific flow (i.e., direct transition between specific types of events).
  • First Event in Case: Select cases starting with specific event.
  • Last Event in Case: Select cases ending to specific event.
  • Case IDs: Select cases with specific case ID's.
  • Variations: Select cases belonging the specific variations.
  • Events by Attribute: Select events having specific events attribute values. This filter rule type is available in Snowflake.
  • Events by Type: Select events having specific events types.

Filter rules can be created for the dashboard (i.e., applied to all charts in the dashboard) by clicking the blue plus button in the header, or to specific charts in the chart settings in the Filter tab. When running the root causes analysis, the root causes criteria is also selected similar to filter rules.