Capture 2.1: May 2021

This is the general release of Capture 2.1.

Known issues

Click here for a list of any prominent issues and limitations with this release.

Secure development policy

As part of our secure development policy, Blue Prism products are evaluated against the following security standards:

  • OWASP Top 10 –The security vulnerabilities that pose the most risk to applications development. For more information, see the OWASP website.
  • SANS CWE Top 25 – The most common software security vulnerabilities found throughout the software development industry. For more information, see the SANS website.
  • Federal Information Processing Standard (FIPS) Publication 140-2 – U.S. government standard that defines minimum security requirements for cryptographic modules in information technology products.
  • Payment Card Industry Data Security Standard (PCI DSS).
  • Health Insurance Portability and Accountability Act (HIPAA).
  • Federal Information Security Management Act (FISMA).

A compliance highlight summary report is available upon request via Product Support.


The following new features and enhancements are introduced in this version of Capture:

  • Improvements to image storage – Previous versions of Capture were potentially constrained by the high level of memory usage, particularly when editing complex processes. To address this issue, Capture 2.1 introduces a change to the image storage architecture. Captured images are no longer stored in the database (.db) file located in the user’s AppData folder. They are now stored in a separate folder in JPG format and are deleted automatically when the user exits Capture if no longer required. This enhancement applies to both the installed (MSI) and non-installer (EXE) versions of Capture 2.1. Learn more...
  • Business objects export – Users can now associate step actions with Blue Prism business objects. Step actions in Capture are not automatically associated with objects and will need to be assigned manually. Users can then choose to auto‑generate a skeleton of the object, for inclusion in the exported BPRELEASE file for further development in Blue Prism. Learn more...
  • Mini-map – To enable process owners and analysts to better navigate and expand very large processes, a new mini-map feature is available, which allows users to view where they are in the overall process, even if the process cascades off screen. Learn more...

Fixes and minor improvements

The following fixes and minor improvements have been made to Capture in this release:

Description of change


An error no longer incorrectly displays when loading a process that has an empty first step. CAP-880
To improve image quality, screenshots are now captured in the resolution of 1920 x 1080 by default. For systems with fewer than 4 GB of available memory, screenshots are captured in a resolution of 1280 x 720. CAP-630

Performance issues caused by insufficient memory when working on large processes, have been significantly reduced in this release. users are now significantly less likely to be required to save their processes and restart Capture, due to improved image storage functionality.


Performance improvements have been made to the time taken to process images when using OCR during capture. Images are now processed in smaller, more regular batches, which means that when the capture is complete, much less time is spent loading the process after the user has completed a capture.


Anchor and page nodes on processes imported into Blue Prism are now correctly aligned with the grid in Process Studio and Object Studio. Previously, such nodes had to be manually adjusted.


To make exported PDD and BPRELEASE processes easier to compare, group numbering has been added to the process map view.


To verify authenticity against anti-virus software, the Capture.exe and Uninstall Capture.exe executables stored in the user’s Programs folder are now digitally signed.


To enable the introduction of auto-generated business objects, captured processes can now be exported in Blue Prism BPRELEASE format. Previously, they were exported in XML format.