Studio InstallerStudio now comes with a lighter setup, bundling only System Activities. All additional packages can be downloaded from the official feed if needed.
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.
StudioX capabilities into StudioYou 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.
Deprecating Windows-LegacyOver 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)
AutosaveStudio 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!
Long Running Workflow PreviewIntroducing 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
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.
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 WebAssistant Web is now available in public preview! Have you had a chance to try it out? Check the details here:
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.
You can now launch multiple apps simultaneously, removing the previous limitation.
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.
We’ve added cross-origin iframes support for our CefSharp WPF implementation. This is now available for CefSharp versions v122.1.120 and newer.
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.
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.
SecureString for TypeInto in UiAutomation APIPreviously, 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)
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.
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.
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.
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.
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.
Which features excite you the most and you are going to try right away? We want to hear what you think! Please use the 
button below 
Hello all,
I am having a issue with the substring method. I do not know the length of the row, so I do:
Length = item.Length.
After that, I want to get a word of the line that I know that begins in 20.
So, how can i get the word? Word = item.Substring(20, Length)
I did that and it is not working.
Thanks
@Angel_Llull
May we ask you to share the string sample, the expected substring with us. Thanks
In case of issues also tell us what you have done so far and what are details on the fail (wrong output, exceptions…)
Hi @ppr
For example in this line: “2201822368201118201118061432000000000912620000000000ABON.REME. COMERC” I want to get “ABON.REME. COMERC”, and until the last 0, there are the same characters for all lines of the document.The problem is that the characters of the text ("ABON.REME. COMERC) can vary.
I am not sure, how can I get the text. Do you have any idea?
Many thanks
@Angel_Llull
give a try on:
if digit part is fixed:
Closed on Nov 26, 2020
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
ashokkarale
sonaliaggarwal47
anjasing
mkankatala
Anil_G
manasrlenka25
A_Learner
SorenB
balaraman.ramiya
sharazkm32