Advanced Filtering with Conditions

Advanced

How to create complex filter conditions to precisely control which elements are visible in the Model Navigator.

Beyond simple search, Metapad's filter system supports complex conditions for precisely controlling which elements are visible.

Basic Filter Conditions

  1. Open the Filters area in the Model Navigator
  2. Click Add Condition
  3. Configure:
    • Field: Which property to filter on (label, description, or any custom property)
    • Operator: How to match (equals, contains, starts with, greater than, etc.)
    • Value: The value to match against
  4. The Model Navigator updates immediately to show only matching elements

Combining Conditions

You can combine multiple conditions:

  • AND (all conditions must match): Use when you need elements that satisfy every criterion
  • OR (any condition can match): Use when you want elements that satisfy at least one criterion

Toggle between AND/OR using the combinator control.

Filter by Type

  • Add a type condition to show only specific Node Types
  • Example: Show only "Server" and "Application" nodes, hiding everything else

Filter by Property Value

  • Filter on any property defined on a Node Type
  • Example: Show only servers where "status" equals "active"
  • Example: Show only requirements where "priority" is greater than 3

Filter by Relationship

A Relationship condition looks at how an element is connected, not at its own fields. Click + Add condition, choose Relationship, and set:

  • has a relationship or has no relationship
  • the relationship type, or of any type
  • the direction: outgoing (it points to …), incoming (… points to it) or in either direction
  • what is at the other end: with any element, with an element of type (pick a type), with a specific element (pick the type, then the element), or with an element matching filter (pick a saved filter)

Examples:

  • Every task in this release: has a relationship ships in, outgoing, with a specific element: the release.
  • Requirements nobody implements yet: of type Requirement, and has no relationship implements, incoming, with any element.
  • Two steps away: save the inner condition as its own filter (say, Concepts on the roadmap) and target it with with an element matching filter.

Saving and Reusing Filters

  • Filter configurations persist within your session
  • Clear all filters to return to the unfiltered view

Tips

  • Start with broad filters and narrow down
  • Combine type filters with property filters for precise results
  • Filters affect only the Model Navigator — the canvas shows whatever is on the active diagram
  • Use filters to create focused views for specific tasks (e.g., "show me all critical, unresolved items")

This content was written collaboratively with AI.