Deep Hierarchy Navigation for Cross-Application Error Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current in-place validation techniques in computer applications are inadequate for identifying all errors, especially when errors are present in linked or referenced objects, leading to inefficiencies and lost productivity, as they fail to detect errors in dependent fields or objects across different applications.

Innovation Solution

The system employs deep hierarchy navigation by instantiating UI components, mapping dependencies, and checking them against validation rules, with errors identified in a popover window and the application focused on the UI component containing the error, even if it resides in a different application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If in-place validation is performed on form fields and directly linked objects, then errors in the current application can be identified, but errors in referenced objects from other applications cannot be detected

Engineering Contradiction:
Improveerror detection capabilityVSAvoidcross-application error tracking
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The validation system is segmented into multiple levels: local field validation, object-level validation, and cross-application referenced object validation. Each level handles specific validation tasks independently, allowing the system to detect errors at any depth of the object hierarchy without conflating validation scopes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements nested validation by placing validation logic within objects that can reference other objects. Validated objects contain embedded validation rules that can trigger validation of referenced objects, creating a nested validation structure where validation occurs at multiple hierarchical levels simultaneously.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Measurement precision

If deep hierarchy navigation is implemented to track all referenced objects, then all errors become detectable, but system complexity increases

Engineering Contradiction:
Improveerror detection completenessVSAvoidvalidation system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary validation by establishing dependency graphs and mapping referenced objects before actual form submission. Validation rules are pre-configured within objects, and the system pre-identifies all referenced objects in the hierarchy, so that when validation is triggered, the work is already prepared and can execute efficiently without complex real-time traversal.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If manual searching is required to find errors in linked objects, then validation can be simple, but productivity is reduced

Engineering Contradiction:
Improveform completion efficiencyVSAvoiderror location accessibility
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The validation system provides immediate feedback by displaying error messages directly in the user interface near the problematic fields. When validation fails, the system highlights affected fields and provides actionable error messages that guide users to the specific issues, eliminating the need for manual searching while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10503365B2Deep hierarchy navigation
Publication Date: 2019.12.10 SAP SE
  • US10503365B2 patent drawing
  • US10503365B2 patent drawing
  • US10503365B2 patent drawing

AI summary

Systems and techniques for deep hierarchy navigation include instantiating user interface (UI) components of an application in an application view on a computing device, where each of the UI components is represented by an application (app) model. For each of the UI components, dependencies on other objects are mapped including paths to the other objects. In response to an action to submit data contained in the UI components, each of the UI components is checked against validation rules. In response to one of the UI components violating one of the validation rules, an error in the UI component violating the rule is identified in a popover window using the mapped dependencies to identify the error. In response to a selection of the error in the popover window, the application is focused on the UI component containing the error.