Low-Code RPA Development Application for Attended and Unattended Robot Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current robotic process automation (RPA) technologies lack efficient application integration capabilities, relying on hard-coded automation and requiring substantial programming expertise, which limits their usability and flexibility in automating repetitive tasks across various applications.

Innovation Solution

A low-code development application is used to link triggers in RPA-enabled applications with RPA processes, allowing for the generation and deployment of instances that can interact with both local and remote RPA robots through Inter-Process Communication (IPC), enabling users to create and execute RPA workflows without extensive programming knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If hard-coded automation functionality is used in current RPA technologies, then automation capability is provided, but programming expertise is required and usability is limited

Engineering Contradiction:
ImproveEase of creating RPA workflowsVSAvoidProgramming complexity required
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer between the user and the RPA execution engine. This layer provides a simplified interface that translates user-friendly actions into executable RPA workflows, eliminating the need for users to write complex code while maintaining full automation capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical system of hard-coded programming with a more advanced system that uses configurable workflows and visual interfaces. This substitution allows users to create automated processes through configuration rather than coding, reducing the barrier to entry while preserving automation functionality.

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

2Adaptability or versatility

If RPA robots are deployed to automate tasks, then task automation is achieved, but integration with applications requires substantial programming knowledge

Engineering Contradiction:
ImproveApplication integration capabilityVSAvoidUsability for non-technical users
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal interface that works across multiple applications and RPA scenarios. The system provides a single, consistent method for integrating with different applications, eliminating the need for application-specific programming knowledge while maintaining broad adaptability.

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

Solution Approach 2:

The patent changes the parameters of interaction by shifting from code-based configuration to parameter-based configuration. Users can integrate with applications by setting parameters and selecting options rather than writing code, making the system accessible to non-technical users while maintaining integration versatility.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If traditional RPA development methods are used, then automation functionality is provided, but development time and complexity increase

Engineering Contradiction:
ImproveRPA process automation efficiencyVSAvoidDevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-configuring templates, workflows, and integration patterns that can be reused across multiple projects. This allows users to start automation tasks with pre-built frameworks rather than creating everything from scratch, significantly reducing development time while maintaining high productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables copying and reusing of successful automation patterns and workflows. Once a workflow is created or imported, it can be copied and adapted for similar tasks, eliminating redundant development work and accelerating the automation deployment process.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11494203B2Application integration for robotic process automation
Publication Date: 2022.11.08 UIPATH INC
  • US11494203B2 patent drawing
  • US11494203B2 patent drawing
  • US11494203B2 patent drawing

AI summary

Application integration for robotic process automation (RPA) using a development application configured for development of RPA-enabled applications is disclosed. The development application in some embodiments may be used for application integration with attended robots that execute locally on the same computing system as an instance of the RPA-enabled application, unattended robots that execute on a remote computing system, or both, creating an RPA-enabled application. One or more user interface (UI) elements, variables, and/or events of an RPA-enabled application may be linked to one or more respective RPA processes, causing respective RPA robot(s) to carry out the associated functionality.