Table of Contents

Microsoft Edge (Chromium) support in Pega Robotic Automation

Interrogate and automate applications that run in the Microsoft Edge browser by using the Pega Edge extension with the Universal Web Adapter in Pega Robotic Automation.

The Pega Edge extension is backwards compatible; the newer versions of the extension work with older versions of Pega Robotic Automation. To see when versions of the extension were released, see the Pega Robotic Automation build notes.

Installing the extension

Use the Setup wizard for Robot Studio and Robot Runtime to install the Pega Edge extension. To update users from the command line, use the command line installation with the INST_Edge=1 parameter to install the extension. For more information, see the installation instructions.

If you install Robot Studio or Robot Runtime without the Pega Edge extension and later want to install the extension, use the web installer utility. This utility is located in the Robot Studio or Robot Runtime installation folder. The following is an example of the command you enter to install the extension and update the messaging host for Edge.

OpenSpan.WebExtensionInstaller.exe Edge -i

For help information about additional parameters that you can include, append the -h parameter to the command.

Enabling the extension

After installing the Pega Edge extension, the first time a user starts Robot Runtime, that user must decide whether to enable or uninstall the Edge extension. End users must enable the extension so Robot Runtime can automate the browser. If end users do not enable the extension, you must perform a manual process to recover and re-install the extension. For more information, contact Pega Support.

Automating Edge

Keep in mind the following considerations as you use Robot Studio to interrogate and automate Microsoft Edge.

Automating tables in Edge

You can interrogate rows of data and cells within those rows. Use cloning to work with tables. For more information, see Interrogating HTML tables with the Universal Web Adapter.

Automating applications that are running in compatibility mode

The following additional considerations apply when you interrogate Microsoft Edge running in Internet Explorer (IE) compatibility mode. Microsoft designed Internet Explorer (IE) mode for situations where you need Internet Explorer 11 to retain compatibility with legacy websites and applications, but also need a modern browser for more modern websites and applications. To automate Microsoft Edge running in compatibility mode, use Pega Robotic Automation 19.1.86 or later.

Any automation control that you previously interrogated can only match the mode in which it was created. For example, if you interrogate a webpage in non-compatibility mode, Robot Studio creates regular Universal Web Adapter controls. If you reload that page in compatibility mode, those controls no longer match. This also applies to frames and other types of nested controls.
  • Interrogate and then stop each Edge adapter before you begin interrogating another Edge adapter. Attempting to interrogate two different Edge adapters simultaneously results in errors.
  • Shut down all Edge processes before you interrogate compatibility mode pages.
  • When you run an automation that contains a Universal Web Adapter with compatibility mode pages, shut down all Edge processes before you start Robot Runtime.
  • When you use multiple Universal Web Adapters with Edge and compatibility mode pages, ensure that the Edge Configuration properties for each Edge adapter are the same.
  • The controls that you interrogate on a compatibility mode page generate legacy web automation controls and match rules.
  • To have access to the properties, methods, and events of a frame or top-level Windows form in your automation, use non-global webpages.

Using Microsoft Group Policy to control Edge policies

If you use a Microsoft Group Policy Object (GPO) to control Edge policies, and you enable the Configure native messaging block list setting in the Native Messaging section to block all extensions, add the following messaging-host executable to the Control which native messaging hosts users can use setting so that messaging host is not blocked:


Also, if you enable the Control which extensions cannot be installed setting in the Extensions section to block all extensions, add the Extension ID to the Allow specific extensions to be installed setting so that the extension can be installed.


Robotic Process Automation Robotics System Architect
Suggest Edit
Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.