Enhanced Plug-Ins Cross-Framework Workflow Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software plug-ins face limitations in invocation across different frameworks and languages, requiring specialized coding and coordination for workflow integration, and lack standard interfaces for API calls, such as REST APIs, restricting their use in network invocations and data processing.

Innovation Solution

Enhanced plug-ins with standardized interfaces for invoking services across different frameworks and languages, enabling workflow integration through logical components that process data and forward it to subsequent plug-ins or endpoint applications using standard API calls like HTTP-GET and HTTP-POST requests, eliminating the need for custom coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard software plug-ins are used, then they can be deployed into a framework, but they require specialized coding and coordination for workflow integration across different frameworks and languages

Engineering Contradiction:
Improvecross-framework invocation capabilityVSAvoidspecialized coding requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The enhanced plug-in architecture implements universal interfaces that allow plug-ins to be invoked across different frameworks and programming languages. The system provides a standardized invocation mechanism that works regardless of the application framework or language used, eliminating the need for specialized coding for each framework integration scenario.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces an intermediary layer consisting of standardized interfaces and protocol handlers that mediate between diverse application frameworks and the plug-in execution environment. This intermediary translates various framework-specific calls into a unified plug-in invocation format, reducing complexity by abstracting away framework-specific details.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If custom workflow integration code is written, then workflow creation is possible, but the process becomes time-consuming and complex

Engineering Contradiction:
Improveworkflow creation efficiencyVSAvoidworkflow integration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining standardized interfaces, protocols, and integration patterns that can be directly applied to workflow creation. Rather than requiring developers to write integration code from scratch, the system provides ready-to-use templates and mechanisms that accelerate workflow assembly and reduce integration time.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If framework-specific plug-in invocation is used, then integration within the same framework is straightforward, but network invocations and cross-language calls are restricted

Engineering Contradiction:
Improvecross-language and network invocation capabilityVSAvoidinvocation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The enhanced plug-in system implements universal invocation interfaces that function consistently across local and networked environments, and across different programming languages. The same interface mechanisms work whether the plug-in is invoked locally within a framework or remotely over a network, maintaining ease of operation while expanding adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10831575B2Invoking enhanced plug-ins and creating workflows having a series of enhanced plug-ins
Publication Date: 2020.11.10 KYNDRYL INC
  • US10831575B2 patent drawing
  • US10831575B2 patent drawing
  • US10831575B2 patent drawing

AI summary

A computer-implemented method includes: receiving, by a computing device, information for composing a first enhanced plug-in, wherein the first enhanced plug-in includes one or more logical components for invoking the first enhanced plug-in by an application running in a different framework as the first enhanced plug-in; receiving, by the computing device, information for creating a workflow that includes a series of a plurality of enhanced plug-ins including the first enhanced plug-in and one or more subsequent second enhanced plug-ins; and invoking, by the computing device, the workflow, wherein the invoking the workflow causes the first enhanced plug-in to receive data from an application running on the same or different framework as the first enhanced plug-in, process the data, and forward the processed data as input data to a particular one of the one or more subsequent second enhanced plug-ins or an endpoint application.