Frequently Asked Questions

About StudioX

Is StudioX for me?

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.

What can I automate with StudioX?

You can use StudioX to automate:

• Web and desktop applications - Fill out and submit forms, extract data, and more.
• Microsoft Office - Automate common tasks you perform in Excel, Word, or PowerPoint.
• Repetitive tasks involving emails, such as sending emails and calendar invites, or downloading attachments from Outlook, Exchange 365, and Gmail accounts.
• File and folder manipulation - Automate various operations such as copying, moving, creating, or deleting files and folders.

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.

Getting Started

How do I install StudioX?

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.

Does StudioX come with a Robot?

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.

How do I learn how to use StudioX?

• Watch the StudioX introduction video (~6m:30s).
• Follow the tutorials in this guide.
• Complete the Citizen Developer learning plan in the UiPath Academy.

How can I run my automations?

• From StudioX, by clicking the Run button in the ribbon.

• From the UiPath Assistant, after publishing the project:

  • If the Robot is not connected to Orchestrator, you can publish projects locally using the Robot Defaults option.
  • If the Robot is connected to Orchestrator, you can publish projects to Orchestrator.

Licensing

Does a StudioX license include an Attended Robot license?

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.

Can I use the StudioX profile if I have a Studio license?

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

Can I use the Studio profile if I have a StudioX Citizen Developer license?

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

StudioX and Studio

Can I open StudioX projects in Studio?

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:

• You can edit existing StudioX projects in Studio, but you cannot create StudioX projects from the Studio profile.
• Only the Main.xaml workflow file can be viewed and edited from the StudioX profile. Additional workflow files can be added to the project and invoked using the Invoke Workflow File activity, but they are not visible when the project is opened in the StudioX profile.
• All activities in the Main.xaml file must be placed inside the SequenceX container activity, the root activity added by default to all StudioX projects.
• Because StudioX only works with simple data types, if you add activities that are not designed for StudioX to the project, StudioX users may not be able to configure them.

Do activities intended for Studio work in StudioX?

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:

• StudioX keeps variable types very simple by design, while many activities designed for Studio require the user to modify and configure specific types which StudioX does not support. If this is the case, the user will not able to successfully use the activity.
• The key properties of StudioX activities are available in the body of the activity (in the Designer panel). StudioX users are not accustomed to configuring activities from the Properties panel.

Can I use StudioX activities in Studio?

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

StudioX and Orchestrator

Can StudioX projects be published to Orchestrator?

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.

Can I develop projects for unattended use in StudioX?

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.

What versions of Orchestrator is StudioX compatible with?

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

Developing for StudioX

Can I create custom activities for StudioX?

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.

Can I create libraries in Studio for StudioX?

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.

Can I create custom Workflow Analyzer rules for StudioX?

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.

Governance and Auditing

What governance capabilities does StudioX offer?

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:

• Create and deploy policies from UiPath Automation Ops, an easy-to-use web application.
• Use a file-based governance model that consists of creating a JSON policy file and deploying the file locally, externally, or via Orchestrator.

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.

How can my organization know what users are doing with StudioX?

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.