In the current Blue Prism architecture, each resource PC will try to establish a connection to every other resource PC. This communication is not needed for standard Blue Prism functionality (scheduling, ad-hoc process runs) and is used only for some feature (eg. resource pools). However, this communication creates spurious network traffic and most importantly raises flags with security teams monitoring network chatter. As the communication is not strictly necessary, it would be useful to be able to disable it completely. I assume there would also be a small, but measurable performance increase across the platform. Note: I do not wish to disable interactive client -> resource PC connections, as these are useful in case the RPA controller needs to "drag 'n' drop" processess.
... View more