Recursive Navigation Stack for Mobile CRM Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile CRM systems restrict navigation capabilities, requiring users to backtrack and navigate through the main menu to access related information, limiting efficiency and user experience.

Innovation Solution

Implementing a recursive navigation method that allows users to directly navigate between related business objects within the CRM system by maintaining a page navigation stack, enabling forward and backward navigation without returning to the main menu, using a metadata-driven application with page definitions that merge data from a logical data model with user requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If users navigate through the main menu to access related information, then navigation structure is simple, but navigation time and user efficiency deteriorate

Engineering Contradiction:
Improvenavigation timeVSAvoidnavigation structure complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system pre-establishes a navigation stack that records the hierarchical path from main menu to current page. This preliminary structuring of navigation data allows users to directly access related information without manually traversing through the main menu, thereby reducing navigation time while maintaining a manageable navigation structure through automated stack management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The navigation stack acts as an intermediary data structure between the main menu system and the detailed CRM pages. It stores the hierarchical path information and enables direct navigation to related business objects by providing pre-computed navigation routes, thus reducing the time users spend navigating while keeping the overall system structure intact.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If recursive navigation is implemented, then user efficiency improves, but system complexity increases

Engineering Contradiction:
Improveuser efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The navigation system is segmented into distinct components: the navigation stack that stores hierarchical paths, the page definition system that defines CRM pages and their relationships, and the data selection mechanism that retrieves relevant business object data. This segmentation allows recursive navigation to be implemented efficiently by managing each component independently, thereby improving user efficiency while controlling system complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The navigation stack and page definition system serve multiple functions: they enable both forward navigation to related business objects and backward navigation to parent pages, support recursive access to nested CRM data structures, and provide a unified mechanism for displaying various types of CRM information. This multi-functionality improves user efficiency without requiring separate systems for different navigation scenarios, thus controlling overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9741060B2Recursive navigation in mobile CRM
Publication Date: 2017.08.22 ORACLE INT CORP
  • US9741060B2 patent drawing
  • US9741060B2 patent drawing
  • US9741060B2 patent drawing

AI summary

A method and apparatus for recursive navigation. In one embodiment of the method, a first reply is generated in response to receiving a first request from a mobile device. The first reply is generated as a function of a page definition, and the first reply comprises data selected from a first object of a logical data model, but not a second object of the logical data model. The first and second objects are distinct from each other. A second reply is generated in response to receiving a second request from the mobile device. The second reply is generated as a function of the page definition, and the second reply comprises data selected from the second object but not the first object.