Frequently Asked Questions

StudioX aims to enable users without coding experience to automate their own repetitive tasks. If you can break a task into the logical steps required to perform it, and have basic technical "know how" such as the ability to proficiently work with Microsoft Excel (for example, you are familiar with formulas such as VLOOKUP, you know how to create pivot tables or how to run macros) StudioX may be the right automation tool for you.

You can use StudioX to automate:

You can automate manual processes across multiple applications. For example, you can design an automation that saves specific Excel files you receive as attachments to Outlook emails, and then fills out web forms with data from those files.

StudioX is a profile in UiPath^® Studio. To use StudioX, install Studio, activate, and select the StudioX profile.

StudioX has the same hardware and software requirements as UiPath Studio.

A Robot is installed together with StudioX to enable you to execute the projects created in StudioX. The Robot cannot be installed on a separate machine.

Yes, UiPath licenses include all of the capabilities from lower licenses/SKUs. This means that a Citizen Developer license includes a production Attended license that enables you to run production automations from UiPath Assistant.

Any license that enables access to the Studio profile also gives you access to the StudioX profile.

The StudioX Citizen Developer license only provides access to the StudioX profile.

Any StudioX project can be opened and edited from the Studio profile. This enables RPA developers to troubleshoot and fix potential issues or add capabilities that a Citizen Developer cannot easily add from the StudioX profile. When editing a project created in StudioX from the Studio profile, it is important to ensure the changes you make do not affect the project's compatibility with StudioX, so that it can still be opened and edited from the StudioX profile. Keep in mind that:

Any activities package can be added as a project dependency in StudioX from the Manage Packages window. For more information about adding package sources and installing packages, see Managing Activities Packages in the Studio Guide.

However, activities intended for StudioX follow different design guidelines, so it may be difficult or impossible to use some Studio activities in StudioX:

All the activities that are available in StudioX can be used in Studio.

You can publish StudioX projects to Orchestrator using the same publishing process as for Studio projects. For more information, see About Publishing Automation Projects in the Studio Guide.

StudioX projects are designed for attended use only and we do not recommend using StudioX when developing projects intended for unattended use. You can update a StudioX project for unattended use in the Studio profile by removing the GEH. We recommend having an RPA developer review the project before publishing it for unattended use as they might want to add extra logging and error handling and to check for hard-coded values that should be stored as assets.

StudioX is compatible with Orchestrator 2019.10 and higher. Compatibility with Orchestrator 2019.10 is limited to licensing and logging.

You can create custom activities for StudioX in the same way as you do for Studio, but make sure to take into account that StudioX activities follow different design guidelines.

Any library published from Studio can be added as a project dependency in StudioX. RPA developers can create libraries following the instructions on the About Libraries page in the Studio Guide.

After a library is created and published from Studio, StudioX users can add the location where the library was published as a package source, and then install the library in projects from the Manage Packages window. For more information about adding package sources and installing packages, see Managing Activities Packages in the Studio Guide.

When creating libraries for StudioX, take into account that StudioX activities follow different design guidelines.

You can create custom Workflow Analyzer rules for StudioX in the same way as you do for Studio. To make a rule available in the StudioX profile, an additional property must be defined. For more information, see Building Custom Rules in the Studio Guide.

Organizations can control access to activities package feeds, Workflow Analyzer rules and settings, and enable or disable features in the product.

You can enforce governance policies in one of the following ways:

For additional control, organizations can create custom Workflow Analyzer rules that enforce specific settings, policies, or behaviors. For more information, see Building Custom Rules in the Studio Guide.

Execution logs contain information about the applications, URLs, Excel and Word files that are used in automations, as well as information about emails sent using Outlook activities. For more information, see Audit Logging.

When a project is published, information regarding the applications and URLs that are used in the automation is included in the package and is displayed in the package release notes and process details in Orchestrator.