Maio de 2026

May 18, 2026

Build number: 2026.0.193

Novidades

Solutions in Studio Desktop

You can now create a new project from a template directly from a Solution. Right-click the Solution in the Explorer panel and select Create Automation from Template. Then, select a template and configure it further. The new project is created as part of the solution folder. This makes it easier to get started with a template without requiring you to create it outside of the solution.

The same template selection experience is available backstage, with each template card exposing a version dropdown and additional information — full description, creator, and last updated date — available on hover.

Non-RPA projects in the Solution Explorer are no longer rendered in a disabled state. Opening a file from a non-RPA project shows a contextual banner explaining the limited editing experience and providing a direct link to edit the project in Studio Web.

The Solution Explorer project icons in Studio Desktop have been updated to match the icons used in Studio Web for Agentic Process, Apps, Agent, API Workflow, and other project types. The JSON file icon has also been refreshed.

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.

When a Catch block in a Try/Catch is selected, the Properties panel now also exposes the exception type as an editable property. Changing it from the Properties panel updates the activity on the canvas, and the reverse.

Correções de bugs

• Minimizing an email activity surfaced a "You must provide a value for Connection" validation error that disappeared when the activity was expanded again.
• Clicking Refresh on the Input arguments field of a Run Job activity regenerated only the input custom-types assembly and left the output assembly stale. As a result, run or debug failed to load the workflow with errors like Unable to create activity builder for Main.xaml or BC30560 'X' is ambiguous in the namespace.
• Studio could not apply the Automation Ops governance policy when the Automation Cloud organization display name contained non-ASCII characters, failing with Request headers must contain only ASCII characters during policy retrieval.
• Create variables and arguments from JSON schemas could not be used when Studio was running in a non-English language.
• Renaming an argument or variable referenced by an Object Repository activity left the activity pointing at the old name, causing an exception at runtime. Studio now warns before you rename arguments or variables that are used in Object Repository activities.

4 de maio de 2026

Número da compilação: 2026.0.192

Novidades

Criação de soluções no Studio

Agora você pode criar soluções diretamente no Studio.Independentemente de você começar com um novo Processo ou com um Modelo, você agora tem uma opção para criá-lo como parte de uma Solução ao habilitar Criar nova solução.

Como parte desse trabalho, Adicionar arquivo, Adicionar pasta e Abrir local do arquivo agora estão disponíveis em todos os tipos de projetos no Explorer, não apenas no projeto de RPA aberto no momento.

Melhorias

Marque atividades como particulares diretamente do cartão de atividade

Clique com o botão direito nas atividades para usar Marcar como particular ou Marcar como público para controlar se os valores da atividade aparecem nos logs de execução.

Correções de bugs

• Ao clicar duas vezes em um erro de validação para uma atividade Flow Decision em um fluxograma, o foco era direcionado ao fluxograma em si em vez da atividade Flow Decision, o que dificultava a identificação de qual atividade estava sem sua condição quando várias atividades Flow Decision estavam presentes.O mesmo comportamento ocorria para os resultados do Analisador de Fluxo de Trabalho quando as atividades tinham seu nome padrão.