Posted: 5 Nov 2018 15:23 EST Last activity: 9 Nov 2018 17:58 EST
An error occured while preforming interrogation:
In the course of attempting to interrogate a Siebel web app I have a lot of problems. The picture attached is of an error that will pop up sometimes when I try to interrogate something. Following this error, I have to restart visual studio or everything I try to interrogate subsequently will throw a similar looking error. Also following this error, my solution starts to get buggy to the point that it is eventually unusable. This happened before. I had to make a new solution and copy over all the os files from the one that went crazy. following this process, the new solution worked perfectly until I had to interrogate another part of the website. One target threw this error, I tried to close visual studio, doing that manifested 20 or so "Object reference not set to an instance of an object" popups which I also have no idea what to make of, and now the solution is showing signs that it, too, is on its way to being totally broken.
I would like to know if some issue like this is know and if there is anything I can do about this other than periodically moving all my os files to a new solution. If it helps, One of the problems with the dead project was determined to be inaccuracies in the osproj file. Something was stopping it from updating tags that tell pega where files are located.
Are you using IE or Chrome for your Siebel adapter? Please note that the interrogation of Siebel using Chrome (UWA) is currently limited to only a few control types. The following is from Robotic Studio build notes:
This hotfix adds support for Siebel OpenUI 16 in Google Chrome by using a Universal Web Adapter.
This hotfix also contains the Pega Robotic Automation Chrome extension version 1.0.65, which includes additional improvements. You must install this extension version to automate Chrome.
This build only includes support for Chrome’s View, List, and Navigation controls. None of the other Siebel controls are supported.
Solutions that use Chrome with interrogated controls in OpenUI are not supported. These controls would have been interrogated as regular web controls under the webpage with a different hierarchy than the one created with OpenUI supported controls