Graphical API Form Mapping for Auto-Filled Dependent Fields

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods require development and deployment of code by skilled developers to map related form fields, which is costly, time-consuming, and cumbersome, and cannot be immediately adapted to on-the-fly changes.

Innovation Solution

A method and electronic device that allows users to graphically configure an API on form fields using building blocks, mapping dependent fields and automatically filling them based on received attributes without requiring code development or deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If code development and deployment is performed to map related form fields, then form field mapping functionality is achieved, but the process becomes costly and time-consuming

Engineering Contradiction:
Improveease of form field mapping configurationVSAvoidtime required for code development and deployment
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent replaces the mechanical system of code development and deployment with a graphical configuration system. Users can map form fields by visually configuring relationships through a user interface, eliminating the need for programmers to write and deploy code. This substitution transforms a technical development process into a user-friendly configuration process, directly resolving the contradiction between ease of configuration and time consumption.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables form field mapping through self-service configuration capabilities. Non-technical users can independently define relationships between form fields using graphical interfaces without requiring developer intervention. The system provides tools for users to autonomously configure API connections, map dependent fields, and manage form field relationships, thereby eliminating the time loss associated with professional code development and deployment.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If code development is performed to map form fields, then form field mapping functionality is achieved, but the process becomes cumbersome and requires skilled developers

Engineering Contradiction:
Improveease of form field mapping configurationVSAvoidcomplexity of development and deployment process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent replaces the complex mechanical system of code development with a simplified graphical configuration interface. Instead of requiring users to write, test, and deploy programming code, the system provides visual tools for configuring form field mappings. Users can define relationships between form fields through intuitive graphical elements, eliminating the cumbersome development process and reducing the skill level required from professional programming expertise to basic user configuration capabilities.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system introduces an intermediary graphical configuration layer between the user and the underlying form field mapping functionality. This intermediary interface translates user-friendly graphical configurations into the necessary system operations, shielding users from technical complexity while enabling form field mapping. The graphical interface acts as a mediator that simplifies the interaction required to achieve form field relationships without exposing users to code development complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If code development is performed to map form fields, then form field mapping functionality is achieved, but changes cannot be made immediately on the fly

Engineering Contradiction:
Improveadaptability to on-the-fly changesVSAvoidtime required for code deployment
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic configuration capabilities that allow form field mappings to be changed in real-time without requiring code redeployment. The graphical configuration system enables users to modify API connections, map dependent fields, and adjust form field relationships dynamically. Changes are applied immediately to the running system, providing adaptability to on-the-fly requirements while eliminating the time loss associated with code development cycles and deployment processes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables preliminary configuration of form field mappings through graphical interfaces before actual data processing occurs. Users can pre-configure API connections and field relationships in advance, and these configurations are applied immediately without requiring subsequent code deployment. This preliminary action capability allows the system to adapt to changing requirements instantly while avoiding the time-consuming iterative process of code development and deployment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12474899B2Method and electronic device for retrieving output on form fields from user interface
Publication Date: 2025.11.18 RAKUTEN SYMPHONY INC
  • US12474899B2 patent drawing
  • US12474899B2 patent drawing
  • US12474899B2 patent drawing

AI summary

Embodiment herein provides a method for graphically configuring an application programming interface (API) on form field to retrieve desired output from user interface (UI) by an electronic device. The method includes displaying, by the electronic device, the UI including form fields to configure the API on the form fields and configuring, by the electronic device, the API to the form field by inputting building blocks using a graphical configuration field. The method includes mapping, by the electronic device, the form field to dependent form field based on the configured API and receiving, by the electronic device, attributes in the form field; determining, by the electronic device, attributes corresponding to the dependent form field by applying the API with the attributes received in the form field; automatically filling the dependent form fields based on the determined attributes corresponding to the dependent form fields and displaying the filled dependent form fields.