You can now create a new project from a template directly from the Explorer. This should make it easier to get started with RPA templates without requiring you to create them outside of the solution.
The same experience of selecting a template is available backstage, with each template card exposing the version dropdown more information (full description and metadata) available on hover.
Non-RPA projects in Explorer are no longer listed in a disabled state and editing them also gives you a direct link to edit them in Studio Web.
Edit activities faster in Compact Mode
Property editing in Compact Mode previously required opening the full Properties Panel for every change. Clicking a pill of an activity opens the Properties Panel pre-focused on the matching field , ready for input.
UI Automation cards allow you to indicate the target directly from the cards. When the project uses Object Repository, the activity card shows the activity name (e.g., Click, Get Text) together with a pill displaying the descriptor name, so it’s clear at a glance which element the activity targets.
Try/Catch, Switch, and Else If
In Compact Mode, the branches of Try/Catch, Switch, and Else If now use a merged-container treatment: each branch’s header (condition, case, or exception filter) and body are combined into a single container per branch, reducing the length of the designer.
Seems now the project name is also authoritatively coming from project.uiproj
And possibly more, but that’s where I stumbled across the “blast radius” of the move to the new solution packaging.
Thinking ahead this will also affect the conventional Config file: For example, the Queue folder/name will also find a new home.
Those who haven’t explored the .uis solutions: I encourage to do so! It’s a zip file, open a Studio Web solution with a bunch of “components”† inside. The json files were enlightening to read.
@alexandru.iordan
†What is the official term for the “components” like Process, Agent, … that are part of a .uis solution?
As I am pushing my “coding agent practice” further: Would be nice if there were ways to “.packignore” when packing with sources.
Inevitably the repositories will accumulate not only LLM related files,
but if we don’t migrate to markdown equivalents of PDD and SDD then the whole “coding agent story” will not take off.
Additionally, I find myself adding a few Python scripts here and there. Learned quickly to keep the .venv outside the Studio project. Still, .py files don’t belong in a sources-included nupkg.
Means: A folder with a UiPath Studio project contains much more files unrelated to a execution on a Robot.
According to my tests the project.json can only do “ignore files from publish”
If that was also capable of “ignore folders”: That would fulfill my needs.
Currently I work around by some post-packaging CICD cleanup.
I noticed the folder name and path to Studio changed from “C:\Program Files\UiPath\Studio\UiPath.Studio.exe” to “C:\Program Files\UiPathPlatform\Studio\26.0.193-cloud.23060\UiPath.Studio.exe.” Was this change documented anywhere? Will the folder name and path change with every new release?
Hey Community!
Still, .py files don’t belong in a sources-included nupkg.