Central management of 'start a personal runtime resource'

[Walter.Koller]

Although the setting 'start a personal runtime resource on this machine when users sign in to Blue Prism' affects the whole environment and I assume it is rarely used (why would someone start BP to make it act as a runtime resource that then takes over the workplace?! why not start the process directly in Studio or send it to a dedicated runtime resource?!).

By default (at least in 6.9 not sure about 7.3.x yet) each user will register his workplace as possible runtime resource, mixing it with dedicated runtime resources and needs to be removed manually.  Having a private runtime resource start when starting BP UI may also cause issues with network ports and other system resources. 

Currently the only option to deactivate the 'start a personal runtime resource' is to login into BP and change it manually, on each workplace/resource, which can only be done with BP admin rights, so users are not even able to change settings for their own workplace.

Some ideas on how to improve the situation:

1. make the 'personal runtime resource' disabled by default 
2. make it a system wide setting
3. allow users to change this setting for their own workplace
4. have this setting easily changeable in an automated way. eg via CLI, config file (that can be amended during install process)
5. make it a centrally managed feature of a runtime resource/workplace similar to eg logging levels that can be changed in System\Resources\Management
6. any other possible idea that might help but is not listed here

[robert.nicklin]

Hi @Walter.Koller,

Thanks for taking the time to raise an idea.

I've reviewed the details and have no further questions for you, so I'm going to set this idea to a Reviewed status for now. Next steps will be to see how many votes this idea collects from the community to see whether this is an idea that has widespread appeal and should therefore be considered for future roadmap.

Regards,

Rob