Mini-Patches

[MikeHiggs]

​Keeping up-to-date with the latest version is Blue Prism is sensible. However, this does cost time, money and effort on enterprises. Being able to apply patches over existing installations would be beneficial.

For instance, the with Google Chrome's frequent release pattern it would be great to apply a patch that accommodates the changes to allow integration rather than going through the full upgrade process.

[Anonymous]

​This would be great!

[VladimirPerić]

In my opinion, the Chrome plugin should be decoupled from the BP release, in such a way that a new Chrome version requires an update of the plugin (which can be distributed and managed independently) and not the whole BP platform.

[AmyTsaousi]

Hi Mike,

Thanks so much for submitting your idea! We are moving it into the Under Consideration status while we route the idea through our internal review process. 

We will update you as your idea moves along the lifecycle.

Thank you!

Amy

[robert.nicklin]

Hello @MikeHiggs,

Thanks for taking the time to raise an idea.

We've taken this feedback into consideration when developing our the Blue Prism Next Generation product set so that updates made to components within are smaller and more frequent. We currently release a new version of our on-premise components (the Design Studio and Digital Worker) approximately every two weeks.

While this is the case for Next Gen, we do not currently plan to change the release and patch cadence for our Blue Prism Enterprise or other on-prem products (i.e. Hub, Desktop, etc.). Based on this update, can you confirm whether you'd like to see this idea marked as "Not Planned" or whether this should be associated to our Next Gen product set and marked as "Delivered"?

I'm going to mark this idea as Needs More Info awaiting your feedback.

Regards,

Rob