SOAP Workflow Configuration via Visual Flow Designer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud computing systems face challenges in efficiently integrating and managing vast amounts of data, particularly in multi-tenant and multi-instance cloud architectures, leading to issues such as data segregation failures and increased downtime.

Innovation Solution

A system and method utilizing an integration hub with a flow designer and SOAP wizard to create and configure SOAP components, enabling codeless development and automated processes for interacting with web-based services, allowing users to define workflows without traditional programming languages, and facilitating efficient data management and integration across disparate systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional programming languages and manual coding methods are used to integrate web-based services, then integration functionality can be achieved, but development time and system complexity increase significantly

Engineering Contradiction:
Improveworkflow integration speedVSAvoidconfiguration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system enables self-service configuration where the SOAP wizard automatically generates integration code and configures workflows without requiring manual programming. Users simply select services and parameters through a graphical interface, and the system automatically handles the complex integration tasks, eliminating the need for traditional code-based development.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual coding mechanics with an automated wizard-based system. Instead of requiring users to write and compile programming code, the SOAP wizard automatically generates the necessary integration logic, configuration files, and deployment scripts through a user-friendly graphical interface, substituting mechanical programming operations with automated software processes.

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

2Reliability

If manual configuration methods are used for SOAP components, then integration can be achieved, but deployment time and resource allocation efficiency decrease

Engineering Contradiction:
Improvedata segregationVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The SOAP wizard performs preliminary configuration actions by pre-generating integration code, validating service compatibility, and preparing deployment packages before actual deployment. This advance preparation ensures that data segregation requirements are built into the configuration from the start and eliminates time-consuming manual setup during deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The wizard acts as an intermediary between the user's integration requirements and the complex SOAP configuration processes. It mediates by automatically translating high-level user selections into detailed technical configurations, handling service endpoint mappings, authentication settings, and data segregation rules without requiring users to manually configure each parameter.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If code-based development is used for workflow automation, then functional flexibility is achieved, but ease of operation and user accessibility decrease

Engineering Contradiction:
Improveworkflow customizationVSAvoidconfiguration accessibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system uses template-based copying where pre-defined workflow patterns and integration templates are provided that users can select and customize. Instead of requiring users to build workflows from scratch using code, the wizard provides reusable templates that can be copied, modified, and adapted to specific needs through simple parameter adjustments in the graphical interface.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The SOAP wizard provides a universal configuration interface that handles multiple types of web services, authentication methods, and integration scenarios through a single unified tool. This multi-functional approach allows users to configure diverse workflows without needing to learn different programming languages or tools for different service types.

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

4Ease of operation

If automated wizard-based configuration is implemented, then ease of operation improves, but system complexity for the wizard itself increases

Engineering Contradiction:
ImproveSOAP component configurationVSAvoidwizard system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The wizard system is segmented into modular components, each handling specific aspects of SOAP configuration such as service discovery, endpoint mapping, authentication, and deployment. This segmentation allows the complex wizard functionality to be broken down into manageable, independently developed modules that can be maintained and updated separately, reducing the complexity burden on any single component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3903181B1System and method for configuring simple object access protocol (SOAP) components
Publication Date: 2026.03.25 SERVICENOW INC
  • EP3903181B1 patent drawingFigure 1
  • EP3903181B1 patent drawingFigure 2
  • EP3903181B1 patent drawingFigure 3

AI summary

A computing system includes a server. The server is communicatively coupled to a data repository local to the computing system and is configured to perform operations comprising creating, via a visual information flow creation tool, at least one information flow object in a series of flow objects of a work flow, and which comprises components that may be used to communicate with systems external to the server via simple object access protocol (SOAP).