Selective RPA Workflow APIs for Reusable Robot Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex RPA projects often require specialized knowledge and are costly due to multiple parties involved in maintenance and customization, and existing automation solutions are not easily reusable or adaptable to specific tasks and environments, posing challenges for 'citizen developers' lacking advanced programming skills.
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 selective execution by RPA robots, and facilitates the formulation of an RPA package for transmission to an RPA conductor.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If RPA workflows are designed by specialized developers using complex programming, then automation functionality is achieved, but the complexity and cost of development and maintenance increase
Solution Approach 1:
The patent employs template-based workflow design where pre-defined automation templates capture complex automation logic. Users can copy and instantiate these templates without programming, transferring the complexity from user operation to template creation by specialists. The template mechanism stores and reuses automation patterns, eliminating the need for users to understand underlying programming complexity.
Solution Approach 2:
The patent introduces an intermediary layer between the user and the automation execution engine. This intermediary consists of the template system and configuration interface that translates simple user selections into complex automation workflows. The intermediary handles the complexity of workflow orchestration, robot coordination, and error handling, while presenting a simplified interface to end users.
2Productivity
If RPA solutions are customized for specific tasks and environments, then task performance is optimized, but reusability and adaptability decrease
Solution Approach 1:
The patent segments automation workflows into modular templates that can be independently configured and reused. Each template represents a discrete automation function that can be selected and instantiated multiple times with different parameters. This segmentation allows workflows to be optimized for specific tasks while maintaining reusability through parameterization and modular design.
Solution Approach 2:
The patent enables workflow adaptability through parameterization, where templates contain configurable parameters that can be adjusted for different environments and tasks. By changing parameters rather than rewriting workflows, the same template can adapt to various scenarios, maintaining both optimization and reusability. The system allows dynamic parameter configuration without altering the core workflow logic.
3Reliability
If multiple parties are involved in RPA project maintenance and customization, then specialized knowledge is applied, but project cost and time increase
Solution Approach 1:
The patent enables end users to perform self-service maintenance and customization of RPA workflows through the template system. Users can modify template parameters, instantiate new workflows from templates, and adjust configurations without requiring specialized developers. This self-service capability reduces dependency on external specialists and accelerates the maintenance process while maintaining automation quality through validated template designs.
Data Source
AI summary
A robotic process automation (RPA) design interface enables selection of an RPA workflow forming a part of a complex RPA project and defines the selected workflow as a distinct executable entity invokable remotely via an API call (e.g., HTTP request) issued to an RPA conductor orchestrating multiple RPA robot execution. The RPA design interface enables user customization for 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 RPA project specification. 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 selected RPA workflow execution on a selected RPA robot.