- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- 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
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
Configuration Steps
In order to enable Studio to interact with SAP WinGUI, you need to perform the following configurations steps on the server side and the client side. This enables the default and recommended element detection framework SAP for interactive selection.
- Launch
saplogon.exe
, log in to your SAP server using your credentials. The SAP Easy Access window is displayed. - Run transaction
RZ11
. Specify the parameter namesapgui/user_scripting
and press Enter on the keyboard or Display in the SAP interface. - In the Display Profile Parameter Attributes window, click the Change Value button on the toolbar and set the New value of
sapgui/user_scripting
toTRUE
. Save the changes.Note: In case your organisation is using more than 1 instance of an SAP system, do not forget to activate the checkbox “Switch on all servers” to ensure a proper activation of SAP scripting across all servers.Depending on the SAP server version, the following parameters may be set to TRUE by default. In this case, change their value to FALSE.
sapgui/nwbc_scripting
sapgui/user_scripting_disable_recording
sapgui/user_scripting_force_notification
sapgui/user_scripting_per_user
sapgui/user_scripting_set_readonly
Note: All changes to parameters in transactionRZ11
are applied with immediate effect and are lost when the system restarts. For changes to be permanent, please contact your SAP System Administrator and use transactionRZ10
.
- Log off and back on again for the changes to take effect.
- Access the Options menu from the Main SAP Logon window.
- Go to Accessibility & Scripting and click on Scripting.
- Check the Enable scripting option.
- Clear the checkboxes for the following options:
- Notify when a script attaches to SAP GUI
- Notify when a script opens a connection
- Save the changes by clicking OK. The SAP WinGUI scripting is now enabled.
To ensure a smooth experience while creating your SAP automation projects, enable the High Speed Connection (LAN) option in SAP. It is usually enabled by default. You can check its status as explained below:
- Right-click the SAP connection you log into, and select Properties from the context menu. The System Entry Properties window is displayed.
- Switch to the Network tab.
- Click the High Speed Connection (LAN) radio button from the Network Settings section.
- Click OK to confirm and save the changes.
Control (amodal) display options are not supported by SAP scripting. In this case Dialog (modal) display options need to be enabled, and this is done as follows:
- From the SAP Easy Access window, click Settings under the Help menu. The Personal Settings for User window is displayed.
- Access the F1 Help tab and select the in Modal Dialog Box option from the Display section.
- Access the F4 Help tab and select the Dialog (modal) option from the Display section.
- Click the Apply button to save changes and close the Personal Settings for User window.
Note: This is a per-user setting. This configuration needs to be set for each client which creates SAP automation. The default setting to Dialog (modal) for the entire system can be configured by the system administrator.
sapgui/user_scripting_per_user
parameter is set to True
.
Execute(16)
action of the authorization object S_SCR
in class BC_A
.
Please speak to your SAP System Administrator and ensure that the user has appropriate authorization rights.