Hey Community!
Here’s what’s new this month.
Studio
Start a solution from the start page
Creating a solution used to mean starting a process first: the only entry point was a Create new solution checkbox inside the New Blank Process dialog, which is why users concluded a solution couldn’t be created from scratch at all. The start page now has a Solution tile next to Process and Library. Give it a name and a location and you get an empty solution, then add projects to it afterwards.
Resolve merge conflicts in text files without leaving Studio
A conflict in a text file — a .cs coded workflow, a .json config, a .txt — used to leave you with the raw conflict markers and a text editor. Text files now open in a real three-way merge instead: Local and Remote side by side, labeled with the branches they came from, and an editable Result pane underneath. This covers text files only; a conflicted .xaml workflow still goes to the visual workflow diff, which is the right tool for it.
Select a conflicting section, tick the version you want to keep, and the result pane updates; you can also type directly into it when neither side is quite right. A counter tells you how many conflicts are still open, and Next Conflict / Next Unsolved Conflict walk you through them so nothing gets missed before you save. Conflicts arriving from a pull, a merge, and a rebase all land in the same place, and project.json gets its own merge handling rather than being treated as anonymous text.
A What’s New page for coding agents
Opening a project now shows a What’s new page once, explaining how coding agents fit across the automation lifecycle — designing, building, reviewing, shipping and troubleshooting real UiPath projects — and what each agent still needs to get there. It presents Autopilot as UiPath’s own agent alongside whatever agent you already use, and links straight to the Tools page where the UiPath skills and the UiPath CLI are set up.
It shows once per revision of the content, so it won’t reappear every time you open a project, and you can get back to it from Help or from an empty designer. If Autopilot is turned off by governance, the page drops its Autopilot content rather than advertising something you can’t use.
Find an argument in Invoke Workflow
The arguments dictionary that Invoke Workflow File opens now has a search box, which matters once a workflow has more arguments than fit on screen. The selected entry stays in view after you search, so you land on the row you were looking for instead of hunting for it again.
if you love merge conflicts.