Alteryx Server Ideas

So there are freemium apps in the gallery and

server customers have their own apps published in their private galleries...

What if one want's to sell apps like in iOS app store,

Provide insights from the app as a service either prepetually, annually or monthly so that the locked apps can be used

• on a basis of pay per monthly subscription model or
• pay per transaction model etc.

possibly payments being handled over Alteryx Public Gallery.

Does the Alteryx roadmap include such a business model in the future?

Best

There needs to be a means for Server Admins to delete/clean up subscriptions and users from the system.

Ref: https://help.alteryx.com/server/11.0/admin/index.htm#Administration/Users.htm%3FTocPath%3DAdminister..., “To revoke a user's access to Gallery, deactivate their user account. You cannot delete a Gallery user's account.”

While testing with version 11.0, default permissions set to NO ACCESS, Security using Windows Active Directory, I gave the gallery URL to a random teammate to see what they could access.  While permissions prevented the individual from most activities, the server still created a USER and SUBSCRIPTION for the individual.  Once testing was completed, there was no means possible to clean up these entries., or at least to do more than set them to NO ACCESS.

For most enterprise applications, it is common practice to be able to purge a user account from a system if they are no longer a member of the company.

Sometimes when using someone else's Gallery App which has a long list of options to select from, I will hit Run before realizing that I haven't set all of the options.  Then, the App fails (obviously).

Rather than just getting a message that my app run failed on the Gallery, it would be nice to have a link then that automatically re-loads the previous options I had set so I would be able to see which option I didn't fill out properly.

Rather than schedule to put things on the 5th day or the 14th day of a month, we often want to schedule our flows to run on the 5th business day or the 14th business day. I know that the term 'business day' means different things in different parts of the world, but I think it would be a feature that many reporting-oriented departments would enjoy. Let people specify a formula or have a table to go off of for their definition of 'business day' and it should be easy to implement.

I would add a <scheduler> label to this but there isn't one.

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.

Can we have search option enabled in Gallery Admin > Jobs to filter on running jobs to specific ones or to check specific job schedules.

When looking at a Workflow in the Gallery there is no way to tell if it currently resides in a collection. As a suggestion, a good place to have this information would be in the header block of a workflow where the version information and number of times a workflow was run is stored.

In stead of having to create an event to notify me when workflows are failing, I would like to easily enable that option from gallery after scheduling a workflow.

Can we make the ability for a developer using Alteryx Designer and having a workflow using in-DB tools to pass along their credentials with the workflow when scheduling to run on Alteryx Server.  An individual user may have access to only certain tables in Teradata for example and the ODBC connection on Server may not have access to the same tables so we need to be able to pass along the encrypted credentials.  THanks!

Everyone on our team would benefit from having access to each other's workflows -- including workflow results and scheduling -- but publishing them to gallery where any user in the company can run it/ download it would present a security issue. Functionality that is not met with Collections. I found a similar idea, but not anything that encompasses the whole thing.

It would be of immense value to have a Team Gallery - something intermediate to the company gallery and the private collection. This would enable our team to have access to modify, publish, schedule workflows as a team.

While Alteryx is a self-service tool for the business there is a need for administrators to get a little more insight to the usage of the installation on the server. Each customer is forced to create their own monitoring tools. I understand NewRelic and Cloudwatch can easily be used but there is a need to split the admin view by organization departments since each dept needs their own resource utilization and workflow report. Logical split view reporting should be facilitated by the Alteryx server product.

It would be great to have an option to show intermediate output in gallery and allow user to modify that intermediate output before running the next step in a chained app environment.

This will come really handy in cleaning messy data which requires some manual input and user can complete their work form single gallery screen.

Currently the only way to achieve it is to build separate workflows/apps where first you have to download the messy data on your local drive and then upload it back via a separate workflow to complete the task.

We get a lot of comparisons with DataStage ETL and what Alteryx can do. DataStage has the capability to partition queries and run on multiple worker nodes to allow the execution to be more efficient and faster than if it ran on one worker. We want similar capability on Alteryx as our case study shows right now that Alteryx is 10X slower than a query ran on DataStage through the GRID.

When you enable SAML authentication for Alteryx Server it does allow Single Sign IN but it does not support Sign OUT. This means that after you close your browser the session remains active. If the browser is opened again and the Gallery page is loaded it will pick up the session that was activated before instead of creating a new session. At the very least a session time out limit should be added.

Currently, Alteryx Server has a setting for how many days to keep Results from scheduled workflows, which prevents your Results log from getting too large.

Unfortunately, this setting is universal to all workflows, regardless of schedule.  If you have monthly jobs sharing a server with jobs that run every 5 minutes (which we currently do), and you set your limit to 30 days, you get at most 1 result from monthly jobs, but 8,640 results from your 5-minute jobs!

A better option would be to keep the most recent X results from any schedule (where X is user-configurable).

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.

Hi,

As part of enterprise alteryx server deployments, would it be possible to remove alteryx server controller tokens and use asymmetric certificates (X509) instead?

Adrian

Please consider adding this feature to the Alteryx PRIVATE Galleries.  This is a feature of the Alteryx Gallery and would be useful for our clients too.

Thanks,

Mark

Hi All,

Is there any plan to create an automated way of publishing apps/workflows to the gallery. This has been a common painpoint for me on several different projects when I explain how manual of a process this is.

I'd imagine this could easily be solved by adding an additional API call to their library. Ideally, you'd be able to point the gallery to a shared folder with workflows you want to push (git repo functionality would even be better), and have it just move the .xml scripts to the server/mongoDB.

Best,

dK