- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Common Connection Errors
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
Picture in Picture
Picture-in-Picture allows you to run attended automations without having to interrupt your current activity on the machine.
Just as you can consume media while using the computer with the help of Picture in Picture, the work you have can be separated as well.
While the Robot works in PiP, your machine is free and you can access your files, modify documents, send e-mails, answer phone calls, and other duties that can only be completed by you.
There are two versions of Picture in Picture, both isolating the automation from your work, and are based on the following technologies:
- Child Session - Processes run in a separate Windows session on the machine.
-
Virtual Desktop - Processes run in the same Windows session but on a virtual desktop.
A PiP process is started from either the Debug tab in Studio, from StudioX, or from the UiPath Assistant.
The PiP technology used by your automations is set from the PiP Type menu in the Project Settings in Studio. By default, this is set to New Session.
The following options are available:
-
PiP Type:
New Session- When the automation is run in PiP, the child session technology is used.-
New Desktop- When the automation is run in PiP, the virtual desktop technology is used.
If a process has been tested and can be safely run in PiP, you can mark it it as such from the Project Settings in Studio.
From the same menu, you can also set it to start by default in Picture-in-Picture, and choose the PiP technology you want to use:
-
PiP Options:
Tested for PiP Usage; Starting in PiP- The automation has been approved to run in PiP mode. When run, it starts in PiP by default.Tested for PiP Usage; Not starting in PiP by default- The automation has been approved to run in PiP mode. When run, it starts in the main session by default.-
Not tested for PiP usage- The automation has not been approved to run in PiP mode. When run, it starts in the main session by default.
When using Invoke Activities such as Invoke Process, Invoke Workflow File, and Run Parallel Process, you can choose the session in which they run.
This is done by setting the Target Session property of the activity in Studio using the following values:
- Current - The child process opens in the same session or desktop the user is in.
- Process Default - The child process uses the configuration set in the Process Settings.
- Main - The child process starts in the user session regardless of where the parent process runs.
-
Picture-in-Picture - The child process starts in Picture-in-Picture regardless of where the parent process runs.
Note:TheTarget Sessionproperty can only be modified from Studio.To alter this property for projects developed in StudioX, you must open them in Studio.
