UiPath June Community Release

UiPath June Community Release

Studio

Save to cloud on Windows projects

You can now store Windows projects developed in Studio in the cloud. Originally only available for Cross platform projects, you can now use this functionality allowing you better access to your projects as well as portability.

To get started, when you create a project, enable the Save to Cloud option.

This will create a project stored online that you can further edit in Studio. When you’re done, simply click on Save to cloud to update the project:
image

You can also store existing projects by navigating to Save>Save to cloud.

The project is accessible in the cloud. From there you can open it in Studio Desktop:

Test Suite

Scrollbar for existing test data

So far, if you had added +7 different test data files to your project, there was no way to select them when choosing ‘test data-> existing file’ due to the fact that only 7 items would show up in the drop down.

We have fixed this issue, by adding a scroll bar to the drop down.

Create Test Data with Autopilot

You need to generate a set of data records for your test case? No problem – Autopilot can generate synthetic test data for you.

Here is how to do it:

  1. Define arguments on your test case for each data field you require
    image003

  2. Select ‘Add Test Data’ on your test case, and select the option ‘Generate with Autopilot’

    Autopilot will now generate a set of data records based on your arguments. Based on the type and name, it will try to create the appropriate data.

  3. In case you are not satisfied with the result and would like to change it, you can use the prompt field under the generated data table.

Coded Automations

Invoking coded automations using libraries

So far, if you had built Coded Workflows in a library project and imported this project into another one, it was not possible to invoke those coded workflows directly, instead you had to expose them via low-code workflows that in tern could be used as activities.

Now now publish coded automations to libraries and invoke them in different projects, within both low-code (XAML) and other coded automations (CS).

Conditional Breakpoints

Like for low-code workflows, you can now set conditions for your breakpoints within coded workflows.

Invoke Coded Workflow File

So far it was possible to invoke a coded workflow file via the ‘InvokeWorkflowFile’ activity, but you had to change the file chooser to ‘AllFiles’ in order for class files to show up.

We have revamped the activity and now show you all potential workflow files in a list – coded and low code.

image012

Auto-discover arguments

So far, arguments from coded workflows did not show up in the Arguments list when using the ‘InvokeWorkflowFile’ activity.

We have changed the behaviour – now you will see all the arguments available.

System activities improvements

Invoke Workflow File activity unified look

The look and the behaviour of the Invoke Workflow File activity has been unified across the Windows and Cross-Platform Projects (both in Studio Desktop and in Studio Web).

We have also modified some of its behaviours:

  • the Arguments property will now be automatically prefilled with any existing arguments in the target workflow upon the selection if the Workflow File Name
  • the colored number next to the Import Argument button (image) has been replaced with several more useful info boxes; to give one example - if the target workflow contains more arguments than there are configured under the Arguments property of the Invoke Workflow File, you receive the following message:
    image
    The most common scenario when you will see this message is when you switch between the workflows. We opted to not auto-reset the previous input, but you can quickly reset your arguments by using the Import Arguments button:
  • you can switch between static names for your arguments vs an expression via the toggle; note that you cannot use the Import Arguments button when using an expression:

For Each activity slight redesign

The initial view of the For Each activity is simplified with the Item name property being moved to the advanced settings:
image
image

To make this transition seamless, the activity name will automatically adjust to the item name:

Compress/Zip files activity new property and file handling adjustments

New property - Allow contents with duplicate names

You can now choose to zip the files with the same name via the new property:
image
It defaults to False.

Dynamic resource files will now be zipped with their original name

For files provided as a dynamic resource (which come from activities such as the Download File activity from the O365 package), the Compress/Zip files activity will now use the original file name rather than the randomly generated one when adding the file to the archive. If the new duplicate files option is set to False, any conflicting names will receive a suffix to make the file name unique.

Extract/Unzip Files activity new property

To accommodate more scenarios (and to keep up with the Compress/Zip files activity improvements above), a new property was added: If file already exists.
It allows you to choose the desired behaviour in case the target zip file contains files with identical names:
image

New Item Added to Queue event trigger output property for the specific content

Following the improvement to the Get Transaction Item activity, the New Item Added to Queue event trigger follows and will now allow you to easily drill into the Specific Data of your queue based on its Orchestrator schema definition:
image

UI Automation

Ask user on runtime error for new UI Automation activities

Starting with UIAutomation 24.4 preview we provided a new functionality which allows the user to decide what to do next when a selector is not found for Attended execution or debugging in Studio. Within that version, the Indicate element option was available for the most used UI Automation activities:

  • Use Application/Browser
  • Click
  • Type Into
  • Set Text
  • Check/Uncheck
  • Select Item
  • Get Text

This new version brings the Indicate element option for the following UI Automation activities as well:

  • Check Element
  • Highlight
  • Hover
  • Keyboard Shortcuts
  • Take Screenshot
  • Get Attribute
  • Inject Js Script

Note that this functionality can be enabled per project, via a project setting from the UI Automation ModernGeneric section: Ask user on runtime error (the default value is False). Also, if the workflow is run in Debug mode in Studio, the user also has the option to save the changes when the execution ends, so that the next run starts directly with the correct selector.

Set Runtime Browser activity in Cross-platform projects and Coded workflows

With UIA 24.4 we introduced the Set Runtime Browser activity which allows setting the browser used at runtime as the default browser configured on the target machine or a specified browser: Chrome, Edge or Firefox.

Set Runtime Browser can now be used in cross-platform projects, bringing this capability to Studio Web and in Desktop projects for other operating systems.

Set Runtime Browser activity can also be used from coded workflows.

Close Popup activity in Coded workflows

With the previous release we introduced the Close Popup activity on both Windows and Cross-platform experiences.

Now the Close Popup activity can also be used from coded workflows. Having it available for your coded workflows is also very helpful for testing scenarios, but not only.

Set Value activity in Coded workflows

The Set Value activity can now also be used from coded workflows.

Studio Web Browser Extensions Upgrade to MV3

We are planning an important upgrade to our Studio Web browser extensions for early June in response to Google’s transition to Manifest V3.

As part of this transition, Chrome will begin disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta) starting June 2024, beginning with Chrome 127 and later versions. More details on Manifest V2 support timeline page.

Our existing Studio Web extensions for Chrome and Edge have been updated to be fully compatible with Manifest V3, while retaining the same extension IDs for both browsers (Chrome and Edge).

This means that once the extensions are updated in the Web Stores, no further action is required from users to receive the new MV3 extensions. They will be automatically updated when the browser is reopened.

Safari UI Automation Support (Preview)

Until now, automations on macOS could only be created from Studio Web using the Chrome browser. However, Safari is typically the preferred choice for Mac users due to its high optimization for Apple hardware and its availability on both desktop and mobile devices.

With this version we are previewing Safari UI Automation support, which allows users to design UI automations in Studio Web using Safari on macOS and to execute browser automations in Safari through the UiPath Assistant on macOS.

You can get started from Studio Web by adding UI Automation activities. You will be recommended to install the UiPath extension for Safari from App Store and after following our easy setup guide to configure the extension, you will be able to start designing your workflows for browser automation in Safari.

Semantic Activities in Windows Projects (Public Preview)

While still in Public Preview, the new Semantic activities: Extract Form Data, Set Value and Fill Form are now available in Windows Projects as well.

CV auto-anchors for Fuzzy selectors

Whenever our Fuzzy selector algorithm won’t be able to find an auto-anchor, CV will now come to the rescue and propose one coming from the AI model.

Computer Vision available in Studio Web

Computer Vision is now fully available in Studio Web as well as a targeting method in Unified Target, using the UiPath CV Cloud Server.

Radio buttons support in Get Attribute

image

Get Attribute now also supports radio button CV targets, not only checkboxes. A new attribute called “checked” will be outputted as True or False, as detected by the CV AI model.

Accents in UiPath Screen OCR

Accents are now available in UiPath Screen OCR not only via the CV Localserver model, but also via the UiPath Cloud Server via a new Project Setting in the OCR > Screen OCR section called “UseAccents”, set to True by default for new projects and False for existing projects.

Please tell us what you think

Which features excite you the most and you are going to try right away? We want to hear what you think! Please use the image button below :slight_smile:

9 Likes

Again so many updates!
One question, invoking and using connections from the Integration Service into the coded workflow? Is that available with this update?

2 Likes

Great work with the updates but this one kind of missed the mark as its easier to view what the CurrentElement is reffered to as, in order to use it in the for each.

CurrentFile.Name etc

I encountered a bug when opening a project from a previous version in the new version

If anyone can help me or is having the same problem:
Issue with Flow Decision in New UiPath Studio Version: Connections Lost and Object Reference Error

2 Likes

I have the same problem

1 Like

So that you can follow the resolution of the bug directly:

2 Likes

When will all these monthly improvements make their way to the Enterprise version of Studio?

As I understand it, Enterprise is released every year in October going forward.

-Jeppe