studio
2023.4
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Trigger-based attended automation
- Overview
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Studio testing
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Last updated Sep 29, 2025
Attended automations are designed to run under human supervision based on input received from humans. Therefore, the actions a user or an application takes are defining for attended automations. Triggers advance attended automations by monitoring whatever action a user or an application takes. In the UiPath attended automation ecosystem, user and application actions are defined as events. Triggers can set off a multitude of events, enabling complex attended automations.
The benefits of the current trigger-based attended automation capabilities are:
- Build highly responsive automations – using triggers for application or form events such as Minimized, or for user events such as Click.
- Work with multiple attended scenarios at the same time – using triggers for multiple application events (Minimized, Restored, Title changed) or user events (Click, Keypress, Hotkey, Mouse) that you can enable at the same time.
- Higher UI (user interface) accuracy and overall performance – using the improved version of the existent capabilities, to better identify UI elements and events.
- Run workflows intermittently – using triggers that you can schedule to either run one time, in sequence, or at the same time.
Here are a couple of scenarios where you can use the trigger-based attended solution:
- Contact Center:
- Customer service - for companies where customer service works via phone calls.
- Sales requests
- Feedback forms
- Survey applications
- Digital Adoption Platforms
- For developing guided tours, to help users navigate through a product, application, or website.
- For developing custom validation for user input.
