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
It's the most wonderful time of the year - Santalytics 2020 is here! This year, Santa's workshop needs the help of the Alteryx Community to help get back on track, so head over to the Group Hub for all the info to get started!

Featured Ideas

I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.

 

SQL Server Management Studio

mackedet_0-1590532280855.png

Schedules on Alteryx Gallery/Server

mackedet_1-1590532639645.png

 

 

I've seen various solutions/workarounds but this seems to be a table-stakes ask?  When scheduling a workflow I should be able to specify which parameter values to run with.  Just two of many use case examples - 

Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business

Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials.  When their credentials change all they would have to do is update the schedule parameters

 

(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)

6-25-2020 5-39-35 PM.png

Situation:

As your analytics work grows - you find yourself using the power of Alteryx to create shared macros.    These act as an accelerator for a team because one team member can us a reusable solution created by another team member.   For example - many teams need to get data out of JIRA (or some other system) so you create a connector that everyone can use.

 

That's going well - and now you have 20 teams all publishing canvasses to your server (possibly 100s of canvasses running in production) which make use of your JIRA connector - all good so-far!

 

Problem:

BUT THEN - you discover an issue with the JIRA connector and you need to fix it and publish a new version!

 

It's at this point that you realise that the canvasses on your server which use your JIRA connector are NOT pointing to it, but they have made a copy and included this inside their canvas.   So when you fix the problem with the JIRA connector - no-one gets the fix!

 

This is because every application uploaded to the server is a yxzp file, which zips up a COPY of all the shared macros and uses this in an isolated way.

So - in order to get the new JIRA connector (with the defect repaired) used instead of the old one you now need to:

- Download EVERY canvas on your server

- Unpack them all to expose the sub-macros being used

- Inspect them to see if they are actually an instance of the JIRA Macro

- Make a list of the owner and application IDs

- reach out by e-mail or phone to every one of these folk to ask them to republish their Alteryx workflow with your new version of the JIRA connector.

 

 

Proposal:

Please can we revisit this - we really do need the power of shared macros - and we also need the ability to fix and manage these like a product over time.   This will have an impact on the engine (hence copying @AdamR ) 

 

Desired end-state:

- When you build a canvas using a shared macro - it doesn't store the macro itself, but rather a reference to the version on the server - unless you explicitly decide to break the connection and take a copy.

- When you check this canvas into the server - your application / yxzp does NOT include a copy of the shared macro - instead it has a reference link

- this means that Alteryx Server can now track which canvasses use this shared macro very simply

- When I fix this shared macro - I can then do an in-place update; or if the interface is not the same (i.e. different inputs or outputs) then this has to be a new version and the users will stay pointing to version 1.

 

This is how shared assets are managed in a micro-service world, which is the way that all of our architecture is going - and it seems important that we build this thinking into the Alteryx infrastructure too.

 

 

 

 

 

 

 

@AdamR ; @Treyson ; @SteveA @DerekK ; @BlytheE 

I am noticing what I think it's a big gap in terms of turnover and job changes.  Even though you can add workflows to a Collection for development and update purposes. Only the original owner/publisher can see the version history for a workflow. At least that appears to be the case in 2020.1

 

Is there any discussion for the road map to include a way to transfer the ownership of a workflow from one user to another? this would alleviate the need to publish a brand new version and then reset all the scheduling. 

Submitting this idea based on the Case #00361430.
 

We are trying to do alteryx workflow chaining based on workflows available in alteryx gallery, but this option is not currently available in alteryx right now and we are raising this idea to enable this feature in upcoming release or existing version patches.

 

Currently couple of methods available; saving the workflow in network share drive and chain the alteryx workflow based on events or run another analytical app on success.

The disadvantage of these methods are,

 

1. We cannot have version history maintained for the workflows in network share drive.

2. We cannot able to run a specific workflow in chaining as the workflows are packaged together.

My team currently uses the API to call a large number of workflows via a Python based scheduler process.  We use this currently by having ~10 users in a single subscription (Private Studio).  

 

All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.  

 

From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.  

 

Are there plans to adjust the API endpoints in the future to better account for this?

 

Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.

 

Thanks

Wanted to grab some attention here regarding the Alteryx gallery search engine (which also bleeds over into searching for schedules and jobs when troubleshooting). 

 

Since a picture is worth a thousand words, I'm pasting two pictures (one attachment) of searching our gallery for the word "Contour" and the word "Signal". Both of these words are in the title of a single workflow - when I search for the word "Contour", the workflow pops up. When I use the first word in the workflow, which is "Signal", it doesn't pop up. 

 

I appreciate all that Alteryx does, but I wouldn't think this should be a difficult issue to fix, and I would imagine there are other frustrations with the functionality here. 

  • Gallery

 

It would be good to have these table headers sizable, so that it can be expanded to display complete Name (and other fields).

 

nanda419_1-1578508155151.png

I have three team members all in the same private studio. We can see each others' workflows. However, when looking at a workflow that another team member has published to the gallery, it looks like:

  1. The workflow has never been run
  2. The workflow is not scheduled to run

This is a massive impediment to collaboration because my team handles ETL for most of the company. If a user complains that their data isn't up to date, whoever receives that support ticket needs to be able to see if the workflow is actually running and whether it was successful or had an error during the last run.

Preventing a team from seeing this for each others' workflow schedules and results means that the only person who can deal with an issue is the person who originally made the workflow. Which makes the idea of a shared private studio wholly pointless as we may as well be operating in different universes.

 

Please create a studio-level setting where all members of a studio can see all schedules and results of all workflows in that studio.

  • Gallery

Currently the server diagnostics (http://localhost/gallery/admin/#!diagnosticscovers a narrow time window (from what I can see - only the last few hours)

 

Current Server Window.jpg

 

.... and if you attempt to zoom out or pan to see a broader time window - the graph gets smaller, but the data does not grow to fill the remaining space

 

zoomAndPan.jpg

 

Please could we request 2 changes:

a) add a time axis on the bottom of this chart so that the user can understand the time dimension 

b) Increase the time available for analytics to an arbitrarily broad set of data (which the admin can configure as a server setup parameter - retention period).   For us - we'd want to keep at least 3 months of data, and be able to view this analytically.

 

Thank you 

Sean

 

 

There is no good way to get server user credentials into a workflow without asking them for it in an App interface.  It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.

  • Gallery

As the Server Admin I'd like to have the ability to view ALL "Workflow Results" for all Subscriptions.This will give the highest level admin the ability to monitor all schedules (on the entire server instance) and monitor if they are unable to complete successfully (example- unable to allocate memory) and any other errors are occurring. 

 

Knowing this information will help the server administrator understand if there are issues with the server itself (e.g. if we need more workers or to simply adjust actual server system settings..etc..)

 

 

 

 

When an artisan moves positions (within or external) away from their current responsibilities, their collections and workflows should be able to be transferred via an administrator to another user.

  • Gallery

We have several clients that operate in a Multi-Forest environment due to mergers and acquisitions.  Currently with Alteryx Server the only option we can offer them is to use Built-In authentication.  A lot of corporate and particularly finance institutions prefer a single sign on approach and utilise Windows authentication to do this.

 

Would it be possible to add support for Multi-Forest organisations into Server to support organisations going through mergers and acquisitions?

 

This would really benefit us in selling Server in to organisations with complex structures and reduce friction in publishing or preparing workflows.

2019.4+ Server now prompts users to select an Encoding Type when downloading a csv on the gallery. Unfortunately there is no way to disable the prompt of which encoding option to utilize or an ability to select a system default. Please provide these server options as this is causing confusion across departments. 

 

.csv output.csv output

.yxdb output, csv format.yxdb output, csv format

(many users like the preview provided by yxdb but want excel download)

 

During development in Designer, when the workflow is configured to output to csv it already has the encoding configured, please provide the option to at least default this at output on the gallery:

.csv config.csv config

 

The only alternative at this time is to republish all workbooks configured to output .csv or .yxdb to be .xlsx. This is not ideal.

 

Note: Scheduled jobs are not affected - I tested a scheduled run and csv files were successfully written out to a file share on the server. Content format appears to not be impacted. 

 

Thanks!

  • Gallery

Now, gallery does not support AD group , need to setup user one by one.

If gallery support AD group synchronization, it is more convenient for gallery admin to manage large number of users.

By assigning AD users to AD group, it will reduce the maintenance task of gallery admin, since gallery admin don't need to grant rights in the gallery directly. 

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

 

  • Gallery

The Save to Gallery window does not resize. When I try to Save my Workflow to my Gallery and Manage Workflow assets, I can not widen that window to see the full path to my assets.

This makes it very hard when you have many assets to know if they need to be included or not with the promotion. It may take two or three attempts guessing what asset is what to get the correct combination to make my App run correctly.

 

Assets.png

 

It would be nice to be able to widen this window much like we can with the Workflow dependencies window.

  • Gallery

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

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

  • Gallery