Blue Prisms reliance on session persistence should be changed in future versions of the product as currently we are facing uneven load balancing with this.
Interesting idea request. Have you got a suggestion of how that might work?
I think the current requirement for Persistance of the VDI has existed since v2 of the product at least (many years). My non-techie understanding is that persistance is required so that the digital worker is available to receive work requests from the application server at a known address for that robot (so we know that robot has the permissions and system access to work the process you have scheduled).
How would an external application like Blue Prism send a command to a robot in your estate that does not persist when the command is sent? Bearing in mind BP customers use every imaginable VDI access tool and infastructure platform so your solution would have to work for every platform tech and tool out there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
