RPA Debugging via UI Element Matching and Error Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Robotic Process Automation (RPA) debugging is hindered by the inability to accurately identify target user interface elements at runtime, leading to errors and requiring advanced technical knowledge for debugging, especially when the UI changes between design and runtime.
Innovation Solution
A method where a software robot searches for UI elements matching specified characteristics and displays an error message indicating which characteristics do not match, along with suggesting alternative target elements, facilitating debugging by providing intuitive error reporting and updating RPA scripts to redirect automation activities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional RPA debugging methods are used, then debugging can be performed, but it requires advanced technical knowledge and is difficult for users without programming skills
Solution Approach 1:
The patent introduces an intermediary debugging system that acts as a mediator between the RPA software robot and the user. This system translates technical debugging information into user-friendly visual representations, including automatic identification of mismatched UI elements and generation of suggested corrections, thereby bridging the gap between complex system behavior and user comprehension without requiring advanced programming knowledge
Solution Approach 2:
The patent replaces manual, step-by-step debugging mechanics with an automated diagnostic system. Instead of requiring users to manually trace through code and UI interactions, the system automatically detects mismatches between expected and actual UI elements, identifies the root causes, and provides corrective suggestions, substituting mechanical debugging processes with intelligent automation
2Adaptability or versatility
If the UI changes between design and runtime, then the system adapts to new interfaces, but target element identification fails leading to automation errors
Solution Approach 1:
The patent implements a feedback mechanism where the debugging system continuously monitors and compares the designed UI structure with the actual runtime UI. When mismatches are detected, the system provides feedback about the specific differences (such as changed element IDs, missing elements, or structural changes) and suggests corrective actions, enabling the RPA bot to adapt to UI changes while maintaining reliable element identification
Solution Approach 2:
The patent applies preliminary action by pre-establishing multiple identification strategies for UI elements during the design phase. The system prepares alternative selection methods and contingency plans before runtime, so when UI changes occur, the debugging system can quickly evaluate which pre-planned identification approach will work and suggest appropriate corrections, preventing identification failures before they occur
Data Source
AI summary
In some embodiments, a robotic process automation (RPA) robot is configured to identify a runtime target of an automation activity (e.g., a button to click, a form field to fill in, etc.) by searching a user interface for a UI element matching a set of characteristics of the target defined at design-time. When the target identification fails, some embodiments display an error message indicating which target characteristic could not be matched. Some embodiments further display for selection by the user a set of alternative target elements of the runtime interface.