Tailored Object Layer for UI Event Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In Service-Oriented Architecture (SOA) environments, user interface scenarios face challenges in representing and supporting success or error messages, copy or paste, and save or load draft operations, as business objects are not designed to handle these features, leading to issues with error message aggregation and field display management.

Innovation Solution

The introduction of an intermediate object layer that handles user interface messages and retrieves data from business objects, integrating with a service layer to provide a tailored object layer that supports user interface events and data display without impacting the underlying business objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If business objects are used directly in user interface scenarios, then the underlying business object design remains simple and unchanged, but user interface features such as error message aggregation, copy paste, and save load draft cannot be properly supported

Engineering Contradiction:

Improveuser interface scenario supportVSAvoidbusiness object design complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a tailored object as an intermediary layer between the user interface and business objects. The tailored object contains reference information to business object nodes and handles user interface-specific operations (error message aggregation, copy paste, save load draft) without modifying the underlying business object design. This mediator approach allows the system to support complex UI scenarios while keeping business objects simple and unchanged.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If business objects are modified to support user interface features, then user interface scenarios can be properly represented, but the design of underlying business objects is impacted and altered

Engineering Contradiction:

Improveuser interface scenario supportVSAvoidbusiness object design stability

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The tailored object serves as a stable intermediary that absorbs all user interface-related modifications. It contains reference information pointing to business object nodes but maintains its own structure for handling UI features. This ensures business object design stability while enabling UI scenario adaptability through the tailored object layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct layers: business objects for core data and logic, tailored objects for UI-specific handling, and user interfaces for interaction. This segmentation allows each layer to evolve independently, maintaining business object stability while enabling UI feature additions through the tailored object layer.

Inventive Principle:

Principle #1Segmentation

3Reliability

If multiple business objects raise error messages independently, then each business object can report its own errors, but aggregation of error messages for user display becomes impossible

Engineering Contradiction:

Improveerror reporting accuracyVSAvoiderror message aggregation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The tailored object merges multiple error messages from different business objects into a single aggregated error message for user display. It maintains references to individual business object errors for accuracy but combines them into a unified presentation, resolving the contradiction between reliable error reporting and manageable error aggregation.

Inventive Principle:

Principle #5Merging (Combining)

4Loss of information

If all fields from business objects are transported to user interface, then complete data is available for display, but memory resource management of client systems and networks is affected

Engineering Contradiction:

Improvedata completenessVSAvoidmemory and network resource consumption

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

The tailored object extracts only the specific field information needed for user interface display from the complete business object data. It contains reference information to business object nodes but selectively presents only necessary fields to the user interface, reducing memory and network resource consumption while maintaining data completeness for displayed fields.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7877695B2Tailored object

Publication Date: 2011.01.25 SAP SE

AI summary

A system for managing user interface events in user interface of a client system. The system includes a service layer including a business object. The system also includes an intermediate object layer comprising an intermediate object associated with the business object, wherein the intermediate object handles user interface messages raised by the business object and retrieves data from the business object for user interface. The system further includes a service manager that provides the retrieved data from the intermediate object for display on the user interface.