- Release Notes
- 2022.4.1
- 2022.4.3
- 2022.4.4
- 2022.4.5
- 2022.4.6
- 2022.4.7
- 2022.4.8
- 2022.4.9
- 2022.4.10
- Getting Started
- Introduction
- The User Interface
- Keyboard Shortcuts
- Signing in to Your Account
- Configuring Studio Settings
- Project Templates
- Orchestration Process
- Background Process
- Robotic Enterprise Framework
- Transactional Process
- Trigger Based Attended Automation
- Creating a Basic Process
- Creating a Basic Library
- Tutorials
- Setup and Configuration
- Hardware and Software Requirements
- Install Studio
- Deployment guidelines
- Services Studio Connects To
- Common Installation Errors
- Modify or Uninstall Studio
- Activate Studio
- About Flex Licensing
- Update Studio
- Command Line Parameters
- Supported Applications and Technologies
- Enabling Gmail for Email Activities
- Opting Out of Telemetry
- Automation Projects
- About Automation Projects
- About Publishing Automation Projects
- About Libraries
- Loading Web Services in Libraries
- Activities Generated from Web Services
- Managing activity packages
- Configuring Activity Project Settings
- Signing Packages
- Governance
- Importing Entities
- Modern Design Experience
- Linking a Project to an Idea in Automation Hub
- Dependencies
- About Dependencies
- Managing Dependencies
- Project Dependencies Mass Update
- Mass Update Command Line Parameters
- Missing or Invalid Activities
- Types of Workflows
- Sequences
- Flowcharts
- State Machines
- Global Exception Handler
- File Comparison
- About File Comparison
- Comparing Files
- Automation Best Practices
- Workflow Design
- UI Automation
- Project Organization
- Automation Lifecycle
- Methodology for reusing UI components
- Source Control Integration
- About Version Control
- Managing Projects With GIT
- Managing Projects With TFS
- Managing Projects With SVN
- Workflow Diff
- Debugging
- About Debugging
- Test Activities
- Debugging Actions
- The Locals Panel
- The Call Stack Panel
- The Breakpoints Panel
- The Watch Panel
- The Immediate Panel
- Remote Debugging
- The Diagnostic Tool
- About The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- Naming Rules
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- Design Best Practices
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Project Anatomy Rules
- ST-ANA-003 - Project Workflow Count
- ST-ANA-005 - Check Project.json Exists
- ST-ANA-006 - Main Workflow Exists
- ST-ANA-009 - File Activities Stats
- Maintainability and Readability Rules
- ST-MRD-002 - Activity Name Defaults
- ST-MRD-004 - Unreachable Activities
- ST-MRD-005 - Redundant Sequences
- ST-MRD-007 - Nested If Clauses
- ST-MRD-008 - Empty Sequence
- ST-MRD-009 - Deeply Nested Activities
- ST-MRD-011 - Write Line Usage
- ST-MRD-017 - Incomplete If
- Usage Rules
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Performance and Reusability Rules
- ST-PRR-004 - Hardcoded Delay Activity
- Reliability Rules
- ST-REL-006 - Infinite Loop
- Security Rules
- ST-SEC-007 - SecureString Argument Usage
- ST-SEC-008 - SecureString Variable Usage
- ST-SEC-009 - SecureString Misusage
- Variables
- Managing Variables
- The Variables Panel
- Types of Variables
- Text Variables
- Example of Using a Text Variable
- True or False Variables
- Example of Using a True or False Variable
- Number Variables
- Example of Using a Number Variable
- Array Variables
- Example of Using an Array Variable
- Date and Time Variables
- Example of Using a Date and Time Variable
- Data Table Variables
- Example of Using DataTable Variables
- UiPath Proprietary Variables
- Arguments
- Managing Arguments
- The Arguments Panel
- Using Arguments
- Imported Namespaces
- About Imported Namespaces
- Managing Namespaces
- Control Flow
- About Control Flow
- Control Flow Activities
- The Assign Activity
- The Delay Activity
- Example of Using the Delay Activity
- The Do While Activity
- Example of Using a Do While Activity
- The If Activity
- Example of Using an If Activity
- The Switch Activity
- Example of Using a Switch Activity
- The While Activity
- Example of Using a While Activity
- The For Each Activity
- Example of Using a For Each Activity
- The Break Activity
- Example of Using a Break Activity
- Object Repository
- About Object Repository
- Creating an Object Repository
- Reusing objects and UI libraries
- Logging
- Studio Logs
- Setup Logs
- OCR Diagnostic Logs
- Logging Levels
- Types of Logs
- Protecting Sensitive Information
- The ScreenScrapeJavaSupport Tool
- About the ScreenScrapeJavaSupport Tool
- Argument Descriptions for the ScreenScrapeJavaSupport Tool
- Studio testing
- Introduction
- Application Testing
- Execution Templates
- Working With Execution Templates
- Testing project templates
- SAP Testing Project
- Test Cases
- Data-Driven Testing
- Test Data File
- Auto-generated Test Data
- Data Service
- Test Data Queues
- RPA Testing
- Test Case Templates
- File Templates
- Test Explorer
- Test Results
- Activity Coverage
- Descriptor Coverage
- Mock Testing
- API Test Automation
- Extensions
- About extensions
- SetupExtensions Tool
- UiPath Remote Runtime
- Extension for Chrome
- Group Policies
- Troubleshooting
- Chrome Extension on Mac
- Extension for Edge
- Group Policies
- Troubleshooting
- Extension for Firefox
- Troubleshooting
- Extension for Java
- Troubleshooting
- Extension for Silverlight
- Extension for Citrix
- Extension for Microsoft Remote Desktop and Apps
- Troubleshooting
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User

Studio User Guide
The Test Activity context menu option part of the Designer panel is used for running a test on the currently selected activity. When clicked, the Locals panel opens displaying the variables and arguments in scope.
Test Activity can be used in two ways:
- add default values to properties and test
- add arguments and/or properties to activity properties and use the Local panel to add values after clicking the Test Activity option.
Double-click the value field of a variable or argument, or click the
icon in the Locals panel, and add a new value. Next, click Step Into to focus and execute the activity, and monitor the variable or argument's value in the Locals panel.
The same is available when clicking Continue, but the values are not visible in the Locals panel.
Please take into consideration that dynamic checks when variables depend on other variables that are defined later are not supported.
Execution logs generated by the Test Activity action are visible in the Output panel. Exceptions in Studio can be bubbled up, which means that the exception may be passed to parent containers in case it may be handled by them.
The Test Activity option is not available during debugging.
Example of Using Test Activity
For the If Activity example, we created a process that asks the user for two numbers, checks to see if one is divisible by the other, and depending on the result, displays a different message in the Output panel.
To check the behavior of the If activity defined in the process, use the Test Activity option, as illustrated below:
The Test Activity action places the activity in the debugger and asks you for values to variables. Once provided, click the Continue button for the debugging process to continue. In this particular case, a message was written in the Output panel with the correct answer, which means that the expressions written in the If activity were correct.
The Create Test Bench option allows for the creation of automation building blocks, which can then be tested and added to the final workflow.
It is used for testing activities, working with variables and debugging the process. All this is done in a test bench workflow, a temporary sequence that’s not part of the current project and that is discarded when closed.
The Create Test Bench option is similar to the Test Activity option, with the exception that the latter is contained and defined in an actual workflow.
To use the Create Test Bench option, go to the Activities panel search bar or use Ctrl + Alt + F keyboard shortcut. Type the name of an activity and right-click to open the context menu.
Select Create Test Bench and the activity is automatically added to a sequence file not included in your project. From there you can add other activities, change their default properties and debug the process. The Output panel displays any logs or errors found during the debugging.
To save the file to your project, simply use the ribbon option Save as, add a file name and save it to the same file path as your project.
Please note that Create Test Bench does not work with Pick Branch activity.
The Run to this Activity option is available when right-clicking an activity in the Designer panel.
This option starts the debugging process and pauses before the selected activity is executed while highlighting it in the panel. If Run to this Activity is triggered when debugging is already paused, the execution continues until the activity is reached.
The Run from this Activity context menu option enters debugging in a pause state, allowing you to make changes to the values of variables and arguments from the Locals panel. Press Continue to start debugging or use actions such as Step Into, Step Over, Step Out.
- When used for an activity inside a scope, the scope activity is also executed.
- An error occurs if you use Run from this Activity for an activity added inside one of the following scope activities: Try Catch, Switch, Parallel, Pick, Trigger Scope, or Retry Scope.