Dashboard Switching via Shared Runtime and Caching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing application navigation mechanisms require users to close the current dashboard before switching, leading to increased memory consumption, load times, and loss of dashboard state, disrupting user workflow and satisfaction.

Innovation Solution

Implementing a common dashboard runtime that shares memory and data among dashboards, allowing seamless switching without reloading assets and preserving dashboard state through caching and shared data structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a new copy of dashboard is loaded on top of existing dashboard when switching, then dashboard switching is enabled, but memory consumption increases and load time increases

Engineering Contradiction:
Improvedashboard switching capabilityVSAvoidmemory consumption
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple dashboard instances into a single shared dashboard container in memory. Instead of creating separate dashboard copies for each instance, the system allows multiple dashboard views to share the same underlying data structures and assets, thereby reducing memory consumption while enabling seamless switching between dashboards.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary loading of dashboard assets and data into a shared cache before switching is needed. By pre-loading and caching dashboard content in the shared dashboard container, the system minimizes load times during actual dashboard switching operations, as the data is already prepared and available for immediate display.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If a new copy of dashboard is loaded on top of existing dashboard when switching, then dashboard switching is enabled, but load time increases due to re-execution of assets

Engineering Contradiction:
Improvedashboard switching capabilityVSAvoiddashboard load time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary loading of dashboard assets and data into a shared cache before switching is needed. By pre-loading and caching dashboard content in the shared dashboard container, the system minimizes load times during actual dashboard switching operations, as the data is already prepared and available for immediate display.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of copying entire dashboard instances including executed assets, the patent creates lightweight references to the shared dashboard container. The switching mechanism copies only the necessary view state and configuration data, while the actual dashboard assets and data remain shared, thereby avoiding redundant asset re-execution and reducing load times.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If existing navigation mechanism is used, then dashboard switching is possible, but dashboard state is not preserved

Engineering Contradiction:
Improvedashboard switching capabilityVSAvoiddashboard state
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent merges the state management of multiple dashboards into a unified system where the shared dashboard container maintains the state for all dashboard instances. When a dashboard is switched to, its state is restored from the shared container, preserving filters, selections, and other user interactions. This ensures that dashboard state is maintained across switching operations.

Inventive Principle:
Principle #5Merging (Combining)

4Quantity of substance

If user must close current dashboard before switching, then memory consumption is reduced, but user workflow is disrupted

Engineering Contradiction:
Improvememory consumptionVSAvoiduser workflow continuity
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent merges multiple dashboard instances into a single shared dashboard container in memory. Instead of creating separate dashboard copies for each instance, the system allows multiple dashboard views to share the same underlying data structures and assets, thereby reducing memory consumption while enabling seamless switching between dashboards without requiring users to close current dashboards.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements a dynamic dashboard switching mechanism where dashboards can be opened, closed, and switched between freely without rigid state management. The shared dashboard container dynamically manages the state of multiple dashboard instances, allowing users to navigate between dashboards in a flexible, workflow-friendly manner while maintaining memory efficiency.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11182056B2Application navigation
Publication Date: 2021.11.23 SALESFORCE INC
  • US11182056B2 patent drawing
  • US11182056B2 patent drawing
  • US11182056B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for quickly switching between multiple dashboards of an application. An embodiment operates by tracking changes made to a first dashboard of an application. The embodiment receives a selection for a second dashboard of the application. The embodiment stores a first data set and a first data state of the first dashboard in a cache. The embodiment removes the first dashboard from memory. The embodiment loads a second dashboard of the application into memory based on the selection. The embodiment then updates the second dashboard in the memory based on a second data set associated with the second dashboard and the shared data associated with a plurality of dashboards.