Generic History Capturing Function for View Parameter Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current view building applications lack a generic mechanism for maintaining history of parameter data, requiring custom APIs for each view, leading to increased code complexity and user inconvenience when modifying views.
Innovation Solution
A generic history capturing function is integrated into the view user interface, allowing dynamic configuration and storage of history information for user-specified parameters, eliminating the need for multiple API creations and simplifying the process of capturing and displaying history data across various views.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a custom API is created for each view to capture history information, then history information can be captured for that specific view, but the code complexity increases and multiple APIs must be created and integrated
Solution Approach 1:
The patent implements a universal history capturing mechanism that works across all views through a single generic API. This API automatically captures history information for any view parameter without requiring view-specific customization, thereby reducing code complexity while maintaining reliable history capture functionality.
Solution Approach 2:
The patent separates the history capturing function from the view-specific logic by implementing it as an independent generic mechanism. This segmentation allows the history capture functionality to be reused across multiple views without duplicating code, reducing overall system complexity while ensuring reliable history information is captured for each view.
2Reliability
If custom APIs are created for each view modification, then history information can be maintained, but development time increases due to additional API customization and integration
Solution Approach 1:
The patent creates a single universal API that handles history information maintenance for all views, eliminating the need to develop and integrate custom APIs for each view modification. This universal approach significantly reduces development time while maintaining reliable history information across all views.
Solution Approach 2:
The generic history capturing mechanism automatically captures and maintains history information without requiring manual API customization for each view. The system serves itself by implementing a self-configuring history capture function that adapts to different views automatically, reducing development time and effort.
3Device complexity
If a generic history capturing mechanism is implemented, then API customization is reduced, but the mechanism must dynamically configure and handle various view parameters
Solution Approach 1:
The patent implements a dynamic configuration capability within the generic history capturing mechanism that allows it to adapt to different view parameters automatically. This dynamic approach enables the single API to handle various view configurations without requiring customization, reducing API complexity while maintaining high adaptability to different views and parameters.
Data Source
AI summary
A system for saving history information of input data to parameters included in a view is provided. The system includes a processor configured to: output an instance of the view; obtain pre-stored view details for the view, including identifiers of the parameters and tables to which input data of the parameters included are to be stored; make a generic API call to save current input data of a parameter to a table, wherein an input to the API call includes the current input data and old data of the parameter; based on the current input data and the old data being different, store the current input data in the table, create history information of the current input data and store the history information in a history table.