Overview
The Case End filter selects or removes cases based on the value of a specified attribute in the last event of each case. This filter examines what activity, resource, status, or other attribute value appears in the final event of a case, allowing you to identify cases that ended in a particular way.
Common Uses
- Identify cases that ended with activities they should not have (e.g., cases ending with "Cancelled" instead of "Completed")
- Select cases that ended with specific purchase order statuses (e.g., "Back Ordered", "Cancelled", or "On Hold")
- Find cases where a particular resource performed the final activity
- Analyze cases that ended with specific approval states or quality check results
- Filter cases based on final customer interaction type or final payment status
- Investigate cases that concluded with error or exception activities
Settings
Event Column: Select the event attribute you want to examine in the last event of each case. This can be any event-level column such as Activity Name, Resource, Status, Department, or any custom event attribute in your log.
Column Values: Choose one or more values from the selected column. Cases where the last event contains any of these values will be selected. The filter shows the percentage of cases that end with each value to help you understand the data distribution.
Remove Selected Cases: When checked, the filter inverts its behavior - cases that match the criteria are removed instead of kept. Use this when you want to exclude cases that ended with specific values.
Examples
Example 1: Select Cases Ending with Incomplete Activities
Scenario: A procurement process should always end with "Clear Invoice" activity. You want to find cases that ended with any other activity to identify incomplete processes.
Settings:
- Event Column: Activity Name
- Column Values: Clear Invoice
- Remove Selected Cases: Checked (to exclude cases ending with Clear Invoice)
Result: The filter removes 99.9% of cases that properly ended with "Clear Invoice" and keeps only the 1 case that ended with a different activity.
Insights: This reveals process deviations where cases did not complete the expected final step, indicating potential process quality issues or incomplete workflows.
Example 2: Find Cases Ending with Specific Resources
Scenario: You want to analyze cases where either Resource 48 or Resource 17 performed the final activity to understand their workload patterns or identify bottlenecks.
Settings:
- Event Column: Resource
- Column Values: Resource 48, Resource 17
- Remove Selected Cases: Unchecked
Result: The filter selects only cases where the last activity was performed by either Resource 48 or Resource 17.
Insights: This helps identify which cases these specific resources are responsible for completing, useful for workload analysis, quality control, or understanding resource specialization in your process.
Example 3: Analyze Cases with Back Order Status
Scenario: In a purchase order process, you want to identify cases that ended with a "Back Ordered" status to understand supply chain issues.
Settings:
- Event Column: Order Status
- Column Values: Back Ordered
- Remove Selected Cases: Unchecked
Result: The filter selects all cases where the final status was "Back Ordered".
Insights: This reveals potential supply chain problems and allows you to analyze common characteristics of back-ordered cases, such as specific vendors, products, or time periods where back orders are more common.
Example 4: Exclude Cancelled Cases
Scenario: You want to analyze only successfully completed cases by removing those that ended with "Cancelled" or "Rejected" statuses.
Settings:
- Event Column: Case Status
- Column Values: Cancelled, Rejected
- Remove Selected Cases: Checked
Result: The filter removes all cases that ended with "Cancelled" or "Rejected" statuses, leaving only cases that reached other conclusion states.
Insights: This creates a clean dataset for analyzing successful process execution patterns without the noise of cancelled or rejected cases.
Output
The filter operates at the case level, meaning it removes or keeps entire cases based on the criteria. After applying the filter:
- Cases where the last event matches any of the selected values will be kept (or removed if "Remove Selected Cases" is checked)
- All other cases will be removed (or kept if "Remove Selected Cases" is checked)
- The percentage of cases removed and kept is displayed in the filter output
- Subsequent analysis will only include the filtered cases
Important Notes:
- The filter examines only the final event in each case, not all events
- Multiple values can be selected, and cases matching any of the values will be included
- The filter treats values as exact matches - they must match precisely
- Null or empty values in the selected column are ignored and will not match any criteria
This documentation is part of the mindzie Studio process mining platform.