Can vault secrets be assigned to global variables

[dushyant.kumar2]

Global variables under Variables seems to be accepting only static(hard coded) values. However, when deploying bot on other self hosted machines some of these values need to be dynamic. Even the static values are not preferred to be hard coded.
I am right now doing it by creating task and keywords that read vault and can pass down values into other different tasks as arguments. but when there are lots of tasks in a bot, it kinda become messy.
Is there a way that Vault secrets can be assigned directly to global variables?

[raivo]

There is also option in Control Room to use environment variables for process which can be used directly

[dushyant.kumar2]

@raivo

o use environment variables for process which can be us

Thank you, it helps to simplify few things.
However it seems more like Process specific work around, will have to do it in all processes independently. I am looking for something that can be used globally in all processes in a workspace and also dont have to pass it again and again into arguments in code. I am not even sure if it is possible just checking about options. in simple words if vault values can be assigned to global variables that solves the issue.

thanks again for checking.

[jippo]

You have to look these thru “security lens”. Using secrets from Vault should be very intentional action when building processes. Making them always available via global variables would be security risk.

Or maybe I misunderstood intention of global variables.

[dushyant.kumar2]

Thanks Jippo.

so I am not considering saving credentials in global variable. but some values that are used in all bots. for example SMTP server details to send emails, COE email distribution lists for failure emails in all bots, root output directory for output files for all bots etc.

what we are looking for is somewhat similar to Assets in UiPath orchestrator and global values in Automation Anywhere control room.

[raivo]

There is upcoming feature for that, no ETA yet. See also:

Store, Share data among different processes in a Workspace

We need to store a JSON object with more than 500 lines of data from one process, and have another process be able to read and update it as needed. However, we have a size limitation similar with Control Vault (if JSON object is big not updating to vault). Can you provide any input on how/where to store and update this variable’s value, and how to share it among different processes in a workspace? Thank you.