Workflow Designer Debugging via Mode Toggle
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business and consumer applications often require complex programming expertise to develop, making it difficult for users to create workflows that access various services and perform actions based on received information, especially when pulling data from remote sources like cloud services.
Innovation Solution
A system and method for developing user applications through a workflow designer that allows users to visualize and test workflows in a graphical user interface, transition workflow steps between development and test modes, and display parameter values, enabling users to create and debug workflows without extensive programming knowledge.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users attempt to develop complex workflows accessing multiple services and cloud sources, then functionality and capability are improved, but programming expertise requirements and system complexity increase
Solution Approach 1:
The workflow development process is segmented into distinct phases: design phase using visual workflow designer for creating workflow definitions, and implementation phase using generated programming code. This segmentation allows users to work at their expertise level - visual design for business users, code generation for technical implementation - while achieving complex multi-service workflow functionality.
Solution Approach 2:
A code generation system acts as an intermediary between the visual workflow designer and the final executable application. The system translates visual workflow definitions into programming code, bridging the gap between user-friendly visual design and technical implementation requirements for complex workflows involving multiple services and cloud sources.
2Ease of operation
If visual workflow designer is used to simplify development, then ease of operation is improved, but ability to debug and test workflows deteriorates
Solution Approach 1:
The system implements feedback mechanisms that display generated programming code back to users in the visual workflow designer interface. Users can view the code that will be generated from their visual workflow definitions, allowing them to verify logic correctness and understand the translation process before final code generation, thereby enabling debugging at the design stage.
Solution Approach 2:
The system performs preliminary code generation and validation during the workflow design phase rather than waiting until final deployment. By generating and displaying code early in the development process, users can identify and correct issues before committing to final implementation, making debugging easier while maintaining visual design simplicity.
3Productivity
If programming code is generated automatically from workflow definitions, then productivity is improved, but control over code quality and customization is reduced
Solution Approach 1:
The code generation system is designed to be dynamic and adaptive rather than rigid. It allows users to configure generation parameters, select different code templates, and customize output based on specific requirements. The system adapts to user needs by providing flexible code generation options while maintaining automated productivity benefits.
Solution Approach 2:
The system performs preliminary code generation during the design phase, allowing users to review and customize the generated code before final implementation. This preliminary action enables users to exercise control over code quality and make necessary customizations while still benefiting from automated generation for standard patterns, balancing productivity with customization control.
Data Source
AI summary
Methods, systems, apparatuses, and computer program products are provided for developing, debugging, and growing workflows. Embodiments enable the developer to test the workflow in place in a workflow designer that displays input/output parameter values for each workflow step during the test run. The developer is enabled to toggle the workflow step(s) between a development mode, where the developer may edit input parameter values, and a test mode, where the developer is displayed (but cannot edit) the input parameter values and is displayed the output parameter values at each workflow step. A record of workflow runs of a workflow is also maintained. The developer is also enabled to transition a workflow from being a business application to a robust software application having additional functionality. The workflow logic generated is transported between a visual workflow designer and a full-blown code editor.