Cloud Integration Plugin Resolving Form Field Dependencies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers face challenges in seamlessly integrating functionalities of cloud-based automation platforms like VMware Aria Automation with third-party platforms due to complex and nested dependencies between catalog items, inhibiting adoption and integration of multi-cloud configurations.

Innovation Solution

A management node with an integration plugin generates scripts to parse and manage form field dependencies, using APIs to dynamically generate client scripts for appearance, value, and constraint dependencies, enabling seamless integration between cloud-based automation platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual integration methods are used to integrate cloud-based automation platforms, then integration accuracy can be maintained, but integration time and complexity increase significantly

Engineering Contradiction:
Improveintegration accuracyVSAvoidintegration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system enables self-service integration by automatically generating client scripts and resolving form field dependencies without requiring manual intervention. The integration plugin autonomously parses API responses, identifies dependency relationships, and configures integrations, allowing the system to integrate itself while maintaining accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical integration processes with automated script-based systems. Client scripts automatically execute form field dependencies, resolve value constraints, and manage integration configurations, substituting human-operated mechanical processes with automated computational mechanisms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated script generation is implemented, then integration speed improves, but system complexity increases due to nested dependencies

Engineering Contradiction:
Improveintegration speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The integration system segments complex form field dependencies into individual manageable units. Each form field's dependencies are parsed and resolved separately through dedicated client scripts, breaking down the complex nested dependency structure into discrete, independently manageable segments that can be processed automatically.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The integration plugin acts as an intermediary between the cloud-based automation platforms and the third-party platforms. It mediates the complex dependency relationships by parsing API responses, identifying form field dependencies, and generating appropriate client scripts that resolve these dependencies, thereby simplifying the overall system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If comprehensive dependency resolution is performed, then integration reliability improves, but processing time increases

Engineering Contradiction:
Improveintegration reliabilityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system performs preliminary action by pre-resolving form field dependencies and generating client scripts before actual integration execution. The integration plugin parses API responses and identifies all dependency relationships in advance, preparing the integration configuration beforehand to ensure reliability while minimizing processing time during actual integration operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250110965A1Script generation for integrating functionalities of cloud-based automation platforms
Publication Date: 2025.04.03 VMWARE INC
  • US20250110965A1 patent drawing
  • US20250110965A1 patent drawing
  • US20250110965A1 patent drawing

AI summary

An example method may include executing, using an integration plugin installed on a first cloud-based automation platform running in a first management node, a schedule job to obtain an API response from a second management node executing a second cloud-based automation platform. The API response may include a custom form schema of a first form associated with the second cloud-based automation platform in a first defined data format. Further, the method may include parsing the custom form schema to determine form fields and dependency of the form fields. Furthermore, the method may include translating the custom form schema into a second defined data format supported by the first cloud-based automation platform based on the parsed custom form schema. Further, the method may include persisting the translated custom form schema in a database associated with the first cloud-based automation platform.