This would help reduce the number of Environment Variables and help collapse / consolidate numerous environment variables into one single Environment Variable name which makes management / use of these a lot easier/efficient.
@EmersonF we have implemented this approach in the past however from a maintenance perspective it doesn't make sense for our production support folks to update 100+ virtualized bot VMs sitting in the cloud on what I call a 'configuration file' for a multi-bot process when the current environment variable functionality can be centrally managed natively in the BP tool especially if there are security constraints to pushing out files and/or accessing them from a network drive
