Wizard Engine Data Management for Multi-Wizard Navigation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face inefficiencies when navigating between multiple wizards in web applications, as they often need to quit one wizard to enter data in another, leading to time-consuming repetition and increased risk of errors due to the loss of entered data and the requirement to follow a specific sequence.

Innovation Solution

A method and wizard engine that allow users to interrupt and store data from one wizard, enabling seamless navigation and resumption between multiple wizards, with data storage options in temporary structures or databases, and customizable rules for inter-wizard interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users follow a specific sequence to complete wizards in web applications, then data integrity between wizards is maintained, but user flexibility and ease of operation deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoiduser flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by automatically storing data from previously completed wizards in a database before the user needs it. When a user activates a wizard, the system proactively retrieves and makes available data from other wizards that the user has already completed, eliminating the need for users to manually navigate through wizards in a specific sequence while maintaining data integrity.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If users can navigate between wizards in any order, then ease of operation improves, but data loss and time consumption increase

Engineering Contradiction:
Improvenavigation flexibilityVSAvoiddata entry repetition
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system introduces a database as an intermediary between wizards. When users complete a wizard, data is automatically stored in the database. When users activate another wizard that requires data from previously completed wizards, the system retrieves the data from the database and makes it available to the user, eliminating the need to re-enter data and allowing navigation in any order without time loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If users must complete wizards in a fixed sequence, then system complexity is reduced, but productivity decreases

Engineering Contradiction:
Improvewizard management complexityVSAvoidtask completion efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system performs self-service by automatically tracking which wizards have been completed and storing their data in a database. When a user activates a wizard, the system automatically retrieves necessary data from the database without requiring manual intervention or complex user management of wizard sequences. This maintains simple system architecture while significantly improving productivity by allowing users to complete tasks in any order without repeating data entry.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8756526B2Wizard in a wizard engine
Publication Date: 2014.06.17 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8756526B2 patent drawing
  • US8756526B2 patent drawing
  • US8756526B2 patent drawing

AI summary

A method for managing a web application initiated by a user is disclosed which enables navigation between two or more wizards while executing said web application. Predefined instructions ensure that a user can execute a plurality of steps in different orders when navigating between two or more wizards without losing any data that has been executed in a previous step. A wizard engine is also disclosed which is adapted to execute the suggested method.