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

I am in the process of migrating apps from the old gallery to the new. I have screen captures of the results from the same app in both. In the older gallery version, if there is only a single file type available, it defaults to that file type and you click the icon for the type. In the new gallery version, you must select a file type before you can download the file, even if there is only a single type available. The dropdown makes sense for one that you have multiple types (like pcxml), but it makes no sense to require the user to go through an extra step to select a type before downloading when that's the only type they can download. Please see all the screen captures. The blue-ish background is from the new gallery.

In prior versions, Gallery Admins could easily and quickly reactivate users that were deactivated (e.g., and employee leaves the company so we inactivate their Gallery account, but then they come back to the company in a few months with the same name and email).  

 

Now, the only way to do this is to edit the Mongo page.


We need a way via the UI to reactivate users, like we did in the old UI.


I suggest adding an option in the current User List/Grid to be able to filter for Inactive users.

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 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

Ability to change the default workflow settings when to also include [Others may view this workflow's history] in a similar way to the other attributes in workflow settings that are set by default.  This would prove beneficial for workflows which are shared across a large team and need to be run on a consistent frequency and are not run headless.  The inability to set this by default leaves a risk that the setting remains unchecked and more than one user triggers that workflow in a given month which could result in a material impact if the output of that workflow is posting to another system in the firm.

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!

Issue: When Workflow names have similar beginnings on server a user cannot distinguish between them because the columns on this GUI are not expandable as would be expected. A user has to make their browser larger and all columns open proportionately.

 

Solution: Change column settings so users can drag column widths to make changes. A bonus would be to allow a user to set a default along with an option to always auto expand all.

 

 

Deliverance_0-1606920874425.png

 

The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections.  The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.

 

Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.

 

This might be considered a subset of the Idea Server API to extract / submit workflows.

 

 

Thank you for your consideration.
Sincerely,

David

 

Hello, I would like improved user management features and/or training

 

  • Display 100 does not seem to work consistently
  • Click /navigate from user to user – once I select a user would like to go to next user
  • Changes I make with filters refresh every time I go back – which means I have to constantly reset my view in between each user
  • Modify user settings in collections – would like to modify user settings instead of delete and re add user

 

 

There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.

 

I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.

 

APIs I am requesting be released:

  • PUT .../gallery/api/collections/{collectionID}/apps/{appID}/
  • POST .../gallery/api/scheduler/

Add Admin ability to place the Alteryx Service (Engine) into Maintenance mode allowing current workflows to complete, but all new workflow processing moved into Queue to allow for server configuration and/or maintenance.

 

Currently, if I want to make a small configuration change (like a memory setting in the Runtime settings) I have to hunt for a quiet window or the lowest level of activity to kill the service (and the running jobs).

 

It would be helpful to flip a 'switch' and have all new jobs go into 'Queue' allowing for the change and service stop/restart ... then pick right back up with the queue in configured order. (execution time, priority level, etc...)

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

 

 

Hi

In a heavily used server environment, and depending on how workflows are deployed, it is possible to accumulate a vast number of "one off" workflows that could/should be deleted  as they would never be used again. In one of our environments we have over 1 million of these.

 

Currently we are manually deleting them 500 at a time but have asked if there is a way to script the delete process to make it more efficient. We have been told that to really delete a workflow you would need to touch at least 4 collections.

 

Can we have a Delete workflow API in one of the next releases in order to address this issue?

 

Thank you

 

Tom Diroff

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'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

Good Day

 

We need a way to read a workflow log file while the workflow is running .. we want to peek inside the log file to see what is happening in the workflow, especially for the  case when the workflow seems to be "hung". This would be an invaluable troubleshooting tool.

 

Currently these worklfow log files are locked by Windows and are inaccessible by all but unapproved 3rd part utilities .. if at all.

 

Often these logs disappear if the workflow needs to be deleted in order to save the environment

 

It is noted that the service logs do not exhibit this behavior, so the request is to

1) allow the running workflow logs to have the same behavior as the service logs

2) provide a work around to allow reading of the running workflow logs

3) ?????

 

Thank you for thinking about this

 

Tom D

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 a very pleasing user experience if we could enjoy the Server usage with a true dark mode. The customization in the Theme-Panel isn't advanced enough to do it ourselves - unless we deep dive into the css-files. The CSS already has a good structure and the dark mode could be enable with just a few changes. 

 

Here is a comparison of my server in light and dark mode.

 

2020-12-18 02-08-31.png

2020-12-18 02-04-28.png

It's probably noticeable that I haven't studied Design, but it should give a rough suggestion how it could look.

 

Obviously not everyone wants a dark mode, therefore every user should have toggle in the user settings to switch between light and dark mode.

When saving to our company's gallery, we must deselect dozens of assets for our numerous workflows every time they need to be resaved, which is very frequent.

 

I would like to suggest a select/deselect all button under manage workflow assets. This would save a considerable amount of time.

Thank you,
Daniel

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. 

Top Liked Authors