Client Experience Framework Table Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large tables with hundreds, thousands, or millions of records in client applications cause performance issues such as slow load times, browser crashes, and difficulties with filtering and sorting functionalities, leading to suboptimal user experience.

Innovation Solution

Implementing a client experience framework that utilizes lazy loading, preview versions with links to list reports, and tab navigation to manage large datasets, allowing users to interact with a subset of data while preserving filtering and sorting capabilities without loading the entire dataset, thereby enhancing performance and user interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire dataset is loaded into the table, then complete data is available for viewing and interaction, but performance deteriorates with slow load times, browser crashes, and difficulties with filtering and sorting

Engineering Contradiction:
Improveapplication performanceVSAvoiddataset size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent divides the large dataset into multiple smaller subsets using pagination, where only the current page's data is loaded and displayed in the table. Users can navigate between pages to access different portions of the complete dataset, avoiding the need to load all data simultaneously and thus preventing performance degradation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements lazy loading where only the necessary portion of the dataset (current page) is loaded into memory and displayed, rather than loading the entire dataset. This partial action approach ensures that filtering and sorting operations are performed on smaller data subsets, maintaining application performance and stability.

Inventive Principle:
Principle #16Partial or excessive action

2Adaptability or versatility

If filtering and sorting functionalities are applied to large datasets, then data manipulation capabilities are enhanced, but performance deteriorates due to processing overhead

Engineering Contradiction:
Improvedata manipulation capabilityVSAvoidprocessing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the large dataset into smaller paginated subsets, allowing filtering and sorting operations to be applied only to the current page's data rather than the entire dataset. This segmentation dramatically reduces processing overhead while maintaining full data manipulation capabilities for each subset.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies filtering and sorting functionalities only to the visible subset of data (current page) rather than the complete dataset. This partial action approach preserves data manipulation versatility while significantly improving processing efficiency by operating on smaller data volumes.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If the table displays all records, then complete information is provided to users, but user experience deteriorates due to slow load times and browser crashes

Engineering Contradiction:
Improvedata completenessVSAvoiduser experience
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent segments the complete dataset into multiple paginated views, allowing users to access all records through page navigation while only loading a manageable subset in each view. This approach maintains data completeness for user access while preventing browser crashes and improving responsiveness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent loads only the necessary portion of data (current page) into the table display, providing users with immediate access to relevant information without the performance penalty of loading the entire dataset. Users can navigate to other pages to access additional data, maintaining overall data completeness while enhancing user experience.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11386264B2Configuring complex tables in a client experience framework
Publication Date: 2022.07.12 SAP SE
  • US11386264B2 patent drawing
  • US11386264B2 patent drawing
  • US11386264B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for displaying object pages containing data displayed in tables in a client application. The client application may provide a user experience framework via which an administrator may pre-configure the behavior of object pages that display data related to the application in table form. A table may be configured to display using lazy loading, tab navigation, or a preview version to list report based on the nature and expected size of the table. When preview version to list report is chosen, a preview version of a table may be provided to a user to allow the user to interact with the data without displaying the entirety of the dataset.