The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

Starting with Windows Sever 2016 edition one could use Docker containers technology on windows environments. My idea is to dynamically convert Designer jobs/workflows  to Docker containers at runtime.

The Admin Gallery api needs to have the ability to get questions,execute jobs, get outputs. Currently I can only get questions, execute jobs and get outputs of my private gallery flows, I need to be able to do this for other Artisan flows without having to have their key/secret.

The WebDAV protocol isn't supported by the Alteryx Scheduler,  due to the security constraints associated with connecting to SharePoint.  This is a server side limitation that should be aligned with the ability of the desktop to preform the WebDAV action.  

*This is an idea from @riverotoledo_21 from the Portuguese Community*

 

  • How to bring user’s variables/information that we want to use within the workflow that will be published in the Analytic App in the Gallery (For example, I believe that all “non-sensitive” information from MongoDB related to the Gallery actual session should become variables)

We are looking for the ability to use Alteryx as PaaS in the Azure cloud similar to how Databricks is working on Azure. So servers spin up when demand shows up and then they spin down.  Where we are not on the hook for server patching etc., but instead, we lease processing power/time from Alteryx in the cloud on an as needed basis. The licensing model will also need to be a scalable to support this type of usage.

Hi there,

 

Please can we extend the support for MongoDB to include MongoDB Enterprise latest versions, and certify at latest version within 3 months of release (both with the connector components, and the server infra)?

 

Given the deep dependence that Alteryx server has on MongoDB, being current with the latest version is critical (since many enterprises have a policy of moving to the latest version within 6 months, and shutting off old after 12.

 

https://docs.mongodb.com/manual/release-notes/3.4/

https://docs.mongodb.com/manual/release-notes/3.2/

 

Mongo 3.2 has been out since Sept 2015, and my understanding is that Alteryx Server is not yet certified for 3.2 - so it may be worth skipping to 3.4 (released 11 Sept 2017).

 

Many thanks

Sean

 

Alteryx Server seems to natively support MicrosoftSQL and Oracle connections on Alteryx Server. It would be helpful to natively support (i.e., a non-ODBC connection) for Cloudera Hadoop as well.

One of our biggest areas of confusion for new users of our Gallery is the Download button. They often click it thinking that will give them their information right away. It would be great if the person didn't see that or the scheduler option if they were not an Artisan, since they can't use the workflow anyway. It would be even better if selecting the workflow took them straight into the question portion.

We have the need to bulk-add users, and to bring in their information (full name; location; etc) from Active directory.

 

Right now, adding users is a 1:1 process which is highly painful.

Desire is to be able to take a list of Kerberos IDs, and bulk add them as users - and then select a group of them and permission either for the gallery; or for designer licenses.

 

cc: @revathi @avinashbonu @Deeksha

I think it would be a great feature to include the performance tuning logs as an optional output in Alteryx Server. 

 - This would allow me the ability to leave performance logging turned on, so I could see what was happening during an automated scheduled run of the workflow. 

 

Performance Log :   <Link> (or attachment)

 

I would also like to see a tool (or tools) as optional outputs such as:

File(s) Generated:  

    <List of Files:    <Link to Files>    <Size of File>

 

These type of outputs would be greatly beneficial options instead of "This Workflow produced No Output"

 

Thanks for reading

Randy

 

Hi all,

 

i hopped onto Azure tonight to see if I could create an Alteryx server to start learning Alteryx server as a skill.    I was expecting the cost to be somewhere in the range of Microsoft SQL server on Azure, or Microsoft Power BI (a few dollars, but not more than $20 per month for limited usage).    I was fairly shocked by the price on offer (8k - 10k per month), with no option to price this by usage.

 

Could we work together to create options for people to stand up their own small Alteryx server like this for the purposes of learning - right now there is no way to learn Alteryx server unless you are actually an admin of a live server, which makes it impossible for people to learn this at home to build their skills (and impedes Alteryx building a base of skilled users in the market).

 

Happy to work with the team to help make this a reality.

 

cheers

Sean

As we continue to build Alteryx Workflows for the business, there is a continued need for an organizational structure for saving and storing Alteryx Workflows within the Alteryx Gallery. Organizing the workflow repository through a "folder hierarchy" will allow users to quickly navigate and find the appropriate workflow. Currently, the workflows are listed in alphabetical order and requires the user to remember the Alteryx Workflow name and click to the proper page. 

 

Any enhancements to the Alteryx Gallery organization structure would be greatly appreciated!

 

Thank you, 

 

KK

 

Currently, many of our most useful apps in the gallery utilises blocked tools (download tool, R tool etc). Every deployment or even minor updates to these apps require emailing the Alteryx Curator account for exception requests. This process is quite cumbersome, although the need for it is understandable. However, given that not a single app from us was ever rejected (and we submitted dozens of requests) , it would be great to have a process in place to apply for a permanent whitelisted status. This would give trusted app authors the ability to deploy apps with blocked tools without emailing the Curator. 

 

 

The search for replacing a workflow is poor (and I get that it is probably challenging to write on the back end) but as a result even if I type in the exact title of the workflow (aka copy and paste) Alteryx replace can't find it. Not only does this mean I have multiple workflows with the same name running around (loads of fun with lack of version control) but it also makes this entire thing more frustrating every time I update a workflow (as normally this also means the scheduling of said workflow breaks).

 

It would be awesome if instead of having to search by title for your workflow that you wish to replace with if you could instead use the URL where Alteryx Gallery put the workflow and then there wouldn't be any confusions about which workflow and you wouldn't have to type.

*This is an idea from @cneivam  from the Portuguese Community*

 

- Gallery in all supported languages

*This is an idea from @cneivam from the Portuguese Community*

 

  • Can’t use CReW macros in Server

Hello Alteryx Devs - 

 

So, I'm poking around the Atlerxy Gallery API stuff with an eye toward building a set of classes that can interact with workflows without exposing Gallery proper to the community at large.  That being said, I was a little dismayed to find that all interactions require inclusion of *user specific* API Keys and Secrets.  It can be dealt with, but ultimately it means that configuring a middleware tier between the real world and Alteryx server requires an additional hierarchical level; i.e., understanding which of the developers came up with workflow X and having *their* API Key / Secret attached at configuration time.  

 

Anyways, it might be easier to just have a global trusted key / (super) secret.  If you get that, you can execute a workflow.  

 

Maybe we have a special studio that people could clone to, and in this way, you'd only have to track a single key/secret outside.  

 

I mean, the existing system works OK for one offs, but if you wanted to have a (semi) modular system in place, dependence on understanding publishing entity specifics seems to muck things up for no discernible benefit.  Of course, maybe in some places there is benefit to this scheme (?), but it is causing me to craft some weird work arounds early in development, which gives me a sinking feeling.

 

Or am I doing it wrong? 

 

Thanks for listening. 

 

brian

I know that the documentation shows that you can setup a worker to a specific QoS so that it will only pick up work for a particular workflow or app, but there could be a greater use for it.

 

For example if the Admin could control what QoS means for each definition.

 

I.E. Application, vs a workflow that runs over an hour, vs in-database tools. Then it will allow the admins to self guide where the work is going.

 

Right now there is only three levels

 

  • Normal workflow execution: QOS = 0
  • Chained application execution: QOS = 4 (all apps in the chain aside from the last)
  • Workflow validation requests: QOS = 6

This was great for Alteryx public, but for private Galleries we need to distribute the work better than FIFO.

Right now we can set the limit of processes a worker can run and each worker will ping the controller when a slot is available so that it can assign a new process. However, this is not efficient and you can truly load balance because you don't know how busy that worker acutally is...

 

We need a way that might be simliar to how we do on DataStage GRID environment where the LSF platform balances that workload across the entire GRID.

The admin (aka curator) needs to be given more control. The admin should have greater control than the users of the system.

 

My organization is in the Healthcare industry and we have HIPAA laws to abide by when it comes to data. Not all users should be able to see all data. Developers should not have complete control over the data they publish.

 

Private studio

  • admin should be able to control if users can publish to Alteryx gallery (compliant issues occur when our organization's data is shared to outside users)
  • admin should be able to control if user can publish to public gallery (compliant issues occur when all users can all see and run workflows)
  • admin should be able to delete subscriptions and users

 

Collections

  • admin should be able to create collections so they can manage the collections and what users have access to (devs should not be able to give any user access to their workflows)
  • admin should be able to control if users can create new collections (again, compliance issues)
  • admin should be able to grant and remove download of workflow rights
  • admin should be able to delete connections

 

Get tips from Tableau as they have admin controls down with their permissions process.

Top Liked Authors