Workflow Manager Automating Legacy System Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computing systems face challenges in efficiently integrating and managing complex workflows due to fragmented computing landscapes, requiring manual re-wiring of integrations and resulting in increased costs and time delays, especially when combining legacy systems and microservices for business operations.
Innovation Solution
A workflow manager system that generates and executes workflows by receiving configuration parameters, identifying connection objects, and arranging functions in a predetermined order, allowing for the creation of templates and execution of workflows with minimal manual intervention, using a user interface for drag-and-drop functionality and providing a runtime environment for synchronous or asynchronous task execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual re-wiring of integrations is performed to combine legacy systems and microservices, then workflow integration can be achieved, but time delays and costs increase
Solution Approach 1:
The patent applies preliminary action by pre-defining connection objects with standardized interfaces and protocols before integration is needed. These connection objects are created in advance with metadata describing their capabilities, allowing workflows to be assembled quickly by selecting pre-prepared connection objects rather than creating integrations from scratch each time.
Solution Approach 2:
The patent uses connection objects as intermediaries between legacy systems and microservices. These connection objects act as standardized adapters that simplify the integration process by providing a uniform interface layer, eliminating the need for custom point-to-point wiring between different system types.
2Reliability
If manual re-wiring of integrations is performed to combine legacy systems and microservices, then workflow integration can be achieved, but costs increase
Solution Approach 1:
The patent applies universality by designing connection objects with standardized interfaces that can work with multiple different legacy systems and microservices types. A single connection object template can be reused across multiple integrations, reducing the need to create custom integration code for each new system combination and thereby reducing costs.
Solution Approach 2:
The patent uses copying by allowing connection objects to be replicated and reused across different workflows. Once a connection object is created and validated for a particular legacy system or microservice, it can be copied and reused in multiple workflows, eliminating redundant integration work and reducing overall integration costs.
3Adaptability or versatility
If end users manually locate and configure functionalities and data, then workflow customization is possible, but time and resources are consumed
Solution Approach 1:
The patent applies self-service by enabling end users to automatically discover and select connection objects based on their workflow needs without requiring deep technical knowledge. The system provides self-service capabilities through automated matching of required functionalities with available connection objects, reducing the time and expertise needed for workflow configuration.
Solution Approach 2:
The patent applies preliminary action by pre-configuring connection objects with metadata describing their capabilities, inputs, and outputs. This preliminary preparation allows end users to quickly configure workflows by selecting from pre-described options rather than manually searching and configuring each component from scratch.
4Adaptability or versatility
If complex integrations are manually configured, then system connectivity is achieved, but device complexity increases
Solution Approach 1:
The patent applies segmentation by breaking down complex integrations into discrete, manageable connection objects. Each connection object represents a single integration point with a specific legacy system or microservice, allowing complex workflows to be constructed by assembling simple, standardized components rather than managing monolithic integration configurations.
Data Source
AI summary
A method, a system, and a computer program product for generating and/or using one or more workflow managers in computing systems. A request to generate a computing workflow is received. The workflow includes a plurality of computing functions. A plurality of configuration parameters associated with the workflow are determined based on the received request. The configuration parameters define a configuration of execution of one or more functions. One or more connection objects for connecting the functions to one or more data sources storing data required for execution of the functions are identified. The plurality of functions are arranged for execution in a predetermined order using the determining plurality of configuration parameters and identified connection objects. The predetermined order is specified using one or more configuration parameters. The workflow is generated, compiled and executed.