Hello Community!
Our company has a Gallery set up of 2 Servers our Alteryx developers access (UAT and Production). Within both of those, we have multiple workers, regionally based (Tokyo, Ireland, US, etc.).
We have been able to build logic for migrating between the two environments that change the more standard things like data connections and have helped our Alteryx developers with a framework to make that happen if they have specific things that may change between UAT and Production (table names, file paths, schemas, etc.). This isn't always needed, but depending on naming conventions and their other processes we may need to make the workflow dynamic.
To do this, we have an environment variable set up on all our workers indicating if it is in UAT or Production. The developer then can build a pretty simple lookup table that filters down to the environment it needs using a Formula Tool and the GetEnvironmentVariable() function. Something like:
| Environment | Shema | Output File Path |
| UAT | schema_uat | //FolderA/FolderB/uat/file.xslx |
| PROD | schema_prod | //FolderA/FolderB/prod/file.xslx |
That being said, we are now getting requests for a third (sometimes fourth) environment, usually to fit other parts of their group's lifecycle management. Currently trying to figure out a way we can support this. For example, they may have a Dev and UAT subscription and/or collection but the developers would like to build their workflows in a way that seamlessly migrate between Dev, UAT, and Production.
Since we don't have a Dev server or worker to use, the Environment Variable solution above isn't going to work. We also tried using Interface tools to specify it, but not a great solution since someone could just run a UAT workflow in Dev or vice versa.
Any suggestions on how we may be able to get a workflow to dynamically change based off some sort of inherited tag, not passed in by the user running the workflow?
