studio
2025.10
false
UiPath logo, featuring letters U and I in white

Studio User Guide

Last updated Oct 30, 2025

2025.10.1

Release date: October 30, 2025

What's New

Studio UX refresh

Studio has a new visual identity that focuses on improving clarity, consistency, and the design experience. Here's what's new:
  • New color theme.
  • More compact layout for panels.
  • The Command Palette in the Title Bar.
  • The ribbon layout is now compact by default.
  • Cleaner dialog boxes.
  • Larger modal widgets.
  • Redesigned scroll bars.


Primary actions in the Title bar

For a cleaner, more compact look, unpin the ribbon. This brings all primary actions directly in the Title bar, giving you more space for building or editing your workflow.



Improved panel docking

We made several changes to how the panels are docked in the Designer:

  • Updated tab placement - Instead of always appearing at the bottom, panel tabs now align with their orientation: vertical panels show tabs on the sides of the Designer, while horizontal panels show tabs at the top when in view.
  • Cleaner layout - The Universal Search bar no longer appears all the time, but only when needed.
  • Simplified controls - Extra panel options have been moved into a new More actions (⋮) button to reduce clutter.
  • Show / Hide panels - Customize your layout and display or hide specific areas to optimize screen space and focus on what’s relevant.

Enhanced design experience for sequence workflows

We are excited to introduce a fresh design experience for sequence-based workflows built to make your automations faster, clearer, and easier to navigate. Whether you are editing a sequence, debugging, or collaborating with team members, these enhancements bring a smoother, more intuitive workflow experience.

This experience is available by default for cross-platform projects and can be enabled for Windows projects by navigating backstage to Settings > Design and selecting the Compact Design Experience option.

Here’s what’s new in the Designer panel:

Slim activity cards

Activity cards are compact and streamlined, helping you see more of your workflow at once, especially in larger workflows.

All activity properties are now displayed in the Properties panel, without needing to change views. Simply select an activity to access all its properties in a centralized location.

Line numbers

Each row has its own line number, making it easy to navigate, review, and debug workflows.

Toggle, disable, or delete breakpoints directly by clicking to the left of a line number. Debug faster and more efficiently, without opening other context menus or panels.

Expand or collapse logic blocks with just a click, including sequences, loops, or Try/Catch blocks.

Selected activity cards are clearly highlighted and always synced with the Properties panel.

Easy to add activities and cases
Precise visual cues now show you exactly where new activities or cases are added, whether between other activities, between steps, or inside branches.

Annotations
Annotations feature an updated visual style:
  • Pinned annotations are now part of the activity card in cross-platform projects.
  • Unpinned annotations can be resized to fit their content and have rounded corners.

Breadcrumbs

The breadcrumb navigational path in the Designer panel header can quickly become hard to read in large workflows with deep nesting. Breadcrumbs now collapse into a drop-down menu once they exceed the available space. This means you can:

  • Quickly expand the drop-down menu to see the full path.
  • Avoid overflowing or truncated breadcrumbs in complex workflows.

Redesigned Data Manager

The Data Manager has received a visual and functional overhaul, making it easier to create and manage variables and arguments through a tabular experience. For more information, refer to Using the Data Manager.



Solutions in Studio

Solutions created in Studio Web can now be opened, edited, and saved in Studio, giving you more flexibility to develop automations together with their resources as a unified whole.

To see how you can benefit from using solutions in Studio, refer to Solutions.

Introducing Long Running Workflows

Long Running Workflow automations allow you to model and automate processes using Business Process Model and Notation (BPMN) concepts applied to RPA.

Long running workflows bring the structure and clarity of BPMN into Studio, using familiar RPA terminology for activities such as Invoke Workflow, Sequence, or Resume after Delay. This approach combines the visual expressiveness of BPMN with the practicality of RPA, making it easier to design, orchestrate, and manage processes that span both automated and human-in-the-loop steps.

Long running workflows have a new designer canvas and use dedicated activities grouped under the Long Running Workflow category in the Activities panel. Each node in the designer represents an activity that can be configured directly in the canvas, or require a few quick configuration steps. Additionally, each node can be tracked in Process Mining to get a view of the process and further optimize it.

You create long running workflows directly from the Design ribbon tab by selecting New > Long Running Workflow. You can also import a BPMN file from the Import Files context menu option in the Project (Explorer) panel.

For more information on how to configure a long running automation, refer to Long Running Workflows in the Studio guide.

For more details about what dedicated activities you can use in your long running workflows, refer to Flowchart Builder activities in the Workflow Activities guide.



StudioX capabilities in Studio

StudioX capabilities are now integrated in Studio, making it easier to design your automations without switching between Studio profiles.

To enhance Excel-driven automations, you can create new Excel resources in Windows projects by using the plus button in the Data Manager and selecting Connect to a new Excel file. Once configured, this file now appears under the Resources section and can be used in the workflow without needing to add a Use Excel File scope.



Additionally, StudioX project templates are now available in the Templates tab, including a blank Task template which can also be accessed from the Start tab. The Project Notebook is available in the Task template and can be used as in StudioX.

StudioX becomes Studio for Citizen Developers. While the name may be slightly different, it’s the same platform that helps Citizen Developers automate their applications.

You can continue working on your existing projects or create new ones just like before, as the experience remains unchanged.



Introducing the Data Mapping editor

We are happy to introduce the Data Mapping editor, a powerful business process automation tool that facilitates mapping complex data objects between systems within a single Integration Service activity. To learn more, refer to Designing Automations.

Project templates governance

You can now control which project templates appear in Studio using governance policies. To learn more, refer to Governance.

Introducing Unified Pricing

We are excited to announce Unified Pricing, our innovative licensing paradigm that brings new licensing plans, user licenses, and a consolidated consumption unit. We are also excited to let you know Studio is now available through Unified Pricing.

For extensive release notes, refer to the Automation Cloud release notes guide.

For detailed Studio licensing information, refer to the Studio user guide.

For overview licensing information, refer to the Automation Cloud admin guide and the Overview guide.

Coded automations features

XML documentation file for your custom code and libraries

You can now access XML documentation files after you publish a project and enjoy the benefit of code documentation for your custom code and libraries. After the project is published, the XML files are generated alongside the DLL and PDB files in your project folder. You can also find them in the lib folder of the generated NUPKG file. Visit Working with Coded automations to learn more about publishing projects that contain coded automations.

Test Automation features

Editing file data during design time

With this latest release, you can directly edit test data from a File type that's displayed in a DataTable format, during design time. This allows you to easily modify cell values, add, or remove rows, saving time and increasing efficiency. You can only edit file data that has primitive data types. Visit Test Data File to check the updates.

Improvements

Performance improvements

Working with large projects? Studio is now faster and more responsive where it matters most:
  • Workflow Designer - Navigate up to 10x faster. Large workflows now scroll and render much faster.
  • Manage Packages - Search is now drastically faster. Results appear in seconds instead of minutes with multiple feeds configured and searching for broad terms.
  • Compile expressions to single assembly: Compile time is reduced by ~30% thanks to backend improvements that you feel in faster execution.
  • Faster Locals panel - Instantly view JIT-compiled objects that took up to 10 seconds to expand.

Tenant switching in Studio

You can now switch tenants directly from Studio, making it easy to manage multiple environments or clients. Simply select your initials from the Title Bar and choose the tenant from the drop-down list.

Search in Orchestrator folders

You can now search for Orchestrator folders when viewing the list of available folders in the status bar. The same functionality is available for Git branches.

Bring changes when switching Git branches

You now have more flexibility to keep or discard uncommitted changes when switching Git branches. Each time you make a change to a project or Studio marks the project as changed, you have the option to bring the changes to the new branch or discard them.

Word wrap in the Expression Editor

The word wrap functionality in the Expression Editor ensures that long expressions automatically wrap to the next line instead of extending beyond the visible area. This makes it easier to view and edit complex expressions without horizontal scrolling.

The functionality is enabled by default, but you can disable it from the word wrap button.

Integration Service connectors in Manage Packages

You can now browse, add, and remove Integration Service connectors directly from the Manage Packages window, making it easier to discover and access third-party applications. To learn more, refer to Managing Connectors.



Automatically imported namespaces

Studio now automatically imports the namespace of any type generated at runtime by an activity (for example, Run Job with agent input or output arguments). This lets you use the type immediately in expressions without manually managing imports.

New tools to keep your Git projects clean

Studio now gives you the option to automatically generate a .gitignore file when adding a project to Git. This file excludes local cache folders, preventing accidental commits of environment-specific or machine-specific data. The built-in .gitignore file enforces best practice by default, which is particularly useful when using external Git tools that do not filter these folders automatically. To learn more, refer to Adding a Project to GIT.
We are also introducing a new Project Cache option under the Remove Unused ribbon button that deletes a project’s cache folders and forces a clear recompilation of all activities and dependencies. This option aims to fix unexpected behaviors that sometimes occur after cloning a project, switching machines, or changing Studio versions, such as missing activities, validation failures, or runtime errors including TargetInvocationException.


Improved Find References panel

The Find References panel is more usable in larger projects. You can now resize columns to better view long paths or display names. Additionally, the panel fully supports coded workflows, making it easier to navigate and understand dependencies across different automation types.

Improved Output panel

The Output panel has a new design and added functionality. For more information, refer to The User Interface.

.NET Framework requirement update

The minimum .NET Framework requirement has been updated from 4.6.1 to 4.7.2.

Improved Project Dependencies Mass Update Tool

You now have control over how the version of a project increments when using the Project Dependencies Mass Update Tool. To learn more, refer to Project Dependencies Mass Update and Mass Update Command Line Parameters.

Enhanced error logs

Error logs provide details about the activity that caused your workflow to fail, including the workflow file name, activity name, and container hierarchy. These details help you quickly locate the activity within your project, and are displayed in Studio, Orchestrator, and Robot logs. For more information, refer to Studio Logs.

Create variables and arguments from JSON schemas

To enhance working with structured data, you can create variable and argument types from JSON schemas. To learn more, refer to Managing Variables.

Improved annotations

You can now reposition annotations in the designer canvas while editing them in flowcharts and long running workflows. Additionally, annotations dynamically resize as you type for improved readability.

Specialized user required for Test Automation projects

We now exclusively allow App Test Developer users to create, publish, and execute Test Automation type projects. For more information on App Test Developer users, visit Test Cloud licensing.

New Studio Legacy instance for Windows - Legacy projects

Windows - Legacy projects now automatically open in a new, dedicated Studio Legacy instance. This ensures long term maintenance support for Windows - Legacy projects. New features, such as solutions, Autopilot™ capabilities, long running workflows, or the enhanced design experience are available only for Windows and cross-platform projects. For more information, refer to About the Windows - Legacy compatibility.

Other improvements

  • The Studio tutorial window no longer shows up once closed.
  • In projects without global variables or global constants, GlobalVariablesNamespace and GlobalConstantsNamespace are no longer removed when removing unused imports.
  • AutopilotTM can now use Object Repository elements from an imported library when generating low-code and coded test cases.
  • Sequences and scope activities have an improved design that minimizes indentation and borders in the activity card.
  • You can now enable autosaving project files from the new Autosave Design setting. You can also set the interval that project files are automatically saved from the Save interval setting.
  • You can view dates and times as either local or relative to UTC in activity fields that use the Date and time selector.
  • You can now include your email address in the Send Feedback window, allowing our product team to reach out for more details about your feedback.
  • You can set the default zoom level for your project files from the Default Zoom Design backstage setting.
  • You can interact with more activity properties in the Locals panel.
  • The Supports Persistence project setting is automatically enabled when an activity that requires persistence is added to a project. Supports Persistence remains enabled even if the activity is removed from the project.
  • The functionality to export workflows to Excel is now available under Export As > Excel File in the Design ribbon tab.
  • We have increased the size of windows that open in Studio, making them easier to work with.
  • You can now view your licensing plan when selecting the icon with your initials in the Title Bar.
  • The variable selection window now prioritizes variables and properties that match the required data type.
  • The Pan Mode, Reset zoom, Zoom drop-down, Fit to screen, and Overview navigation buttons are now grouped under a floating window in the Designer panel.
  • You can now control what activities are hidden in the Activities panel through a governance policy.
  • The Error List panel has been renamed to Errors.
  • You can now navigate to the product licensing documentation directly from the Studio Backstage View, giving you quick access to information about you current license and what is included in other plans.
  • The License Acceptance window no longer appears when installing an activity package. (NOT DONE)
  • Your licensing plan is now visible when selecting the Copy Info button in the Help backstage tab.
  • The Use Variable window now features improved icons, tooltips, and UI elements.
  • Studio now shows a loading animation when opening project files.
  • Activities that use file and folder resources now feature a search functionality, allowing you to quickly find what you need within the current folder and all its child folders.
  • The IResource data type is now available directly in the drop-down menu as one of the primary data types when configuring arguments.
  • We have improved how error and warning messages appear in activities.
  • Panels in the bottom area of the Designer feature text as well as icons when collapsed.
  • Stack traces are no longer visible in the Output panel for known exceptions.
  • The icon used to reset the zoom level back to the default value has received a visual update.
  • To create a new RPA test case, you can now go to the Design tab, open the File group, and select New from the dropdown list.
  • The Breakpoints and Bookmarks panel is now named the Markers panel.
  • The active scope location is now highlighted when changing a variable's scope in the Data Manager panel.
  • We improved the design of the Try/Catch activity, making it easier to configure and manage exceptions.
  • The required properties for the Assign activity are now visible directly in the activity card.
  • To create a new RPA test case, you can now go to the Design tab, open the File group, and select New from the dropdown list.
  • AutopilotTM can now use Object Repository elements from an imported library when generating low-code and coded test cases.
  • You can now record your interactions with UI elements and translate them into coded automations.
  • The actions for adding and removing rows, when you generate test data using Autopilot, are now more visible. Visit AI-generated test data to check the visual updates.
  • A Preprocessing document message appears in the bottom-left corner of the status bar when debugging large workflows for the first time.
  • The source control plugin for GIT can now communicate with the ssh.exe executable.
  • You can now select multiple options when retrieving list items in activity fields.

Bug Fixes

  • After switching to the StudioX profile, you could not create a new project from a template if the user interface language was set to Korean.
  • An argument converted from a variable with no default value set in Studio appeared to have a default value when configuring the process in UiPath Assistant and Orchestrator.
  • Publishing some projects with missing dependencies in a GitHub CI/CD pipeline did not return validation errors.
  • You could not publish libraries to the library tenant feed when enforcing an Automation Ops governance policy that removed the tenant processes feed.
  • Compiling some projects containing test cases took longer than expected.
  • Using special character quotes " (0x201C) in strings caused a JIT compilation error at runtime in Windows projects.
  • The Export as Image context menu option did not work as expected in flowchart workflows.
  • Renaming arguments in a library added as a dependency and republishing the library prevented the custom activity from being displayed as expected after updating the library version.
  • The connections between flowchart activities were not visible in some projects.
  • The Project Type drop-down menu in the New Template window was not keyboard accessible and was not announced by screen readers when focused.
  • Creating or opening a project on a machine that was not connected to the internet was slower than expected.
  • A Document size exceeds database limit error occurred when debugging some projects that contained a large number of test cases. To reduce the project's database size and minimize the risk of encountering the error, activity properties such as TargetImageBase64,ImageBase64, and IconBase64 are no longer stored in the project's database. This fix brings the following improvements:
    1. Improved execution stability - Debugging a project affected by this issue could previously lead to execution freezes.
    2. Enhanced publishing process – Projects affected by this issue might have failed to publish with the following error: The project has Workflow Analyzer errors and cannot be published. Check global publishing settings allowed by your team.
    3. Refined Workflow Analyzer results - Analyzing an affected project could trigger errors such as: ERROR: Workflow Analyzer error - The parsed workflow document size exceeds database limit. Please break the workflow into smaller parts.
  • Publishing a project that contained a library deployed to Orchestrator via an Azure DevOps Extension CI/CD pipeline sometimes failed.
  • You could not edit or delete the Finally block in a Try Catch activity in some projects created in a previous version of Studio.
  • Studio became unresponsive when creating a global variable from the Data Manager.
  • The tooltips created in a Windows - Legacy library that was migrated to the Windows compatibility were not visible when the library was used in a Windows project.
  • An 'Action" is ambiguous, imported from the namespaces or types error occurred in some projects when assigning values to a variable.
  • An unexpected Office365Message !<NotSupportedException> error message appeared in the Local Value window when debugging some Windows projects that contained activities from the Microsoft 365 activity package.
  • Certain context menu options were unavailable when right-clicking an activity inside the Then section of an If activity in some Windows projects.
  • Using the F9 keyboard shortcut to remove a breakpoint did not work as expected.
  • A BC30451: 'Newtonsoft' is not declared. It may be inaccessible due to its protection level. Variable 'Newtonsoft' is missing. Please use Data Manager to recreate it. validation error occurred when using the Assign activity in some projects.
  • You could not browse the list of connection assets in a Microsoft 365 Scope activity if an Orchestrator folder contained more than 1000 assets.
  • Setting the HideGettingStartedScreen governance parameter to true did not disable the Studio welcome screen.
  • A LibGit2Sharp.LibGit2SharpException: remote authentication required but no callback set error occurred when cloning some remote Git repositories from an on-premises Azure DevOps Server.
  • Using the Delete key while editing a variable’s annotation in the Data Manager deleted the variable.
  • A CS0234: The type or namespace name 'Ui' does not exist in the namespace error occurred when publishing some projects.
  • A CS0204: Only 65534 locals, including those generated by the compiler, are allowed error occurred when publishing some projects containing sequences with a large number of activities.
  • Studio became unresponsive in some projects when switching focus to another application and then back to Studio.
  • Text edited in activities was not saved when switching focus to other panels in some projects.
  • Global variables did not work as expected in some projects created from the Robotic Enterprise Framework project template.
  • The Rich Text Composer used in the Body as HTML activity option did not work as expected in some projects.
  • An unexpected error occurred when creating a variable in some StudioX projects.
  • You could double-click to edit Object Repository elements from imported UI libraries.
  • A System.NotSupportedException: Specified method is not supported error occurred when solving Git conflicts caused by Object Repository elements in some projects.
  • The Invoke Workflow File activity caused a System.IO.FileNotFoundException: Could not load file or assembly error in some projects.
  • Some workflow files were marked as modified when expanding an If activity.
  • The Find References option for Object Repository elements incorrectly listed unrelated files in projects with multiple UI Automation activities.
  • Two variables were incorrectly created in the Data Manager instead of one when using an Assign activity inside two nested For Each UI Element activities.
  • The default Notes variable was incorrectly removed when using Remove Unused > Variables in projects created from the Task project template.
  • Object Repository did not work as expected in projects upgraded from Studio versions prior to 2024.10 when the modern design experience was not enabled.
  • Data Service activities did not work as expected in some projects that were created in Studio Web, edited in Studio, and then reopened in Studio Web.
  • The keyboard shortcut to move focus between tabs in Backstage View (CTRL + Tab) was incorrectly announced by some screen readers.
  • An unexpected error occurred in some projects when invoking a workflow containing an Extract Table Data activity and assigning a new CultureInfo("nl-NL") value to CultureInfo.CurrentCulture.
  • The Watch panel did not display the correct scope value for variables that had the same name as a For Each activity’s iterator variable during debugging.
  • Changes to an activity’s display name in the Designer panel were not saved when switching focus to other panels in some projects.
  • Studio crashed while scrolling through projects containing large nested workflows with the following error: UiPath.Studio.Contracts.RecoverableException: Studio closed the active project due to a critical internal error.
  • A validation error occurred when publishing some projects that contained a library with a corrupted .metadata file even if project validation was successful.
  • Studio could not open some projects that contained a library with unresolved types.
  • While debugging a XAML workflow within a project that contained CS files, an 'Unexpected error during library compilation: Value cannot be null. (Parameter 'type')' error occurred, which caused the compilation to fail.
  • A System.ObjectDisposedException: Cannot access a closed pipe error occurred when debugging some workflows containing a large number of objects passed as variables.
  • The Extract as Workflow context menu option did not work as expected in some projects.
  • The Manage Packages button was missing in some projects.
  • Compiling some projects containing test cases took longer than expected.

Removed Features

The ST-DBP-026 - Delay Activity Usage Workflow Analyzer rule is no longer available. Please note that if a project is published with this version of Studio and executed with an older version of Robot, the Delay activity will suspend and never resume.

Activity Package Versions

The following activity packages and versions are included in the UiPathStudio.msi installer and can be found in the local feed.

Activity package

Version

UiPath.UIAutomation.Activities

UiPath.System.Activities

UiPath.Excel.Activities

UiPath.Mail.Activities

UiPath.Word.Activities

UiPath.ComplexScenarios.Activities

UiPath.Presentations.Activities

UiPath.Testing.Activities

UiPath.WebAPI.Activities
UiPath.Form.Activitiesv25.10.0
UiPath.Callout.Activitiesv25.10.0

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.