Hierarchical Rule Inheritance with Source Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring and managing rules across different hierarchical levels in complex systems is a challenging task, as existing methods lack efficient mechanisms for rule inheritance, editing, and execution management.
Innovation Solution
Implementing a rules management system where rules created at higher hierarchical levels are automatically inherited by lower levels, with clear indication of source and editable local copies, allowing toggling of rule execution while preserving ordering, and restricting edits to inherited rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If rules are configured at multiple hierarchical levels independently, then each level can customize rules locally, but the complexity of managing and synchronizing rules across levels increases significantly
Solution Approach 1:
The patent implements a hierarchical rule inheritance structure where higher-level rules contain or encompass lower-level rules, similar to nested dolls. Each hierarchical level can have its own rule set while inheriting from parent levels, allowing local customization without managing all rules independently. The interface displays rules in a nested manner showing inheritance relationships, reducing management complexity while preserving adaptability.
Solution Approach 2:
The rule management system provides multi-functional capabilities: it can inherit rules from higher levels, allow local customization, enable selective activation/deactivation, and provide clear indication of rule sources. This universal system handles multiple rule management scenarios through a unified interface, reducing the need for separate management mechanisms at each level.
2Adaptability or versatility
If all rules are made editable at all levels, then local customization is maximized, but consistency and control from higher hierarchical levels are compromised
Solution Approach 1:
The patent applies different editability qualities to rules based on their hierarchical origin. Inherited rules from higher levels are marked as non-editable to maintain consistency and control, while locally created rules are fully editable. The interface clearly distinguishes between inherited and local rules through visual indicators, allowing users to understand which rules can be modified and which maintain organizational consistency.
Solution Approach 2:
The system allows users to create local copies of inherited rules when customization is needed. Instead of directly editing inherited rules (which would compromise consistency), users can copy them to create modifiable local versions. This copying mechanism preserves the original inherited rules for consistency while enabling local adaptations through copies.
3Ease of operation
If rule execution is automatically inherited without indication of source, then simplicity is maintained, but the ability to determine and manage rule origins is lost
Solution Approach 1:
The patent uses visual indicators (such as different colors, icons, or markings) to distinguish between inherited rules and locally created rules in the interface. Inherited rules are clearly marked to indicate their source hierarchical level, while maintaining automatic inheritance functionality. This visual differentiation preserves ease of operation by keeping the inheritance process automatic while preventing loss of source information through clear visual cues.
Data Source
AI summary
Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved.