RPA Workflow Test Execution for Application Change Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Robotic process automation (RPA) systems face challenges in maintaining stability due to application and environment changes, lacking effective maintenance and exception handling, leading to frequent bot failures.

Innovation Solution

A computer-implemented method for creating and executing test cases for existing workflows to identify environmental and automation issues, reporting failed tests, and notifying users, which includes creating test cases for workflows, executing them to detect issues, and providing results with failure notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If RPA bots are implemented to automate processes, then productivity is improved, but reliability deteriorates due to application changes and environment changes

Engineering Contradiction:
Improveprocess automation efficiencyVSAvoidbot stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically detecting application changes and environment changes before they cause bot failures. Change detection mechanisms monitor applications and environments proactively, identifying modifications ahead of time so that bots can be updated or adjusted before stability is affected

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback loops where bot execution results, error logs, and performance metrics are continuously analyzed. This feedback enables automatic adjustment of bot parameters and triggers alerts when reliability thresholds are breached, allowing the system to self-correct and maintain stable operation despite external changes

Inventive Principle:
Principle #23Feedback

2Ease of operation

If RPA implementations focus on happy paths, then ease of operation is improved, but reliability deteriorates due to lack of exception handling

Engineering Contradiction:
Improveautomation implementation simplicityVSAvoidexception handling capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments the automation workflow into distinct components: happy path execution, exception detection zones, and error handling modules. This segmentation allows the main workflow to remain simple and easy to implement while dedicated exception handling segments manage reliability concerns separately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system prepares exception handling mechanisms in advance by pre-defining error handlers, fallback procedures, and recovery protocols for anticipated failure scenarios. This cushioning ensures that when exceptions occur, the system can gracefully handle them without compromising overall reliability

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If manual testing of workflows is performed, then reliability is improved through issue detection, but productivity deteriorates due to increased time consumption

Engineering Contradiction:
Improveworkflow issue detectionVSAvoidtesting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs self-testing by automatically executing test cases, analyzing results, and generating reports without human intervention. The automated testing framework independently validates workflow correctness, detects issues, and even self-corrects certain problems, eliminating the need for manual testing while maintaining high reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous automated testing that runs alongside bot execution, providing ongoing validation rather than periodic manual checks. This continuous action ensures issues are detected immediately upon occurrence, maintaining reliability without interrupting productivity

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11789853B2Test automation for robotic process automation
Publication Date: 2023.10.17 UIPATH INC
  • US11789853B2 patent drawing
  • US11789853B2 patent drawing
  • US11789853B2 patent drawing

AI summary

Test cases for existing workflows (or workflows under test) may be created and executed. A test case may be created for a workflow in production or one or more parts of the workflow, and the created test case for the workflow, or the one or more parts of the workflow, may be executed to identify environmental and/or automation issues for the workflow. A failed workflow test may be reported when the environmental and/or automation issues are identified.