It would be nice to be able to have some way to be able to create tokens that would be stored globally and to be able to be consumed by Workflow. So, that the end user would not necessarily have to go into a workflow and locate tokens, such as, email addresses, or repository paths, etc. In addition, multiple workflows could access the same global tokens so that if you were changing something that applied to multiple workflows, you wouldn't have to locate and modify them all individually. You could simply modify the Global token and it would automatically apply to all workflows that were using that token.
Discussion
Discussion
Feature Request: A method for saving global variables in Workflow that could be changed by the end user
Thanks for this request, I've passed it along to the workflow team for consideration in a future release.
In the meantime: one strategy that we've seen work well is to create a "Get Environment Variables" workflow, the purpose of which is to just output these global variables. Then anytime a workflow needs a global token, you just have it invoke your "Get Environment Variables" workflow instead of hardcoding the token in each workflow. Similarly, if you are in cloud, you might try using a decision table for this.
This is a cool idea. We do an absurd amount of document processing and it's very common for us to have more than one workflow sharing common variables like email content templates, email destinations, document paths, etc.
As a result, when something changes, I do sometimes find it challenging to remember every single process that will be affected and it would be fantastic if I could just change it in one place.
Usually what I end up doing is storing the value in a database and using a lookup so I can accomplish that, but it would be much easier if there was a global token-like system for the same purpose since using a lookup means I also need to use try-catch and everything just in case.