Close popover

Table of Contents

Google Chrome support in Pega Robotic Automation

Pega Robotic Automation includes limited support for for interrogating and automating the Google Chrome browser by using the Universal Web Adapter. An extension to Chrome adds this functionality by using the Universal Web Adapter.

The following table lists the versions of Robot Studio that work with the corresponding Chrome versions:

Supported Chrome versions Corresponding version of Pega Robotic Automation Applicable extension
38 - 59

8.0.1012 - 8.0.1080

1.0.12 - 1.0.50

60 and later

8.0.1012 - 8.0.1066
8.0.1067 and later

1.0.12 - 1.0.50
1.0.50 - 1.0.69

60 and later

8.0 SP1 2004 - 8.0 SP1 2009
8.0 SP1 2010 - 8.0 SP1 2055
8.0 SP1 2056 - 8.0 SP1 2060
8.0 SP1 2061 - later

1.0.85
1.0.86 - 1.0.90
1.0.94
1.0.95

60 and later

19.1.01 - 19.1.03
19.1.04 - 19.1.13
19.1.14 - 19.1.18
19.1.19 - 19.1.31
19.1.32 - 19.1.42
19.1.43 - 19.1.53
19.1.54
19.1.55 - 19.1.61
19.1.62 - 19.1.66
19.1.67 - 19.1.68
19.1.69
19.1.70 - 19.1.75
19.1.76 - 19.1.78
19.1.79 and later

1.0.86
1.0.90
1.0.91
1.0.93
1.0.94
1.0.95
1.0.96
1.0.97
1.0.101
1.0.104
1.0.107
1.0.108
1.0.109
1.0.110

The Chrome extension version 1.0.50 and later is signed with CRX version 3. CRX version 3 is not compatible with Google Chrome version 59 and earlier.

Installation

Use the Setup wizard for Robot Studio and Robot Runtime to install the Chrome plug-in. If you are updating several users, you can use the command line installation command with the INST_CHROME=1 parameter to install the plug-in from the command line. If omitted, the Chrome plug-in is not installed. For more information, see the installation instructions for your version of Robot Studio or Robot Runtime.

Automating Chrome

Keep in mind the following limitations when automating the Chrome browser:

  • You can interrogate cells within simple tables, but the table designer is not available for the Universal Web Adapter. Complex tables cannot be matched based on the table schema.
  • Property changed events are not supported.
  • Cancellable events are not supported.
  • Plug-ins, such as Java, are not supported.
  • There is limited support for Adobe Flash. However, Adobe ended support for Adobe Flash on December 31, 2020. For more information, see Adobe Flash and Apache Flex application support.
  • 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.62 or later and version 1.1.101 of the Chrome extension.

Chrome-specific limitations

  • When installing the Chrome extension and running it for the first time on a Robot Runtime machine, end users must respond decide whether to enable or uninstall the Chrome extension. End users must enable the extension for Robot Runtime to inject. If an end user does not enable the extension, a manual process must be run to recover and install the extension again. For more information, contact Pega Support.
  • To support multiple concurrent adapters, you must have version 8.0.1028 or later. For more information, see Using multiple Chrome adapters within a Studio solution.
  • To support frames, you must have version 8.0.1038 or later.
  • To support non-global webpage interrogations, you must have version 8.0.1042 or later.

Using Microsoft Group Policy to control Chrome policies

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

openspan.translators.web.chrome.messaginghost

Also, if you enable the Configure native messaging blacklist setting in the Extensions section to block all extensions, you must add the Extension ID to the Configure extension installation whitelist setting so that the Chrome extension can be installed.

The extension ID differs, depending on how you install the Chrome extension. If you install the extension using the Setup wizard or from the command line, you would enter: 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.