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
Don't forget to submit your entry for the Excellence Awards by October 30! | Need more information about the program? Check out the blog here

Featured Ideas

So - one of the biggest challenges that we have with the MongoDB used by Alteryx Server is that we continually have issues with locking (where our admins have to go in and undo locks)

Additionally - the current implementation of MongoDB connectivity does not support full Kerberos authentication which means that we're on a non-compliant install (which in a large enterprise is an uncomfortable place).

 

Given that a very large amount of what the server does is transactional - it would make sense to have an option to use a large-scale SQL server instead of using Mongo.   For large enterprise customers, there must be flexibility to allow the databases that they have large supported instances of (my strong preference would be MS SQL 2016).

 

MS SQL natively supports XML so all the canvasses can be stored in native format.   Additionally, MS SQL allows very fast query across XML, and given the clustering and reporting capabilities in MS SQL, this would dramatically increase our ability to self-manage our infra.

 

Given that Alteryx is looking more and more at large Enterprise customers - a move to a large-scale clustered SQL env as the back-end would be a very positive move.

 

NOTE: as we consider DB options for a SQL backend - please consider your large-scale enterprise customers.   For example - MS SQL or Oracle or DB2 are all much more prevalent in enterprises than databases like Postgres - so it's important to focus on the enterprise support for the DB that you choose.

 

@Deeksha @avinashbonu @revathi @BenBu

 

We have a usecase where we want to check how often a workflow runs via the API so we can automate the consumption reporting we do internally. Right now the API only reads out workflows that were scheduled using said API. That doesn't make a whole lot of sense. Enabling it to also read out all the other workflows would really make this a powerful feature for us and I suspect others.

So, .YXI files are great, they allow a much simpler installation process of macros from the Gallery to your local machine and server. 

 

However one problem; they are not supported to be hosted on the Alteryx Gallery. This means that in order to share .yxi files they have to be hosted on some other drive and then you have to have a workflow in the alteryx gallery which provides users with the download link.

 

This makes that clean process a bit less clean, and it also causes problems with big customers who cannot whitelist these share drives for which the .yxi files are hosted. I myself have had about 20 emails from one global consulting firm in the US requesting access to a macro, I can't link them to the content as they are blocked, and therefor I have to email them individually. 

 

It's a tad tedious and ruins the 'install experience'.

 

If you don't know what I'm talking about you can follow my colleagues (Peter Gamble-Beresfords) blog here:

 

https://www.theinformationlab.co.uk/2017/10/05/create-share-alteryx-tool-installer-yxi-file/

 

What I'm asking for is simple, support for .yxi files in the Alteryx gallery, in the same way you do with macros.

 

Ben

Hi,

 

We have more than 100 workflows scheduled in different intervals for a day. Inorder to monitor this we have to manually check in the workflow results if the workflow ran successfully or not. 

 

Say a workflow is scheduled every 30mins then we have to check this 48times in a day manually in the Gallery results if it ran successfully or not.

Similarly we will have N number of workflows scheduled with different intervals.

 

We feel its too time consuming to manually verify this.

It will be good if there is a notification when there is a failure in the run, so we can check it only then rather than checking it every 30mins.

Password is required to execute any command on LLS. Last time we forgot the password, only way to retrieve it was to reinstall the LLS ! 

A command to reset password in LLS should do.

 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

When we create a shared macro on the Gallery, the desire is that we are able to:

- publish this down to users simply and seamlessly

- Allow them to use these assets in their canvasses

- Allow them to simply update to the latest version of the asset on an existing canvas.

 

Unfortunately - right now the only way to distribute shared macros is to create a shared folder; and the only way to manage version upgrades of a shared macro is to manually find every single usage and manually upgrade.

 

 

Hi

 

It will be great to make visibility of workflow execution results to other users in same subscription.

 

As of now, only schedules are visible to all users in a subscription, but not the workflow execution results executed by a user to other users in same subscription. 

 

This will avoid duplicate execution of same workflow by multiple user in a team as it will provide option to cross check the execution results by other users, if executed already, before execution of same workflow.

 

Regards

Haribabu Muppaneni

Right now, if you are using Windows Authentication, you can map AD group and users on the Permissions and Collections tab.  But for some reason, you can't use AD groups on the Data Connections tab.  Most of our databases are already secured by in-house AD groups in which you have to be a member in order to access that database.  Instead of managing a 2nd, most likely duplicate, list of users in the Data Connections tab I would like to be able to map the pre-existing AD group to that data connection.  That also means I don't have to service access requests.  If someone wants access to a database, they talk to the database owners, get added to the group and then they automatically can pull that data into Alteryx.

I work at a large organization where Security and Privacy are of utmost importance. The ideology that we need to follow is Least Privilege and Need to Know.

 

We (Curators) do not want all the Artisans to publish workflows to Home Page, either knowingly or unknowingly. We however do want to allow a few power users to publish their work in Home Page, but currently the Gallery does not provide the ability to pick and choose who can share workflows publicly. We are educating users to not share any contents publicly, but as we scale up, it will be difficult to manage and govern this.

 

I'm suggesting to implement a global Yes/No feature that will Enable/Disable Artisans to publish contents in Home Page (just like the way we have for Jobs/Scheduling feature). Further, in Users section, Edit User setting needs to have a Yes/No button that will allow Curators to let certain Artisans place workflows in My Company's Gallery.

 

Organizations that never want any workflow to be shared publicly can disable this feature using global Yes/No button. Organizations (like the one I work at) that want to enable this only for certain Artisans, can set the Global Yes/No to No, and then in Users tab, they can pick and choose the Users that need this functionality (which will override the global default). Finally Organizations that do not really care about this functionality can just set the global setting to Yes.

 

Hoping other organizations find value in this functionality as well. Thanks.

The ability to select a workflow or app within the Gallery web interface and change its name. This would maintain its historical run data, version control revisions, placement in collections, etc. 

 

Use case: As a workflow or app continues to be developed over time, the name may need a revision to continue reflecting the workflow's function. 

 

Best regards,

Ryan

I love the gallery data connection feature - we're going through some big systems architecture changes, resulting in new locations for many datasets. Having a single place in the Gallery Admin area to update connection information works beautifully.

 

We're running into issues with the gallery-hosted data connections when trying to run some apps on our private gallery though. The trouble comes up when the gallery-hosted data connection appears inside a macro that's part of an app. We get an "Unable to translate alias" error when trying to run these types of apps.

 

If we have an app using gallery-hosted data connections that are outside of a macro, the gallery is able to resolve the connection alias fine and work properly. The issue only appears when the gallery data connection is part of a macro used inside an app.

 

We use macros a lot in our app development because it allows us to use standard methods for accomplishing common tasks. Using macros also enables us to set up automated testing workflows to make sure our processes produce expected results. As it is, we're unable to take full advantage of the gallery-hosted data connections because they don't work within macros, and instead have to continue using hardcoded connection strings. These are a bigger maintenance burden as our underlying systems evolve and are updated.

Hello,

We use external corporate scheduler and we would like to start scheduling Alteryx workflows in this way. However, collections don't have API which would simplify our way of running workflows which we are shared by the users. Are you planning to enable such feature?

 

Best,

Piotr Zawistowski

The shared data connections from the Gallery have been very helpful in centralizing data connection information between desktop users and their workflows when saved to the Gallery. The In-DB tools currently cannot take advantage of the Gallery Data Connections and require a completely separate setup that is both confusing and adds additional connection management work for creation/password changes. 

 

It would be a great enhancement to Alteryx if all connections for the different types of tools could be centrally managed from the shared Data Connections manager found in the Gallery.

 

Best regards,

Ryan

My company uses R Shiny and maybe in the future Python Dash to create multiple analytic apps, dashboards, etc for multiple people to run across our company. One thing that would be nice to to have these R Shiny workflows run off of the Alteryx Server as that would allow us to use Alteryx Server to keep permissions and ease of use.

 

I propose an update to the Alteryx Server that would allow for R Shiny apps to be run in the Alteryx Server with all functionality of custom R interactive plots, etc etc just like what you'd see in one hosted on a R Shiny Server.

 

The benefits of this would allow for my company to only have to manage one server instance (Alteryx) to run all of this. Since R/Python is allowed/used in Alteryx workflows already, can you add the ability to visualize R Shiny code/plots/interactions/etc within Alteryx Server itself?

The only reference I can find to this idea is here : https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Share-Results-in-a-Collection/m-p/231 .  It references that the feature of "sharing workflow results" was "on the Roadmap" in 2014.  I did some searching through the current Ideas page and cannot find anything.  I also reviewed the release notes since Alteryx 10.5 and cannot see that this was added.

A user approached me today with a problem of "Many people need access to the results of this data, and I want everyone to be able to see all the results".  While you could potentially email these results to a specified user set, that would require maintaining both a collection and an email tool in the job, and could potentially cause notification fatigue if users only care when they go to the Alteryx Gallery.  Similarly, results could be saved to a networked location, but that would require a user to go to two locations in order to find this information.

As such, having a toggle that allows users with permission to view a workflow, to also see the results of any/all users, would be huge. 

Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful. 

 

Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline.  I’ll share both files soon. 

 

Here are the top 5 features for the Scheduler.

 

  1. Workflow priority ranking. When two or more workflows are scheduled to run at the same time, ‘priority’ sets the order of execution. Priority is set at the time of scheduling the workflow. Values range from 1 to 100. If a priority is not set the default is 50. The ‘priority’ field can be read from Mongo db. 

 

Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field. 

 

  1. Restrict which controller and workers a specific workflow can run on. Default is to run on all servers. At the time of scheduling a workflow can designated to restrict which server to execute on. This creates a field called ‘restrict’ which server it cannot execute on. 

 

Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning.  Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows. 

 

  1. Set sequence of successfully completed workflows. 

FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.

 

Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db. 

 

  1. If a workflow fails you can set the number of attempts to run successfully. Report attempts greater than 1 in a new field called ‘attempts’ that can be read from the Mongo db. 

 

Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx. 

 

  1. If a workflow runs more than X minutes the scheduler kills the workflow and reports a workflow error with a unique code called ‘execution-limit’.  This code can be read in the mongo db. The defaut is 90 minutes and can be set to any number of minutes. Each workflow can have it’s own limit. 

 

Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows. 

It would be helpful to have a central Logging tool for large & complex environments.

 

This would be useful to allow teams to have a central way of logging data transformation errors by error-type; severity; alteryx Canvas; etc.

Right now, there's a message tool, but this doesn't provide a way to create well structured central logging across a team; especially once deployed to a server environment.

 

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

It would be nice to be able to change the Gallery URL from:

to:

The reason being to make it easier for end users to find the server/content.

 

Original forum post here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Changing-the-Gallery-URL-on-Alteryx-S...

Many people maintain valuable information in Excel files, and many organizations, like ours, also use SharePoint to store and share structured and unstructured information. We see most user-generated and maintained data in Excel files in SharePoint document libraries, and one of the great benefits of Alteryx is the ability to join that Excel data with other data sources.  Unfortunately, the v11.0 Scheduler cannot resolve the UNC-style ( \\server@SSL\DavWWWRoot\site-name\document-library\filename ) addresses, so workflows that access this valuable SharePoint Excel data must be run manually. The SharePoint List Input tool can read the list-style metadata for Document Library files, but does not access the file content.

The Scheduler should be enhanced so that scheduled workflows can read Excel data stored in SharePoint Document Libraries. 

Allow to create custom user security groups server .

Sales
User1
User2
Studio1


Supply chain
User3
User 4
Studio3
Studio1
......
Top Liked Authors