Overview
The Remove Activity with Same Date filter removes specific activity events from cases when they occur on the same calendar day as another specified activity. This event-level filter is designed to clean process logs by eliminating redundant or secondary activities that happen on the same day as a primary activity. You specify which activity to remove and which activity to use as the reference date comparison.
Common Uses
- Remove redundant validation steps when primary approval happens on the same day
- Clean logs by eliminating duplicate processing activities on the same calendar day
- Filter out secondary notification events that occur on the same day as primary notifications
- Remove follow-up activities when they happen on the same day as the initial activity
- Clean up process logs where alternative paths were logged on the same day
- Simplify process flows by removing same-day redundant activities
Settings
Activity to Remove: The name of the activity you want to remove from cases.
Activity to Compare To: The reference activity for date comparison. If this activity exists on the same calendar day as the activity to remove, the removal activity is filtered out.
| Setting | Purpose | Example Value |
|---|---|---|
| Activity to Remove | Specifies which activity events to remove | "Secondary Check" |
| Activity to Compare To | Reference activity for date comparison | "Primary Validation" |
Examples
Example 1: Removing Redundant Validation Steps
Scenario: Your loan approval process has both "Automated Credit Check" and "Manual Credit Review" activities. When both occur on the same day, it means the manual review caught issues immediately, making the automated check redundant in the log. You want to remove "Automated Credit Check" events that occur on the same day as "Manual Credit Review."
Settings:
- Activity to Remove: "Automated Credit Check"
- Activity to Compare To: "Manual Credit Review"
Result:
Any "Automated Credit Check" event that occurs on the same calendar day as a "Manual Credit Review" event in the same case is removed. For example, if Case #LOAN-5678 has "Automated Credit Check" at 9:00 AM on October 15 and "Manual Credit Review" at 2:00 PM on October 15, the automated check is removed from the log. If they occur on different days, both activities are retained.
Insights: This simplifies your process flow by removing redundant automated checks when manual review happened the same day. The resulting log better represents the actual decision-making workflow, showing manual review as the primary validation method for these cases while preserving cases where only automated checks occurred.
Example 2: Eliminating Duplicate Notifications
Scenario: Your customer service system sends both "Email Notification" and "SMS Alert" when a ticket is resolved. For analysis purposes, you only want to track the primary "Email Notification" and remove "SMS Alert" events that occur on the same day, as they represent the same business event.
Settings:
- Activity to Remove: "SMS Alert"
- Activity to Compare To: "Email Notification"
Result:
Any "SMS Alert" event that occurs on the same calendar day as an "Email Notification" event is removed. If Case #TICKET-123 has "Email Notification" on October 15 and "SMS Alert" also on October 15, the SMS alert is removed. Cases where SMS alerts occur on different days than email notifications retain both events.
Insights: By removing same-day duplicate notifications, you get a cleaner view of unique customer communications without double-counting notification events. This provides more accurate counts of customer touchpoints and simplifies process flow visualization.
Example 3: Cleaning Alternative Process Paths
Scenario: Your invoice processing workflow has both "Standard Approval" and "Express Approval" paths. When both occur on the same day, it means the invoice was initially routed to standard approval but then expedited. You want to remove "Standard Approval" events when "Express Approval" happens the same day to show only the final approval method.
Settings:
- Activity to Remove: "Standard Approval"
- Activity to Compare To: "Express Approval"
Result:
Any "Standard Approval" event that occurs on the same calendar day as an "Express Approval" event is removed from the case. If Case #INV-9876 has "Standard Approval" at 10:00 AM and "Express Approval" at 3:00 PM on the same day, the standard approval is removed, showing only the express approval that actually processed the invoice.
Insights: This clarifies process paths by showing the actual approval method used rather than intermediate routing steps. Your process mining visualization becomes cleaner, showing express approval as the single approval activity for these cases while preserving standard approval for cases that didn't get expedited.
Example 4: Removing Same-Day Follow-Up Activities
Scenario: Your support ticket system logs both "Ticket Assigned" and "Agent Follow-Up" activities. When both occur on the same day, the follow-up is part of the initial assignment process rather than a separate activity. You want to remove "Agent Follow-Up" events when they happen on the same day as "Ticket Assigned."
Settings:
- Activity to Remove: "Agent Follow-Up"
- Activity to Compare To: "Ticket Assigned"
Result:
Any "Agent Follow-Up" event occurring on the same calendar day as "Ticket Assigned" is removed. If Case #SUP-4567 has "Ticket Assigned" on October 10 and "Agent Follow-Up" also on October 10, the follow-up is removed. Follow-ups on subsequent days are retained as they represent separate touchpoints.
Insights: This distinguishes between immediate follow-ups (part of assignment) and delayed follow-ups (separate process steps). Your process metrics become more accurate, showing true follow-up rates while eliminating same-day activities that are really part of initial assignment.
Output
This filter operates at the event level, removing individual events from cases:
- Only the specified "Activity to Remove" events are affected
- Events are removed if they occur on the same calendar day as the reference activity
- Comparison uses calendar dates only (ignores time of day)
- Cases remain in the dataset even if events are removed
- All other event attributes and properties are preserved
- If no events match the removal criteria, the original data is returned unchanged
Use this filter to clean process logs by removing redundant or secondary activities that occur on the same calendar day as primary activities, simplifying process flows and providing clearer insights into actual business operations.
This documentation is part of the mindzie Studio process mining platform.