Alteryx Server Ideas

It would be great if i as a developer could create a DB alias connection and for it then to be available to other developers and distributed via the server.

Collaborative working like the above does seem rather limited at the moment.

It might be helpful to be able to use an API to call and pass parameters to/from an Alteryx App or Workflow on an Alteryx Server.  Then a user could use a  browser or another application to call an Alteryx app/workflow.

As a system admin, I need a simple, reliable way to back up the Alteryx Server without shutting it down first. A hot-backup (and restore) utility that includes a consistent copy of MongoDB plus any other server config files would allow me to do this.

It would be great if the admin could change some default settings on the Alteryx Gallery page. For example, where we have the list of apps, show Detail view and sort by App name ascending by default.

 

Allow the artisan to turn off the ability of a member to download app results.  Some of the information is highly confidential, and we don't want them to be able to easily print out a list of this information and have that list "floating around".  Or take sensitive client data with them to another job if they leave us and use that to profit their new employer.

When replacing an app in the gallery, it appears that you always see the original upload date (which is good to have), and then simply a version number.  It would be great if you could add an additoinal field that shows the most recent replace date.  That way you would know that "SampleApp v4" is the 4th replacment, and that 4th replacement happened on date mm/dd/yyyy.  Also, while it's replacing, there is no indication that it is doing the replace.  An hour glass or some indicator telling you to sit tight would be nice.

When a process is running in foreground, the GUI does an excellent job of giving feedback to the user as to which "step" the job is running and how much data is processing through the active tools.  When that same job is scheduled, the amount of information is limited to when the job began execution.

If a tool was able to give checkpoint status out to the user, we could better monitor the progress of scheduled jobs.  The visibility to the job is most important for long running jobs.  We've unfortunately had instances where we have had to cancel jobs and to restart them not knowing how close or how far from finishing they were.

Thanks for your consideration,

Mark

Analytics Gallery needs the ability to save my question choices - so I don't need to re enter them every time I run the app.