PBE frequently asked questions
Pega Browser Extension (PBE) , included in all 19.1 and 22.1 builds, provides implementation benefits to automation developers and is compatible with Chromium Manifest V3.
With this component, you can automate applications that run in Chrome and Edge. PBE includes the extension and the native messaging host. The native messaging host transmits communications between the browser and either Robot Runtime or Robot Studio.
What is Manifest V3?
Manifest V3 is the latest version of the manifest for Chromium extensions from the Chromium Project. Manifest V3 replaces Manifest V2. Chrome and Edge require Manifest V3. For more information, go to the following website: https://developer.chrome.com/docs/extensions/mv3/intro/.
What is a manifest file?
Google Chrome and Microsoft Edge are based on the open-source Chromium browser
platform. Chromium browser extensions require a JSON-formatted manifest file
(manifest.json). This file describes the behavior of the
extension and provides essential information about the extension, including its
name, version, an array of permissions the extension might use, and other technical
details.
What is a self-hosted extension?
Self-hosting is the practice of hosting an extension outside of the Chrome Web Store. Self-hosting provides several advantages, including making it easier and quicker for you to distribute extensions to your users.
Self-hosting also allows Pega to continue to automate and maintain compatibility with automations that use the ExecuteScript or InvokeScript methods. Self-hosting allows the Pega RPA team to release builds faster.
Installing the Pega Browser Extension
Any build of version Robot Studio or Robot Runtime version 22.1 that you download from the My Pega website includes the Pega Browser Extension and a Setup wizard that you can use to install it.
After you install PBE, use the Pega Synchronization Engine to maintain the version of PBE running on your system.
How do I prepare for PBE?
Add the extension ID to the ExtensionInstallAllowlist policy in the Group Policy Editor for your Active Directory Domain Service to enable users to use a self-hosted extension. Alternatively, you can set the ExtensionInstallForcelist policy to force-install an extension on your users’ computers. For more information on setting Group Policy, see the following articles:
- Using Microsoft Group Policy to control Chrome policies
- Using Microsoft Group Policy to control Edge policies
How do I install PBE?
Robot Studio and Robot Runtime include PBE. You can install PBE by itself or as part of a Robot Studio or Robot Runtime installation. To install PBE as part of a Robot Studio or Robot Runtime installation, select the option to install PBE when you run the Setup wizard. For more information, see the installation instructions.
Can I use the Pega Synchronization Engine to install PBE?
No. You must initially install and configure all new components. After you install PBE, you can configure the Pega Synchronization Engine to ensure proper maintenance and updates.
Pega Robotic Automation project compatibility
The Pega Browser Extension is compatible with version 19.1 and version 22.1 robotic automation projects in most cases.
Can I have both 19.1 and 22.1 runtimes in my implementation?
Yes. PBE works with both versions of Pega Robotic Automation. However, you cannot have both PBE and the older extensions in your implementation. If you have both 19.1 Robot Runtime and 22.1 Robot Runtime installed, you must use PBE. For more information about using PBE with 19.1, including details on when to update your 19.1 implementations to use PBE, see the Pega Browser Extension (PBE) FAQ for version 19.1.
What browser versions does PBE support?
The Pega Browser Extension works with Chrome versions 88 and later; and all versions of Edge.
Previous topic Browser support Next topic Google Chrome support