Alteryx Server Ideas

In the gallery you have the ability to replace a workflow with another, however when doing so the version history only indicates "Package Replaced" (see image below)

Would it be possible to change the default text and input something more meaningful, since in my case I use this field for version control/auditing so it would be good to know what changes came with the replaced version.

Second ask, but maybe not as important as the first.

Sometimes the package we are replacing with itself might have several versions, but these are completely lost when the files are combined.

Would it be possible to keep that version history when the package is replaced.

Eg. Original File is at Version 10. This will be replaced by a package that is at Version 3.

Possible solution would be to have the new version be Version 13 which includes the 10 versions from the original file and the 3 from the new. 

Thanks!

I have Designer Apps that work really well using the Browse tool to provide the outputs to display and download in the Apps.

This does not work when I push the Apps to Server.

I find this very restricting and would like to suggest that the Browse Tool be enable to generate its outputs in Server Apps.

I would like the Browser outputs to be enabled for download into Excel, PDF, etc as well so the Server Apps behave in a similar way to the same Apps in Designer.

When a workflow is run manually in the gallery the user is able to enter input parameters. However when using the schedule functionality this option is not available and a separate workflow needs to be developed to dynamically derive input parameters. Effectively two separate versions of the workflow need to be created and maintained.

If this functionality could be built into a future version of Alteryx this would be of significant benefit.

It would be nice having the ability to alter the timeout of the file upload on Alteryx Analytic Apps uploading to the Gallery.  Having it restrained by time and not file size makes it so that users with poorer internet speeds will not even be able to upload moderate sized files.  

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.

In the Alteryx Gallery UI, it's possible to set up workflow credentials so that a workflow published to the gallery runs as a specific user.  

Unfortunately when that workflow is run from the Alteryx Gallery API, it appears to only ever run as the Alteryx Server Run-As account. 

Our developers in working with this figured out that if they called the (undocumented) API that runs the actual Alteryx Gallery directly, they can achieve what they want, but it seems a risky strategy.

The idea would be:

-Either unify the APIs so that the Gallery itself uses the same API to run workflows as what you present as the "Gallery API" (the eat your own dogfood way)

-Alter the Gallery API to enable us to run as a different workflow credential

Without this, we're forced to permission the run-as account to access anything that uses this method, which in turn then becomes a bit of a security hole (any workflow run will have access to everything that the run-as account uses) 

Hi,

@patrick_digan pointed out to me today that in my ignorance I thought that the "On Success - Show Results to User" option in Interface Designer did something on Alteryx Gallery, like it does when run locally.  I tried to prove him wrong (I've been manually checking off what outputs I want since day 1! How could it not have been doing anything?!) and failed miserably.  As far as we can tell, this functionality is simply non-existent within Gallery.

Please add this functionality so that we can suppress files (without reverting to hacky tricks like changing the output location so the Gallery can't see the output) with a simple check box.

Link to my shame, where I very openly explained exactly how I thought I had been solving this problem the whole time, and how after testing and review, it looks like I hadn't done anything with this configuration.

All these check boxes... and they don't change anything!

We have several workflows that call other workflows (i.e. via the Conditional Runner macro) but are running into some versioning challenges since we moved to storing all of our workflows in our gallery.  When I publish a workflow that references another workflow, I can bundle it up with the workflow when I save it, but then Alteryx places that workflow into the /externals directory, which is obvioulsy not the same as the workflow that we've saved to our gallery.  An example:

I have two workflows in our gallery...one that generates a TDE and one that calls that one if certain file availability and time conditions are met.  The "master" version of each is in the gallery, which is what we want...

...but when I load or save the Sales Analytics workflow in Designer, I have to bundle the TDE workflow with the main workflow in order for it to run from Gallery.  But now I've created a disconnected version of the TDE workflow and if I forget to update it when I update the version in the Gallery, I'll be running the wrong version.  I know I could store these workflows in a network directory, but that seems to defeat the purpose of the Gallery.

If I'm not missing something insanely obvious, I think this would be a very important feature enhancement, namely the ability to pull in a Gallery workflow into another workflow.

The job timeout function is a perinate issue on the the Alteryx server because scheduling workflows on the server that overlap with another workflow can cause bottleneck issues. Depending on the number of workers and the other workflows, the workflow in question could fail to run or not complete running at the desired date and time. I recommend a view option of the Schedule Forecast feature for all users, so as to allow all users to effectively schedule workflows on the Alteryx server that do no conflict with other workflows. 

Our Organization uses a Password Manager to automate the update of service account credentials used in Windows Services. 

Would like to request the ability to leverage that functionality with the Run As user inside of Alteryx Server Settings used with Workflows. 

This would increase application security, while ensuring the process is automated, thereby limiting issues from human interaction.

Examples of these types of application are ERPM(Enterprise Random Password Manager), Thycotic Secret Server, and I am sure there are others. 

In regulated environments, like banks, there is a requirement to fully segment Alteryx Jobs so that people on either side of a Regulatory Wall cannot access each other's canvasses or results.

As an example:

- Public vs. private side in Broker/Dealer banks

- Compliance or HR or Finance need to be segmented from all other areas in most banks

What is needed here is for any canvasses belonging to each of these walled-off areas to be controlled so that they cannot be shared across the wall, and results cannot be viewed across these areas.   This also means that the Gallery Environment needs to be capable of being segmented fully within 1 installed environment.

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

We have situations where some workflows that are scheduled end up having intermittent connection issues to other databases that result in the workflow running to timeout. The timeout settings are set in the server, but it would be nice if you could set an override value for a lesser timeout in the runtime settings for individual workflows and basically use the server setting as a not to exceed value. We have a multi-node environment with multiple worker nodes and about 250 artisans. We have some regularly scheduled workflows taking the full amount of time in the timeout setting and obviously if a couple of normally quick running workflows ran to timeout that causes issues with the queue.

Apparently I click too fast sometimes when saving a project, but there are a number of times where the workflow name hasn't populated when saving to the gallery and it ends up saving a blank file name. This is a pain because I can't do anything with the one in the gallery because there is nowhere to click on it, so I can't use the replace function and have to re-save it and re-add it back into any collections that it was in.

I realize that I just need to slow down, but I do this frequently enough where it absolutely drives me crazy. Being able to change file names in the gallery would be a big plus instead of just using the replace option.

Workflows which are scheduled and continuously failing in a row 5 times need to stop/disable the schedule. Sent a mail to the workflow owner stopped schedule due to continuous error.

For Administrating the schedule workflows this feature helps a lot. Many users create workflows and dump into server and schedule it and forgot it if we implement this strategy, it will be helpful to both users and Admin team.

We really like the idea of the Server Usage Report.  But the PDF is somewhat limited and we use Power BI instead of Tableau.  It would be great if the Workflow had an option for outputting to Power BI.

When rerunning a failed manual job, the same Priority is used, but the Optional Job Name is not and cannot be re-entered on submit.  User has to go to Workflow results page and Edit to add the Optional Job Name for a rerun.

I suggest the Optional Job Name text box be added to the rerun submit page.

Prefill using the original job's value if one exists.

Thanks,

MJ

Currently, this is completely manual with whoever is assuming the schedule creating it under their profile and then the old schedule being deleted.

This can happen often in organization where a user leaves the company or assumes a new role requiring some else to maintain those schedules. It would be convenient if there was an option to reassign the owner of a schedule to simply this process.

The workflow result window shows the Name/workflow, AMP, Priority, Assigned worker, Run as, Completed at, Runlenght, and Runtyp of the workflow. The following feature would also be useful on the page.

1. Showing the creation date of the workflow without taking queue time into consideration
2. The option to change the time zone would make it easier to analyze the logs
3. Detailed insight about the particular workflow results, such as average execution time, failure count, and success count with date filtering. 

As we look at upgrading Alteryx Server - one of the challenges is that it's an all-or-nothing approach; and there doesn't seem to be a guided wizard approach to upgrading.

The upgrade process would be much less intimidating if we could create a Migration tool which can work across versions - similar to Microsoft SQL Server which has the.    This would allow us to:
- Migrate a subset of assets up or down versions

- Migrate across servers to do consolidation or to split loads into different servers for the purpose of segregation

- Progressively migrate over time to limit the risk.

cc: @JohnPelletier