- Release Notes
- Getting Started
- Introduction
- About Backward and Forward Compatibility
- The User Interface
- Keyboard Shortcuts
- Signing in to Your Account
- Configuring Studio Settings
- Orchestration Process
- Background Process
- Robotic Enterprise Framework
- Transactional Process
- Trigger Based Attended Automation
- Creating a Basic Process
- Creating a Basic Library
- Tutorials
- 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
- Variables
- Arguments
- Imported Namespaces
- 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
- Test Suite - Studio
- Extensions
- Troubleshooting
Trigger Based Attended Automation
Trigger Based Attended Automation is a project template based on a Sequence, that is tailored to monitor certain triggers such as a mouse or keyboard event and deploy an automation. This sequence contains a Trigger Scope activity named Monitor Agent Action that contains triggers for clicks, keystrokes, and hotkeys, a Get Source Element activity to retrieve UiElement objects and a container for adding event handling logic.
The template allows you to configure triggers and add other trigger activities based on the project needs. These triggers are monitored simultaneously and the Event Handler is executed once for any occurring event. The Use Foreground activity allows running a specified set of activities in the foreground.
The default dependencies of this project template are UiPath.Excel.Activities, UiPath.System.Activities, UiPath.Mail.Activities, and UiPath.UIAutomation.Activities.
