- 8 minutes to read

Advanced Filters, Saved Searches & Performance

Complete reference for Mapify's advanced search capabilities — filter operators, saved searches, syntax examples, search UI components, and performance optimization for enterprise-scale deployments.

Advanced Filter Syntax

Power users can combine search terms with filter operators for precise queries.

Filter Operators

Operator Description Example
type: Filter by entity type type:integration SAP
owner: Filter by owner name or team owner:john type:service
status: Filter by monitoring status status:active Finance
tag: Filter by compliance/custom tags tag:GDPR tag:Production
domain: Filter by domain name domain:Finance SAP
protocol: Filter by communication protocol protocol:REST API
modified: Filter by last modified date modified:7d owner:john
created: Filter by creation date created:30d type:integration

Date Filter Syntax

Use relative or absolute dates:

  • Relative: 7d (7 days), 2w (2 weeks), 3m (3 months), 1y (1 year)
  • Absolute: 2026-01-01 (ISO format), 2026-01 (month), 2026 (year)
  • Range: created:2025-01-01..2025-12-31

Boolean Operators

Combine filters with logical operators:

  • AND (default): SAP Finance (both terms required)
  • OR: SAP OR Salesforce (either term matches)
  • NOT: SAP NOT Finance (exclude matches)
  • Grouping: (SAP OR Salesforce) AND tag:GDPR

Complex Query Examples

Find all GDPR-regulated SAP integrations modified in last 30 days:

tag:GDPR type:integration SAP modified:30d

Find REST or SOAP services in Production domain with active status:

(protocol:REST OR protocol:SOAP) domain:Production status:active

Find database resources created in 2025 with unassigned owners:

type:database created:2025 owner:unassigned

Find integrations with a specific custom metadata value:

type:integration CostCenter:12345

Saved Searches Feature

Saved searches store frequently used queries for one-click re-execution. Common use cases:

  • Recurring compliance audits – tag:GDPR modified:7d (weekly GDPR check)
  • Team dashboards – owner:"Sales Team" status:active
  • Incident response – status:error modified:1d (recent failures)
  • Architecture reviews – type:integration domain:Finance protocol:SOAP (legacy SOAP)

Saved Search Workflow

graph TD A[User Enters Search Query] --> B[Apply Filters and Execute] B --> C{Results Satisfactory?} C --> |No| A C --> |Yes| D[Click Save Search Button] D --> E[Enter Search Name and Description] E --> F{Set Visibility} F --> |Personal| G[Save to User Profile] F --> |Shared| H[Save to Team Workspace] G --> I[Search Appears in My Saved Searches Dropdown] H --> J[Search Appears in Team Saved Searches Dropdown] I --> K[One-Click Re-Execution Anytime] J --> K

Diagram: Workflow from entering a search query to saving and reusing it as a one-click saved search.

Saved Search Data Structure 

{
  "searchId": "550e8400-e29b-41d4-a716-446655440000",
  "searchName": "Weekly GDPR Compliance Check",
  "searchDescription": "All GDPR-regulated entities modified in last 7 days",
  "searchQuery": "tag:GDPR modified:7d",
  "createdBy": "john.smith@company.com",
  "createdDate": "2026-01-19T10:30:00Z",
  "lastExecuted": "2026-01-19T14:22:00Z",
  "executionCount": 47,
  "visibility": "shared",
  "sharedWith": ["compliance-team", "finance-team"],
  "schedule": {
    "enabled": true,
    "frequency": "weekly",
    "dayOfWeek": "monday",
    "time": "09:00",
    "emailResults": true
  }
}

Scheduled Saved Searches

Administrators can schedule saved searches to run automatically and email results:

  • Daily compliance checks – Run tag:GDPR status:error every morning at 8 AM
  • Weekly architecture reviews – Email protocol:SOAP domain:Finance results every Monday
  • Monthly capacity reports – Run type:system modified:30d on the first of each month

Configuration: Mapify > Search > Saved Searches > [Search Name] > Schedule Settings

Search Syntax Examples

Basic Search Examples 

SAP Finance

type:system CRM

protocol:REST API

Intermediate Search Examples 

owner:john.smith

modified:7d

tag:GDPR

Advanced Search Examples 

type:integration tag:GDPR owner:"Finance Team" modified:30d

(protocol:REST OR protocol:SOAP) domain:Production status:active

type:database created:2025 owner:unassigned

NOT owner:john.smith

type:integration CostCenter:12345

Search UI Elements

All search UI components use Font Awesome icons with full accessibility attributes.

<div class="mapify-search-container">
  <label for="global-search" class="visually-hidden">Search integrations, systems, services, and resources</label>
  <div class="search-input-wrapper">
    <i class="fas fa-magnifying-glass" aria-hidden="true"></i>
    <input
      type="search"
      id="global-search"
      name="globalSearch"
      placeholder="Search integrations, systems, services..."
      aria-autocomplete="list"
      aria-controls="search-results"
      aria-expanded="false"
      aria-describedby="search-help"
      autocomplete="off"
    >
    <button type="button" class="clear-search" aria-label="Clear search" hidden>
      <i class="fas fa-xmark" aria-hidden="true"></i>
    </button>
  </div>
  <span id="search-help" class="help-text">
    Try: "type:integration SAP" or "owner:john status:active"
  </span>
</div>

Autocomplete Dropdown 

<ul id="search-results" role="listbox" aria-label="Search results" hidden>
  <li role="option" aria-selected="false" data-entity-id="123">
    <div class="result-icon">
      <i class="fas fa-diagram-project" aria-hidden="true"></i>
    </div>
    <div class="result-content">
      <div class="result-title">
        <strong>Salesforce CRM Integration</strong>
        <i class="fas fa-star" aria-hidden="true" title="Recently accessed"></i>
      </div>
      <div class="result-metadata">
        <span class="entity-type">Integration</span>
        <span class="separator">•</span>
        <span class="owner">Owner: Sales Team</span>
        <span class="separator">•</span>
        <span class="status">
          <i class="fas fa-circle-check" aria-hidden="true"></i>
          Active
        </span>
      </div>
    </div>
  </li>
</ul>

Saved Searches Dropdown 

<div class="saved-searches-menu">
  <button
    type="button"
    class="btn-saved-searches"
    aria-label="Open saved searches menu. Currently 8 saved searches available."
    aria-haspopup="true"
    aria-expanded="false"
  >
    <i class="fas fa-clock-rotate-left" aria-hidden="true"></i>
    Saved Searches
    <i class="fas fa-caret-down" aria-hidden="true"></i>
  </button>

  <div class="saved-searches-dropdown" role="menu" hidden>
    <div class="dropdown-section">
      <h3 class="dropdown-heading">My Saved Searches</h3>
      <button type="button" role="menuitem" data-search-id="550e8400">
        <i class="fas fa-magnifying-glass" aria-hidden="true"></i>
        Weekly GDPR Compliance Check
        <span class="search-count">(23 results)</span>
      </button>
    </div>

    <div class="dropdown-divider"></div>

    <div class="dropdown-section">
      <h3 class="dropdown-heading">Team Saved Searches</h3>
      <button type="button" role="menuitem" data-search-id="770ea622">
        <i class="fas fa-magnifying-glass" aria-hidden="true"></i>
        Recent Failures
        <span class="search-count">(3 results)</span>
      </button>
    </div>

    <div class="dropdown-divider"></div>

    <button type="button" class="btn-manage-searches" role="menuitem">
      <i class="fas fa-gear" aria-hidden="true"></i>
      Manage Saved Searches
    </button>
  </div>
</div>

Performance Considerations

Mapify search is optimized for enterprise-scale deployments with 10,000+ entities.

Performance Optimization Strategies

Strategy Implementation Benefit
**Indexed Search** Full-text indexing on all searchable fields (SQL Server FTS or Elasticsearch) Sub-second search response for 100,000+ entities
**Client-Side Caching** Cache search index in browser localStorage (max 5,000 entities) Instant autocomplete for frequently accessed entities
**Pre-Filtered Results** Apply domain/owner filters before fuzzy matching Reduces search space by 70-90% for most queries
**Lazy Loading** Load top 50 results initially, fetch more on scroll Improves perceived performance for broad queries
**Query Debouncing** Wait 300ms after last keystroke before executing search Prevents server overload during fast typing
**Result Compression** Compress search results before sending to client (gzip) Reduces network bandwidth by 60-80%

Client-Side vs Server-Side Search Trade-Offs

Approach Pros Cons Best For
**Client-Side** Instant autocomplete, works offline, reduces server load Limited to ~5,000 entities, requires full data download, no real-time updates Small to medium deployments (<5,000 entities)
**Server-Side** Scales to millions of entities, real-time data consistency, advanced filtering Network latency (50-200ms typical), requires persistent connection Enterprise deployments (>5,000 entities)
**Hybrid (Recommended)** Client-side for autocomplete, server-side for complex queries More complex implementation, requires cache invalidation logic Most production environments

Search Performance Benchmarks

Expected performance targets:

  • Autocomplete response: <100ms for 10,000 entities
  • Simple search (1-2 terms): <200ms for 50,000 entities
  • Complex filter query: <500ms for 100,000 entities
  • Fuzzy search: <1 second for 100,000 entities
  • Saved search execution: <2 seconds for queries with aggregations

Note: Run Mapify > Diagnostics > Search Performance Test to benchmark your specific environment.

Next Steps