Alteryx Server Ideas

The shared data connections from the Gallery have been very helpful in centralizing data connection information between desktop users and their workflows when saved to the Gallery. The In-DB tools currently cannot take advantage of the Gallery Data Connections and require a completely separate setup that is both confusing and adds additional connection management work for creation/password changes. 

It would be a great enhancement to Alteryx if all connections for the different types of tools could be centrally managed from the shared Data Connections manager found in the Gallery.

Best regards,

Ryan

I'm really enjoying the new Save As functionality to push to the gallery, but had a request that would make it even more useful for me. 

I saw that you can open workflows directly from the Gallery and edit them with version control, but it would be nice if it was possible to do a Save As on a local workflow and point it at an existing copy on the server.  I need to maintain a local copy of my workflow for dev/prod separation, but currently my way to push to prod is to do a Save As to my Private Gallery, remove the existing copy from the company gallery, and then share my newly created workflow into the company gallery.  This causes some headaches like no version control, switching out icons everytime, and overall just a messy way to push to prod.  

It would be helpful if there was a way to overwrite an existing workflow in the gallery rather than editing it directly.  

I would like to collaborate with my team, but also maintain my own personal private studio.

Is that on the road map?

-Dan

I love the gallery data connection feature - we're going through some big systems architecture changes, resulting in new locations for many datasets. Having a single place in the Gallery Admin area to update connection information works beautifully.

We're running into issues with the gallery-hosted data connections when trying to run some apps on our private gallery though. The trouble comes up when the gallery-hosted data connection appears inside a macro that's part of an app. We get an "Unable to translate alias" error when trying to run these types of apps.

If we have an app using gallery-hosted data connections that are outside of a macro, the gallery is able to resolve the connection alias fine and work properly. The issue only appears when the gallery data connection is part of a macro used inside an app.

We use macros a lot in our app development because it allows us to use standard methods for accomplishing common tasks. Using macros also enables us to set up automated testing workflows to make sure our processes produce expected results. As it is, we're unable to take full advantage of the gallery-hosted data connections because they don't work within macros, and instead have to continue using hardcoded connection strings. These are a bigger maintenance burden as our underlying systems evolve and are updated.

The only reference I can find to this idea is here : https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Share-Results-in-a-Collection/m-p/231 .  It references that the feature of "sharing workflow results" was "on the Roadmap" in 2014.  I did some searching through the current Ideas page and cannot find anything.  I also reviewed the release notes since Alteryx 10.5 and cannot see that this was added.

A user approached me today with a problem of "Many people need access to the results of this data, and I want everyone to be able to see all the results".  While you could potentially email these results to a specified user set, that would require maintaining both a collection and an email tool in the job, and could potentially cause notification fatigue if users only care when they go to the Alteryx Gallery.  Similarly, results could be saved to a networked location, but that would require a user to go to two locations in order to find this information.

As such, having a toggle that allows users with permission to view a workflow, to also see the results of any/all users, would be huge. 

Hello,

The Analytics team for our company services 9 different lines of business, and it would be helpful to create sub folders within each line of business. It would be helpful to be able to restrict the access for each individual sub folder also. Our team deals with different teams within each line of business, and they may need to have different access due to sensitive content. 

Thanks,

Erik M

It would be nice to have an inbuilt function(s) that return an identifier (NTLogin for instance when the gallery is setup with windows auth) of the user running the app on the gallery.

Functions like - USERNAME(), DOMAINNAME() etc., helps.

I know that it can be achieved via the "__cloud:UserId" call , which is not officially supported by alteryx. It adds value if it is inbuilt within the product itself.

Regards,

Sandeep.

Currently, if you want to change from Built-in to Windows Authentication, you have to:

To switch authentication types, you'll need to start from scratch.


1. Stop the AlteryxService
2. Open a Windows Folder Explorer and go to the directory you have MongoDB loaded (System Settings->Controller->Persistence->Data Folder
3. Rename or delete that folder (a simple backup would be to rename the folder, you can move it to another directory as well)
4. Open the Alteryx Server System Settings and click next to Gallery->General.
5. Select the new Authentication process you would like to use.
6. Finish the System Settings and the new database will be created.

The Gallery and Scheduler databases are closely tied.  Workflows that are uploaded, results created, and schedules created from the Gallery are stored in the Scheduler database.  So you will need to start from scratch on both the Gallery and in the Scheduler.

This is a non-starter for any company that has any amount of time invested in establishing the use of the Gallery.   Starting over is not an option, but improving security, streamlining access protocols as a part of overall data governance is a must.  Please consider fixing the authentication protocol to make it so we don't have to start over.

Thank you,

Today, if I want to save a job onto the Alteryx Gallery, I need full permissions to do so and it is a manual process.  For some organizations, this level of access is deemed excessive, which can make properly leveraging the Alteryx Gallery difficult.  Having the ability to write a "deployment" script that could publish a workflow to the Gallery, and potentially add a new workflow to a Collection would be incredibly helpful in these cases.

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.

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

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.

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

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

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

My team currently uses the API to call a large number of workflows via a Python based scheduler process.  We use this currently by having ~10 users in a single subscription (Private Studio).  

All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.  

From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.  

Are there plans to adjust the API endpoints in the future to better account for this?

Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.

Thanks