Best-practice guidance for automating any application in a Production environment is to implement version control (to include any browsers being automated). In a stable PROD environment, it's important that underlying software being automated is not changed without thorough testing first -- auto-updates of browsers in PROD should be disabled to ensure automations continue working as originally designed and modeled for a particular browser version. Before updating to the latest version in PROD, testing your existing browser-based automations designed against the old browser version in a lower testing environment against the new browser version is strongly recommended to ensure they'll continue to work as expected, or to catch and troubleshoot any issues found in the Processes before they can cause service interruptions in PROD.
As a general example, you wouldn't want to update versions of Outlook or Excel in a live Production environment without thorough testing of the new/updated software with existing Process automations in a lower environment first to ensure they work according to your business requirements and without error.
Just as well, our Product QA teams require some lead time before the latest versions of browsers can be tested and certified as supported for use with Blue Prism, then noted as such in our browser compatibility matrix documentation. Preventing auto-updates to the latest version ensures you'll remain on a version of the browser supported for use with BPE until the newer versions can be evaluated.
Some relevant Knowledge Base documentation on this topic:
For your proposed plan, it should be noted that there can be differences in the browsers introduced between the beta channel versions and stable release versions of these browsers that could be unaccounted for.
With regard to your internal security team, implementing version control of applications in Production environments typically requires exceptions. By nature, a secured PROD environment accounts for the lack of human users - rather it's restricted to digital workers repeating the same programmed tasks - so the security risks of remaining on an older/stable version are negligible as potential vulnerabilities are not exploitable.
