Automating Excel Popup Windows
As one of the use cases of the Robotics automation, when opening Excel file, it pops up a window (not an error message) that contains clickable buttons and some forms. When clicking on the button on the popup window, another window pops up. Can Pega Robotics handle these popup windows?
I tried the following two things, with no luck so far:
1. Using OOTB Excel connector -> Don't know why but the popup window didn't come up.
2. Using Windows Application (specifying Excel.exe with MonitorAll) with using General DOS Console to run "Excel.exe /r xxx.xls" -> The popup window appeared. The interrogation of Windows Application was "sort of" successful (couldn't interrogate the parts, but could just interrogate the broader "area"). In this case, the Robot couldn't execute the automation against the popup window (I tried SendKeys mothod).
Any suggestions?
Accepted Solution
ServiceNow
JP
Thanks. After interrogating the Excel as a Windows Application, we could successfully performed the SendKeys method to the Excel popup window. That is, setting Path to "C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE", setting StartMethod to "Start", and setting Arguments to "/r "C:\temp\filename.xls"". And I interrogated the popup window's title bar, which is the object the SendKeys method is performed on. That worked fine. Just a nonintuitive workaround though.
Pegasystems Inc.
US
This type of automation is not generally supported. The Excel Connector works with the COM object and there may be some way through COM to do what you want. I am surprised that you are not seeing the popups when using the Excel Connector.
Accepted Solution
ServiceNow
JP
Thanks. After interrogating the Excel as a Windows Application, we could successfully performed the SendKeys method to the Excel popup window. That is, setting Path to "C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE", setting StartMethod to "Start", and setting Arguments to "/r "C:\temp\filename.xls"". And I interrogated the popup window's title bar, which is the object the SendKeys method is performed on. That worked fine. Just a nonintuitive workaround though.