Workflow Conversion Between WYSIWYG, Text, and Machine Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems require manual intervention and are prone to errors when converting between different formats of workflow inputs, such as natural language, graphical user interfaces, and machine-readable markup languages, leading to inefficiencies and inaccuracies.
Innovation Solution
A system utilizing a machine learning model and graph parsing algorithm to automatically convert workflow inputs between human-readable text, graphical user interfaces, and machine-readable markup languages, enabling seamless three-way conversion among these formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual intervention is used to determine workflow steps and convert between formats, then flexibility and control are maintained, but time consumption increases and errors are introduced
Solution Approach 1:
The system enables self-service automation where the workflow processing system automatically determines workflow steps, contacts organizations, and converts between formats without requiring manual user intervention. The automated system serves itself to perform these tasks, eliminating the time-consuming manual processes while maintaining accuracy through consistent automated execution.
Solution Approach 2:
The patent replaces the mechanical manual process of determining workflow steps and converting formats with an automated computational system. The manual mechanical action of users typing and converting data is substituted with automated software processes that use machine learning models and parsing algorithms to perform the same functions more efficiently and accurately.
2Adaptability or versatility
If multiple formats (GUI, natural language, markup language) are supported for workflow input, then user convenience and accessibility are improved, but system complexity increases
Solution Approach 1:
The system introduces an intermediary conversion layer that translates between multiple input formats (GUI workflows, natural language, markup language) and a standardized internal workflow representation. This intermediary layer handles the complexity of format conversion centrally, allowing the system to support multiple formats without increasing the complexity of each individual format handler.
Solution Approach 2:
The workflow processing system is designed with universal capabilities to accept and process multiple input formats through a single unified interface. The system performs multiple functions (parsing, converting, validating) across different format types using the same core processing logic, reducing overall system complexity compared to having separate specialized systems for each format.
3Productivity
If automated conversion between workflow formats is implemented, then productivity and accuracy are improved, but the need for robust conversion algorithms increases system complexity
Solution Approach 1:
The system performs preliminary actions by pre-defining the conversion algorithms and parsing rules for each input format before actual workflow conversion is needed. The machine learning models are pre-trained and the parsing algorithms are pre-configured to handle specific format patterns, allowing rapid automated conversion without requiring complex real-time decision-making during the conversion process itself.
Data Source
AI summary
An executable in a user-readable format that corresponds to a workflow function is received. The workflow function can be a stepwise process within a workflow. The executable is converted using one of natural language processing or a graph parsing algorithm and then an executable file is accessed. The executable file corresponds to the executable where the workflow function is associated with a task library function created by a machine-level language and stored at the executable file. The executable file is converted using the other of the natural language processing and the graph parsing algorithm. The converted executable file is then linked to a second user interface that is configured to present the workflow function in the user-readable format according to the stepwise process within the workflow.