This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We have several workflows that call other workflows (i.e. via the Conditional Runner macro) but are running into some versioning challenges since we moved to storing all of our workflows in our gallery. When I publish a workflow that references another workflow, I can bundle it up with the workflow when I save it, but then Alteryx places that workflow into the /externals directory, which is obvioulsy not the same as the workflow that we've saved to our gallery. An example:
I have two workflows in our gallery...one that generates a TDE and one that calls that one if certain file availability and time conditions are met. The "master" version of each is in the gallery, which is what we want...
...but when I load or save the Sales Analytics workflow in Designer, I have to bundle the TDE workflow with the main workflow in order for it to run from Gallery. But now I've created a disconnected version of the TDE workflow and if I forget to update it when I update the version in the Gallery, I'll be running the wrong version. I know I could store these workflows in a network directory, but that seems to defeat the purpose of the Gallery.
If I'm not missing something insanely obvious, I think this would be a very important feature enhancement, namely the ability to pull in a Gallery workflow into another workflow.