Dynamic Form Component Injection for Enterprise SaaS Customization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

SaaS web applications lack enterprise-specific validation rules and support capabilities, limiting their customization and usability for end users.

Innovation Solution

A computing system that includes a web server and an enterprise server providing a library of custom form components to replace existing form components in a web application, allowing for user-specific support capabilities like custom helper functions, reduced dropdown options, and voice input support without modifying the web application itself.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If SaaS web applications use standard form components, then the application is simple to deploy and maintain, but the application lacks enterprise-specific validation rules and support capabilities

Engineering Contradiction:

Improveenterprise-specific customization capabilityVSAvoidsystem architecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments form components into standard components (provided by the SaaS application) and custom components (provided by the enterprise server). Each component type handles specific functionality, allowing the system to maintain simplicity while adding customization capabilities through modular component injection.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer (the custom component injection mechanism) between the standard SaaS application and the end user. This intermediary allows enterprise-specific customization to be injected without modifying the core SaaS application, resolving the contradiction between adaptability and complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the web application is modified to add enterprise-specific features, then the application provides better enterprise support capabilities, but the application loses its standardization and requires changes to the web application itself

Engineering Contradiction:

Improveenterprise-specific support capabilityVSAvoidapplication deployment simplicity

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system performs preliminary action by pre-defining custom form components on the enterprise server before they are needed. When a user accesses the application, the appropriate custom components are automatically injected based on user context, eliminating the need to modify the web application for each enterprise-specific requirement.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system makes the application dynamic by allowing custom form components to be injected at runtime based on user context and enterprise requirements. This dynamic injection mechanism enables the application to adapt to different enterprises without requiring modifications to the core application code or redeployment.

Inventive Principle:

Principle #15Dynamics

3Ease of operation

If custom form components are injected to replace existing components, then user-specific support capabilities are provided, but the system requires additional processing to analyze and replace components

Engineering Contradiction:

Improveuser-specific customizationVSAvoidpage rendering speed

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The system applies partial action by only injecting custom form components where they are needed, rather than replacing all components. The system analyzes the DOM tree to identify specific form components that require customization and injects only those, minimizing the impact on rendering performance while still providing user-specific customization.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10878057B2Web application with custom form components

Publication Date: 2020.12.29 CITRIX SYSTEMS INC

AI summary

A computing system includes a web server to provide a web application, and an enterprise server to provide a library of custom form components to be used to customize web pages in the web application. Each custom form component corresponds to an existing form component on one of the web pages. A client computing device accesses the web application and the library of custom form components via an embedded browser, renders one of the web pages from the web application, and analyzes the rendered web page for existing form components. The existing form components in the rendered web page are compared to the library of custom form components for a match. For each match, the existing form component in the rendered web page is replaced with the matched custom form component from the library of custom form components. The web page with the custom form components is re-rendered for display.