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
- 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
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- 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 Nov 4, 2024
Trigger-based attended automation
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.
