Using multiple Chrome and Edge adapters within a Robot Studio solution
Sometimes in an automation, you might require multiple Universal Web Adapters to automate a Chrome or Edge browser at the same time. In addition, you might need to interrogate a multi-tab, multi-window environment.
Chrome or Edge can be running when you start a Universal Web Adapter. The adapter catches up to the top-level documents already running.
The system tracks tabs as you interrogate the browser and at runtime. Interrogation highlights the selected tab controls as you move the Capture icon over each Chrome window.
Because all documents are visible to all Universal Web Adapters, use the AcceptedDomains property to determine which domains the Universal Web Adapter should recognize. You cannot interrogate any documents you exclude by using this filter property, nor do those documents match at runtime. The property contains a collection of filters, so you can include more than one filter property to declare which domains the adapter should recognize. This lets you focus the adapter on only those documents you want it to process.
There are three scenarios which can occur when you start the Universal Web Adapter:
- Set the StartMethod property to Start. Then, when a Chrome or Edge Universal Web Adapter starts, a new Chrome or Edge window appears and goes to the page you specified in the StartPage property. If Chrome or Edge was not running, the system starts it.
- Set the StartMethod property to MonitorAll, and the adapter starts, but no new windows or tabs are created. The system does not start Chrome or Edge.
- If Chrome or Edge is already running when you start the adapter, the adapter processes all top-level documents based on the way you set up the AcceptedDomains property.
If you set the adapter to Start, it does not stop until all Chrome or Edge processes are closed. For more information, see General web properties, methods, and events.
Keep in mind the following limitations:
- The system only supports one profile automated by Robot Runtime.
- You cannot use a Windows adapter to interrogate HTML elements with Chrome or Edge.
- A maximized Chrome or Edge browser with windows scaling set to anything other than 100% results in a slight deviation in highlighting.
- When downgrading, refresh the cache so the Chrome or Edge target factory appears when you interrogate the solution. Downgrading with account credentials that differ from ones used when you logged in does not remove the old extension for the other accounts. The system checks this extension for backwards compatibility.
- IBrowserWindow events are not supported.
- The CreationDateTime and Focused IBrowserWindow properties not supported.
- The following IBrowserWindow methods are not supported:
Focus GetActiveForm GetFormAbove GetFormBelow GetScreenShot PerformClick PerformDoubleClick PerformRightClick ResetState SendKeys Previous topic Automate dialogs in Chrome and Edge Next topic Hiding or reparenting