SaaS Integration Framework Using Pre-defined Workflow Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software integration frameworks for SaaS functionality over computer networks are inefficient, leading to increased processing, storage, and data transmission resource requirements, which can be costly and latency-prone, and often require more capable hardware, hindering faster integration development and deployment.
Innovation Solution
A versatile integration framework that allows an online software platform to select and implement a workflow framework from a catalog, transmitting a software package with pre-defined integration points and requests/responses to embed SaaS functionality into applications, enabling faster integration and reducing resource demands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current software integration frameworks are used, then integration functionality is provided, but processing resources, storage resources, and data transmission resources are increased
Solution Approach 1:
The integration framework is segmented into reusable workflow framework templates and application-specific implementations. The OSP maintains a library of workflow framework templates that can be selectively applied, dividing the integration process into manageable, pre-defined segments that reduce processing overhead compared to building integrations from scratch.
Solution Approach 2:
Workflow framework templates are prepared in advance by the OSP and stored in a library. When an integration partner needs integration functionality, they select from pre-prepared templates rather than creating integrations dynamically. This preliminary preparation of integration frameworks reduces processing resources required at runtime.
2Productivity
If current software integration frameworks are used, then integration functionality is provided, but hardware capabilities are required to be more capable
Solution Approach 1:
The workflow framework templates are designed to be universal and applicable across multiple applications and integration scenarios. A single template can serve multiple purposes across different client systems, reducing the need for specialized hardware capabilities in each specific integration case.
Solution Approach 2:
Instead of creating custom integration logic for each application, the system uses copies of proven workflow framework templates that have been previously developed and optimized. These templates can be replicated and applied across multiple integrations, reducing the computational complexity and hardware requirements for each new integration.
3Reliability
If current software integration frameworks are used, then integration is achieved, but latency is increased
Solution Approach 1:
Workflow framework templates are validated, optimized, and ready for deployment in advance. When an integration is needed, the pre-validated template can be immediately applied without requiring runtime compilation or extensive processing, thereby reducing latency while maintaining reliable integration functionality.
Solution Approach 2:
The system allows selection of different workflow framework templates based on specific integration requirements. By changing parameters such as the chosen template type and configuration, the system can optimize for different performance characteristics including latency reduction while maintaining the necessary integration reliability.
Data Source
AI summary
An online software platform (OSP) electronically receives a selection of a workflow framework of a plurality of workflow frameworks. Each workflow framework includes a configuration to embed software-as-a-service (SaaS) functionality provided by the OSP into an application that uses the SaaS functionality. The OSP electronically provides services for determining respective resources for individual relationship instances between different entities. In response to receiving the selection, the OSP causes a remote system that hosts the application to implement the selected workflow framework. This is performed by transmitting a software package to the remote system, in which the software package exposes a set of pre-defined integration points with the SaaS provided by the OSP to provision the steps in one or more of the workflows of the selected workflow framework or defines a specific set of requests and responses with the SaaS provided by the OSP.