Saved Views – Save, Share & Restore Custom Graph Configurations

^{New .7.x}

Saved Views (also called Node Formations) in Nodinite Mapify enable you to save specific graph configurations—including filters, layouts, zoom levels, and entity selections—so you can instantly return to the same view later. Whether you're conducting monthly compliance audits, preparing stakeholder presentations, or analyzing recurring patterns, Saved Views eliminate the need to recreate complex filters every session.

Saved Views support both personal views (private to your account) and shared views (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.

Why use Saved Views?

• 40% faster analysis – Skip manual filter recreation; load saved configurations in one click
• Team collaboration – Share standardized views across departments for consistent reporting
• Recurring workflows – Perfect for monthly audits, compliance checks, and stakeholder presentations
• Audit readiness – Maintain compliance-specific views (GDPR, SOX, HIPAA) for regulatory reviews
• Knowledge sharing – New team members can learn system architecture by exploring pre-configured views
• Executive presentations – One-click access to business-friendly visualizations

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

What is a Saved View?

A Saved View is a snapshot of your current Mapify configuration, including:

• Active filters – Entity types, domains, owners, compliance tags, date ranges
• Graph layout – 2D or 3D visualization mode, node positioning, zoom level, camera angle
• Selected entities – Specific Agents, Applications, Resources, Services, or Integrations to display
• Visual settings – Node colors, edge visibility, label display preferences
• Metadata – View name, description, creator, creation date, last modified date

When you load a Saved View, Mapify instantly reconstructs the exact graph configuration you saved—no manual adjustments needed.

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

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

• Switch to 2D layout 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.
• 3D layouts: 3D visualizations with 1,000+ nodes may impact performance on older hardware. Use 2D for presentations.
• 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. Use 2D layout instead of 3D.

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