studio
2022.10
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
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- About SAP Fiori Automation
- Identifying SAP Fiori Elements
- 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
Identifying SAP Fiori Elements
Studio User Guide
Last updated Dec 4, 2024
Identifying SAP Fiori Elements
SAP Fiori uses the UI5 framework to display its elements on the page. Selectors generated for these elements are easy to recognize
by the
ui5
attributes in selectors.
A selector for a SAP Fiori element contains the
<webctrl>
tag, similar to other web UI elements.
There are two types of
ui5
attributes for SAP Fiori selectors:
- Static attributes - such as
ui5-class
,ui5-role
,ui5-type
,ui5-label
,ui5-tooltip
- Dynamic attributes (based on the properties of the target element) - such as
ui5p-value
, ui5p-type
Note that
ui5*
attributes are specific to SAP Fiori elements.
The
ID
attribute of SAP Fiori elements is added by default to corresponding selectors only if it has a static value. Using a dynamic
value for the ID
attribute can generate unreliable selectors. In this case, it is recommended to adjust your selectors using static ui5 attributes.
You can use the entire range of activities from the
UiPath.UiAutomation.Activities
package to create your automation
projects.
Note: Recorders and Data Scraping are currently not supported.