Dynamic Metadata Repository for Web Service Input Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Dynamic backend systems with changing metadata definitions pose challenges for web service input calls, as current methods require timely updates and are often cumbersome, especially when dealing with multiple languages and new or expanded data values.

Innovation Solution

A computerized method that obtains a list of code value and code description pairs from a repository, allowing for exact or partial matching of inputs, with contextual help provided for ambiguous matches, enabling validation and association of inputs with corresponding code values without requiring specific pre-knowledge of allowed values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If metadata is updated timely to reflect backend system changes, then data access correctness is improved, but system complexity and maintenance effort increase

Engineering Contradiction:

Improvedata access correctnessVSAvoidmetadata update complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically retrieves updated metadata from the backend system through web service calls and updates the metadata repository without requiring manual intervention. This self-updating mechanism eliminates the need for developers to manually track and update metadata when backend systems change, reducing maintenance complexity while ensuring data access correctness.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system establishes a feedback loop where the web service continuously queries the backend system for metadata changes and updates the repository accordingly. This automated feedback mechanism ensures that the metadata repository always reflects the current backend system state, maintaining reliability without increasing manual maintenance effort.

Inventive Principle:

Principle #23Feedback

2Manufacturing precision

If developers manually update metadata for dynamic backend systems, then data structure accuracy is improved, but time consumption and operational difficulty increase

Engineering Contradiction:

Improvedata structure accuracyVSAvoidmetadata update time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically retrieving and storing metadata from the backend system before it is needed for data access. The metadata repository is proactively updated with the latest data structure information, so when applications need to access data, the accurate metadata is already available without requiring time-consuming manual updates.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The manual mechanical process of developers updating metadata is replaced with an automated electronic system that uses web services to retrieve and update metadata programmatically. This substitution eliminates the time-consuming manual effort while maintaining data structure accuracy through automated synchronization with the backend system.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If the system supports multiple languages and dynamic data values, then system versatility is improved, but complexity of managing allowed inputs increases

Engineering Contradiction:

Improvemulti-language supportVSAvoidinput validation complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The metadata repository serves as a universal mechanism that handles multiple languages and dynamic data values through a single standardized structure. By storing code descriptions and allowed values in the metadata repository, the system achieves multi-language support and adaptability to changing data requirements without creating separate validation mechanisms for each language or data type, thus avoiding increased complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Stability of the object's composition

If the web service is created with a fixed list of allowed inputs, then system stability is improved, but adaptability to new values decreases

Engineering Contradiction:

Improvesystem stabilityVSAvoidsupport for new values

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system transitions from a static, fixed list of allowed inputs to a dynamic metadata repository that automatically updates with new values from the backend system. The web service queries the metadata repository at runtime to obtain the current list of allowed inputs, enabling the system to adapt to new values while maintaining stability through consistent validation mechanisms. This dynamic approach allows the system composition to evolve without requiring code changes.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10402243B2Input analysis for dynamic data object definitions

Publication Date: 2019.09.03 SAP SE

AI summary

Techniques are described for generically providing a solution to developers in supporting web service input calls to systems with dynamic definitions. An example method includes obtaining, from a repository, a list of code value and code description pairs associated with the particular data type. The obtained list is searched for a particular code description matching the string value of the identified input. In response to identifying a particular code description exactly matching the string value of the identified input, the string value of the identified input is associated to the particular code value corresponding to the particular code description. The particular backend application is then executed based on the particular code value associated with the string value of the identified input.