Filtering in QPR ProcessAnalyzer

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search

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. The order matter in some rules, because the rule is evaluated to an eventlog that is the result of the previous rule evalution. For example, if excluding event types, the number of events in a case changes, and thus subsequent filter rules may give different results. Cases/events are excluded if there is a single filter rule, that excludes the cases/events (thus 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 filter in the main header by hovering your mouse over the filter dropdown menu (without clicking) and choosing Save as new filter from below. There must be at least one filter rule, to be able to save the filter.

Savingfilters.png

This will prompt a pop-up window where you can name your filter. You can also define whether to set the filter is your private filter (Private) or published to all users (Public). The filter can also be made Default Public making it as the default filter used when the model is opened.

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.

File:Filterruledisableing.png

Filter actions

Users with Analyzer roles for the project can modify and delete the saved filters of models in that project. 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.

File:Filteroptions.png

When you go to the "Actions" tab you have the following options:

  • 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 this filter permanently.
  • Replace: Replace the rules of this filter with the currently selected rules in the header.
  • 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).

File:Filteractions.png

Filter Rule

For example, the following filter rules are available:

  • 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".
  • Include/exclude cases having certain event type(s): For example, include cases that have event types "Invoice Created" or "Invoice Paid" (either or both).
  • 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.
  • 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.
  • Include/exclude cases based on flow duration: For example, include cases the flow from "Sales Order" to "Outbound Delivery" is over 5 weeks.
  • 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".
  • Include/exclude cases having certain event attribute value(s): For example, include cases having event(s) with event attribute "Organization" is "Finance".
  • Include/exclude cases having certain part of variation: For example, include cases where variation starts with "Sales Order sent" -> "Invoice Created" -> "Invoice Paid".
  • Include/exclude event types: For example, include event types "Sales Order sent", "Invoice Created" and "Invoice Paid".