Generally, both are perfectly capable of achieving most requirements, however, from my (rather limited) experience I’ve noticed the following issues in Blue Prism:
- Iterating through collections in excess of 2000 records caused System.OutOfMemoryExceptions and demanded 3+ hours to process.
This resulted in us having to utilise a code block, achieving the same thing, but in a fraction of the time and with a minimal resource footprint. - RDP usage causes serious issues when using BP, though this is somewhat the case in UIPath I believe.
- Selectors are more difficult to use and feel more limited.
In addition, there have been numerous instances wherein the “spy” feature crashes.
Although I prefer UIPath, Blue Prism is far superior from a debugging perspective, allowing you to view all assigned data during runtime and step out of, into and over components flawlessly.
While these features exist in UIPath, I find they frequently fail/crash in medium/large projects.
With that said, this is entirely my opinion and my experience with Blue Prism is limited to one project.