Workflow API Visual Interface for Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing environments, managing and processing increasing amounts of data becomes challenging due to the complexity of analyzing, interacting with, and providing reports for vast data resources, particularly for non-technical users tasked with automating and troubleshooting IT and organization-related functions.
Innovation Solution
The implementation of custom workflow Application Programming Interfaces (APIs) that allow users to create and execute information flows visually, using software tools that present a flow chart view, enabling graphical manipulation of data processing without requiring programming skills, and providing both server-side and front-end Flow APIs for asynchronous execution and enhanced security through access control lists.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional programming methods are used for creating workflows, then automation capability is achieved, but ease of operation deteriorates due to requiring programming skills
Solution Approach 1:
A visual workflow designer interface acts as an intermediary between users and the automation system. Users interact with graphical elements (flow charts, drag-and-drop components) rather than writing code directly. The system translates these visual representations into executable automation logic, bridging the gap between user-friendly interaction and complex automation capabilities.
Solution Approach 2:
The patent replaces the mechanical system of text-based programming with a visual manipulation system. Instead of typing and editing code text, users drag, drop, and connect graphical workflow elements. The system captures these visual actions and automatically generates the corresponding automation logic, substituting manual coding mechanics with intuitive visual interactions.
2Ease of operation
If visual workflow tools are implemented, then ease of operation improves for non-technical users, but device complexity increases due to additional software layers
Solution Approach 1:
The system is segmented into distinct functional layers: a visual workflow designer interface for users, a workflow definition engine for processing visual inputs, and an execution engine for running automated tasks. Each layer handles specific responsibilities independently, managing complexity through modular separation while presenting a simplified interface to users.
Solution Approach 2:
The visual workflow designer serves multiple functions: it acts as both the user interface for creating workflows and the definition mechanism for specifying automation logic. The same visual elements and drag-and-drop interactions handle workflow creation, configuration, and validation, consolidating multiple functions into a single universal tool that reduces overall system complexity.
3Adaptability or versatility
If custom workflow APIs are developed, then adaptability improves for different use cases, but manufacturing precision deteriorates due to increased customization options
Solution Approach 1:
A universal workflow API framework is implemented that handles multiple use cases through a consistent interface. The same set of standardized components, connection types, and execution mechanisms supports diverse automation scenarios. This universal framework ensures implementation consistency across different workflows while maintaining high adaptability through configurable parameters and extensible components.
Solution Approach 2:
The system achieves adaptability through parameter configuration rather than structural changes. Workflows are customized by modifying parameters (data sources, transformation rules, execution timing) of standardized components rather than changing the underlying architecture. This approach maintains manufacturing precision by keeping the core structure consistent while allowing flexible parameter adjustments for different use cases.
Data Source
AI summary
A computing system includes a server. The server is communicatively coupled to a data repository and is configured to store a data in the data repository. The server is further configured to create, via a visual information flow creation tool, at least one information flow object, wherein the at least one information flow object comprises a flow, a sub-flow, an Action, or a combination thereof. The server is also configured to interface with the at least one information flow object via a front-end application programing interface (API), a back-end API, or a combination thereof. The server is additionally configured to execute the at least one information flow object via the front-end API, the back-end API, or a combination thereof, and to retrieve results obtained by executing the at least one information flow object via the front-end API, the back-end API, or the combination thereof.