Dynamic Inquiry UI for Low-Code Instance Data Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems require significant development resources to create self-service user interfaces for updating application instance data, and they fail to dynamically determine suitable fields for updating based on the current situation, limiting access to non-application users.

Innovation Solution

A low-code extension mechanism that generates a generic inquiry system allowing non-application users to update instance data through automated processes, using a generic infrastructure and automatically-generated content, facilitating efficient data updates across various object types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If self-service user interfaces are developed individually for each object type, then users can modify instance data, but significant development resources are required

Engineering Contradiction:
Improveself-service data modificationVSAvoiddevelopment resources
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a universal self-service user interface framework that can be applied across multiple object types without requiring individual development for each type. The system uses a generic infrastructure with configurable components that automatically adapt to different object types, eliminating the need to build separate interfaces for each object type while maintaining full functionality for data modification.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If self-service user interfaces are provided for non-application users, then data accessibility is improved, but infrastructure and access management must be implemented

Engineering Contradiction:
Improveaccess to non-application usersVSAvoidinfrastructure and processes
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary framework that enables non-application users to access and modify instance data without requiring direct integration into the application's core infrastructure. The system uses a configurable self-service interface layer that acts as a mediator between external users and the application's data management systems, providing controlled access while avoiding the complexity of building custom infrastructure for each user type.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If all fields of an instance are made accessible for updating, then user convenience is improved, but security and relevance are reduced

Engineering Contradiction:
Improvefield accessibilityVSAvoidsecurity and relevance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements local quality control by selectively enabling or disabling access to specific fields based on user roles, object types, and contextual conditions. The system allows different sets of fields to be accessible depending on the user's authorization level and the specific object being modified, ensuring that only relevant and secure fields are exposed to each user type rather than exposing all fields universally.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12487996B2Low-development system for dynamic information queries
Publication Date: 2025.12.02 SAP SE
  • US12487996B2 patent drawing
  • US12487996B2 patent drawing
  • US12487996B2 patent drawing

AI summary

Systems and methods include reception of an instruction to initiate an inquiry associated with a first instance of a first object type, querying of a system for object metadata defining a plurality of fields of the first object type, generation of a first user interface presenting one or more of the plurality of fields, reception of user input to the first user interface, the user input specifying a first one or more fields of the presented one or more of the plurality of fields, generation of the inquiry specifying the first one or more fields and the first instance, transmission of the inquiry, reception of a response to the inquiry including data associated with the first one or more fields and the first instance, and instructing of a system to update the data associated with the first instance of the first object type based on the received data associated with the first one or more fields and the first instance.