Alteryx Server

Share your Server product ideas - we're listening!

Lifecycle of assets

each canvas in our environment goes through initial dev; then a testing phase; then into production usage after completing testing & peer review.

 

Currently the server environment has no concept of progression or promotion so we have to set up our own Dev; UAT; and Prod gallery & server - this really is very clunky because assets have to be manually copied across.

 

What would be more effective is:

- Allow a single asset to have a lifecycle (like you do in GIT) - so that it can go through dev and testing as a branch of the main code

- Once ready - user then changes the lifecycle type to "testing" or "UAT" and pushes it to users

- Once signed off, the user then promotes this to a production flow, and it replaces the current production version

 

There are a few areas where we'd need to do some thinking (dependancy tracking; branching; changing connection details as you promote so that you can hit the prod data stores etc) - but fundamentally this would go a VERY long way towards eliminating much of the admin involved in running the gallery.

3 Comments
Status changed to: Inactive
 

The status of this idea has been changed to 'Inactive'. This status indicates that:

 

1. The idea has not had activity in the form of likes or comments in over a year.

2. The idea has not reached ten likes.

3. The idea is still in the 'New Idea' status. 

 

However, this doesn't mean your idea won't be implemented! The Community can still like and comment on this idea. With enough renewed interest, this idea can be brought back into the 'New Idea' status. 

 

Thank you for contributing to the Alteryx Community and the Alteryx Product Idea Boards!

12 - Quasar
12 - Quasar

Enterprise life-cycle management would be a very helpful addition for larger organizations that leverage Alteryx server and want to use it in a way that fits with best practices.