Chrome, Edge, and Firefox integration
Blue Prism uses a native messaging host application to communicate with the browser extension. When a browser is launched from Blue Prism, a native messaging host application is started behind the scenes that listens for any incoming messages from Blue Prism and sends them to the browser extension.
The Blue Prism installer automatically installs the configuration settings for the native messaging host, regardless of whether the user selects to install any of the browser extensions or not. An additional registry key for the native messaging host is created and points to a JSON file which provides details on the allowed extensions and the location of the executable.
There are three Blue Prism browser extensions:
- Chrome – Used to automate applications and web pages in Google Chrome.
- Firefox – Used to automate applications and web pages in Mozilla Firefox.
- Edge – Used to automate applications and web pages in Microsoft Edge.
Browser-based applications can also be automated natively via a Citrix virtual desktop environment in which Blue Prism has been installed with the browser extensions enabled.
Manifest V2 and V3 support
For the Chrome and Edge extensions, we differentiate between Manifest V2 and V3 support according to Google's and Microsoft's guidance. For more information, see the guidance from Google and Microsoft.
Mozilla have not announced a date by which they will remove support for MV2 browser extensions so the Blue Prism Firefox browser extension still uses Manifest V2 and is therefore not impacted by this change.
The following Manifest V2 and V3 support applies to Blue Prism 7 versions:
- Native Manifest V2 browser extension support is provided by default in Blue Prism version 7.0.
- Native Manifest V3 browser extension support is provided in Blue Prism versions 7.1 and 7.2 as follows:
For up-to-date testing and compatibility data about the Blue Prism browser extensions, see the Browser extension compatibility matrix.