Conditional Branching Validation System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for creating data manipulation expressions in computer systems are complex, error-prone, and lack the ability to perform conditional branching, validation, and integration with workflows or searches, requiring separate validations for each record and lacking support for expressions to be grouped or combined with other searches.
Innovation Solution
A method for conditionally branching validations using tokenized inputs and metadata, allowing for the creation of validation expressions that can be applied to records without writing programs or scripts, enabling conditional execution of child validations based on data values such as category, family, or audience, and integrating with user interfaces for constructing expressions and performing searches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate validations are defined for each record value, then validation coverage is improved, but device complexity and operation time increase
Solution Approach 1:
The validation system is segmented into a parent validation that handles common logic and child validations that handle specific cases. The parent validation dynamically selects and executes appropriate child validations based on record values, eliminating the need to define separate validations for every possible record value while maintaining comprehensive validation coverage.
Solution Approach 2:
The validation system transitions from static, fixed validations to dynamic, conditional validations. The parent validation uses conditional branching based on record field values to dynamically determine which child validation should execute, allowing the validation logic to adapt to different record values without manual reconfiguration.
2Adaptability or versatility
If manual expression creation is required, then validation customization is improved, but ease of operation deteriorates
Solution Approach 1:
The system provides self-service validation creation through template-based approaches and automated validation generation. Users can select from pre-defined validation templates and configure them with minimal input, or have the system automatically generate validations based on data patterns, eliminating the need for manual expression writing while maintaining customization capability.
Solution Approach 2:
The validation system allows customization through parameter configuration rather than expression programming. Users modify validation behavior by changing parameters such as field selections, comparison operators, and threshold values within a graphical interface, transforming complex validation logic into simple parameter adjustments.
3Manufacturing precision
If tokenized inputs are used, then manufacturing precision (syntax correctness) is improved, but device complexity increases
Solution Approach 1:
The system introduces an intermediary layer between the user and the validation logic through a graphical user interface that mediates expression construction. This interface provides visual building blocks, drag-and-drop components, and automated syntax generation, translating user actions into correct validation expressions without requiring users to understand the underlying syntax complexity.
4Adaptability or versatility
If conditional branching is added, then adaptability is improved, but device complexity increases
Solution Approach 1:
The validation system uses a nested structure where child validations are contained within the parent validation framework. The parent validation encapsulates the conditional branching logic and manages the selection of child validations, hiding the complexity of conditional logic from the user while providing powerful adaptability through the nested validation hierarchy.
Data Source
AI summary
Conditionally branching a validation allows branch-specific child validations to execute based on the values of data in a specific record. This allows for example a conditional branch to call another validation to validate records having particular category field values, family values and/or audience level/name/values. Embodiments comprise an interface that assists users through the use of automatic tokenizing and/or pick lists of field names and fields values, including a measurement builder for entering legal tokenized measurement values with applicable units of measure. Embodiments of the invention allow knowledgeable users to rapidly create expressions to ensure that the legal syntax and semantics of an expression are not violated while providing the user with pick lists and measurement values within legal ranges and with applicable units of measure. Validations rules are generated and performed on desired records in a computer system database without requiring programs, scripts or queries to be written.