Form Field Synchronization via Client-Side Dependency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In client-server environments, synchronizing dependent form fields in database applications is costly and inefficient, leading to user confusion due to stale information when updates are not properly reflected.

Innovation Solution

A system is implemented that includes a database tier, an application tier, and a client tier, allowing for the automated updating of dependent form fields without modifying the database contents, with options to generate updated values at the client, server, or combined application/database tier, ensuring timely and accurate synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If client-side database applications are used to synchronize dependent form fields, then field synchronization functionality is provided, but time and performance costs become very expensive in client-server environments

Engineering Contradiction:
Improvefield synchronization functionalityVSAvoidtime and performance cost
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent introduces a form controller as an intermediary component that manages the synchronization of dependent form fields. The controller receives notifications of field changes, determines dependencies, and coordinates updates across multiple fields without requiring expensive client-side database queries. This mediator approach resolves the contradiction by providing synchronization functionality while minimizing performance overhead through intelligent field dependency management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional client-side synchronization methods are used, then dependent fields can be updated, but the performance cost becomes very expensive in web environments

Engineering Contradiction:
Improvesynchronization accuracyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-defining field dependencies and relationships at design time. The system establishes a dependency map that identifies which fields depend on others before runtime operations occur. When a field changes, the pre-established dependency information allows the system to immediately identify and update only the affected dependent fields, ensuring synchronization reliability while maintaining high performance through avoided redundant operations.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If form fields are synchronized in real-time, then user confusion from stale information is prevented, but system resource consumption increases

Engineering Contradiction:
Improvestale information preventionVSAvoidsystem resource consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by implementing selective synchronization that updates only the specific dependent fields that are actually affected by a change, rather than performing a comprehensive refresh of all form fields. The form controller analyzes field dependencies and triggers updates only where necessary, preventing user confusion from stale information while minimizing unnecessary system resource consumption by avoiding excessive full-form refreshes.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9449063B2Synchronization of form fields in a client-server environment
Publication Date: 2016.09.20 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9449063B2 patent drawing
  • US9449063B2 patent drawing
  • US9449063B2 patent drawing

AI summary

A database tier maintains and provides access to a database. An application tier receives and responds to requests for a form. The form includes data defining a first UI control for displaying a first value from the database and a second UI control for displaying a second value from the database that is dependent upon the first value. A client tier renders the form to show the first value in the first UI control and to show the second value in the second UI control. The client tier also detects a modification to the first value and causes an updated second value to be generated in response to detecting the modification to the first value. The updated second value is displayed by way of the second UI control. The updated second value is generated at the client tier, the application tier, the database tier, or at a combined application/database tier.