Workflow Model Implicit Backtracking Node Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software development kits for mobile cloud applications are complex due to convoluted workflows resulting from low-level constructs, making it difficult for developers to design and manage applications without knowledge of underlying programming languages, especially with the need to account for numerous edges between nodes.
Innovation Solution
A workflow model that supports implicit backtracking, allowing developers to generate applications using a drag-and-drop interface by defining node types that either support or do not support backtracking, simplifying the process by automatically adding backward edges during compilation based on node types and rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a workflow model uses low-level constructs to represent application logic, then the application can be executed on mobile devices, but the workflow becomes convoluted and difficult to understand without programming language knowledge
Solution Approach 1:
The patent segments the workflow into distinct node types (interactive nodes, logic nodes, data nodes) with clearly defined roles and characteristics. Each node type encapsulates specific functionality, making the overall workflow easier to understand and manage while maintaining execution capability on mobile devices.
Solution Approach 2:
The patent introduces a mid-level abstraction layer between the low-level mobile device execution and the high-level workflow design. This intermediary layer uses structured node types with implicit backtracking rules, which automatically handle the complexity of edge management and translate high-level node definitions into executable low-level instructions.
2Reliability
If the workflow model includes explicit edge management between nodes, then the application flow can be precisely controlled, but the complexity of edge tracking increases significantly
Solution Approach 1:
The patent implements self-service through implicit backtracking, where the workflow model automatically manages edge connections and backtracking behavior based on node type definitions. The system serves itself by automatically generating the necessary control flow edges without requiring explicit developer intervention, thereby maintaining reliable flow control while reducing edge tracking complexity.
Solution Approach 2:
The patent applies preliminary action by pre-defining backtracking rules and edge management behavior during the node type definition phase. Rather than managing edges dynamically during execution, the system prepares the control flow structure in advance through node type specifications, which automatically determine edge connections and backtracking paths during compilation or interpretation.
3Ease of manufacture
If developers use drag-and-drop interface to design workflows, then the ease of application development increases, but the ability to handle complex backtracking logic decreases
Solution Approach 1:
The patent achieves universality by designing node types that simultaneously support simple linear workflows and complex backtracking logic through a unified interface. The same drag-and-drop node types can be used for both simple sequential operations and complex control flow with implicit backtracking, making the system versatile while maintaining ease of use.
Solution Approach 2:
The system handles complex backtracking logic through self-service mechanisms where the workflow model automatically generates the necessary control flow and edge management based on node type definitions. Developers simply drag and drop nodes without needing to explicitly program backtracking logic, as the system self-generates the appropriate control structures during compilation or interpretation.
Data Source
AI summary
Example embodiments disclosed herein relate to development of an application. An interface can be provided to develop an application using multiple nodes associated with a workflow model. The workflow model can include implicit backtracking based on node type.