UiPath 2024 December Community Release

UiPath 2024 December Community Release

Studio and StudioX

:mortar_board:Studio Installer

Setup Simplification

Studio now comes with a lighter setup, bundling only System Activities. All additional packages can be downloaded from the official feed if needed.

Simplified Sign-in experience

Connecting to Studio is now more straightforward with a single sign-in option. For those needing to connect via client credentials or machine key (for unattended deployment), the Assistant and command-line options remain available.

:footprints: StudioX capabilities into Studio

You can now create a StudioX Task directly from Studio without having to switch profiles. Simply navigate to the Templates and search for the Task which will enable you to create a StudioX workflow. You can take advantage of Project Notebook and other StudioX capabilities. With this change, you can also consume StudioX templates.

Citizen Developers can continue using StudioX as before, without any changes.

:gear: Deprecating Windows-Legacy

Over the last few years, we’ve shifted focus from Windows Legacy projects and invested in Windows and Cross-Platform. We believe we are now at the next stage and starting with this release, creating or editing Windows-Legacy projects is not supported anymore. Opening existing Windows Legacy projects only gives you an option to convert them to Windows projects.
This means that the Studio 2024.10.x release will be the last long term support version that supports legacy projects (please refer to the Product lifecycle page for more information)

:floppy_disk: Autosave

Studio now supports autosave, allowing you to work on your projects without worrying about losing your progress. To enable this feature, simply head over to Backstage Settings. Happy creating!

:loudspeaker: Long Running Workflow Preview

Introducing Long Running Workflow, a new canvas in Studio that uses BPMN concepts to help you model and automate advanced processes. Currently under preview, you can get started with the Long Running Automation template (make sure to Include prerelease) and build workflows that integrate tasks, decision points, data flows, systems integration and human collaboration all while leveraging UI, API & API-powered capabilities.

The Invoice Processing workflow below has been built using the Long Running Workflow canvas and uses concepts like User Tasks, Service Tasks, Gateways, Message Intermediate Catch Events and many more.

Learn more about it here:
Long Running Workflows Community Preview - News / Product News - UiPath Community Forum

System 24.12.0-preview activities

Try Catch, Switch and Timeout Scope

We unified the look of those activities between Studio Web and Studio Desktop.
See below for a comparison between the old and new look:

Note: This new look is only available starting with this Studio version and System 24.12.0-preview activity package.

Start Job

We adjusted the Start Job activity to work the same as Invoke Workflow File and Invoke Process. It now follows the same concept of having the arguments grouped under the single property:

Assistant

:rocket: Assistant Web

Assistant Web is now available in public preview! Have you had a chance to try it out? Check the details here:

UX improvements

Dynamic resize

We’ve replaced the collapse/expand button with a more intuitive resizing feature. You can now expand or collapse the application simply by dragging the edges.

Launch more than one app

You can now launch multiple apps simultaneously, removing the previous limitation.

One place for all the details

Automations from the Marketplace or Automation Store now include all information in a single tab, the Details tab. We’ve removed the More Details tab to create a cleaner, more streamlined layout.

UIAutomation

Chromium-based embedded browsers

Cross-origin iframes support for CefSharp

We’ve added cross-origin iframes support for our CefSharp WPF implementation. This is now available for CefSharp versions v122.1.120 and newer.

Coded automations

Activities In Coded Workflows use Project Defaults for Timeout

UI Automation activities in coded workflows now use the project ‘s default values for activity timeouts instead of having to manually enter a value for each. The timeout value is taken from Project Settings > UI Automation Modern > Timeout.

Option to choose when to close the target app

The behavior in coded workflows was to always kill the target application by default and this couldn’t be changed from the activity itself. We now have a Close option for the target application, that we can use anywhere in the coded workflow, when needed.

Overload with SecureString for TypeInto in UiAutomation API

Previously, in coded workflows the TypeInto activity supported just string as parameter type for the text:

TypeInto(TargetAnchorableModel target, string text)
TypeInto(string target, string text)

We added overloads with SecureString as type for the text parameter, for Studio Coded Workflows:

TypeInto(TargetAnchorableModel target, SecureString text)
TypeInto(string target, SecureString text)

Core UI Automation

Expose WaitForReady property in selection helper

The Wait for Page Load property with its three values (None, Interactive, Complete) was configurable from the Properties panel for UI Automation modern activities. We’ve now made it available in the Options section of the Selection Helper.

The Application Card attaches exclusively by its defined selector

Starting with UIAutomation 24.12 we changed the Use Application/Browser activity attach logic such that it will attach exclusively by its defined selector (at run-time).

For newly created Use Application/Browser activities it is inhibited the previous attach logic that tries to attach by fuzzy title / URL. For example, if there are two browser tabs open with the same URLs and different titles, the title attribute from the Window selector will be used for matching the browser tab.

Auto-verify Execution for Type Into in pure Computer Vision scenarios

This enhancement ensures that execution verification is automatically applied when only Computer Vision (CV) is available, significantly improving the resilience and reliability of automations. For scenarios where selectors are available, Auto-Verify Execution ensures that the input is validated by checking if the expected value has been correctly entered after execution. Now, this same robust mechanism extends to pure CV scenarios, where no selectors are present.

Semantic Icon Descriptions for Objects and Activities

We’re enhancing the Object Recorder with the power of the CV AI Model to generate Semantic Icon Descriptions: the model now outputs semantic descriptions of icons, improving object naming for elements captured through the Object Recorder, including features like Capture All Elements. Additionally, these semantic descriptions are used to rename activities based on pure CV icon targets, ensuring greater clarity and consistency across your automation workflows.

Hebrew and Arabic Support for UiPath Screen OCR

The latest update brings support for Hebrew and Arabic to Screen OCR. This enhancement allows you to seamlessly extract text in these languages, improving automation capabilities for users working with right-to-left scripts.

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 A red button labeled "Reply" with a blue left-facing arrow icon. (Captioned by AI) button below :slight_smile:

12 Likes

@loginerror,

Amazing line-up of the updates. Starting soon to explore :v:

5 Likes

Thank you for your effort. Good job.

2 Likes

Process Diagram! :+1::sparkles::sparkles::sparkles:

1 Like

I don’t get it. How? It’s Studio not StudioX. The entire UI is from Studio. It will be very hard for a lot of StudioX users to find what they need in this UI.

3 Likes

Same problem here, Using StudioX Task generate a Studio project.

It can be seen in the Debug button, which should not appear in Studio X

I also tried to open previously created Studio x projects and it opens them as Studio.

Hi everyone,

Thank you for your feedback regarding StudioX capabilities in Studio. Core StudioX capabilities, including creating a Task, Exception Handling, Excel integration (Project Notebook, Excel resources) are now available in Studio and this should remove the need to switch profiles. For StudioX projects (Tasks, existing projects), the experience should be similar between the two. The difference comes from the additional capabilities available. As you mentioned, the Studio UI is present but this should only add to the existing functionality, not remove it.

StudioX is available under a Citizen Developer license without any changes.

Looking forward to your feedback!

Thanks for sharing the update. During my testing found the below issue -

After we drag and drag an activity, the dependency is taking so long to be added. My assistant is connected, and studio version is 2025.0.157

Steps I performed :

  1. I created a blank project.
  2. Drag and Drop a click activity and it started adding the dependency for Ui Automation.
  3. The installation of dependency is working for more than 7-8 minutes so eventually closed it.

RPA_Blank_Project.zip (79.2 KB)
Sharing the screenshots and project for reference.

Thank you

Here’s a suggestion: Could we have an interface where we can select the packages we want whenever we create a new project?

For instance, I always want the UI Automation and Excel packages to be included by default in all my automations. So, in Studio Settings, I select these two packages as my default packages.

Thanks,
Mukesh

Hi @mukeshkala

You can predefine any templates that you want. Simply start a new project, install the required packages, and then (from the DESIGN tab) select Export As → Template.

2 Likes

NOT a fan of the new Try/Catch. Couldn’t find documentation for it anywhere. I see the variable names for catch blocks has been removed. Am I missing something, or is that entirely counterintuitive? How should a new user know what the name of the catch variable is? Dislike that I can no longer see the topmost sequence name when the TRY block is collapsed.

Could you point me to the learning plan that reflects this updated version?