studio
2022.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
- 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
- About Salesforce Automation
- Support for Salesforce Lightning Interface
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Studio User Guide
Last updated Dec 19, 2024
Support for Salesforce Lightning Interface
When automating the Salesforce Lighting interface, the out-of-the-box generated selectors contain specific Lightning attributes
that are stable and will not change over time, thus making them very reliable and resilient to UI changes. This means the
UI Automation activity package is a great choice for automating this environment. The attributes are
sfl-path, sfl-name and sfl-type.
Note:
Any UiPath.UIAutomation.Activities package can be used to automate Salesforce Classic and Lightning UI interfaces through the generic UiPath browser automation support.
UiPath.UIAutomation.Activities v21.10 or above is required to create automation projects for Salesforce Lightning interface by using the specific attributes described below.
Most elements in Salesforce Lightning can be identified by using the
sfl-path attribute. You can find several examples below:
A selector identifying a search input field; the selector contains the
sfl-path attribute determining the precise path of the element:
A selector identifying an icon:
In some cases, however, the
sfl-path attribute might not be enough to precisely identify the element you are trying to automate. In these cases, the sfl-name and sfl-type attributes are exposed in UIExplorer and can be included in the selector as needed:
