@Robu1
Thank you very much for answering my question so quickly and efficiently.
I checked the permission levels of the applications involved in the process, and they were the same. In our company, obtaining administrative privileges is a rather bureaucratic process, so there would be no possibility for the user to have two different permission levels. In addition, the issue occurred on different days, which further supports this conclusion.
The system name and path used to identify the window were quite simple, as previously described.
I was not able to test for possible UIA blocking, but I eventually resolved the issue as follows: I re-captured, on the user’s own computer, the screens required for the flow. Surprisingly, after doing this, PAD was able to correctly identify the windows.
I still do not fully understand why PAD, on the user’s computer, could not recognize the windows that had been previously captured, but worked once they were captured locally. I verified that all element names were the same, and they were. The only difference was that I had renamed the element captured on my computer, which apparently may have affected PAD’s behavior. I assumed that renaming elements was merely a cosmetic change, but I am not certain whether this was the root cause of the issue. In any case, the most important thing is that the solution worked.
Thank you very much.
