- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot session (previously Picture-in-Picture)
The Robot session window allows you to run attended automations without having to interrupt your current activity on the machine.
There are two versions of a Robot session, 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.
To set the PiP technology for your Robot session, or to indicate if the process should start in a Robot session by default:
-
Open the desired UiPath Studio project, then select the Project panel on the left side.
-
Open the Project Settings menu.
-
From the PiP Options dropdown menu, select an option to indicate whether the project was tested using Picture in Picture and whether it should start in a Robot session by default:
- Tested for PiP Usage; Starting in PiP - The automation has been approved to run in PiP mode. When you run the process, it starts in a Robot session by default.
- Tested for PiP Usage; Not starting in PiP by default - The automation has been approved to run in PiP mode. When you run the process, 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 you run the process, it starts in the main session by default.
-
From the PiP Type dropdown menu, select the technology to isolate the automation from the user session:
- New Session - When you run the process in PiP, the child session technology is used.
-
New Desktop - When you run the process in PiP, the virtual desktop technology is used.
When using Invoke activities such as Invoke Process, Invoke Workflow File, and Run Parallel Process, you can set the session in which they should run.
This is done by setting the Target Session property of the activity in Studio using one of 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 a Robot session regardless of where the parent process runs.
Note:You can edit the value of the Target Session property only from Studio.
To modify this property for projects developed in StudioX, you need to open them in Studio.
To start the Robot session:
-
In UiPath Studio/StudioX > Debug tab, select the Picture in Picture option, then run your process.
-
In UiPath Assistant, select the desired automation. In the right side panel, turn on the Run in PiP toggle, then run your process. The Robot session window pops up.
To interact with the screen within the Robot session, click on the Join button that appears on hover. Doing so expands the Robot session to full screen on your main display.
To exit full screen, click Leave Robot session. This returns you to the Robot session window, which is configured to remain on top of other applications.
To close the Robot session, click X. A prompt asks for your confirmation to end the Robot session.
