Form Customization via Separate XML Representation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for customizing forms in model-based systems require creating new forms, which leads to issues with software updates, as the original software vendor can no longer update customized forms, resulting in frustration and inefficiency due to the need for manual reconfiguration and potential errors during software upgrades.
Innovation Solution
The approach involves capturing and storing user interface customizations in a separate representation, such as an XML file, allowing for serialization and application to the form without modifying the original form in persistent memory, enabling updates and consistency across multiple installations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new customized form is created by copying the original form, then the form can be modified to show additional relationships and properties, but the original software vendor can no longer update the customized form in future versions
Solution Approach 1:
The patent segments the form into two independent parts: the base form (provided by the software vendor) and the customization layer (stored separately as XML or other data structures). This segmentation allows the base form to be updated by the vendor while the customization layer remains intact and can be reapplied to updated versions, resolving the contradiction between customization capability and update efficiency.
Solution Approach 2:
The patent extracts the customization information from the original form and stores it separately in a persistent storage location. By taking out the customization layer and storing it independently, the system enables vendors to update the base form without losing customizations, thus maintaining both customization capability and update efficiency.
2Reliability
If the customized form is modified to account for vendor updates, then the form remains functional with new features, but substantial time and effort are spent on reconfiguration
Solution Approach 1:
The patent performs preliminary action by capturing and storing the customization state before vendor updates occur. The customization layer is saved in advance, allowing it to be automatically reapplied to updated forms without requiring time-consuming manual reconfiguration, thus reducing reconfiguration time while maintaining form functionality.
Solution Approach 2:
The patent creates a copy of the customization information in a persistent storage location. This copy can be automatically applied to updated forms, eliminating the need for manual reconfiguration and significantly reducing the time required to maintain form functionality across software versions.
3Reliability
If customizations are applied in a test environment and then manually applied in a production environment, then the customizations can be tested first, but the process is time consuming and error prone
Solution Approach 1:
The patent creates a persistent copy of the customization information that can be automatically transferred from test to production environments. This copy mechanism ensures that customizations tested in the test environment are accurately reproduced in the production environment without manual intervention, improving both accuracy and deployment efficiency.
Solution Approach 2:
The patent enables the customization system to serve itself by automatically capturing, storing, and applying customization information across different environments. This self-service capability eliminates manual copying and reduces errors, improving both reliability and productivity in the customization deployment process.
Data Source
AI summary
Techniques are described herein for customizing a form (a.k.a. a dialog) in a model-based system. For instance, the form may be customized without the need to modify the form in persistent memory, such as read-only memory (ROM), a hard disk, a magnetic disk, an optical disk, etc. A representation of a customization (e.g., an extensible markup language file, a management pack, etc.) regarding the form is captured in memory, such as a random access memory (RAM), and stored in a file or a database. For instance, the representation of the customization may be stored separately from the form. The representation of the customization is retrieved from the file or the database and applied to a rendering of the form.