IT3868: RPA Debugging in UiPath

Robotic Process Automation (RPA) Debugging in UiPath

• RPA is robotic process automation
• IT3868/C-Robotic Process Automation course covers debugging in UiPath
• UiPath is a software platform for automating business processes

Understanding Debugging

• Debugging involves identifying and removing errors in a program
• UiPath allows debugging and handling exceptions

Exception

• An exception is an error that disrupts normal program execution
• Exceptions represent deviations from expected business outcomes
• Common exceptions include time exceptions, I/O exceptions, user exceptions, and class exceptions

Exception Handling

• Responsive process methods address runtime errors
• Precautionary methods prevent deviations
• Enables program resumption from interruption point

Types of Exceptions

• System Exception: A disruption due to system failure
• Business Rule Exception: A disruption in the business process

Business Exception

• Deviation from standard business practices or process rules
• Example: An email subject changing unpredictably results in an inability to pick the email
• Solution: Use unique identifiers to avoid misidentification

System Exception

• Example: If Outlook isn't functioning, the robot can't open attachments
• Causes: System failure
• Solution: Develop code to be error-proof against system issues

Introduction to Debugging

• Debugging identifies and removes errors in a given project
• A UiPath project includes stages of: Start, Design, Execute, Stop, Debug
• Tools include: Step Into, Step Over, Break, Validate Breakpoints, Slow Step, Open Logs, Debug, Highlight elements, Log Activities, Break on Exceptions

Debugging Tools

• Properties Inspector Panel: Displays properties of actively used components, values of variables, and debugging scope
• Locals Panel: Shows values of variables during program execution, scope-based highlighting for active variables
• Output Panel: Shows a detailed log of the workflow's current state, executed activities, and status of the robot

Locals Panel

• Shows values of all variables within scope, highlighting currently active variables

Output Panel

• Provides a detailed log, workflow status, and the status of all executed activities

Properties Inspector Panel

• Displays active action properties, values of variables, and debugging scope

Debugging Techniques

• Setting Breakpoints: Pauses the program execution for inspection at a specific location
• Highlight Elements: Shows impact on application during debug mode
• Step Into: Pauses execution at the next line of code
• Step Over: Skips execution of the current line of code to the next line
• Slow Step: Lowers execution speed for better observation
• Methods and Techniques of debugging: Highlighting elements for workflow process testing

Setting Breakpoints

• Pauses the program at a specific location, allowing inspection
• Locations to set breakpoints can be: Run, Step, Debug, Step Into, Step Over, validate Breakpoints, Slow Step

Other Debugging Techniques

• Step Into: Move into the next instruction/action to debug
• Step Over: Jumps over instructions without debugging them
• Slow Step: Reduces program execution speed
• Highlight Elements: Shows application impact during debug

Common Automation Issues

• Element Not Found: The target object is not visible to the automated process
• Timing Issues: The application/webpage takes longer to load than expected

Element Not Found

• The automated process cannot find the element required for interaction
• Reasons include incorrect selectors or application running in the background
• Solution: Correct identification, verification, and handling of visibility issues

Strategy for Solving the Issue

• Element Not Found: Send window messages, indicate screen, and edit the selector using tools like UI Explorer
• Steps: Indicate the location of the element not found
• Edit the selector and verify in UI Explorer to fix the problem

Timing Issue

• The screen takes longer than expected to load.
• Causes: System latency, application response delays.
• Example: Web page load time depends on internet speeds
• Strategies: Slow Step, Use element that exists; add an if condition; use the type into activity

Try Catch Activity

• Part of UiPath error-handling
• Enables program recovery from errors
• Handles specific error types rather than halt the program execution

Try Catch Activity (Contd.)

• Used to handle errors in a UiPath workflow
• Try Block: Contains activities susceptible to error
• Catch Block: Handles specific exceptions
• Finally Block: Contains activities executed regardless of errors

Throw Activity

• Used to trigger a specific exception
• The catch block handles that exception

The Throw Procedure

• Step 1: Drag and drop the Try-Catch activity and drag the Throw activity inside the Try block
• Step 2: Specify the exception type and message in the Expression Editor of the Throw activity
• Step 3: Matching error type in the catch block