studio
2024.10
true
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- 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
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- 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
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- 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
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- 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
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Last updated Dec 4, 2024
2024.10.7
Release date: 4 December 2024
Using consumed and unconsumed test data queue items in data-driven testing
Experience greater flexibility in data-driven testing by choosing to process test data queues based on their consumption status. In the test data queue Query Builder, you can now choose to use test data queue items based on the following statuses: all, consumed, or unconsumed. For more information, visit Add Test Data Queue Items.
Workflow Analyzer rule for invalid coded parameters
We have introduced the ST-USG-017 Workflow Analyzer rule for coded automations, which
throws an error when the
Execute() entry method contains
out or ref parameters. For more information
about the rule and recommendations, visit ST-USG-017 - Invalid parameter modifier.
- Workflow Analyzer rules tailored for coded automations are now visible in the Workflow Analyzer panel.
- Now, if a connection to Integration Service fails in coded automations, a warning message appears in the Output panel notifying you of the issue.
- An error message is now triggered when attempting to create a new project in StudioX if the required project dependencies cannot be retrieved from the available feeds.
- Importing arguments of type Dictionary in an Invoke Workflow File activity did not work as expected in some projects.
- After switching to the StudioX profile, you could not create a new project from a template if the user interface language was set to Korean.
- An argument converted from a variable with no default value set in Studio appeared to have a default value when configuring the process in UiPath Assistant and Orchestrator.
- Unexpected validation errors
occurred in some projects when converting a
DataTablevariable. - In some projects containing Else If activities, the universal search returned inconsistent results depending on what project files were opened. The issue was fixed in the UiPath.System.Activities package v24.3.0 and newer.
Naming a project containing coded automations with names used in activity packages results in a compilation failure. To avoid this, we recommend to rename the project. For more information about names that can cause this issue, and how to avoid it, visit Assembly compilation errors.
The following activity packages and versions
are included in the
UiPathStudio.msi installer and can be found in
the local feed.
|
Activity package |
Version |
|---|---|
|
UiPath.UIAutomation.Activities | |
|
UiPath.System.Activities | |
|
UiPath.Excel.Activities | |
|
UiPath.Mail.Activities | |
|
UiPath.Word.Activities | |
|
UiPath.ComplexScenarios.Activities | |
|
UiPath.Presentations.Activities | |
|
UiPath.Testing.Activities | |
|
UiPath.WebAPI.Activities | |
| UiPath.Form.Activities | v24.10.5 |
| UiPath.Callout.Activities | v24.10.5 |
