I just discovered, almost by chance, that UiPath Studio allows you to create global variables.
And my question is: What does it add if the arguments already exist?
Now it would be possible to create a project with several workflows and not have to be creating arguments, I simply create global variables and that’s it.
I don’t understand why after so many years UiPath has now created this possibility. In addition, it can lead to errors that I think are avoided with arguments.
Also, although in a more convoluted way, global variables could be created previously, but you have to know the method using enviroment.
Is there perhaps a use that I am not able to see that makes these variables very different from the arguments?
Because if so, it would be good to know it in order to apply it in my developments 
For most automations I consider a best practice the use of arguments instead of Global variables when using different workflows
There are specific use cases of global variables like the ones you can find in Attended Automation Framework to exchange values/states when executing this event-based automation
I recommend you to explore it
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.