Web Application Component Attribute Override Mechanism

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In web application builders, developers face challenges in overriding default decorator attribute values and restricting attribute configurations for specific components, leading to undesirable rendering and configuration issues.

Innovation Solution

The system introduces decorator override rules that allow developers to modify specific attributes and restrict modifications by non-developers, ensuring consistent and visually appealing component rendering within containers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If decorator rules are applied to render web application components, then component rendering consistency is improved, but developer ability to override default attribute values is restricted

Engineering Contradiction:

Improvecomponent rendering consistencyVSAvoiddeveloper ability to override attributes

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system segments attribute configuration into two distinct layers: decorator-level default attributes and component-level override attributes. This segmentation allows decorator rules to establish consistent defaults while developers can selectively override specific attributes on individual components, resolving the contradiction between rendering consistency and customization capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing attribute overrides at the specific component level rather than applying uniform rules globally. Each component can have its own set of overridden attributes while maintaining the decorator's default rendering for non-overridden attributes, enabling localized customization without compromising overall consistency.

Inventive Principle:

Principle #3Local quality

2Ease of operation

If non-developers are allowed to modify component attributes, then ease of operation is improved, but component rendering quality deteriorates

Engineering Contradiction:

Improvenon-developer configuration abilityVSAvoidcomponent rendering quality

Core Design Contradiction:

Ease of operationVSManufacturing precision

Solution Approach 1:

The system performs preliminary action by pre-configuring decorator rules with default attribute values and rendering logic before non-developers attempt to modify components. These pre-established rules act as guardrails that allow non-developers to operate easily while ensuring that modifications remain within quality boundaries defined by the decorator.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where decorator rules continuously monitor and enforce attribute configurations. When non-developers modify attributes, the decorator evaluates whether the modifications comply with rendering quality standards, providing implicit feedback through acceptance or rejection of changes, thus maintaining quality while allowing operational flexibility.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If decorator override rules are implemented, then attribute configuration control is improved, but system complexity increases

Engineering Contradiction:

Improveattribute configuration controlVSAvoidsystem structure complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the decorator component to serve multiple functions: establishing default attributes, rendering components, and managing override rules. This multi-functionality consolidates what could be separate complex systems into a single cohesive decorator architecture, reducing overall system complexity while maintaining comprehensive attribute configuration control.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10402174B2Overriding component attributes in a web application builder

Publication Date: 2019.09.03 SALESFORCE INC

AI summary

Disclosed are examples of systems, apparatus, methods and computer program products for overriding component attributes in a web application builder. A database system maintains a multi-tenant database associated with a number of users and a number of web application components each with one or more component attributes. The system displays a user interface for the web application builder framework with a layout including a number of web application components, and processes decorator rules for rendering the components. The system also processes decorator override rules for some attributes of the components. The system displays the prepared user interface with decorator rules and overrides, and, based on a user request to access one or more attributes of the components, presents those attributes for display with the decorator override rules applied.