Configuration-Driven Rule Evaluation for Updating Conditional Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized software applications face challenges in updating conditional logic, which often introduces errors and is difficult to track due to frequent modifications, especially when used by many users, and hardcoded conditions complicate maintenance.
Innovation Solution
A system and method for automatically generating and applying conditions using a configuration file with dynamic rules and a workbench module that retrieves and processes rules from a repository, allowing for frequent updates without modifying code, and includes a web-based interface for result display.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conditional logic is updated frequently in centralized software applications, then the software can adapt to changing requirements, but errors and software bugs are introduced more frequently
Solution Approach 1:
The patent segments conditional logic into separate, independently deployable modules or services. Each conditional rule can be updated, tested, and deployed independently rather than modifying the entire centralized codebase, reducing the risk of introducing system-wide errors while maintaining adaptability.
Solution Approach 2:
The patent introduces an intermediary layer (such as a rules engine or configuration service) that sits between the user interface and the core application logic. This intermediary handles conditional logic updates without requiring changes to the underlying application code, allowing frequent adaptations while protecting the core system from errors.
2Device complexity
If conditional logic is hardcoded as static if-then-else statements, then the software structure remains simple, but tracking and maintaining the logic becomes difficult
Solution Approach 1:
The patent replaces hardcoded conditional logic with external representations such as configuration files, database records, or JSON schemas that can be copied, versioned, and tracked independently from the application code. These external representations can be reviewed, audited, and maintained without modifying the software source code.
Solution Approach 2:
The patent transforms static, hardcoded conditional logic into dynamic, configurable rules that can be modified at runtime or through configuration updates. This allows the logic to adapt to changing requirements while maintaining a clear separation between the application framework and the business rules, improving trackability.
3Stability of the object's composition
If code updates are performed during scheduled downtime, then system stability is maintained, but productivity and response time to requirements changes are reduced
Solution Approach 1:
The patent implements periodic or scheduled retrieval of configuration updates by the distributed components, allowing the system to remain stable during core operational hours while automatically incorporating rule updates during off-peak periods without requiring full system downtime.
Solution Approach 2:
The patent performs preliminary validation and testing of conditional logic updates in a staging environment before deploying them to production. This preliminary action ensures system stability while enabling faster update cycles, as validated configurations can be deployed with confidence without requiring extensive testing during downtime.
4Productivity
If updates are deployed without advance notice to users, then the software can respond quickly to requirements changes, but users lose track of modifications
Solution Approach 1:
The patent implements feedback mechanisms that notify users of conditional logic changes through the user interface. When rules are updated, users receive notifications or can view change logs that explain what has changed and how it affects their workflows, maintaining awareness while enabling rapid deployment.
Solution Approach 2:
The patent provides preliminary notification to users about upcoming changes through configuration metadata or user interface annotations before the changes are fully deployed. This allows users to prepare for modifications while maintaining the ability to deploy updates quickly.
Data Source
AI summary
Systems and methods for automatically generating and applying selected conditions to process data are provided. A system receives an application request, which includes one or more fields and one or more corresponding data items. The application request may originate from an artificial intelligence system executing a machine learning model. The system also receives a configuration file from a configuration repository and processes the same to identify a plurality of rules. For each selected rule of the plurality of rules applicable to selected fields the one or more fields, the system evaluates the selected rules against selected data items associated with the selected fields. Based on the evaluating, the system determines a result of the application request and transmits the result for display.