And Filter

Overview

The And Filter is a logical filter that combines multiple filters using AND logic, where a case is included only if it matches ALL of the individual filter conditions. This powerful case-level filter allows you to create precise filtering scenarios by requiring cases to satisfy multiple criteria simultaneously. Unlike the OR filter where matching any condition is sufficient, the AND filter requires every condition to be met.

Common Uses

  • Find cases matching multiple specific attribute values
  • Create complex business rules requiring all criteria
  • Combine activity and attribute conditions
  • Filter for cases in a specific state with specific characteristics
  • Build precise compliance filters with multiple requirements
  • Identify cases meeting all quality or performance thresholds

Settings

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

How it works:

  1. The first filter is applied to the original dataset
  2. Each subsequent filter is applied to the result of the previous filter
  3. Cases are progressively narrowed down through each filter
  4. The final result includes only cases that passed all filter conditions

Note: You can include 2 or more filters. With zero or one filter, the operation returns the input unchanged.

Examples

Example 1: Multi-Attribute Matching

Scenario: You want to find high-value orders from a specific region that are still in progress. All three conditions must be met.

Settings:

  • Filter 1: Cases with Attribute "Region" equals "Western"
  • Filter 2: Cases with Attribute "Order Value" greater than 10000
  • Filter 3: Cases with Attribute "Status" equals "In Progress"

Result:

Only cases matching ALL conditions are included. Case #1001: Region=Western, Value=$15,000, Status=In Progress - INCLUDED. Case #1002: Region=Western, Value=$5,000, Status=In Progress - EXCLUDED (value too low). Case #1003: Region=Eastern, Value=$20,000, Status=In Progress - EXCLUDED (wrong region).

Insights: AND logic lets you define precise case populations for targeted analysis. The order of filters can affect performance but not results - put the most restrictive filter first for faster execution.

Example 2: Activity and Resource Combination

Scenario: You want to analyze cases where a specific activity was performed by a specific resource. Both conditions must be true.

Settings:

  • Filter 1: Cases with Activity "Manager Approval" present
  • Filter 2: Cases with Attribute "Approver" equals "John Smith"

Result:

Cases where "Manager Approval" occurred AND it was performed by John Smith are included. This filters first for cases with the approval activity, then for cases where John performed it.

Insights: Combining activity and resource filters helps analyze individual performance, workload distribution, or identify training needs for specific activities.

Example 3: Time and Value Thresholds

Scenario: You need to find cases that took longer than 30 days AND had a value over $50,000 for executive review.

Settings:

  • Filter 1: Cases with Duration greater than 30 days
  • Filter 2: Cases with Attribute "Case Value" greater than 50000

Result:

Only high-value, long-running cases are included. These represent the most critical cases requiring executive attention - they're both financially significant and experiencing delays.

Insights: Intersecting multiple criteria helps prioritize limited resources. These cases likely need immediate intervention as they combine both risk factors.

Example 4: Compliance Multi-Check

Scenario: Your compliance audit requires cases that have all required approvals: manager approval, finance approval, AND legal review.

Settings:

  • Filter 1: Cases with Activity "Manager Approval" present
  • Filter 2: Cases with Activity "Finance Approval" present
  • Filter 3: Cases with Activity "Legal Review" present

Result:

Only cases with all three approval activities are included. Cases missing any required approval are excluded from this compliant population.

Insights: This identifies your fully compliant case population. The inverse (cases NOT matching all conditions) would show compliance gaps requiring investigation.

Example 5: Exclusion with AND Logic

Scenario: You want to find incomplete cases from a specific vendor that haven't been touched in the last 7 days.

Settings:

  • Filter 1: Cases with Attribute "Status" not equal to "Completed"
  • Filter 2: Cases with Attribute "Vendor" equals "Acme Corp"
  • Filter 3: Cases with Last Activity Date before [7 days ago]

Result:

Cases matching all three criteria are flagged: they're from Acme, incomplete, and stale. These require immediate follow-up as they may be stuck or forgotten.

Insights: Combining status, attribute, and time-based filters helps identify specific problem populations requiring action.

Comparison with OR Filter

Aspect AND Filter OR Filter
Logic All conditions must match Any condition can match
Result Size Generally smaller (more restrictive) Generally larger (more inclusive)
Use Case Precise targeting Broad capture
Execution Sequential filtering Union of results

Output

This filter operates at the case level using intersection logic:

  • Applies filters sequentially, each narrowing the result set
  • Returns only cases matching ALL filter conditions
  • If any filter returns zero cases, the final result is empty
  • Preserves all case and event attributes for included cases
  • Filter order doesn't affect results but can affect performance
  • Returns original dataset if zero or one filter is provided

Use AND filters to create precise, multi-criteria filtering rules where cases must satisfy every condition. This is ideal for compliance checking, targeted analysis, and identifying cases meeting specific complex criteria.

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