Alteryx Server Ideas

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

In order to migrate workflows from our UAT environment to a Production server environment, we are looking for an API capability to work with the server:

- Query canvasses by name or ID (to get a list of canvasses)

- Extract Canvas to a particular location (by ID)

- Upload canvas including dependancies (with parameters for team; collection; etc)

This would assist with automating the UAT to Prod process until Alteryx Promote can step into this gap.

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

User who share Apps/Workflows with other users in a collection are not able to see the results of the other users executions directly in the gallery.

Could you please add the possibility to share workflow results in the Alteryx Gallery?

The Alteryx Server Usage Monitoring & Reporting  reports are very useful. In order to automate the distribution and leverage our Tableau Server we have modified one of the macros within to publish the TDE to the Server and reworked the workbook to point to it. This is a fairly time consuming process to do, so the idea is to introduce a version of the workflow which pushes the datasource, producing a version of the workbook pointing to it.

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/

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

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

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

Analytics Gallery needs the ability to save my question choices - so I don't need to re enter them every time I run the app.

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.

Currently the e-mail settings for the server are set up using a wizard and are not available within the admin UI.

Please could you add an explicit section to the Admin UI to allow the admin team to set up approved SMTP settings, allowing this all to be managed in one admin console.

Further: Can you allow the admins to push these settings down to the desktop users.   This would allow the admin team to control the SMTP usage and prevent data leakage.   It would also reduce complexity for the user since the SMTP settings are all pre-set making eMail tools; and Events easier to set up.

On Success --> Do This

On Fail --> Do that

The lack of control and flexibility around the scheduler seems to cause people to bury the logid down in runner macros or unnessarily poll custom log tables to see if a status has changed.

I am aware of a couple of clients calling for this functionality. This can be performed via command line but it realy needs to be in the scheduler options.

We currently have the ability to store connections on the server which protects the credentials - however this capability does not exist for APIs for Sharepoint sites etc.

Please could you extend this to cover authentication for ALL connectors?

Many thanks

Sean

cc: @revathi

I like to be able to access and run my apps from my iPhone.

Hi,

I have described my issue in the Community post here:

https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Version-Management-in-Gallery/m-p/120319#M3...

Is there a way to retrieve an exact date when new version of a workflow was uploaded to Gallery? I know it works when it is today, yesterday or couple days ago but after that you can only see "2 months ago" etc. in Creation Date, which is not sufficient for any version management.

Thank you

Use Cases:

1. As a server admin, planned PM outages should be scheduled.  These outages should prevent jobs from beginning execution (window of time) prior to the outage.  Jobs running at the time of the cut-off should be system-cancelled.  
2. As a server admin, unplanned outages should cause running jobs to stop.  At the conclusion of an outage, jobs that are system cancelled should be restarted.

Currently, we use Task Manager to control Alteryx Service (or command line).  An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities.  While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't.  Other admins have asked what is "hanging" alteryx service up for a STOP command.  I have explained that all jobs must be stopped in order for a quick restart of the service.  

We're using a single server today (this client) and plan to add workers to the configuration.   It would be helpful to know where work is running and be able to use admin functions across the servers.

Cheers,

Mark

As an admin - would like to have the following features on the Gallery

1. add summary cards to TOP of user page that show same summary as diagnostics page

2. "export to excel" icon 

3. ability to filter date

4. allow selection of ALL

5. allow me to default my settings choice so its always "all" - screen shot below

We spent almost a full day on Friday internally, and also about 3 or 4 hours of time for 3 Alteryx Server engineers (thank you all - MattH; ZachH; WayeW) and Ben Burkholder trying to get our gallery server to start.

Error message was "

Failed to construct Gallery daemon process, process exited code <9002>

This was all that was provided in the server log files; the gallery log files; and the Windows Event Viewer.

In the end, it turned out that the issue was very simple - the MongoDB had open locks in place that needed to be deleted; and then the service came up immediately.

Several man-days of our effort; as well as the precious time of the Alteryx Engineers who gave up their Friday afternoon to help could have all been avoided if the error-message on the server failure said "Login failure on server due to open locks - please clean out locks on db.locks collection" with a link to the solution or a lookup code that be researched on the Alteryx support site.     

Please could we go through the server service and eliminate all the exit codes and replace with human-friendly error messages - that way we could allow this kind of issue to be self-diagnosed, and allow the Alteryx Engineers to spend their time building the next generation of Alteryx Server rather than diagnosing a table lock.

cc: @avinashbonu @revathi @Deeksha @BenBu @WayneWooldridge @MattH @SteveA @ZachH 

Please support SAML 2.0 for gallery

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

Admin settings for the Alteryx server are currently split between the Admin GUI in the gallery (screenshot 1 below) and a tool called "Alteryx System Settings" (screenshot 2 below).

Please could you move all of the system settings into the Admin section of the GUI.   Not only will this allow an admin to administer the settings remotely (rather than having to be logged into the actual server with an interactive login which is needed now) - it will also consolidate them into one place which makes things easier for admins to ensure that all settings are set up correctly.

This could be done progressively - a little bit in every release - over the next couple of releases, it does not need to be done in a big reengineering or a massive big-bang release (in fact - progressive release is much more favourable since you learn along the way and big-bang releases are well known to be failure prone).

cc: @TanyaS