- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
2023.4.2
Release date: 7 June 2023
The separation between design time and runtime packages that was disabled in the previous patch has been re-enabled. In Windows and cross-platform projects, a new Project Settings option, Separate Runtime Dependencies, now lets you enable or disable the separation at the project level. The option is enabled by default.
The Include Sources option was also moved from the Publish window to the Project Settings window, enabling you to configure it per project.
Organizations can control both options using governance policies.
You now have the option to open a XAML file both in the Designer panel and as a read-only text file in a separate tab by right-clicking the XAML file in the Project panel and selecting Open in Text Editor.
- The separation between design time and runtime packages was not handled correctly when there were conflicts between the package versions used in projects and those used in libraries installed in the projects.
- Some activities packages were marked as
"found empty" in the Project panel when installed in Windows libraries. The affected
packages include:
Microsoft.VisualBasicSystem.IO.FileSystem.AccessControlSystem.Security.AccessControlSystem.Security.Cryptography.XmlSysten.Security.Principal.WindowsSystem.Text.Encoding.CodePagesSystem.Text.RegularExpressions
- An assembly reference error occurred in some projects when using the Verify Expression activity to verify an expression. To apply the fix, select to import missing references from the dialog that appears when opening the file.
- Using the Universal Search bar to search within a Windows project did not return results from all workflow files.
- Project validation failed if a Windows - Legacy project contained a CV Screen Scope activity and the OCR engine was changed from UiPath Screen OCR or UiPath Document OCR.
- Changing the value for the list of items property in a For Each activity when the activity was in focus resulted in unexpected changes appearing in the workflow.
- An error occurred when trying to perform a fresh per-machine installation on a machine where Studio had been previously installed per user.
- Further improvements were made to a fix for higher than expected memory consumption when multiple interdependent libraries were installed in a project.
- A Could not load file or assembly error occurred when running a cross-platform project from UiPath Assistant or Orchestrator if the project had the UiPath.DocumentUnderstanding.Activities v2.2.0 package added as a dependency.
-
Project compilation failed when running a C# project that contained a library added as a dependency if the library included an activity with the In argument of type Newtonsoft.Json.Linq.JObject and the project included a variable or argument of the same type assigned to the input property of the custom activity.
- Test cases wrapped in Execution Templates that threw an exception while running them from the Test Explorer panel using either Run All in View or Run All, caused the auto-generated XAMLs to gradually open. This behavior affected the performance of project execution.
- Workflows designed with activities from custom libraries threw the following error when analyzed with the Descriptor Coverage: An internal error occurred. It is recommended to restart UiPath Studio.
- The Auto-generated test data
feature failed to create a default value for
Booleanvariables. - Workflows were missing activity highlighting when using Activity Coverage.
.NET Framework 4.6.1 is currently the minimum required version for running Windows - Legacy projects. Starting with Studio 2023.10, the minimum requirement will change to .NET Framework 4.7.2. Check the Deprecation Timeline for the latest updates regarding upcoming deprecations.
UiPathStudio.msi installer and can be found in the local feed.
| Activity package | Version |
|---|---|
| UiPath.UIAutomation.Activities | v23.4.6 |
| UiPath.System.Activities | v23.4.3 |
| UiPath.Excel.Activities | v2.20.2 |
| UiPath.Mail.Activities | v1.20.0 |
| UiPath.Word.Activities | v1.16.1 |
| UiPath.ComplexScenarios.Activities | v1.4.0 |
| UiPath.Presentations.Activities | v1.11.1 |
| UiPath.Testing.Activities | v23.4.1 |
| UiPath.WebAPI.Activities | v1.16.2 |
| UiPath.Form.Activities | v23.4.4 |
| UiPath.Callout.Activities | v23.4.4 |
