- 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
- 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
Technology Comparison
Depending on your environment, type of automations, and applications used, you can choose one of the two available PiP technologies.
PiP - Child Session is best suited for complex automations that make use of hardware events and image-based automation, while PiP - Virtual Desktop provides a faster process start time and can run on more Windows operating systems.
If both PiP technologies are compatible with your environment and automations, PiP - Virtual Desktop is recommended as it is faster and uses less resources to start the automation. You can also keep a PiP - Child Session instance open throughout the day to achieve similar performance when starting an automation.
The main differences are presented below:
