UiPath 26.0.197 July Community Release

News Release Notes
1

UiPath 26.0.197 July Community Release

:waving_hand: Hey Community!

Here’s what’s new in this release.

Studio

Solutions: debug across projects, publish as a whole

Solutions now have more improvements to make them first-class functionality in Studio: debug across projects with cross-project calls resolved automatically, and publish the solution with the new Publish Solution wizard.

Debugging resolves cross-project calls automatically

Debug a file that calls into another project via Run Job and the call just resolves - no manual Save Solution to Cloud step, no setup before hitting Debug. Studio deploys the sibling projects to a debug folder in your Personal Workspace, where they run as Orchestrator jobs when invoked. That preparation runs only when it’s needed: if Studio can tell your file never reaches a Run Job call, it’s skipped and debugging starts right away. Breakpoints and stepping stay in the project you’re debugging - invoked projects run remotely.

Publish Solution wizard

Publishing a solution now has a dedicated home in the ribbon: the Publish Solution split button. It opens a wizard that packages all projects in the solution - set the package name, version, description, and release notes, then choose where it goes:

  • Orchestrator Tenant Feed - the package lands in your tenant feed; deploying and activating it stays a separate step.
  • Orchestrator Personal Workspace Feed - publishes, then automatically deploys and activates, so it’s ready to run right away.
  • Custom - packs it to a local folder, nothing is uploaded.

Need to publish just one project? The split button’s menu also offers Publish Active Project and Publish Active Test Cases - these skip the wizard and publish only the project you’re working in, and the same actions remain in the project’s context menu.

Outside solutions, the Publish button works exactly as it always has.

Try it

Open a multi-project solution and debug a file that calls into another project via Run Job - the cross-project binding gets provisioned automatically. Then hit Publish, pick a target, set a version, and publish everything in one step.

Invoke Code’s new editor

Invoke Code’s plain text preview has been replaced with an inline, ActiPro-powered editor:

  • Syntax highlighting and line numbers appear directly on the activity card - no more popup needed for quick edits.

  • Expand to a full code editor if you need to to see more code

  • Get IntelliSense, multi-cursor editing, and find/replace right inside the activity card.

  • Available starting with the System activities package v26.6.1 - update the package to get the new editor.

Try it: update the System package to 26.6.1 or later, drop an Invoke Code activity onto the canvas, and start typing directly into the card.

Multi-select context menu catches up

Right-clicking multiple selected activities now surfaces the same actions you’d get from a single activity - Disable, Surround with Try Catch, and more - instead of a stripped-down menu. Every applicable action now runs against your entire selection, not just the first activity.

More file types get syntax highlighting

Studio’s file editor used to highlight only C#, VB, XML, and JSON. It now shares the same syntax engine as Invoke Code’s editor, so more languages get proper treatment.

  • .py, .sql, .ps1, .java, and .js files now render with full syntax highlighting instead of plain text.

Empty states for Properties and Outline

The Properties and Outline panels no longer sit blank when nothing is open. Both now show a clear icon-and-message empty state until you open a file and select an activity.

image-20260706-105147
image-20260706-1051473455×2062 366 KB

Previous release notes

Please tell us what you think

What excites you the most? What is your experience? We want to hear what you think! Please use the A red button labeled "Reply" with a blue left-facing arrow icon. button below :slight_smile:

2

I am a fan of the Solutions and glad to see them coming to the Desktop IDE.
Packaging assets is a great relieve.

I have to fully explore the “solution deployments create Orchestrator sub-folders” and what it means for coding agents and libraries: Inheriting optionally a modern-folder nuget feed it seems that “lowest applicable version” can be pushed further into the missing “range” territory.

3

Trying to download this release from https://download.uipath.com/UiPathStudioCloud.msi (enterprise installation), but it seems the last version hosted there was 26.0.194. Is there a new location to download from? I cannot download the community version on my work laptop.

4

Can we check if the invoke activity broke for non-compact studio users. I am no longer able to expand the box on the newest version.

5

This also applies in the compact mode, by the way. The Invoke Code window is no longer sideways-scrollable and does not have syntax highlighting as reported.

6

This is for STS release, right, not for LTS?

For LTS the version series is 2025.x, so does that mean all the 2026.x features from STS are due for LTS?

7

Cross-posting the official reply:

Studio 26.0.197 and the latest System activity package 26.6.2 do two things together:

  • as explained above in the post, it allowed the Invoke Code activity to benefit from a new, better code editor experience
  • side effect: the older Studio versions with the latest System activity package will now default to a worse experience
8

You gotta start including that information in the release notes and documentation.

9

That second bullet point was never mentioned in this forum post, the release notes, nor as a requirement when upgrading the package in Studio. It was only mentioned that if you want the new editor, upgrade to 26.6.1. If you can, please pass on this restriction to the documentation team so they can document it publicly.