I want to click on Allow for the SAP GUI Security Pop up
I am using click image as other clicks did not work but with this when running on the debug I was able to click though and go to the next flows but the issue arises when running unattended - I read online and updated some session settings such as resolution width (1920) Resolution Height (1080) and resolution depth (32) under
Advanced robot options but still the issue is persistent when I run the process unattended.
FYI - we cannot change the SAP configuration not to trigger the pop up as that is part of the group policy - @Anil_G@Yoichi
Is the popup showing up every time you try to run the process or it’s random?
it’s better to first check for the popup visibility.
Use check app state to see if popup showed up, if yes, then go and click the image you are trying to else proceed normally.
Also how are trying to click, using modern click activity? If yes then that activity automatically recognizes the cv or image parts in the element and creates a selector.
Hi @sonaliaggarwal47
Thanks for the prompt response -
The pop up happens every time the process exports excel file to the local folder.
Yes, modern click activity - Also, I’d like to emphasize that I am able to run (click on allow and go to the next flow) it on a debug mode but fails to click on “Allow” when running unattended.
When you say debug mode, have you tried “running” the process instead of debug mode. Does it run fine then? If it doesn’t then it can be an issue that process runs too fast and skipping the part of clicking .
Please note that Debug run is usually slower than the run mode, so adding some delay or checking the app state before trying to click really helps.
But if process runs fine in run mode like debug mode but fails only during unattended session then I would suggest to take screenshot before the click activity and right after the click activity as well so as to shed light on what is showing up in screen when bot is trying to click the popup.
Also enabling properties for click activity like simulate click or send window messages also helps.
Sorry I have corrections to make - I was running the Run file from the bot server (using the bot/service account) not from orchestrator. When I said unattended I meant not on a debug mode
@ashokkarale - that would have been a great resolution, but it is part of the group policy - when someday upgrade or patching happens it is going to happen again
So you are saying when you are running by clicking debug, bot is able to click?
But when you click on run/run file, bot is not able to click?
And you are trying attended only as of now not unattended(means not from orchestrator )?
If answer to all of the above is yes, then
Do you see a popup appearing on the screen? And bot just missed to identify it?
can you add activity check app state for this pop up and under target appears, add your click activity.
have you tried to identify the allow element using Uiexplorer from studio? Is it able to identify ? May be you should try like this (using classic activity) and see if it works.
a simpler one would be I see remember My decision option…if you do that once is it not working?
also run file is not unattended ..unattended is running from orchestartor with not logging to machine yourself
if run file fails, either it is coming as a separate window try using separate use app/browser or introduce a delay or increase timeout.(but rather than this one time handling manually would be better)
