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

It would be nice if the Gallery Admin could download the workflow from the workflow page within the UI, without having to run API calls or having to add himself temporarily to someone else's studio. 

I would like to be able to view all schedule results from all users in my Gallery.  Currently, I can see the "Workflow Results" for any schedules I create.  But I cannot see them for users unless they share them.  As admin, I want an option on the Gallery Admin screen just like there is on the Gallery user screen to see "Workflow Results" for every schedule that is in the Scheduler Database, regardless of who the user shared it with.

 

Currently, the only way to accomplish this is to go to Designer, View Schedules, connect to the Controller, and go to the Results tab.  This should be built into the Admin screen in the Gallery.

currently, there isn't any way to fully delete (safely) a user from the gallery. So if there is a previous client or previous employee in gallery, we cannot clean up the gallery settings - only "disable". It would be great to have a "trash can" symbol next to the users where we can remove them from the server and keep all of the users clean. 

I would suggest a service split to simplify maintenance actions in the Alteryx Server.

 

Split Alteryx Service into 5 services:

 

 Alteryx controller

  • Dependencies: Alteryx Database
  • Purpose: Controls job submissions
  • Meaning: The Alteryx controller Service stopped means neither the users or the scheduler can submit new jobs

Alteryx Database

  • Dependencies: N/A
  • Purpose: Database
  • Meaning: The Alteryx Database Service stopped means all the platform is down

Alteryx Gallery

  • Dependencies: Alteryx Database
  • Purpose: Controls the Web UI
  • Meaning: Alteryx Gallery Service stopped means the gallery web page is down

Alteryx Scheduler

  • Dependencies: Alteryx controller, Alteryx Database
  • Purpose: Controls the scheduled jobs
  • Meaning: The Alteryx Scheduler Service stopped means the users can still submit jobs manually but scheduled jobs wont be submited

Alteryx Worker

  • Dependencies: Alteryx controller, Alteryx Database (only applicable if the server where the Alteryx Worker Service is running the Alteryx controller)
  • Purpose: Executes the jobs
  • Meaning: The Alteryx Worker Service stopped means no job will be executed on the node

 

This service split will help perform some maintenance tasks and enables the Platform Administrators to shutdown the platform correctly shutting down the services in the correct order.


Usage Example 1 (Cold Backup):

  • Stop the controller so no more jobs can be submitted
  • Stop all the workers
  • After all the workers have stopped the Alteryx Database Service and the rest of the remaining services can be shutdown
  • Preform the Cold Backup
  • Start the services

Usage Example 2 (Changes in the worker configuration - By doing this the users will still have access to the gallery and their jobs):

  • Make changes in the worker configuration
  • Restart only the worker service

Usage Example 3 (Changes in the Gallery Page or Configurations):

  • Stop the Gallery Service
  • Make the changes
  • Start the Gallery Service

One of our Server customers has a need to disable all schedules temporarily across all worker nodes.  I do not see an easy way to do this unless we go into each worker's settings and disable from there, but this is not ideal.

 

The reason is for scheduled maintenance windows during a large upgrade or migration.  Currently stopping the Alteryx Service on each worker is time consuming.

 

Thank you! 

Hi there,

 

On the server product you have the ability to set up timeouts to avoid server resources being hogged by any one canvas.

Currently this setting only applies to scheduled canvasses - however this leaves a gap where users can just run this manually.

 

Please can you extend this setting to also cover manually initiated jobs too?

 

SeanAdams_1-1639433415953.png

 

 

 

 

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

 

 

Currently, in order to run an app via the API, you have to have uploaded the app to your private studio. Frankly, I don't find this function useful because you have to download then re-upload an app in order to gain access to the API. The API would be more useful if when an app is shared with you (or a collection is shared with you), then it would also allow for that app to be run via API by the user it was shared with. Right now, the only person who can run the app via API is the user who originally uploaded said app. 

Currently, Alteryx Server lacks rich job scheduling functionality to other products like Control-M and Informatica's Scheduler

 

Feature Requests:

 

1) Ability to configure job retries on failure without having to rerun the workflow based on a  event trigger: https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/How-to-run-a-workflow-from-an-event...

 

There are common occurrences where a workflow may fail to connect to Input sources and a retry would normally resolve the issue. 

 

2) More user friendly way to setup dependencies between scheduled workflows.  For example, if workflow A fails it triggers workflow B to run.  If workflow B runs without errors, it triggers workflow C to run.  Currently, we would need to configure this based upon events.  A complex chain of scheduled workflows becomes difficult to manage and scale.

 

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

Hello!

Currently one of the pain points when looking at integrating Alteryx Server into an organisation, is the role of a Curator, and who should be given that role. Of course, from an IT perspective, they want governance and control over data connections, users, and configuration - as it is important that users aren't simply able to change the default role to Curator and give all users access to the Administration portal, for instance. On the other hand, a Super User is typically given Curator access to allow for adjustments to all other sections of the Administrator Portal, that IT quite frankly don't care about.

 

What would be useful, is for a new role to be created, elevated from Curator. Let's call them 'Super Curator'. These 'Super Curators' (or, User-Curators, for a less exciting name) have access to all of the Admin portal as usual. 'Curators', would now only have access to the following (Highlighted yellow for Curator access):

TheOC_0-1656070199656.png

 

This would aid the conversation from an IT perspective, allowing them to take control of user, data connection, and credential administration, whilst leaving the rest of the control to the other Curators. As this wouldn't always be a requirement, it would be useful to allow for a toggle of this setting within the Configuration on the Gallery. This would also not effect pre-existing setups of curators, as in the update of implementation, all current Curators should be adapted into 'Super Curators'.


 

Thanks,
TheOC

We leverage Active Directory groups to manage user permissions to most of our company's resources like databases, file shares, applications, etc.  This idea is for the ability to manage a Gallery Data Connection via an Active Directory group.  In many cases, our AD group membership actually dictates what permissions a gallery connection should have, but we must manually add/remove users to the Alteryx connection to keep it synched with AD.

 

I think there are several ways Alteryx could be enhanced to support this; i.e. the AD group could be specified on the connection itself or it could be inherited from a Studio where the subscription is enhanced to support assigning AD groups to it (which could benefit other areas of Alteryx).

 

I'm told by Alteryx support that this functionality is unsupported but to post the idea here.  If anyone knows of workarounds to this limitation I'd certainly be interested!

This idea has been touted in different flavours over the years (but not implemented), but I'd like to push it a little further:

 

1. Create the ability to collaboratively edit an Alteryx workflow - e.g. like you can edit Microsoft documents collaboratively. If the front-end is primarily an XML interface, this should in theory be possible?

2. Version control (not version tracking) - i.e. automatically state the differences in scripts between versions and allow for checking in and checking out of code

3. Power BI & Tableau Prep have the ability to see exactly what changes were made and to reverse steps to get back to a specific stage of development: it would be great to have a panel that tracks all the edits you've made since you started editing the workflow

 

In simple terms, a modern, interactive way for multiple developers to work together, but also to encourage the use of Server to "check in" your application and to avoid developers saving the same file over & over again locally.

In the Alteryx Gallery Collections the Workflow Upload Date doesn't sort properly. Instead of sorting chronologically (ex: Jan first Dec last) it sorts by number (Dec goes before April because Dec starts with a 1 while April starts with a 4), see attached for an example. 

 

CMMartinez_0-1649944723939.png it flips back and forth between 2022 and 2021

 

 

In the example November and December are first because the month starts with a 1. Then April follows because it starts with a 4.  Then it starts to get messy because it does this:

  • 12/16/2021
  • 4/04/2022
  • 4/26/2021
  • 5/02/2021

That 2022 is in the middle purely because 4 < 5, that's not right.

 

I tried exploring the settings to see if I could change this but I didn't find an option to do so.

 

Two potential solutions:

  • Change the format of the date to YYYYMMDD, then if it sorts numerically it will still work
  • Don't sort numerically and instead sort chronologically, ex: April goes before December

As collections get big sorting for the most recent workflow becomes a nightmare with the current improper sorting mechanism.

 

If I'm mistaken and this option already exists please let me know.

Thanks!

Chris

 

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 

Hello all,

This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensi...

I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series

image.png

 

So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration

Moreover, Alteryx Server Additional Capacity license should be 4 cores.

Best regards,

Simon

It would be nice to have workflow version information on the Workflow Results page for every running status.
The reason for that is after workflow was scheduled and then the published version has been changed, there is no way to follow versions.

We noticed that the Alteryx sessions are tab oriented and not browser oriented. When opening a new tab the user is compeled to sign in again.
We would like to have an option to make the sessions more browser oriented like a "keep me signed".
Ex:
- Opening a new tab
- Going to the gallery through a published app link

It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).

 

My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events.   On a large implementation, this becomes very difficult to manage.

 

Standard notification for job failures.png

It would be good to have a new field with the owner of the data connection, when users asks to be part of a data connection, we should know who is the identified owner to contact and ask for approval.

Thanks.

 

Regards

Joana Santos

Top Liked Authors