- 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
- 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
About SAP Fiori Automation
Automation projects for SAP Fiori can be created out-of-the-box, so you are not required to install a dedicated SAP extension or set of activities.
We provide support for SAP Fiori versions 1.52 and above which are in Maintenance by SAP. You can check this page for more information about supported versions and maintenance status.
SAP Fiori automations can be created on the following web browsers:
- Internet Explorer
- Mozilla Firefox - requires the Extension for Firefox
- Google Chrome - requires the Extension for Chrome
- Microsoft New Edge Browser - requires the Extension for Edge (Chromium)
The UiPath.UIAutomation.Activities package v20.6 or above is required to create automation projects for SAP Fiori.
The entire range of activities from the UIAutomation Activities Pack can be used, with the following specification:
- The SimulateType property is recommended for the Type Into activity.
- The SimulateClick property is recommended for the Click activity.
- The Table Cell Scope activity can be used for SAP Fiori table automation. This includes Auto scrolling for SAP Fiori Tables feature, which allows UiPath to scroll automatically to the right cell in any SAP Fiori tables without knowing the exact place of the required value.
Support for all browser controls is provided for SAP Business Client. This allows users to take an advantage of the same performance and SAP Fiori capabilities as in Google Chrome using UiPath Studio. All SAP Fiori elements are properly recognized with all their SAP FIORI specific properties, all SAP Fiori version are supported.
