SAP Gui Scripting selectors not triggering on SAP in Citrix environment

Help IT Automation
1

Hi guys,

Recently I am dealing with an unexpected topic while automating SAP in Citrix.

While using an older version of UiAutomation Activities package, SAP GUI Scripting selectors are triggered. With a more recent version, they are not (the red icon does spin). We need to update our package to a more recent version, so we cannot mantain the older.

Here is the facts:

  • With UiAutomation 2022.10.4, SAP GUI Scripting selectors are visible.
  • With UiAutomation 2023.4.11, SAP GUI Scripting selectors are visible.
  • With UiAutomation 2024.10.19 SAP GUI Scripting selectors are NOT visible. General selectors are.
  • UiPathRemoteRuntime 2024.10.19 is installed in the machine
  • RZ11 parameters are correct
  • SAP Scripting is enabled in SAP.

Does anyone know what might be the reason for this difference? For us, it would not make sense to refactor everything to use CV, as Ui Automation activities were working perfectly.

Thanks in advance

2

Hi @Bruno_0 ,

If general selectors work but SAP ones don’t, the channel is fine — only the SAP provider on the server side isn’t loading.

What version is your UiPath Extension for Citrix on the client? You mentioned RR and the package but not that one. If it’s still from an older Studio it won’t negotiate the newer SAP schema and you just get the generic tree. Reinstall it from Studio 24.10, then close all sessions from Connection Center and log in fresh (restarting Studio doesn’t do it).

Also check RR on the exact server that served the session, not just the one you patched — if SAP is published from a pool it’s easy to land elsewhere. And if 24.10.19 went in as an upgrade over an older RR, uninstall, reboot, install clean. That misses the SAP plugin registration quite often.

The RR log on the Citrix server (%LocalAppData%\UiPath\Logs) will tell you if the SAP plugin loaded while you indicate.

No need to move to CV for this.

3

Hi @Bruno_0 ,
You can follow these steps:

  1. Verify that UiPath Remote Runtime and Ui Automation Activities versions are compatible. If you’re using UiAutomation 2024.10.19, make sure the Remote Runtime installed on the Citrix machine is also the correct 2024.10 version.
  2. Reinstall or repair UiPath Remote Runtime on the Citrix server/VDI.
  3. In UI Explorer, check if the target is detected as SAP WinGUI or only as a generic Citrix window.
  4. Ensure the SAP GUI version is supported by the newer UiPath package.
  5. Try enabling Modern UI Automation and reinstalling the SAP-specific extensions.
  6. Compare package release notes, as some newer versions changed how SAP selectors are exposed in remote environments.

Thanks

4

@Bruno_0

Please share some sample screenshot comparing the issue.

5

Hi guys,

Thank for your support!

The version of UiPath Extension for Citrix installed on the client is 24.10.128.59771

I have freshly installed from Studio.

I also asked the admin to remove the older RemoteRuntime versions and install only the 2024.10.19 version, which would allows us to test with different Ui Automation package versions.

Regarding the testing, here are the screenshots:

  • UiAutomation package 2024.10.19. Trying to select parameter name is not possible. I can select menu bar and elements which do not rely on SAP GUI Scripting:

UiAutomation 2024-10-19
UiAutomation 2024-10-191384×663 55.5 KB

UiAutomation package 2023.04.11. SAP Gui Scripting selectors are possible as Parameter Name can be selected

I would post the picture, but as a new user, I can only post one picture

I can also post both menubar selectors so you can see the difference.

I do not find a cause for this difference. UiPath Remote Runtime 2024.10.19 supports both packages, but they behave differently. Unfortunately we cannot use a lower version

6

UiPath UiAutomation 23.4.11. SAP GUI Scripting enabled selectors are possible

UiAutomation 2023-04-11
UiAutomation 2023-04-111367×690 67.7 KB

7

Thanks for testing that properly @Bruno_0 , that rules out the usual suspects — same RR, same extension, only the package changes, so this sits in the activities package itself.

Two things that would nail it down:

Bisect it. Try 23.10.x and then 24.4.x on the same machine. If it breaks at 23.10 that’s the release where SAP element detection moved onto the new driver, and it tells you (and support) exactly what changed rather than “somewhere between 23.4 and 24.10”.

While you’re in UI Explorer with 24.10, check the UI Framework dropdown. If it’s sitting on UI Automation or Active Accessibility, switch it to Default and re-indicate the Parameter Name field. In the newer packages the framework choice is not always inherited the way it used to be in Citrix sessions, and a wrong framework gives you exactly what your screenshot shows — menu bar and window chrome fine, scripting-backed controls invisible.

If neither helps, this is a regression and worth a support ticket. Attach both selector trees for the same menubar element (23.4 vs 24.10) — that comparison is what gets it triaged fast, and you already have it.

In the meantime you don’t have to refactor to CV. Package dependencies are per project, so keep the SAP automations in their own process pinned to 23.4.11 and move everything else to 24.10. Not elegant, but it buys you time without touching the workflows.