Release date: 27 January 2021
- When you install using the .msi installer, a screen now prompts you to choose what to install at the beginning of the installation process. The installation is configured based on your choice, and you only need to use the advanced options of the installer if you want to select the Studio or Robot features to install.
You can select one of the following:
- Studio - Installs UiPath Studio, Assistant, and the user-mode Robot for creating and testing automations.
- Assistant - Installs UiPath Assistant and the user-mode Robot for running attended automations.
- Unattended Robot - Installs the service-mode Robot for running scheduled unattended automations (via Orchestrator) and UiPath Assistant for troubleshooting.
- When you first launch Studio after installation, you are now prompted with the recommended licensing method for your installation scenario:
- If you used an installer downloaded from Automation Cloud, you are prompted to activate by signing in to your UiPath account.
- If you used an installer obtained after your organization purchased the on-premises UiPath Platform, you are prompted to activate by connecting to Orchestrator with your machine key.
- If you installed Studio as part of a trial of the on-premises UiPath Platform, you are prompted to activate by adding a license key.
- If you perform a fresh installation and you have an Enterprise license, the Studio profile is now automatically selected based on the license allocation in Orchestrator. If you installed Studio as part of a trial of the on-premises UiPath Platform, you are prompted to select which profile to use during activation (Studio, StudioX, or Studio Pro).
- You can now enforce the governance policy through Orchestrator by creating a uipath.settings.config folder and either adding the contents of the governance file in an asset named uipath.studio.governancepolicy or adding the path to the governance file in an asset named uipath.studio.governancesource. For more information, see Governance.
- The following location settings can now be configured through the governance file: Project path, Publish process URL, Publish library URL, Publish project templates URL.
- The tooltip displayed when you hover a project from the Open Recent list in the Start tab in Studio Backstage View now also displays the path to the project.json file.
- A new option named Search by Description has been added to the View Options menu in the Activities panel. When this option is enabled, searching in the Activities panel returns results from activity descriptions as well as activity names. By default, this option is not enabled and searches return results from activity names only.
- To make it easier to identify screens and elements from the Object Repository, unique IDs are now displayed in the Edit Screen and Edit Element windows. In addition, when you open the windows from the Snippets panel, a version number is displayed as well.
- For greater clarity, the Workflow Analyzer Rules Location setting in Studio Backstage View > Settings > Locations has been renamed Custom Workflow Analyzer rules location. In addition, its corresponding tooltip includes more details about the location.
- The Connect package source has been renamed Marketplace to correspond with the renaming of the collaborative library of RPA components to UiPath Marketplace.
- If you debug a file or a project that contains Pick and Pick Branch activities with both Slow Step and Execution Trail enabled, the execution gets stuck when it reaches the Pick activity. As a workaround, disable one of the options (use either Slow Step or Execution Trail, but not both).
- Because the namespace of several System activities has changed after version 19.4, if you added one of the affected activities to the list of Favorites using version 19.4 or earlier of the System activities package, the activities no longer appear in the Favorites list when you update the package to a version after 19.4. The available workaround is to add the activities to the Favorites list again.
The activities with a changed namespace are: Log Message, Filter Data Table, Message Box, File Change Trigger, Invoke Code, Retry Scope, Do While, and While.
- When you publish a project to a custom URL that becomes unavailable while the Info dialog box at the end of the publishing process is open, if you click the Location link in the dialog box, it can take longer than expected (over 1 minute) for an error to be displayed and inform you that the location cannot be found.
- An error occurs when you use the Test Activity feature for an activity that requires a scope.
- Renaming a Studio Pro test project that includes test cases causes an error when publishing the tests.
- Design time and runtime performance of C# projects is lower when compared to VB.NET. When runtime performance is essential, we recommend using VB.NET instead of C#. We plan to update the speed related to C# with future updates.
- You cannot delete an activity within a mock file if the mock file is derived from an unresolved activity.
- Pressing Enter in multi-line editors that have a single-line height no longer adds a new line, it now submits the expression instead.
- The Expression Editor no longer opens with the cursor positioned at the end of the line; the cursor position is now at the start of the line.
- Fixed an issue that could cause publishing a library to fail when the library contained Invoke Workflow File activities.
- When you publish from the command line with the command
UiPath.Studio.CommandLine.exe publish, the output now displays the process name, publish location, and version.
- Fixed an issue that could cause a namespace used in a deeply nested activity to be incorrectly removed when you selected to Delete All Unused option from the Imports panel context menu.
- If a process contains an activity from a library and the
Environment.CurrentDirectoryfunction is used in that activity, the current directory of the process no longer incorrectly changes to the current directory of the library.
- Activities packages that are available by default for new processes no longer have missing dependencies when Studio is not connected to Orchestrator, all external feeds are disabled, and the local feed is the only enabled package source.
Updated about a month ago