Known issues and limitations

This page lists all known issues and limitations of the latest version of Blue Prism Capture.

If you are a Enterprise for BP® Blue Prism Enterprise customer and would like to raise a support ticket, please contact customer support by following the normal process, as defined in How to get help from customer support on the customer portal.

  • The action items in a screenshot cannot be reordered by dragging.
  • Steps in a process are not draggable in the main user interface.
  • Only PNG and JPG image formats are currently supported for screenshots.
  • Resizing or rotating screenshots in the step editor is not possible.
  • When replacing a screenshot in the step editor, bounding boxes will be removed. The step action will not be deleted.
  • There is no option to save as, saving will overwrite current process. If the process title is changed, the previous process will not be overwritten on save.
  • Deleting a decision point will also delete all attached connections/branches.

  • For systems with fewer than 4 GB available memory, screenshots are in 1280 x 720 resolution.

  • There is no way to cut and paste a step into the number one position.
  • There is no way to add an empty step within the step editor screen.
  • There is no way to start a blank process, you must first record a process or open a saved process.
  • Whilst the drag mouse icon is shown, the user is not able to drag step actions to reorder.
  • If two decision point are inline in the process map view, both with connection arrows referring to a previous step, these lines will overlap.
  • When highlighting text in pop up windows, if the mouse moves off of the pop up, then the pop up will close.
  • An anti-virus scan of Capture may occur on first launch. This may produce a JavaScript error message. Please relaunch Capture if this occurs.
  • A JavaScript error may be produced during launch of Capture. If this error continues to occur, delete comtypes_cache folder from: C:\Users\USERNAME\AppData\Local\Temp. If this does not resolve the error, contact support.
  • If Capture is closed while importing a process (via “Open file”), allow for backend services to close down prior to relaunching Capture.
  • Passwords are not censored by the Capture tool and will be included in the step action. It is important to ensure that the process is thoroughly reviewed prior to exporting and distributing. See Omit/remove sensitive data for further details.
  • The tool cannot record actions in applications that need admin permissions (e.g. task manager). To record the actions in these applications the Capture tool must run with admin privileges.
  • The Capture tool supports a maximum of two monitors.
  • Dual monitor setup will only work if both monitors are horizontally aligned, otherwise the highest resolution monitor must be set as the primary monitor. For both scenarios, the monitors must have the same scaling (e.g. 100%).
  • Memory usage does not reduce until Capture is closed and restarted. A warning message will appear if usage is too high, with a recommendation to save the process and restart the program.
  • Mouse scroll and hover-over actions are not recorded by the Capture tool.
  • When uninstalling Capture, all saved process files will be lost. Files that have been exported will not be lost.
  • If a second instance of the portable version (.exe) of Capture 2.1 is launched, you will be unable to capture a new process.
  • Capturing may be impacted by CPU performance when relying on OCR spying. This may result in missing information of spied elements on slower systems.
  • Actions performed on a numeric keypad (numpad) are not recorded by Capture tool.
  • Only one template is available for PDD export.
  • Microsoft Visio must be installed if Visio map export is required.
  • Visio map will not export if the user has an instance of Microsoft Visio running on their system. It must first be closed prior to Visio export.
  • PDD will not export if there are special characters in the Version field of the Export menu.
  • Steps that are manually added to the process will not be taken into consideration in the time taken field of the PDD.
  • The time taken fields in the PDD may be incorrect when reordering steps in the process.
  • The contents numbering does not automatically update in the PDD, the user is required to manually update.
  • Process export is skeleton process and so many of the Blue Prism best practices are not followed in this version.
  • Process title will be truncated when exporting to .bprelease to allow for importing into Blue Prism.
  • If a decision point has 2 connections, when imported into BP, the connections will be overwritten with Yes and No to align with decision node logic in Process Studio.
  • Decision responses may require switching within Process Studio. The first connection will always be Yes when imported into BP (this is only applicable for decision points with 2 connections).
  • Capture does not communicate with Blue Prism directly, there is no way to verify if the auto-generated object is already in your existing object library.
  • Object names are not case sensitive. Ensure that object naming is consistent throughout the process (for example, an object name of Example and example will result in two business objects being exported, causing an error on import into Blue Prism).