Dynamic Schema Adapter for Workflow Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise workflows face challenges in adapting to changes in remote service schemas, leading to failures or incomplete data access due to hardcoded schema dependencies, which complicates integration with third-party services.
Innovation Solution
The implementation of graphical user interfaces (GUIs) and mechanisms that allow for dynamic schema introspection and adaptation during workflow design, enabling the definition of metadata and integration actions that can handle unknown or changing schemas, allowing workflows to access and manipulate remote service data without requiring explicit schema knowledge.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the remote network management platform uses hardcoded schema dependencies to access remote service data, then the integration with remote services can be initially established, but the workflows will fail or be unable to access information when the remote service schema changes
Solution Approach 1:
The patent implements dynamic schema retrieval where the workflow engine automatically obtains updated schema definitions from the remote service at runtime. Instead of using static hardcoded schemas, the system dynamically queries the remote service metadata API to retrieve current schema information, ensuring workflows adapt to schema changes without manual intervention or failure.
Solution Approach 2:
The system establishes a feedback mechanism where the workflow engine continuously monitors remote service schema changes by periodically querying the metadata API. When schema changes are detected, the workflow definitions are automatically updated with the new schema information, creating a closed-loop system that maintains synchronization between the workflow engine and remote service schemas.
2Adaptability or versatility
If the remote network management platform manually updates schema definitions to match remote service changes, then schema synchronization can be maintained, but the time and complexity of integration increases significantly
Solution Approach 1:
The workflow engine implements self-service by automatically retrieving schema definitions from the remote service metadata API without requiring manual intervention. The system autonomously queries for updated schemas, parses the metadata, and updates workflow definitions in the background, eliminating the need for developers to manually track and update schema changes.
Solution Approach 2:
The system performs preliminary schema retrieval by querying the remote service metadata API in advance of workflow execution. Schema definitions are fetched and cached before workflows need to access remote service data, so when schema changes occur, the workflow engine already has the updated schema information ready to use.
3Adaptability or versatility
If the workflow definitions are made flexible to accommodate schema changes, then adaptability improves, but the complexity of workflow design and execution increases
Solution Approach 1:
The patent introduces a schema adapter layer that acts as an intermediary between the workflow engine and remote service schemas. This adapter automatically retrieves schema definitions from the remote service metadata API and translates them into workflow-compatible formats, shielding the workflow design from schema complexity while maintaining flexibility to adapt to schema changes.
4Ease of manufacture
If the platform introspects the remote service's current schema during workflow design, then the workflow can utilize available information effectively, but the time required for workflow definition increases
Solution Approach 1:
The system performs preliminary schema introspection by automatically querying the remote service metadata API during workflow definition. The schema adapter retrieves and caches schema definitions in advance, so when designers configure workflows, the schema information is already available, reducing the time needed for workflow definition while ensuring accurate utilization of remote service capabilities.
Data Source
AI summary
Persistent storage may contain metadata actions and integration actions related to a remote service, wherein the remote service includes a remote service application programming interface (API) that provides access to structured data, and a metadata API that provides access to a schema of the structured data. Processors may be configured to: (i) generate and provide, for metadata action design graphical user interfaces (GUIs), options for specification of a metadata action, where the metadata action defines a metadata query to the metadata API, rules for parsing the schema, and a normalized format for the structured data; (ii) generate and provide, for integration action design GUIs, options for specification of an integration action, where the integration action defines a structured data query to the remote service API and an indication that the metadata action is to be used to represent a result of the structured data query in the normalized format.