Overview
The Keep Events with Same Value as Case Attribute filter compares event-level attributes with case-level attributes to retain only matching events. This specialized event-level filter removes events from cases where the event attribute value doesn't match the corresponding case attribute value, then returns only cases that have at least one matching event. It's particularly useful for filtering events by organizational context, geographical regions, or business rules where event characteristics must align with case-level properties.
Common Uses
- Keep only events handled by resources from the same region as the case
- Filter events to match case-level business rules or constraints
- Retain events where the processing location matches the case origin
- Focus on events performed by the designated department for each case
- Remove events handled by incorrect organizational units
- Ensure event-level assignments align with case-level routing rules
Settings
Case Column Name: The name of the case attribute to use as the reference value.
Event Column Name: The name of the event attribute to compare against the case attribute.
Keep Event If Null: Choose whether to keep events where the event attribute is null.
- Keep null events (true): Events with null values in the event column are retained, along with matching events
- Remove null events (false): Only events with non-null values that exactly match the case attribute are kept
| Setting | Purpose | Example Value |
|---|---|---|
| Case Column Name | Reference attribute at case level | "Customer Region" |
| Event Column Name | Attribute to compare at event level | "Processing Region" |
| Keep Event If Null | Handle null event values | True or False |
Examples
Example 1: Filtering Events by Regional Alignment
Scenario: Your customer support process assigns cases to regions based on customer location. However, sometimes support agents from other regions handle tickets due to workload balancing. You want to analyze only events where the "Agent Region" matches the "Customer Region" to measure regional performance accurately.
Settings:
- Case Column Name: "Customer Region"
- Event Column Name: "Agent Region"
- Keep Event If Null: False
Result:
For each case, only events where the agent's region matches the customer's region are kept. Case #SUP-1234 with Customer Region = "Northeast" keeps events handled by Northeast agents but removes events handled by Southeast or Western agents. Cases with no matching events are excluded entirely from the results.
Insights: This shows you true regional performance where agents handled cases from their own regions. By filtering out cross-region handling, you can measure how efficiently each region serves its own customers and identify whether certain regions consistently need help from other regions.
Example 2: Analyzing Department-Specific Workflows
Scenario: Your approval workflow routes cases to specific departments based on request type. You want to analyze only events performed by the designated department for each case to understand how well departmental routing works when followed correctly.
Settings:
- Case Column Name: "Assigned Department"
- Event Column Name: "Processing Department"
- Keep Event If Null: True
Result:
For each case, events where the processing department matches the assigned department are retained. Case #REQ-5678 with Assigned Department = "Finance" keeps all Finance department activities. Events with null Processing Department values are also kept, which might represent automated system activities. Cases without any matching events are removed from the analysis.
Insights: This reveals how often cases stay within their assigned department versus being escalated or transferred. By including null events, you retain system activities while focusing on departmental alignment. This helps identify cases that required cross-departmental collaboration and measure single-department processing efficiency.
Example 3: Validating Location-Based Processing Rules
Scenario: Your manufacturing process has a business rule that parts must be processed at facilities in the same country where the order originated for regulatory compliance. You want to verify this rule is being followed by keeping only events where "Processing Country" matches "Order Country."
Settings:
- Case Column Name: "Order Country"
- Event Column Name: "Processing Country"
- Keep Event If Null: False
Result:
For each order, only processing events that occurred in the same country as the order origin are retained. Order #MFG-9876 from Germany keeps only events processed at German facilities, removing any events processed in other countries. Orders with all events filtered out indicate complete rule violations.
Insights: This provides compliance validation by showing which orders were processed entirely within the correct country. Orders that disappear from the filtered data indicate rule violations that need investigation. You can quickly identify and remedy compliance issues before they become regulatory problems.
Example 4: Analyzing Resource Assignment Accuracy
Scenario: Your project management system assigns team members to projects based on their skill set. Each case has "Required Skill Level" and each activity has "Resource Skill Level." You want to analyze only work performed by appropriately skilled resources.
Settings:
- Case Column Name: "Required Skill Level"
- Event Column Name: "Resource Skill Level"
- Keep Event If Null: True
Result:
For each project case, only activities performed by resources with the matching skill level are retained. Project #PROJ-4567 requiring "Senior" skill keeps only events performed by Senior-level resources. Events with null skill levels (perhaps automated or unassigned activities) are kept because Keep Event If Null is true.
Insights: This shows you what portion of work is performed by appropriately skilled resources versus over-skilled or under-skilled assignments. By analyzing these filtered cases, you can measure productivity when skill levels are correctly matched and identify patterns in skill mismatches that affect project efficiency.
Output
This filter operates at both event and case levels with unique behavior:
- Event-level filtering: Removes events where the event attribute doesn't match the case attribute
- Case-level result: Returns only cases that have at least one matching event
- Non-matching events are removed from all cases
- Cases with zero matching events are completely excluded from results
- When Keep Event If Null is true, events with null values in the event column are retained
- When Keep Event If Null is false, only exact non-null matches are kept
- All other event and case attributes are preserved
Use this filter to ensure event-level activities align with case-level rules, validate organizational routing, or focus analysis on correctly assigned work while identifying exceptions.
This documentation is part of the mindzie Studio process mining platform.