Skip to main content
LinkedIn
Copied!

Table of Contents

Automating applications that run on Google Chrome

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

The Pega Chrome 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.

The Pega 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. For versions of Chrome that are signed with CRX version 2, use Pega Chrome extension versions 1.0.12 - 1.0.49. For more information, see Pega Robotic Automation version 8.0 build notes.

Installing the extension

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

If you install Robot Studio or Robot Runtime without the Pega Chrome 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 would enter to install the extension and update the messaging host for Chrome.

OpenSpan.WebExtensionInstaller.exe Chrome -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 Chrome extension, the first time any user starts Robot Runtime, that user must decide whether to enable or uninstall the Chrome extension. Automation developers, of course, would enable the extension. Automation end users must enable the extension too, so the automation can automate the browser. If automation 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 Chrome

Keep in mind the following considerations when you automate applications that run in the Chrome browser:

  • 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 have access to the properties, methods, and events of a frame or top-level Windows form in your automation, use non-global webpages. To interrogate non-global webpages, you must have version 8.0.1042 or later.
  • Property changed and Cancellable events are not supported in Chrome, but are supported in Internet Explorer.

Automating tables in Chrome

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.

Working with the shadow DOM

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, 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 block list setting in the Native Messaging section to block all extensions, perform the following steps to provide Robot Studio and Robot Runtime with the access they need to function correctly.

  1. Start the Microsoft Local Group Policy Editor.
  2. Select Computer Configuration > Administrative Templates > Google > Google Chrome > Native Messaging.
  3. In the Configure native messaging allowlist setting, add the following messaging-host executable to so that messaging host is not blocked:

openspan.translators.web.messaginghost

  1. Save your changes and close the Local Group Policy Editor.

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.

 

 

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us