Web Service Workflow Automation via Scripted Replay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face labor-intensive and tedious processes when completing multiple projects using different web services, such as designing brochures, due to repetitive tasks that require manual navigation and security operations across multiple services, which are difficult to automate without significant programming knowledge.

Innovation Solution

A method and system for recording and securing scripts of user interactions with multiple web services, allowing for automated execution of these services without individual manual operation, using browser extensions to capture and replay user activities, including security operations, and storing data securely in a Document Bucket.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually complete multiple projects using different web services, then they can access and use each service individually, but the process becomes labor-intensive and tedious due to repetitive tasks across multiple services

Engineering Contradiction:
Improveease of using multiple web servicesVSAvoidtime spent on repetitive tasks
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent combines multiple independent web service interactions into a single unified workflow execution. The workflow engine orchestrates sequences of web service calls, allowing users to define once and execute repeatedly without manual intervention for each step, thus merging repetitive operations into an automated process.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent enables users to pre-define workflow configurations that capture the sequence of operations across multiple web services before execution. This preliminary setup includes defining service endpoints, parameters, and execution logic in advance, so that when the workflow is triggered, all preliminary actions are already prepared and can be executed automatically without repeated manual configuration.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If users automate web service composition using programming languages or scripting, then automation capability is achieved, but significant programming knowledge and skill are required

Engineering Contradiction:
Improveautomation of web service executionVSAvoidprogramming knowledge required
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The patent introduces a workflow engine as an intermediary layer between the user and the web services. This engine handles the complexity of service composition, orchestration, and execution automatically. Users interact with a simplified workflow definition interface rather than writing complex service composition code, while the engine mediates the actual service calls and coordinates the automation process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal workflow execution platform that can handle multiple different web services through a common interface and standardized interaction patterns. This multi-functional system allows the same automation mechanism to work across diverse services without requiring service-specific programming knowledge, making automation accessible to non-programmers.

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

3Ease of operation

If graphical user interface based composition is used to drag and drop service representations, then users can visually compose services, but services with user interfaces cannot be processed and user interfaces are not preserved

Engineering Contradiction:
Improvevisual service compositionVSAvoidability to handle services with user interfaces
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the service interaction process into distinct phases: workflow definition (visual composition of service sequences) and execution (where actual service interactions occur). This segmentation allows the visual composer to handle high-level workflow structure while preserving the ability to interact with services that have their own user interfaces during the execution phase, maintaining both visual ease-of-use and interface adaptability.

Inventive Principle:
Principle #1Segmentation

4Reliability

If security requirements are implemented for each web service, then data protection is achieved, but users must pass security requirements multiple times for each service

Engineering Contradiction:
Improvedata securityVSAvoidrepeated security operations
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent merges multiple individual service authentication operations into a single unified authentication process. The workflow engine establishes security credentials once at the beginning of workflow execution and reuses them across multiple service calls within the workflow, eliminating the need for users to repeatedly enter credentials for each service while maintaining security through the engine's managed authentication process.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8881303B2System and method for executing web services
Publication Date: 2014.11.04 XEROX CORP
  • US8881303B2 patent drawing
  • US8881303B2 patent drawing
  • US8881303B2 patent drawing

AI summary

The subject embodiments provide a method such as a web service method. The method is used to execute two or more web services that have respective web user interfaces, and are operationally independent of each other. The method comprises: (i) executing the two or more web services under manual operation of a user; (ii) recording a script based on activities of the user in the execution; (iii) securing the recorded script; and (iv) executing the two or more web services by playing said secured script without individually executing them. The method is user friendly; highly customizable; and safe with respect to document retrieval and submission.