- 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
- SAP Automation
- About SAP WinGUI Automation
- Configuration Steps
- Supported SAP WinGUI 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
About SAP WinGUI Automation
Enabling SAP WinGUI API scripting allows you to create reliable automations for the SAP WinGUI. Studio and Robots require SAP WinGUI scripting to be enabled on the local machine as well as on the server side. Before you can create your first automation projects for SAP, you need to go over the configuration steps.
UI elements in SAP are known as controls, and you might need a particular approach or activity to detect and use them. Find out more about supported SAP elements.
The following versions of SAP WinGUI are supported for Windows 7 and Windows 10, for both architecture types (32-bit and 64-bit). SAP Logon and SAP Logon Pad are supported on all versions.
- SAP WinGUI 7.40
- SAP WinGUI 7.50
- SAP WinGUI 7.60
- SAP WinGUI 7.70
All available themes (such as Quartz, Belize, Blue Crystal, or Corbu) can be used for SAP automation.
The following activities are specifically tailored for SAP automation:
- SAP Logon
- SAP Login
- SAP Expand Tree
- Table Cell Scope
- SAP Call Transaction
- SAP Click Toolbar Button
- SAP Read Statusbar
- SAP Select Menu Item
- Expand ALV Tree
- Expand ALV Hierarchical Table
- SAP Select Dates in Calendar
- SAP Click Picture on Screen
All SAP WinGUI activities above mentioned are supported and work with Object Repository.
Wildcards and Regular expressions can be used inside selectors generated for SAP WinGUI elements.
technical ID
, but also Text
, Tooltip
and Type of SAP control
attributes. Complex SAP controls such as SAP Tables, SAP Grids and SAP Trees do not have these attributes available, as
identification is done differently.
In case SAP WinGUI API scripting is not activated or not allowed in your organization, you can interact with the SAP WinGUI interface with help of Computer Vision activities.
When SAP WinGUI cannot be automated through SAP API Scripting due to misconfiguration or incomplete configuration, the below error message is displayed:
Please follow the configuration steps to verify and to correct the settings.
The Enforce hard timeout setting can be found in Project Settings > UI Automation Classic > SAP. If the setting is set to True, the Robot terminates the SAP activity execution and it throws an error after the timeout specified in the activity target. You can catch and handle the error message in a Try Catch activity. By default, the setting is set to False.
This setting is useful in cases when you might want to end a long running SAP activity, or when SAP becomes stuck or unresponsive, or network or connection issues arise.