🔍

Text Search

Filters

Overview

The Text Search filter performs comprehensive text-based searching across your process data, allowing you to find cases or events containing specific text, numbers, or values. This intelligent filter automatically detects the data type of your search term (string, number, boolean, date) and searches through compatible columns in both case attributes and event attributes. It supports case-sensitive and case-insensitive searches, and can return either complete cases or individual matching events.

The filter is particularly powerful for exploratory analysis when you need to quickly find all occurrences of a specific value (like an order number, customer name, or error code) anywhere in your process data without needing to know which specific attribute contains it.

Common Uses

  • Quick Search: Rapidly locate cases or events containing a specific order number, invoice ID, or customer name without knowing which column it appears in.
  • Error Investigation: Find all cases mentioning specific error codes, error messages, or exception text scattered across different attributes.
  • Customer Analysis: Search for a customer name or ID across all customer-related fields to see their complete process history.
  • Value Tracing: Track specific values (like part numbers, product codes, or account numbers) throughout the process regardless of which attribute contains them.
  • Data Validation: Identify cases containing unexpected or incorrect values by searching for specific patterns or text.
  • Multi-Attribute Search: Search across many attributes simultaneously without creating multiple individual filters.

Settings

Search Text: The text, number, or value you want to search for. The filter automatically detects whether this is a string, integer, decimal number, boolean, or date/time value and searches through compatible column types accordingly. For text searches, the search looks for partial matches (contains).

Search Source: Determines where to search for the text:

  • Cases and Events (default): Searches both case-level attributes and event-level attributes
  • Cases: Searches only case-level attributes (case properties)
  • Events: Searches only event-level attributes (activity properties)

Filter Type: Controls what the filter returns when searching events:

  • Case: Returns complete cases that contain at least one matching event
  • Event: Returns only the individual events that match the search criteria

Case Sensitive: When enabled, the search requires exact case matching. When disabled (default), the search is case-insensitive.

Remove Filter: When enabled, returns cases/events that do NOT match the search criteria instead of those that do match. This inverts the filter logic.

Examples

Example 1: Finding a Specific Order Number

Scenario: You need to find all data related to order number "ORD-12345" but you're not sure which attributes contain the order number (it might appear in OrderID, ReferenceNumber, CustomerOrderNumber, etc.).

Settings:

  • Search Text: "ORD-12345"
  • Search Source: Cases and Events
  • Filter Type: Case
  • Case Sensitive: No
  • Remove Filter: No

Result: The filter returns all cases where "ORD-12345" appears in any case or event attribute, giving you the complete process history for that order.

Insights: This rapid search capability eliminates the need to manually check multiple attributes or create multiple filters. You instantly see all process data related to the order regardless of where the order number was recorded.

Example 2: Investigating Error Messages

Scenario: Your system logs error messages in various fields, and you want to find all cases that encountered the error "Connection timeout" anywhere in the process.

Settings:

  • Search Text: "Connection timeout"
  • Search Source: Events
  • Filter Type: Case
  • Case Sensitive: No
  • Remove Filter: No

Result: The filter returns all cases that have at least one event with "Connection timeout" in any event attribute.

Insights: This helps you:

  • Identify how many cases were affected by this specific error
  • Analyze patterns in when the error occurs
  • See what activities or process paths lead to the timeout
  • Determine the impact on case duration and outcomes

Example 3: Finding High-Value Transactions

Scenario: You want to find all cases containing transactions over 10000 in any numeric field (amount, value, cost, price, etc.).

Settings:

  • Search Text: "10000"
  • Search Source: Cases and Events
  • Filter Type: Case
  • Case Sensitive: No
  • Remove Filter: No

Result: The filter automatically detects "10000" as a numeric value and searches through all integer and decimal columns, returning cases where any numeric field contains values matching or containing 10000.

Insights: This broad numeric search helps identify high-value cases even when the value might be stored in different attributes across different process types or activities.

Example 4: Excluding Test Cases

Scenario: Your event log contains test cases with "TEST" or "test" in various attributes, and you want to exclude all of them from your analysis.

Settings:

  • Search Text: "test"
  • Search Source: Cases and Events
  • Filter Type: Case
  • Case Sensitive: No
  • Remove Filter: Yes

Result: The filter returns all cases that do NOT contain "test" in any attribute, effectively removing all test cases from your analysis.

Insights: The inverted logic (Remove Filter = Yes) provides a quick way to clean your data by removing unwanted cases without needing to know exactly which fields contain test markers.

Example 5: Finding Events with Specific Resource

Scenario: You want to see only the individual events performed by a specific user "John Smith" across all cases, not the complete cases.

Settings:

  • Search Text: "John Smith"
  • Search Source: Events
  • Filter Type: Event
  • Case Sensitive: No
  • Remove Filter: No

Result: The filter returns only the individual events that contain "John Smith" in any event attribute. Each returned event shows what activities this specific resource performed.

Insights: By using Filter Type = Event instead of Case, you get granular visibility into exactly what this resource did, which is useful for:

  • Resource performance analysis
  • Workload assessment
  • Compliance checking
  • Training needs identification

Scenario: Your process uses document type codes where capitalization matters (e.g., "PO" for Purchase Order vs "po" for internal reference), and you need to find only cases with the official "PO" designation.

Settings:

  • Search Text: "PO"
  • Search Source: Cases
  • Filter Type: Case
  • Case Sensitive: Yes
  • Remove Filter: No

Result: The filter returns only cases where "PO" appears with exact capitalization in case attributes, excluding cases with "po", "Po", or "pO".

Insights: Case-sensitive searching ensures precision when your data uses capitalization for semantic distinction, preventing false matches from similar but different values.

Output

The filter returns a filtered dataset based on your settings:

  • When Filter Type = Case: Returns complete cases (with all their events) where the search text was found in at least one attribute
  • When Filter Type = Event: Returns only the individual events that match the search criteria
  • When Remove Filter = Yes: Inverts the logic, returning cases/events that do NOT match the search criteria

The search automatically adapts based on the data type of your search text:

  • Text strings: Searches all text columns using partial matching (contains)
  • Integers: Searches integer, decimal, and text columns
  • Decimals: Searches decimal and text columns
  • Booleans: Searches boolean, decimal, and text columns
  • Dates/Times: Searches text columns only

Technical Notes

  • Filter Type: Can operate at case level or event level depending on settings
  • Performance: Optimized with automatic data type detection and targeted column selection
  • Search Behavior: Uses "contains" matching for strings, allowing partial matches
  • Null Handling: Null values are ignored and never match any search text
  • Data Type Detection: Automatically converts search text to the most appropriate data type for optimal matching
  • Column Selection: Intelligently selects which columns to search based on detected data type

This documentation is part of the mindzieStudio process mining platform.

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