Dynamic Multi-Model Node Table Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional two-tiered client-server architectures are inefficient and brittle, especially in large enterprises, due to tight coupling of business logic, presentation logic, and user interface, making it difficult to maintain and update applications dynamically.

Innovation Solution

A system and method for dynamically configuring a table with data from multiple model nodes, allowing users to select and add attributes from various nodes as columns, with configuration data stored separately from system data storage, enabling flexible and scalable multi-tiered architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If business logic, presentation logic and user interface logic are tightly coupled in client-side code, then the application can be implemented with a simple two-tiered architecture, but the client-side code becomes very brittle and difficult to maintain when business rules change frequently

Engineering Contradiction:
Improvearchitecture complexityVSAvoidmaintainability
Core Design Contradiction:
Device complexityVSEase of repair

Solution Approach 1:

The patent segments the monolithic client-side application into distinct modular components: user interface components, presentation logic components, and business logic components. Each component is independently configurable and can be updated without affecting the others, resolving the brittleness issue while maintaining architectural simplicity through controlled complexity management.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If business logic is changed frequently in response to changing business rules, then the application remains adaptable to new requirements, but updating client-side applications on a large number of different clients becomes a difficult task

Engineering Contradiction:
ImproveadaptabilityVSAvoidupdate time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic configuration capabilities where business logic components can be modified and reconfigured without requiring full client-side application updates. The system allows runtime configuration changes and incremental updates, enabling frequent business rule changes while minimizing deployment time and effort across multiple clients.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If configuration data is stored in system data storage with program code and data, then data management is simplified, but the system lacks flexibility for dynamic configuration and personalization

Engineering Contradiction:
Improvedata management complexityVSAvoidconfiguration flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent extracts configuration data from the system data storage and separates it into dedicated configuration storage mechanisms. This allows configuration data to be managed independently from program code and system data, enabling dynamic configuration changes, user personalization, and flexible table column customization without affecting core system operations or requiring system-wide updates.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8589394B2System and method for dynamically configuring a multi-model node table
Publication Date: 2013.11.19 SAP SE
  • US8589394B2 patent drawing
  • US8589394B2 patent drawing
  • US8589394B2 patent drawing

AI summary

A system and method are described for dynamically generating a table containing data from multiple model nodes. For example, a computer-implemented method according to one embodiment of the invention comprises: displaying a plurality of attributes from multiple different nodes of an application; providing a user interface allowing a user to select attributes from the plurality of attributes to be displayed as columns within a table; receiving an identification of a set of attributes within the plurality of attributes selected by the user; and storing the identification of the set of attributes as configuration data within local data storage, the local data storage being separate from a system data storage in which program code and data for the application is maintained.