Workflow Hooks for Application Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for automating workflows across multiple software applications are either expensive and require significant modifications or rely on complex programming skills, limiting the ability to utilize the full capabilities of diverse software applications without the constraints of enterprise resource planning systems or specialized workflow languages.

Innovation Solution

A workflow processing language with hooks that provide programming interfaces to various applications, allowing for the conversion of input streams into processable objects and output streams, enabling interaction with a range of applications like databases, e-mail, and issue tracking software without extensive programming knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If enterprise resource planning (ERP) software is used to automate workflows, then workflow automation is achieved, but the solution becomes extremely expensive and requires major modification of workflows

Engineering Contradiction:
Improveworkflow automationVSAvoidworkflow modification complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system segments the workflow automation problem into two parts: a standardized workflow engine and separate application-specific adapters. This allows the core workflow logic to remain simple and standardized while the adapters handle application-specific complexities, avoiding the need for major workflow modifications required by ERP systems.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the workflow engine with adapters) between the workflow definition and the applications. This intermediary translates standardized workflow commands into application-specific operations, eliminating the need to restructure workflows to fit application capabilities while avoiding the complexity and cost of ERP systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If specialized workflow languages like BPEL are used, then workflow definition capability is provided, but skilled programmer input is required and full application capabilities cannot be utilized

Engineering Contradiction:
Improveapplication capability utilizationVSAvoidprogramming skill requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The workflow engine provides universal, application-agnostic workflow definitions that can interact with multiple different applications through standardized adapters. This allows non-programmers to define workflows using simple, standardized commands while the adapters handle the complexity of interacting with diverse applications, thereby utilizing full application capabilities without requiring specialized programming skills.

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

Solution Approach 2:

The adapter layer acts as an intermediary that translates standardized workflow commands into application-specific operations. This allows the workflow definition language to remain simple and universal while still accessing the full capabilities of various applications, eliminating the need for skilled programmers to write complex application-specific workflow logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If consistent input and output formats (e.g., XML) are required from all applications, then workflow standardization is achieved, but many applications cannot be used and specialist programming is required to adapt inputs and outputs

Engineering Contradiction:
Improveworkflow development easeVSAvoidapplication compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces adapters as intermediaries between the standardized workflow engine and diverse applications. These adapters handle format conversion and protocol translation, allowing the workflow engine to use consistent, simple commands while supporting a wide variety of applications with different input/output formats without requiring specialist programming to adapt each application.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of requiring applications to conform to a specific format (XML), the system creates adapter copies that translate application-specific formats into the standardized workflow commands. This allows the workflow engine to maintain simple, consistent operations while supporting diverse applications, eliminating the need for format adaptation programming.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11023839B2Workflow integration
Publication Date: 2021.06.01 MASTERCARD INT INC
  • US11023839B2 patent drawing
  • US11023839B2 patent drawing
  • US11023839B2 patent drawing

AI summary

A method of constructing a workflow is described. The method is carried out by a programmed processor and a memory of a computing apparatus using a workflow processing language. One or more hooks are provided in the workflow processing language. Each hook is adapted to provide a programming interface to one of one or more applications. An input stream is received and converted into an input object that can be processed by the workflow processing language. A workflow with hooks to one or more applications is then used. The one or more hooked applications are used through the programming interface provided by the respective hook to prepare and provide an output stream. The computer apparatus adapted to construct and perform such workflows is also described.