a month ago
Hi,
We recently upgraded from 6.10.x to 7.4.
I have noticed a strange behaviour in Activate application. The action itself does not throw any exception, meaning that Blue Prism considers the Activate complete, however the desired application does not actually activate (not brought to the foreground). This results in later actions, such as write (Global Send Keys), in a later stage writes in the wrong application since it's not the active one.
We are running the application we try to activate is Edge. Therar are three instances och Edge running in this particaular case, with three different web pages.
The problem occurs while debugging the process, but without any intervention of the user.
When entering retry stage, and the process yet again activates, it is working as intended.
Any suggestions on how to resolve the issue?
/William
a month ago - last edited a month ago
Hi,
Suppose you have the 3 applications [A,B,C]
When you finish with Application A detach from it then try to attach to B.
For activate try to do it in one navigation stage put the whole windows (win32) minimize then maximise then activate the application with 0.5 of wait berween each action.
If these solution doesnt work let me know and we will test something else.
4 weeks ago
Hi,
Thanks for your reply.
So this is a problem introduced in the newest version of Blue Prism? This has been working fine in version 6.10.2 which was the version we ran before the problems occurred.
Let me explain the situation a little bit more:
All the application windows are already maximized, and the entire window is spied using W32. And you are correct in the guess that there are three Edge applications running, A, B and C.
So what I'm really after is to clarify whether there has been any changes in the activate window functionality in version 7?