Selective Draft Saving for Business Data Fields

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face performance issues and high operational costs due to the need to temporarily save attributes for all data fields in applications, especially when not all entities require draft enablement, and legacy systems may not support selective draft saving, leading to inefficient data handling and user interface constraints.

Innovation Solution

Implementing a system that selectively enables draft attribute saving for specific entities, generating metadata to determine which fields to save temporarily, and suppressing attempts to store attributes for non-draft-enabled fields, allowing for improved performance and reduced implementation efforts by only saving data based on business requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If draft attributes are saved for all data fields, then data loss is prevented and productivity is improved, but system performance deteriorates and operational costs increase

Engineering Contradiction:

Improvedata loss preventionVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the data model into entities and identifies which specific entities require draft enablement. Instead of enabling draft for all data fields, the system selectively enables draft only for entities that need it, thereby preventing data loss for critical data while avoiding the performance penalty of saving drafts for all fields.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies different draft-saving behaviors to different entities based on their specific requirements. Some entities are configured with draft enablement while others are not, allowing the system to optimize performance by applying the draft-saving mechanism only where necessary rather than uniformly across all data fields.

Inventive Principle:

Principle #3Local quality

2Duration of action of stationary object

If draft attributes are saved for all data fields, then data continuity is maintained, but network load increases and implementation complexity increases

Engineering Contradiction:

Improvedata continuityVSAvoidimplementation complexity

Core Design Contradiction:

Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The system segments the form into multiple entities and evaluates each entity's draft requirements independently. This segmentation allows the implementation to focus only on entities that need draft functionality, reducing the overall implementation complexity compared to enabling draft for all fields.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies draft enablement partially - only to the extent necessary for specific entities. This partial action approach maintains data continuity for critical entities while avoiding the excessive complexity of implementing draft functionality across the entire data model.

Inventive Principle:

Principle #16Partial or excessive action

3Reliability

If draft enablement is added for data fields requiring additional programming, then data protection is improved, but development effort and cost increase

Engineering Contradiction:

Improvedata protectionVSAvoiddevelopment effort

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The patent segments the data model into entities with different draft requirements. By identifying and enabling draft only for entities that need it, the system reduces the development effort required compared to adding draft enablement to all fields, while still providing adequate data protection for critical entities.

Inventive Principle:

Principle #1Segmentation

4Adaptability or versatility

If harmonizing data to legacy systems is implemented, then system compatibility is improved, but performance is affected and implementation cost increases

Engineering Contradiction:

Improvesystem compatibilityVSAvoidsystem performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the data model to identify entities that interface with legacy systems. By applying draft enablement selectively to only those entities that require it, the system maintains compatibility with legacy systems for necessary data while avoiding the performance degradation that would result from harmonizing all data fields.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11816424B2Conditional save of draft enabled business objects

Publication Date: 2023.11.14 SAP SE

AI summary

Disclosed herein are system, method, and computer program product embodiments selectively saving draft attributes. In some embodiments, a server generates a form comprising data fields. The server defines associated with the form. The server detects an event associated with the form. Each of the of data fields includes a respective attribute. The server identifies one or more of data fields that are to be draft-enabled in response to the event based on a definition of the event. The server further identifies at least one data field of the plurality of data fields for which draft-enablement is to be removed. The server generates metadata for the at least one data field removing the draft-enablement and stores a draft of each respective attribute for each of the plurality of data fields, excluding an attribute for the at least one data field in a data storage device.