You will need to switch to the Windows Control tab when interrogating. Here you can create a control from the Chrome Legacy Window. Just right click on it and select Create Control. Remove the default Control ID match rule or else it will most likely only match until you close the browser.
You can rename the resulting control - it will have a generic name. In this example I have named it browserWindow.
This control will allow you to send keys to the browser screen. You will not be able to guarantee which control will process the keys however.
I have tried this already but send keys does not seem to work though the function is enabled.. I am trying to send TAB key. is there any alternate measure where I can send keys using the chrome.exe directly
There has been a change to support for Chrome and as a result this post no longer applies. This change was made in 8.0.1027. Here are the release notes for it:
This hotfix adds support for running multiple Universal Web Adapters simultaneously to automate the Google Chrome browser. Here are some additional benefits:
Chrome can be running when you start a Chrome Universal Web Adapter. The adapter catches up with the top-level documents that are already running.
There are now multiple ways to close a document within a Chrome browser. For instance, you can stop the browser, stop just matched documents, stop all tracked documents, or do nothing. For more information, see the BrowserStopMethod property.
Tabs are now accurately tracked while interrogating and at runtime. Controls correctly highlight the selected tab’s controls as the interrogation cursor moves over each Chrome window.
Because all documents are visible to all Chrome Universal Web Adapters, use the new AcceptedDomains property to specify which domains the adapter should recognize. This lets you focus the adapter on only the documents that you want it to process.
Note these other changes:
The List Browsers and Frames button is now the List Windows and Documents button. When you click this button, the system displays all tracked documents with the parent for each tracked document as the browser form that the document resides in. This indicates that the relationship between a top-level document and its form is dynamic. You can tear off a tab into a new form or drag a tab from one form onto another and join it to that form.
To implement this feature, Studio/Runtime no longer injects native modules into the Chrome process. Instead, the Pega Robotic Automation Chrome extension is loaded in Chrome. This means that the following form-level functions, which require native injection, are no longer supported for the Chrome browser:
Hey that sounds promising, any tips on how to do this? I'm relatively new to the software :(
I got what im trying to do working with IE and SendKeys, but I'm wanting to try and get it working with Chrome, to avoid a windows security popup that I cant seem to interrogate and automate when the user trys to log in with IE.