Saved Maps (Saved Views) – Save, Share & Restore Custom Graph Reports

^{New .7.x}

Saved Maps (also called Saved Views or Node Formations) in Nodinite Mapify let you define a report-style graph once and re-run it later. You choose the filter logic, the entity scope, and the relation depth, then Mapify renders exactly what you asked for. This is different from the static rendering pages: Saved Maps require design work because you are deciding what to include before the graph is built.

Saved Maps support both personal maps (private to your account) and shared maps (accessible by your entire team), making them ideal for collaboration and standardization across distributed teams.

Example of Saved Views dropdown menu showing personal and shared views for quick access.

Example of the Saved Maps filter builder showing how nested conditions turn into a reusable report definition.

Why use Saved Maps?

• Save complete report context - Store your selected Items and Relations scope, nested AND/OR groups, depth, deleted-item handling, and display options as one reusable Mapify Map
• Rerun complex queries instantly - Reopen recurring analysis views without rebuilding filter combinations each time
• Standardize team reports - Share the same saved map across teams so everyone starts from the same graph and relation rules
• Duplicate and iterate safely - Clone an existing map, adjust filters, and save variants without overwriting the original baseline
• Keep large landscapes manageable - Use saved depth and relation settings to focus on relevant neighborhoods instead of the full graph
• Improve audit consistency - Keep named compliance maps so recurring audits open with identical scope and filter intent

Note: Saved Views require Mapify licensing. Contact Nodinite Sales to enable this feature.

What is a Saved Map?

A Saved Map is a reusable graph report definition, including:

• Active filters – Entity types, domains, owners, compliance tags, date ranges, and nested AND/OR groups
• Graph scope – Items, Relations, Include Deleted, Only with relations, Include Related, depth, and back-traversal settings
• Selected entities – Specific Agents, Applications, Resources, Services, or Integrations to display
• Visual settings – Node colors, edge visibility, label display preferences
• Metadata – Map name, description, creator, creation date, last modified date

When you load a Saved Map, Mapify renders the exact graph definition you saved. You are not choosing from a static snapshot; you are re-running the report logic against the current data.

Build Filters Like Log Views

Saved Maps use the same mental model as Log View filters. You pick a field type, combine conditions with AND and OR, and then apply the operator that fits the chosen field.

Example of the Mapify Type selector showing the field families you can filter against.

Choose a Mapify Type

The first step is selecting the field type. That choice determines which operators are available next.

Different field types expose different values and different comparison rules. That is why the operator list changes after you choose the field.

Combine Conditions with AND and OR

You can nest groups, just like Log Views, to build logic such as:

(Type = Integration OR Type = Service) AND (Owner = Finance Team OR Owner = Compliance Team)

This lets you group conditions around business meaning instead of flattening everything into one long filter line.

Pick the Operator for the Field Type

After you choose the field, Mapify shows the mathematical operators that fit that field.

Example of the mathematical operator selector showing values such as equals and not in for the selected field type.

The available operators depend on the chosen field type. For example, text fields and list fields do not behave the same way, so their operators are not identical.

Scope Options

Saved Maps do more than filter by field. They also control how much of the surrounding graph is included.

Items

Example of the Items selector showing that any Nodinite entity can be part of the saved map scope.

Items define which Nodinite entities are allowed to match. Use this when you want to display any and all entity types that meet the filter criteria.

Relations

Example of the Relations selector showing which relation paths are included in the saved map.

Relations define which links appear in the map. If you clear a relation path, Mapify can skip intermediate entries, so you may show A and Z while omitting the nodes in between.

Additional Scope Controls

• Include Deleted - show soft-deleted entities when you need to investigate historical data or removed relationships.
• Only with relations - only keep items that actually have at least one relation, which removes a lot of noise from large landscapes.
• Include Related - include related entities so the graph can expand beyond the initial matches.
• Depth - control how far Mapify should traverse when related entities are included.
• Allow back-traversal - include child associations when the selected item is the starting point, which can unfold many more relations.
• Search button - refresh the content after you adjust the filter logic or scope options.

Saved Maps are especially useful when the same reporting shape is needed repeatedly. The saved definition determines what the user sees every time the map is opened.

Personal vs Shared Saved Views

Common Use Cases

Compliance Audits

Scenario: Monthly SOX compliance audits to verify financial integrations meet regulatory requirements.

Solution: Create a Shared View "SOX Financial Integrations" filtering by Domain: Finance, Compliance Tags: SOX, Entity Types: Integrations and Services, Owner: Finance Team.

Benefit: Auditors load the view in one click, ensuring consistent scope every month.

Stakeholder Presentations

Scenario: Business stakeholders need monthly updates on integration health without technical jargon.

Solution: Create a Shared View "Executive Dashboard" showing high-level integrations only, color-coded by health status, grouped by domain.

Benefit: Executives see business-relevant information instantly.

Recurring Analysis

Scenario: Your team investigates SAP integration patterns weekly to identify optimization opportunities.

Solution: Create a Personal View "SAP Performance Analysis" filtering by System: SAP ERP and SAP CRM with metadata showing Response Time and Error Rate.

Benefit: Analysts start investigations immediately without manual configuration.

Team Onboarding

Scenario: New team members need to understand your integration landscape architecture.

Solution: Create Shared Views: "Architecture Overview" (all domains), "Sales Systems" (Sales domain + dependencies), "Critical Path Integrations" (mission-critical workflows).

Benefit: New hires explore pre-configured views, accelerating learning from weeks to days.

User Workflow

Workflow Steps

Creating a Saved View

1. Configure your graph – Apply filters, adjust layout, set zoom level, select entities
2. Click "Save View" ()
3. Enter view details: name (required), description (optional), visibility (Personal or Shared)
4. Confirm save – View appears in Saved Views dropdown

Loading a Saved View

1. Open Saved Views dropdown ( Saved Views)
2. Browse views: My Views (personal) or Shared Views (team-wide)
3. Click view name – Mapify instantly applies all saved settings

Updating a Saved View

1. Load the view, make your changes, click "Update View" (or "Save View" → "Overwrite existing")
2. Permission required: Only the original creator or administrators can update Shared Views

Deleting a Saved View

1. Open dropdown → hover over view → click → "Delete"
2. Permission required: Only the original creator or administrators can delete Shared Views

Designer Actions

The Mapify designer page provides the controls you use to work with saved maps.

• View map - navigate to the interactive view mode page for the current map.
• Add Map - create a new Saved Map.
• Duplicate - clone the existing map. The map must be pristine and have no pending changes before it can be cloned.
• Save - save the current map definition.

These actions are what make the page a report-definition tool rather than a static rendering page.

Example: Creating a GDPR Compliance Audit View

Step 1: Apply Filters

Domain: Customer Data, CRM, Marketing
Compliance Tags: GDPR, Personal Data, EU Region
Entity Types: Integrations, Services, Resources
Owner: Data Protection Team

Step 2: Adjust Layout

• Set the graph position and zoom for clarity
• Group by Domain to show organizational structure
• Color-code by compliance status: Green = Compliant, Yellow = Review Needed, Red = Non-Compliant

Step 3: Save

Name: GDPR Compliance Audit Q1 2026
Description: Quarterly GDPR audit covering Customer Data, CRM, and Marketing integrations.
Visibility: Shared (accessible by Data Protection Team and Auditors)

Every quarter, auditors open Mapify, select "GDPR Compliance Audit Q1 2026" from Shared Views, and immediately see the current compliance status.

Technical Specifications

The Saved Views data structure is a JSON schema stored as a database record. Key technical aspects:

• Data structure: JSON object with required fields (viewId, viewName, createdBy, visibility, filters, layout, schemaVersion) and optional fields (description, selectedEntities, sharedWith, tags, isFavorite)
• Storage: Recommended: database storage (SQL Server MapifyViews table) with soft deletes, REST API access, and client-side session caching
• Schema versioning: Semantic versioning ("1.0.0") with backward compatibility rules and automatic MINOR migrations
• Conflict resolution: Optimistic locking via lastModifiedDate comparison; conflicts show user options to reload or save as new view
• Performance targets: <100ms to list 1,000 views, <300ms to save a new view

For complete JSON schemas, SQL database schema, API endpoint definitions, versioning migration examples, and conflict resolution code, see Technical Specifications.

UI/UX Patterns

The Saved Views interface provides fast, accessible access from the Mapify toolbar:

• Desktop: Dropdown panel from toolbar (search box → favorites → personal → shared → action footer)
• Tablet: Side panel slides in from right
• Mobile: Full-screen modal with collapsible sections and touch-friendly 44×44px targets
• Keyboard shortcuts: Ctrl + S to save, Ctrl + O to open, Arrow keys to navigate, Esc to close
• Accessibility: Full WCAG 2.1 AA compliance — ARIA roles, screen reader announcements via aria-live, visible focus indicators
• Error handling: Specific error messages with recovery actions for network failures, deleted views, and concurrent edit conflicts
• Loading states: Inline spinners, progress dialogs for large renders, toast notifications for confirmations

For complete HTML examples, keyboard shortcut reference, accessibility implementation, loading state patterns, and responsive CSS, see UI/UX Patterns.

Naming Conventions

Establish organizational naming conventions to maintain consistency:

Personal Views:

[Your Initials] - [Purpose] - [Date/Version]
Examples:
  JD - SAP Analysis - 2026-01
  MK - Quick Debug - v2

Shared Views:

[Category] - [Purpose] - [Period/Version]
Examples:
  Compliance - GDPR Audit - Q1 2026
  Executive - Monthly Dashboard - 2026-01
  Onboarding - Architecture Overview - v3

Benefits: Alphabetical sorting groups views by category; clear purpose reduces duplicates; version tracking prevents outdated views.

Best Practices

• Name views descriptively – Use "SOX Financial Audit Q1 2026" instead of "My View 1"
• Add descriptions – Explain purpose and context for team members who didn't create the view
• Review periodically – Delete outdated personal views to reduce clutter
• Standardize shared views – Establish naming conventions and governance
• Use personal views for experiments – Test filter combinations before sharing with the team
• Version shared views – Use version numbers (v1, v2) or dates for evolving views
• Avoid over-sharing – Keep personal experimental views private to reduce noise

Performance Considerations

• Large datasets: Views with 10,000+ entities may take 3–5 seconds to load. Optimize by filtering to essential entities.
• Complex filters: Views with 10+ active filters are slower to apply. Combine related filters or use custom metadata tags.
• High edge density: Dense relation graphs can become harder to read. Use depth limits and relation filters to keep views focused.
• Concurrent users: Shared Views are read-only during loading to prevent conflicts.

Troubleshooting

Issue: Saved View not appearing in dropdown
Solution: Refresh Mapify or check permissions. Shared Views require appropriate team membership.

Issue: View loads but filters don't match expected results
Solution: Entities may have been deleted or modified since the view was saved. Update the view with current filters.

Issue: Cannot update Shared View
Solution: Only the original creator or administrators can update Shared Views. Save your changes as a new Personal View.

Issue: View loads slowly
Solution: Reduce entity count with more specific filters. Lower depth and narrow relation scope for faster rendering.

Next Steps

• Technical Specifications – JSON schema, storage, versioning, conflict resolution
• UI/UX Patterns – Dropdown, shortcuts, accessibility, mobile
• Search and Discovery
• Ownership and Team Management

Related Topics

• Mapify Overview
• Repository Model
• Custom Metadata
• Multi-User Collaboration