Hi All,
I am one of many users on data teams who use Alteryx at my company. The team I am on consists of five users, down from six. We have fifty-plus workflows published and running in our team collection.
The user we recently lost published many of our workflows. Now we have to manage updates to them all. To do this I've documented ten steps to make these changes and most of those are simply to take over another user's workflow. It would be about three otherwise. Doing the math, this is over 500 steps to make relatively simple updates (updating a server path in one tool for each). This should be, at the worst, 150 total. We could even devise a plan to automate this update and make it even easier/faster, but the additional server steps cannot be addressed by us.
We want to ensure that others who can access our workflows and possibly edit them if we're not available. We do not want to use the current process which involves
- Opening from server in Designer
- Writing down current refresh schedule
- Change / test locally
- Delete the existing schedule
- Asking IT to delete existing version
- Saving the updated workflow to the server
- Adding to the collection
- Testing/validation on server
- Re-Scheduling
- Adding the schedule
This should be as easy as or simpler than:
- Open from server
- Change / test
- Save to server
- Test/validate
All of our other applications follow the second, shorter path, sometime enabled by using a service account what all members can publish with.
How do we do this?
Thanks