Alteryx Server Ideas

Big time user of the Gallery API. In fact, I wrote an R package for it (shameless plug: https://cran.r-project.org/package=alterryx).

It is great that you can queue a job for an application using the Gallery API but it would be great if I could also cancel a running job.

If a job fails it would be perfect if we could set something in the workflow settings so that the job would retry again in X number of minutes for the next Y number of times. We have jobs that connect to external resources and sometimes the network will reset and will cause the connections to all drop. An example would be I want a workflow to try again in 10 minutes for a maximum of 5 times so over the next 50 mins it will retry every 10 mins if it fails

I really want to see this feature in new versions. Its frustrating the lack of options we have with scheduling workflows on the server. I need to have my process run every 10 mins but only on certain days and in certain time windows. Creating a schedule for this is impossible unless I manually create hundreds of schedules. 

I have a few workflows that I have hosted on out Gallery Server and I have them scheduled.

Ex: Process A is scheduled to run every 10 mins Mon – Sunday.

Problem: I only need Process A to run Every 10 Mins on Mon – Sat from 2 AM to 6 PM

Currently there is not a scheduling configurations that allow this type of schedule. How can I get my workflow to run every 10 mins but only during certain times and on certain dates?

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.

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

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. 

I've been writing applications and regularly need to REQUIRE fields for data entry.  When I do, I include ERROR MESSAGES at minimum.  Often I label the field as something like:  Name (Required).  Wouldn't it be nice to have a red star or have the data field in another color for background?  Taking this a step further, the validation rules being activated within the screen (rather than during run) would be awesome.

As long as I'm posting ideas, it would be nice to have an Alteryx supported function to identify the user within the application global variables.  For users, it would make my apps more friendly if they could save their configuration (*.yxwv) in the gallery.  Extending that thought, within my application I would like to be able to have easy access to their responses as well.

My use case for access to the .yxwv file data is that I will repeat some of the fields back to the user within my output.  When needed I will write the responses to a text input tool and format it for display in the output.  That requires an additional action and maintenance within the application.

Just a few application thoughts.

Thanks,

Mark

As an enhancement to the gallery, I'd like to be able to save my application parameters in the gallery in a similar fashion to when I run an app locally.  Users can view the results of an application run, but can't save the parameters that created the run.  I'll go a step further than this and ask for another enhancement.  I'd like to be able to access the questions & responses within the execution of the app to display them during reporting.t

Use case:

For a list generation application, I need to present to the user the criteria applied during the selection process.

Input Address: 49015

Type of Vehicle: Chevy

Minimum Year: 2010

Maximum Year: 2015

I've got a working solution that is okay, but not very "Alteryx-easy".  I need to have a second update attached to the interface tool to update the user response.

Thanks for your consideration,

Mark

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! 

It would be really useful to be able to obtain the user name of some one running an app in the Gallery. This could be used for instance in row level security for people running an app that produces a report and that data is considered sensitive

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

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

When we create a shared macro on the Gallery, the desire is that we are able to:

- publish this down to users simply and seamlessly

- Allow them to use these assets in their canvasses

- Allow them to simply update to the latest version of the asset on an existing canvas.

Unfortunately - right now the only way to distribute shared macros is to create a shared folder; and the only way to manage version upgrades of a shared macro is to manually find every single usage and manually upgrade.

It would be helpful to have a central Logging tool for large & complex environments.

This would be useful to allow teams to have a central way of logging data transformation errors by error-type; severity; alteryx Canvas; etc.

Right now, there's a message tool, but this doesn't provide a way to create well structured central logging across a team; especially once deployed to a server environment.

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

Right now, if you are using Windows Authentication, you can map AD group and users on the Permissions and Collections tab.  But for some reason, you can't use AD groups on the Data Connections tab.  Most of our databases are already secured by in-house AD groups in which you have to be a member in order to access that database.  Instead of managing a 2nd, most likely duplicate, list of users in the Data Connections tab I would like to be able to map the pre-existing AD group to that data connection.  That also means I don't have to service access requests.  If someone wants access to a database, they talk to the database owners, get added to the group and then they automatically can pull that data into Alteryx.

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

Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful. 

Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline.  I’ll share both files soon. 

Here are the top 5 features for the Scheduler.

1. Workflow priority ranking. When two or more workflows are scheduled to run at the same time, ‘priority’ sets the order of execution. Priority is set at the time of scheduling the workflow. Values range from 1 to 100. If a priority is not set the default is 50. The ‘priority’ field can be read from Mongo db. 

Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field. 

2. Restrict which controller and workers a specific workflow can run on. Default is to run on all servers. At the time of scheduling a workflow can designated to restrict which server to execute on. This creates a field called ‘restrict’ which server it cannot execute on. 

Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning.  Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows. 

3. Set sequence of successfully completed workflows. 

FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.

Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db. 

4. If a workflow fails you can set the number of attempts to run successfully. Report attempts greater than 1 in a new field called ‘attempts’ that can be read from the Mongo db. 

Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx. 

5. If a workflow runs more than X minutes the scheduler kills the workflow and reports a workflow error with a unique code called ‘execution-limit’.  This code can be read in the mongo db. The defaut is 90 minutes and can be set to any number of minutes. Each workflow can have it’s own limit. 

Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows. 

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