🔍

Or Filter

Filters

Overview

The Or Filter is a logical filter that combines multiple filters using OR logic, where a case is included if it matches ANY of the individual filter conditions. This powerful case-level filter allows you to create complex filtering scenarios by combining different filter types into a single operation. Instead of a case needing to satisfy all conditions (AND logic), it only needs to satisfy at least one condition to be included in the results.

Common Uses

  • Include cases from multiple regions or business units in a single analysis
  • Select cases that meet any of several different priority or value criteria
  • Combine different attribute conditions to capture exception cases
  • Create flexible filtering rules where multiple paths lead to inclusion
  • Build complex business rules with multiple qualifying conditions
  • Identify cases that satisfy any of several compliance or quality criteria

Settings

Filter List: A collection of individual filters that will be combined using OR logic. Each filter in the list represents a condition, and a case is included if it matches ANY of these conditions.

How it works:

  1. Each filter in the list is evaluated independently against the original dataset
  2. Results from all filters are combined using set union (OR logic)
  3. Duplicate cases are automatically removed
  4. The final result includes any case that matched at least one filter condition

Note: You need at least 2 filters in the list for meaningful OR operation. With fewer than 2 filters, the original dataset is returned unchanged.

Examples

Example 1: Multi-Region Analysis

Scenario: You want to analyze orders from both the Eastern and Western sales regions. Instead of running two separate analyses or using a complex attribute filter, you can use an OR filter to include cases from either region.

Settings:

  • Filter 1: Cases with Attribute "Region" equals "Eastern"
  • Filter 2: Cases with Attribute "Region" equals "Western"

Result:

Any case where Region = "Eastern" OR Region = "Western" is included in the results. Case #12345 from Eastern region is included, Case #67890 from Western region is included, but Case #11111 from Northern region is excluded. If you had 1,000 cases total with 300 Eastern and 250 Western, your result would contain 550 cases.

Insights: This lets you compare and analyze multiple regions together while excluding others. You can identify best practices from high-performing regions, compare processing patterns between regions, and measure combined performance of specific geographical areas.

Example 2: Priority or High-Value Cases

Scenario: Your analysis should include both high-priority cases (Priority = "High") and high-value cases (Order Amount > $10,000), as both types require special attention regardless of the other characteristic.

Settings:

  • Filter 1: Cases with Attribute "Priority" equals "High"
  • Filter 2: Cases with Attribute "Order Amount" greater than 10000

Result:

Any case marked as high priority OR with order amount exceeding $10,000 is included. Case #ABC with Priority = "High" and Amount = $5,000 is included (high priority). Case #DEF with Priority = "Medium" and Amount = $15,000 is included (high value). Case #GHI with Priority = "High" and Amount = $12,000 is included (matches both). Low-priority, low-value cases are excluded.

Insights: This captures all cases requiring special handling for any reason, whether due to customer importance (priority) or financial significance (value). You can analyze resource allocation for VIP cases and measure whether high-priority or high-value cases receive faster processing.

Example 3: Multiple Status Conditions

Scenario: You want to analyze cases in any active state - those that are "In Progress," "Pending Review," or "Awaiting Approval." Any of these statuses indicates an active case that needs attention.

Settings:

  • Filter 1: Cases with Attribute "Status" equals "In Progress"
  • Filter 2: Cases with Attribute "Status" equals "Pending Review"
  • Filter 3: Cases with Attribute "Status" equals "Awaiting Approval"

Result:

Cases with any of the three active statuses are included. Case #100 with Status = "In Progress" is included, Case #200 with Status = "Awaiting Approval" is included, but Case #300 with Status = "Completed" is excluded. This gives you a complete view of active workload across all active states.

Insights: By combining multiple active statuses, you can analyze current workload comprehensively, identify bottlenecks in any active phase, and measure overall active case duration without needing to analyze each status separately.

Example 4: Exception Case Identification

Scenario: You want to identify exception cases that require investigation - those that took longer than 30 days OR had more than 50 events OR were handled by more than 5 different resources.

Settings:

  • Filter 1: Cases with Case Duration greater than 30 days
  • Filter 2: Cases with Event Count greater than 50
  • Filter 3: Cases with Unique Resource Count greater than 5

Result:

Any case meeting at least one exception criterion is included. Case #AAA with 45-day duration is included (long). Case #BBB with 65 events is included (many events). Case #CCC with 8 different resources is included (many handoffs). Normal cases meeting none of these criteria are excluded.

Insights: This identifies problematic cases that exhibit any form of exceptional behavior requiring investigation. You can analyze what makes these cases different, identify common patterns among exception cases, and develop strategies to prevent or handle exceptional situations more effectively.

Example 5: Compliance or Audit Criteria

Scenario: Your audit process needs to review cases that meet any of several risk indicators - cases from restricted countries, cases above the approval threshold without manager approval, or cases flagged by the fraud detection system.

Settings:

  • Filter 1: Cases with Attribute "Country" is one of ["Country A", "Country B", "Country C"]
  • Filter 2: Cases with Attribute "Amount" greater than 50000 AND "Manager Approval" equals "No"
  • Filter 3: Cases with Attribute "Fraud Flag" equals "Yes"

Result:

Any case triggering at least one risk indicator is included for audit review. This could be 5% of total cases, but these are the highest-risk cases requiring detailed examination. The OR logic ensures you capture all cases requiring attention for any reason.

Insights: By combining multiple risk indicators with OR logic, you create a comprehensive audit population without missing edge cases. This ensures thorough compliance coverage while focusing audit resources on cases with genuine risk indicators rather than reviewing everything.

Output

This filter operates at the case level using union logic:

  • Evaluates each constituent filter independently against the original dataset
  • Combines all results using set union (no duplicates)
  • Returns any case that matched at least one filter condition
  • Preserves all case and event attributes for included cases
  • Requires at least 2 filters for meaningful operation
  • Returns original dataset if fewer than 2 filters are provided

Use OR filters to create flexible, comprehensive filtering rules where multiple different conditions can lead to case inclusion, making it ideal for capturing diverse scenarios in a single analysis.

This documentation is part of the mindzie Studio process mining platform.

An error has occurred. This application may no longer respond until reloaded. Reload ??