Event Based Validation Web Application UI

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web application development frameworks lack efficient event-based validation mechanisms, making it difficult to manage user interface events and perform actions based on validation conditions in a scalable and user-friendly manner.

Innovation Solution

A publish-subscribe model for event-based validation is implemented, allowing developers to define publishable UI events with trigger event definitions that include event subscribers, validation conditions, and resulting actions, enabling dynamic validation and action execution within web application pages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional validation mechanisms are used in web application frameworks, then the system structure remains simple, but the ability to manage user interface events and perform actions based on validation conditions becomes inefficient and difficult to scale

Engineering Contradiction:
Improvevalidation efficiencyVSAvoidsystem structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The validation system is segmented into independent event subscribers, each responsible for specific validation conditions. Events are divided into different types (focus, blur, input, etc.) and handled by specialized subscribers, allowing modular development and easy scaling without increasing overall system complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An event bus is introduced as an intermediary component that decouples event sources from validation handlers. The event bus receives UI events, routes them to appropriate event subscribers, and manages the validation workflow, enabling efficient event handling while maintaining system simplicity through standardized communication protocols

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If event-based validation with multiple subscribers is implemented, then the scalability and user-friendliness of validation management improve, but the complexity of defining and managing event definitions increases

Engineering Contradiction:
Improvevalidation management scalabilityVSAvoidevent definition complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Event definitions are designed as universal templates that can be extended for specific validation needs. The publishable event definition structure provides a standardized framework that works across different validation scenarios, while allowing customization through trigger event definitions and event subscribers, reducing the need to create new definitions for each case

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

Solution Approach 2:

Event definitions, trigger conditions, and subscriber configurations are prepared in advance during application development. The system pre-registers event types, validation conditions, and corresponding actions, so that during runtime, validation occurs automatically without requiring complex runtime configuration or manual event routing logic

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If real-time validation and action execution are implemented, then user interaction quality and error handling improve, but the processing time and system resource consumption increase

Engineering Contradiction:
Improveuser interaction qualityVSAvoidprocessing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

Validation is triggered periodically based on specific user interactions (focus, blur, input events) rather than continuously monitoring all inputs. This event-driven periodic validation provides real-time feedback at critical moments without imposing continuous processing overhead, maintaining user interaction quality while optimizing resource usage

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs validation selectively based on the type of UI event and the specific field being interacted with. Not all fields require the same level of validation intensity or frequency. The event subscriber mechanism allows the system to apply appropriate validation actions only where needed, reducing unnecessary processing while maintaining comprehensive error handling

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10007493B1Event based validation
Publication Date: 2018.06.26 EMC IP HLDG CO LLC
  • US10007493B1 patent drawing
  • US10007493B1 patent drawing
  • US10007493B1 patent drawing

AI summary

Event based validation includes detecting a user interface (UI) event in a page of a web application, and identifying a event subscriber of multiple event subscribers to the UI event. The event subscriber defines a validation condition, which is tested. When the validation condition is satisfied, an action, defined by the event subscriber is performed.