UiPath StudioX

The UiPath StudioX Guide

About Automation Projects

An automation project is a sequence of activities that a Robot can execute to automate a series of tasks you perform on your computer. You create and view the automation project in the Designer tab of StudioX.

When you create a project in StudioX, the project files are saved in a folder with the project name to a location of your choice. By default, projects are saved in the %USERPROFILE%\Documents\UiPath directory.

The project folder includes:

  • a Main.xaml file that contains your main workflow.
  • a project.json file that contains information about your automation project.
  • an Excel file, by default Project_Notebook.xlsx, if you did not configure your project to use a different Project Notebook.
  • a .screenshots folder, with informative screenshots, if your project contains UI automation activities.
  • a GlobalHandlerX.xaml file that contains a workflow designed to determine the project’s behavior when an execution error is encountered.
  • a RuntimeExecutionError_Template.html file that contains a template for the error message to display when an execution error is encountered.

Publishing Automation Projects

Publishing an automation project means archiving the workflow and all the other files in the project folder so that it can be sent to Robots and then executed.

If the Robot is connected to Orchestrator, you can publish StudioX projects to Orchestrator and run them from UiPath Assistant. If the Robot is not connected to Orchestrator, you can publish your projects to the Robot Defaults and run them from UiPath Assistant.

The publishing process for StudioX is the same as the one for Studio. For more information, see About Publishing Automation Projects in the Studio guide.

Adjusting Project Settings

To configure the settings of each project, select Project > Project Settings in the StudioX ribbon.

Field Description for the Settings Window




Change the name of the project. Such names may contain whitespace characters. When naming projects, keep in mind that whitespace characters are removed at publish time. This field accepts up to 128 characters.


Change the project description. This field accepts up to 500 characters.

Package Icon

Optionally, define a custom icon for the project. You can browse to and select a file, or enter a path or public URL to an ico, jpeg, jpg, or png file up to 1MB in size.

After the project is published, the icon is displayed as follows:
For task automations, in the Assistant next to the process name, making it easier to identify it in the list of processes.
For templates, next to the template in Home (Studio Backstage View) > Templates.
:information-source: The icon is not visible in Manage Packages if a local file is used for a library published to Orchestrator or a feed that does not support embedded icons, In this case, specify the icon using a URL.

PiP Ready

Set to Yes to indicate that the project was tested using Picture in Picture. If set to No, the user will be warned every time they start from the Assistant that this project may not work correctly when run inside Picture in Picture.

Starts in PiP

Set to Yes to indicate that the process should be run by default using the Picture in Picture feature.

Updated about a month ago

About Automation Projects

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.