Table of Contents

Microsoft Edge (Chromium) support in Pega Robotic Automation

Pega Robotic Automation includes limited support for interrogating and automating the Microsoft Edge browser by using the Universal Web Adapter. An extension to Edge adds this functionality. The following table lists the versions of Robot Studio that work with the corresponding Edge versions:

Supported Edge version

Corresponding version of Robotic Automation

Applicable extension version

87.0.664.52 and later 19.1.79 and later


87.0.664.52 and later

19.1.76 - 19.1.78


87.0.664.52 and later

19.1.70 - 19.1.75



Use the Setup wizard for Robot Studio and Robot Runtime to install the Pega Edge plug-in.To update multiple users, you can use the command line installation with the INST_Edge=1 parameter to install the plug-in. If you omit this parameter, the Pega Edge plug-in is not installed. For more information, see the installation instructions.

Automating Edge

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

  • You can interrogate cells within simple tables, but the table designer is not available for the Universal Web Adapter. You cannot match complex tables based on the table schema.
  • Property changed events are not supported.
  • Cancellable events are not supported.
  • Plug-ins, such as Java, are not supported.
  • Compatibility mode for pages is not supported.
  • The Universal Web Adapter does not support event collection for Pega Workforce Intelligence™.
  • There is no utility for converting a legacy web adapter into a Universal Web Adapter.
  • If your solution interrogates and automates controls that are under Shadow Document Object Models, use Pega Robotic Automation 19.1.70 or later.

Edge-specific limitations

After installing the Edge extension, the first time a user starts Robot Runtime, the user must decide whether to enable or uninstall the Edge extension. End users must enable the extension for Robot Runtime to inject into the target. If an end user does not enable the extension, you must run a manual process to recover and install the extension again. For more information, contact Pega Support.

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.

The extension ID differs, depending on how you install the Edge extension. For example, if you install the extension by using the Setup wizard or from the command line, the extension ID is: lajjpilliikppcbaghjehndpfdiiphbe.
Suggest Edit

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.