RPA Workflow API Invocation for Reusable Robot Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing RPA technologies are complex, costly, and require specialized knowledge, making them difficult for non-technical users to maintain and customize, and are often tailored to specific tasks and environments, limiting their reusability and adaptability.
Innovation Solution
A computer system with an RPA design application that allows users to select and configure RPA workflows through user-defined API call parameter values, enabling the formulation of an RPA package for selective execution by RPA robots, facilitating user-friendly automation development and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RPA workflows are designed by specialized developers using complex tools, then automation functionality is achieved, but the system becomes difficult to maintain and customize for non-technical users
Solution Approach 1:
The patent introduces an API as an intermediary layer between non-technical users and the complex RPA workflow system. Users can invoke workflows by making simple API calls with basic parameters, without needing to understand the underlying automation logic. The RPA conductor acts as a mediator that receives these simple API calls and translates them into complex workflow executions, thus shielding users from system complexity while maintaining full functionality.
Solution Approach 2:
The patent transforms the interaction model from complex graphical interface operations to simple parameter-based API calls. By changing the interface parameters from visual drag-and-drop operations to structured data parameters in API requests, the system becomes accessible to non-technical users while maintaining the same automation capabilities.
2Adaptability or versatility
If RPA solutions are tailored to specific tasks and environments, then task-specific automation is achieved, but reusability across different contexts is limited
Solution Approach 1:
The patent makes RPA workflows universally accessible through a standardized API interface. The same workflow can be invoked from different applications, platforms, and environments by making API calls with appropriate parameters. This universal interface allows a single workflow to serve multiple purposes and contexts, dramatically improving reusability without requiring separate customizations for each use case.
Solution Approach 2:
The patent enables dynamic workflow selection and configuration through API parameters. Workflows can be selectively invoked with different parameter values to adapt to various contexts and environments. The RPA conductor dynamically routes API calls to appropriate workflows and adjusts execution based on provided parameters, allowing the same workflow infrastructure to handle diverse tasks without static hardcoding.
3Reliability
If multiple parties are involved in maintenance and customization of RPA projects, then specialized functionality is maintained, but maintenance speed and cost increase
Solution Approach 1:
The API serves as an intermediary that standardizes interaction with RPA workflows, reducing the need for multiple specialized parties. Non-technical users can independently perform maintenance and customization by making API calls, without requiring involvement from RPA developers. This reduces coordination overhead and maintenance costs while maintaining system reliability through the standardized interface.
Solution Approach 2:
The patent enables non-technical users to perform self-service maintenance and customization of RPA workflows through the API. Users can independently modify workflow parameters, invoke workflows with different configurations, and adapt automation to their needs without external assistance. This self-service capability dramatically improves maintenance efficiency while preserving automation reliability through the controlled API interface.
Data Source
AI summary
In some embodiments, a robotic process automation (RPA) design interface enables a user to select an RPA workflow forming a part of a complex RPA project, and define the selected workflow as a distinct executable entity that can be invoked remotely via an API call (e.g., HTTP request) issued to an RPA conductor orchestrating the execution of multiple RPA robots. The RPA design interface enables the user to customize a set of API call parameters (e.g., HTTP method, URI, input and/or output arguments) for invoking the respective RPA workflow. The user-defined, workflow-specific API call parameter values may then be transmitted to the RPA conductor, for instance as metadata attached to a specification of the RPA project. In turn, the RPA conductor automatically generates an API specification (e.g., OpenAPI or Swagger™) for the workflow fragment. In response to receiving an API call configured with the respective workflow-specific call parameter values, the RPA conductor selectively triggers execution of the selected RPA workflow on a selected RPA robot.