Understanding access rights while automating SAP

Introduction
With Leapwork it's very easy to automate business flows under SAP GUI, however, users need to understand a few access-related details before starting automation on SAP GUI with Leapwork. Below mentioned scenarios describe a few examples where Leapwork will not be able to run SAP GUI due to differences in access levels.

Scenario 1
SAP GUI is running as Administrator, and the user tries to run the test using Leapwork Local Agent.
In this scenario, Leapwork Agent (which is a service) is running with non-admin rights and SAP GUI is running as administrator, due to this difference in access levels between 'Leapwork Local Agent' and 'SAP GUI', Leapwork Agent will not be able to access SAP API and hence test will fail.

Note: In this specific case, Leapwork Studio must be started as an administrator to be able to match SAP GUI access level else it will not even execute the start block.

Scenario 2
User is Local Administrator (in Windows 10, 8.1/8), user starts Leapwork Studio as Administrator and tries to open SAP GUI using the "Start Application" block. In this scenario, Leapwork Studio will start SAP GUI as administrator, but Leapwork Agent is still running with non-administrator access, due to this difference in access levels between 'Leapwork Local Agent' and 'SAP GUI', Leapwork Agent will not be able to access SAP API and hence test will fail.

To be able to run SAP GUI test on remote agent please run SAP GUI without admin Access. User will be able to run SAP GUI automation on Local Display(s) in Preview mode with the below access levels:

When both SAP GUI and Leapwork Studios are started as administrators.
In case both SAP GUI and Leapwork Studios started with non-administrator privilege.
Leapwork Studio is running as administrator and SAP GUI is not.

Note: Leapwork supports SAP GUI 7.

For any clarification, contact our Priority Support.