studio
2022.4
false
- 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
OUT OF SUPPORT
Studio User Guide
Last updated Oct 23, 2025
You can use Data Service, both in Automation Cloud and Automation Suite, as a source for your data-driven testing. The data is imported from Data Service entities, exposing the fields as workflow arguments. All imported entities are stored in the Project tab, under Entities. To ensure you have the necessary licenses for using Data Service, visit License allocation and management.
You can perform data-driven testing with Data Service only with version 22.4 or higher of the Testing.Activities package.
Important: After importing a data service entity, an argument is generated in the Arguments panel. The name of the argument must stay the same. If you change the name of the argument, you can't access the data anymore.
- When you configure a Data Service source, the data is fetched from the first entry in the enitity.
- To Run and Debug test cases with dynamic test data, use the Test Explorer. The data comes from the Data Service entity during runtime, and the Test Explorer populates the values at runtime.
- If you close your session and open the project again, you need to run the file with data variation again to load the test data.
- If you update the entity, you need to run the file with the data variation to load the updated test data.
- Test cases with data variations that are empty are marked as failed.
- A test case setup is created in Orchestrator, when you execute test cases containing data variations from Data Service.
- For data-driven testing, the argument name generated by Data Service-driven test
cases does not comply with the ST-NMG-002 workflow analyzer rule recommending the use of
in_and_outprefixes. Adapting the argument name to fit this rule may prevent data retrieval from the Data Service entity. - If you create a data-driven test case that accepts an input argument, publish it
in a test set, and attempt to define the argument value directly from the
Orchestrator UI, the input argument value does not get passed to the test
variations.
Workaround: To overcome this limitation, add the input argument directly to the Data Service entity.
When you add test data to your test case, you can filter the entity to retrieve only specific fields from Data Service. You can configure the filters by using the built-in Query Builder.
- Create a new test case with test data, or add test data to an existing test case.
-
Click Source and select Data Service from the dropdown list.
Note: If the option is not available, check the requirements. - Select an entity or use the search function to look for it.
- Click the Filter icon to open Query Builder.
- Use the first dropdown list to filter by a criterion (e.g.,
CreateTime). - (Optional) You can add rows and groups when you click Add and then configure the conditions.
- (Optional) You can select to filter by all or any of your criteria by choosing AND or OR.
- Enter a Name for your filter.
- (Optional) Use the Range to configure specific row intervals. This is useful if you have hundreds of fields in your entity.
-
Click OK to confirm.
The data is fetched from the entity and added to the test case as an Argument Type. Only the first entry in the entity is fetched. You can access the data through the arguments.
- Already using a CSV file for your data-driven testing? You can upload it to Data Service using batch activities.
- Update or remove test data.