UI View Compatibility Checking for Data Dependency Errors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing user interface customization processes face issues where changes to a base user interface view can lead to errors or incorrect data presentation in newer views, especially when data items are deleted, without clear error indications.

Innovation Solution

Implementing a compatibility checking mechanism that employs two user interface models during design time and runtime, ensuring that changes to user interface views do not affect dependent views by tracking data dependencies and enforcing compatibility rules, thus preventing incompatible changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a newer user interface view is generated using an older interface view as a base, then the generation process is simplified and productivity is improved, but changes to the older interface view can adversely affect the newer interface view, causing errors or incorrect data presentation

Engineering Contradiction:
Improveuser interface generation efficiencyVSAvoiddata presentation accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary compatibility checking during the design time phase before the newer interface view is deployed. By analyzing dependencies between the older base view and the newer derived view in advance, the system identifies potential conflicts and prevents incompatible changes from being applied, thus ensuring data accuracy while maintaining generation efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism that monitors changes to the older interface view and automatically checks their compatibility with dependent newer views. When incompatible changes are detected, the system provides feedback to prevent the changes from being applied, thereby maintaining data presentation accuracy without compromising the ease of interface generation

Inventive Principle:
Principle #23Feedback

2Ease of manufacture

If data items are deleted from an older interface view, then the interface is simplified and maintenance is easier, but errors occur during execution or incorrect data is presented without clear error indications

Engineering Contradiction:
Improveinterface maintenance easeVSAvoiderror detection difficulty
Core Design Contradiction:
Ease of manufactureVSDifficulty of detecting and measuring

Solution Approach 1:

Before allowing deletion of data items from an older interface view, the system performs preliminary dependency analysis to check if any newer interface views depend on those data items. If dependencies exist, the deletion is blocked and a clear error message is displayed, preventing execution errors and making the conflict detectable before it causes problems

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides immediate feedback when a user attempts to delete a data item that is referenced by newer interface views. The feedback mechanism displays clear error messages indicating which newer views would be affected, making it easy to detect and correct the issue before it leads to execution errors or incorrect data presentation

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10067773B2Compatibility checking for user interface customization
Publication Date: 2018.09.04 SAP SE
  • US10067773B2 patent drawing
  • US10067773B2 patent drawing
  • US10067773B2 patent drawing

AI summary

Example embodiments of compatibility checking for user interface customization are described. In an example embodiment, a first user interface view including first data items is accessed, each of the first data items referencing a corresponding data item of a data source. Whether the first user interface view is referenced by a second user interface view is determined. Based on the first user interface view not being referenced by a second user interface view, changes to any of the first data items of the first user interface view are allowed during a design time of the first user interface view. Based on the first user interface view being referenced by the second user interface view, one or more of the first data items of the first user interface view being referenced by the second user interface view are identified, and changes to the identified data items are prevented.