Centralized Page Flow Engine for Web Navigation Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional page flow frameworks face maintenance challenges due to complex page flow logic being embedded within each page, which becomes cumbersome when pages are added or deleted, requiring frequent modifications to the logic across multiple pages.
Innovation Solution
A page flow engine is introduced that navigates between pages using the current page and associated properties, allowing the page flow logic to be centralized and removed from individual pages, simplifying creation and maintenance by using a travel log for navigation and storing visited pages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If page flow logic is embedded within each page, then each page can independently determine navigation, but the maintenance complexity increases significantly when pages are added or deleted
Solution Approach 1:
The patent extracts the page flow logic from individual pages and places it in a centralized page flow engine. The engine receives the current page identifier and properties as input, processes the navigation logic centrally, and returns the next page identifier. This extraction eliminates the need for each page to contain its own navigation logic, significantly reducing maintenance complexity while preserving navigation functionality.
Solution Approach 2:
The centralized page flow engine serves as a universal navigation controller for all pages in the system. Instead of each page having its own dedicated navigation logic, the single engine handles navigation for multiple pages by receiving current page identifiers and properties, determining the next page based on centralized rules, and returning the result. This multi-functional approach reduces overall system complexity.
2Ease of repair
If page flow logic is centralized in a separate engine, then maintenance becomes easier when pages are added or deleted, but the system architecture becomes more complex
Solution Approach 1:
The patent introduces a page flow engine as an intermediary component between the pages and the navigation logic. This mediator receives requests from pages (current page identifier and properties), processes the navigation decision centrally, and returns the next page identifier. The intermediary approach simplifies maintenance by centralizing logic while managing architecture complexity through a well-defined, simple interface.
Solution Approach 2:
The system is segmented into distinct components: individual pages that render content and a separate page flow engine that handles navigation logic. This segmentation allows each component to have a single, well-defined responsibility, making the system easier to maintain despite the added architectural layer. The page flow engine is a self-contained unit that can be modified independently of individual pages.
3Productivity
If complex page flow logic is placed within each page, then navigation can be determined locally, but the overall system becomes harder to modify and maintain
Solution Approach 1:
The patent extracts complex page flow logic from individual pages and consolidates it in a centralized engine. The engine receives minimal input (current page identifier and properties) and returns the next page identifier, maintaining fast navigation decisions while eliminating the need for each page to contain complex navigation code, thereby improving system maintainability.
Data Source
AI summary
Aspects of the subject matter described herein relate to a page flow framework. In aspects, a page flow engine includes logic to navigate between pages. To make its determination of what page is next, the page flow engine uses an indication of the current page and may also use properties associated with the pages. These properties may be filled in as a user enters values on the pages, for example. The page flow engine does not need any additional information to determine the next page besides the current page and the properties. The page flow engine may also store the pages visited in a travel log. This may be used to return previous pages. The page flow engine allows the page flow logic to be removed from the pages and placed in a centralized component. This simplifies creation and maintenance of page flow.