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

@SteveA did an article about server logging a few years ago which was very helpful.

https://community.alteryx.com/t5/Engine-Works-Blog/A-deeper-dive-into-Server-logging/ba-p/22389

 

... and in the training events at Inspire this year there was a session on how to find and interpret server logs.

 

it would be very useful for large server environments to move away from discrete log files as much as possible, and instead move towards a world where the logs are stored in a data format, and one logging infra is used for all so that an admin team can see these all in one place.

 

Granted - the initial boot-up of a server, where it needs to connect to the logging DB is going to be a challenge - but after this initial primary boot sequence it would be great if all server logs and logging events were stored in a database of some kind so that we can analyze and collect events.     That way, server admins can have a great UI experience; as well as a great analytical experience without having to regex through multiple different .LOG files.

Use case: I need to schedule a workflow to run every 2 hours each day, with the first run at 7am and the last run at 7pm

Current solution: I need to create seven daily schedules for each hour that i need the workflow to run

Idea: Add an intraday "Start Time" and "Stop Time", or "Between" to the "Minutes / Hours" schedule type, so i can create one schedule that meets the use case requirements

Example schedule with new parameters that meets use case requirements:

Start Time = 7:00 AM

Stop Time = 7:00 PM

Repeat Every = 2 hours

 

Start Time could default to 12:00 AM

Stop Time could default to 11:59 PM

 

screenshot.png

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

For professional alteryx admins - it is important to know if a particular asset has been updated (so that we can bring the updated version into our env), with some idea of release notes so that we can understand if the update breaks backward compatibiity and what has been changed.

 

Additionally - it would be very helpful for admins to be able to be notified of new assets created by particular authors whom I trust.

As Alteryx makes more and more use of the Public gallery - it would be valuable for Alteryx to explicitly have a section devoted to items that are certified by Alteryx so that we can be safe bringing them into our corporate env.

 

The assets created by Alteryx are currently listed with Alteryx as the author, however it would be useful to have a completely separate section with Alteryx assets only, and with these broken down by type.

0 Likes

If you are viewing schedules, on the Queue Panel, you should have the option to refresh the information to get an idea how far things are progressing.  If you swipe back and forth between panels you get updated % done information, so it is definitely available.  Not the most pressing need, but a very easy fix. 

 

Ninja Edit:  Did not know there was a dedicated server ideas forum so I removed a part. 

The AlteryxService addtoqueue command is great, but it leaves me wanting more.  My simple use case is to run WorkflowB via the addtoqueue command in an after run event from WorkflowA, which is run daily.  The result is that i end up with a cluttered scheduler with many instances of WorkflowB that i need to manually clean up, since addtoqueue creates a new record in AS_Applications each time it runs

It would be useful if there was an AlteryxService command for each of the subroutines already built in to the scheduler front end app: schedule workflow, update workflow, add workflow, remove workflow, edit schedule, etc

MongoDB objects could be identified by oid which the user can get from querying the AlteryxService database

I don't want to rebuild what you've already built, just need a little more control over it 🙂

image.png

 

 

 

 

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

 

 

 

 

I wish Alteryx would allow more control over user access to scheduling workflows. Currently there is only a radio button that globally allows users to access the scheduler. I wish we had another layer where we could limit access by Permissions. For example, we would like all Artisans and Curators to have access to the scheduler, but not viewers.

 

 

each canvas in our environment goes through initial dev; then a testing phase; then into production usage after completing testing & peer review.

 

Currently the server environment has no concept of progression or promotion so we have to set up our own Dev; UAT; and Prod gallery & server - this really is very clunky because assets have to be manually copied across.

 

What would be more effective is:

- Allow a single asset to have a lifecycle (like you do in GIT) - so that it can go through dev and testing as a branch of the main code

- Once ready - user then changes the lifecycle type to "testing" or "UAT" and pushes it to users

- Once signed off, the user then promotes this to a production flow, and it replaces the current production version

 

There are a few areas where we'd need to do some thinking (dependancy tracking; branching; changing connection details as you promote so that you can hit the prod data stores etc) - but fundamentally this would go a VERY long way towards eliminating much of the admin involved in running the gallery.

Please Enable OAuth 2.0/OpenID Support for Alteryx Server  & Connect. Currently, it supports only AD , SAML . 

 

Current SAML has limitations, Unable to import Security groups from LDAP/AD if SAML is enabled.  

 

 

Given the need for administrators to be able to perform analysis and monitoring on server performance; user usage etc - it is necessary to provide full documentation for both the API and the database underlying the server so that admins can use this to good effect.

 

Ref: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...

 

Although very limited documentation is available on the server API (https://gallery.alteryx.com/api-docs) what we're looking for is a much more fully formed and navigable experience like some of the examples below.

 

This will make building helper processes substantially easier; as well as allow admins to fully manage their environment.

 

Many thanks

S

cc: @HeatherMHarris @revathi @AshwiniChezhiyan @LizaNemchynova

 

We've confirmed with @KevinP that the Alteryx Gallery / Server API does not currently support downloading canvasses in unzipped data-stream format. (https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...)

 

Please can we add an API end-point that allows the following:

  • Connect to the gallery and download a canvas; along with all of its sub-canvasses and helper macros. 
  • Format required:
    • Plain XML (not zipped)
    • Provided in a data stream so that we can perform analytics and surveillance on this data
    • Fields required
      • Canvas filename
      • Application ID
      • Some unique ID per macro / sub-macro
      • XML for the canvas
      • Last run date
      • Last changed date
      • Environment (this is important once Server actually allows a Dev; UAT; Prod progression cycle - so we can see which environment people are in)
      • User details who uploaded
      • User details who are marked as the owners
      • Any other meta-tags on the canvas (important once server allows for meta-tagging of canvasses for categorisation)

 

Current API only allows this to be downloaded to a zipped file; which then needs to be unzipped; and then loaded back into a data stream.

 

Thank you

S

 

CC: @revathi @AshwiniChezhiyan @LizaNemchynova 

 

Currently there are certain locations on server that are paginating content results:

 

  • /gallery/#!apps/studio
  • /gallery/admin/#!apps
  • /gallery/admin/#!subscriptions
  • /gallery/admin/#!users

Each of these pages require users to either know exactly what they want to find by using keyword filtering or know exactly what page they want to go to and use the bottom arrows/page numbers to navigate to that page. Ditching pagination for something more intuitive helps users that may not be as acclimated with the depth of content when there are a lot of results, and also saves users multiple click interactions to find what they want.

 

There are tons of solutions for this, but infinite scroll is the most user-friendly & least taxing server & client side.

 

https://infinite-scroll.com/ has code & examples, and jquery seems to be the most widely used implementation.

 

pagination.png

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. 

Option to update ownership to any other valid license holder as needed.

 

Use Case: Currently the canvas owner is marked by default as the user publishing the canvas to production.

However, we have seen instances where the person moves teams and would like to hand it over to another person.

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.

Enhance the USER tab in Gallery for showing the active user status, last login time

 

Easy to filter out the active user

Allow Admin to kill user session 

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.

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