DocsAutomate Chrome and Edge with the Application Modeller
The Application Modeller provides a dedicated spy mode for interacting with Chrome and Edge.
- In the Application Modeller wizard, enter a name for the application model and click Next.
-
Select the Browser-based Application (Chrome, Firefox or Edge Chromium) option. You can then choose to continue using a browser that is already running or a browser launched from an executable.
The Firefox browser extension is not available for installation from Blue Prism 7.2. The latest Blue Prism version that includes the Firefox extension is Blue Prism 7.1.2. For more information, see the Upgrade notices.
- Continue through the wizard, completing the following fields:
Target page title – When configuring the Application Modeller using a browser that is already running, the window title can be specified. This ensures that the correct tab or window is identified when attaching to the browser. The visible window title is sometimes appended with further text that is not visible to users. Blue Prism adds a * wildcard at the end of the entered text to ensure that the window can be correctly identified. If the window title is not found for attaching, Blue Prism uses the executable to open
This option is only available when modelling a browser that is running.
- Executable path – The location of the
Start page URL – The address of the browser application or web page to be spied. Several URLs can be added, separated by a space. Command line parameters can be appended to a URL, also separated by a space.
If a URL is not entered, the browser opens an about:blank URL and the user must replace it with a valid URL.
- Application manager mode – The browser extension is only compatible with the Embedded (default) Application Modeller mode when launching or attaching to
A list of web page attributes and their descriptions for
Use Tracking ID to automate multiple browser instances of the same type from a single Blue Prism instance
The spy mode used for interacting with
When launching a browser instance, a tracking ID can be applied as an output parameter in the Navigate stage and stored in a Text data item.
When detaching or terminating a browser instance, a tracking ID can be applied as an input parameter in the Navigate stage and only that instance of the browser will be detached/terminated.
The tracking ID can be used in Read, Write, and Wait stages to restrict Blue Prism to only interact with the browser instance that was created in the Launch action matching the tracking ID. This is useful if you have a process that needs to interact with two instances of the same Single Page Application (SPA), as controls in the first browser instance will also appear on the second instance of the browser resulting in spying errors. If using a tracking ID, only the instance of the browser you want to interact with will respond.
Automate multiple browser instances of the same type from multiple Blue Prism instances
You can open multiple instances of Blue Prism and spy multiple browser instances of the same type on the same device without conflict. If a user has two or more separate instances of Blue Prism on the same Windows environment, they can launch a browser from each Blue Prism instance and only spy the browsers launched by a particular instance. This can be combined with tracking IDs to further limit the spying to individual instances of the browser being spied.
The following video demonstrates how to spy and automate multiple browser windows at the same time.
