Known limitations

This page lists all known minor limitations of the latest version of Blue Prism Capture. Click here for a list of any prominent issues with this release.

If you are a SS&C | Blue Prism® Enterprise for BP 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 cannot be dragged in the main user interface.
  • 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.

  • 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 start a blank process, you must first record a process or open a saved process.
  • Capture cannot record actions in applications that need admin permissions (e.g. task manager). To record the actions in these applications Capture must run with admin privileges.
  • Capture supports a maximum of two monitors.
  • 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 the Capture.
  • 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.
  • 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.
  • 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).