Alteryx Server Ideas

While working in the Gallery, I think the file browse tool should allow the user to import a file without selecting a sheet or <list of sheet names> as is does locally.  

For example, I have created an app in which the user is able to import a file with multiple sheets, and all sheets are brought into separate input data tools with a single file browse tool (shown below).

Since the user does not select a sheet name, the file browse tool only brings in "SelectedFileName.xlsx|". The action tool is then set to replace a specific string "SampleFileName.xlsx|". This allows the input data tools to take this new file name, and add each respective sheet name to the end.

However, when working in the Gallery, the user is required to select a sheet name or list of sheet names, meaning a file browse tool is required for each sheet that you would like to import (shown below). This is a huge inconvenience for the application user, as they have to select the same file numerous times to import every sheet. 

Please let me know if you would like me to provide any more information, I would be happy to do so.

Thanks,

Matt

Issue: When Workflow names have similar beginnings on server a user cannot distinguish between them because the columns on this GUI are not expandable as would be expected. A user has to make their browser larger and all columns open proportionately.

Solution: Change column settings so users can drag column widths to make changes. A bonus would be to allow a user to set a default along with an option to always auto expand all.

Please provide the ability to bulk add/delete users to a gallery. This would be useful for on-boarding/off-boarding large companies, departments, and external customers. For public-facing galleries, this would provide us the ability to on-board/off-board entire customers of ours. 

The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections.  The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.

Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.

This might be considered a subset of the Idea Server API to extract / submit workflows.

Thank you for your consideration.
Sincerely,

David

The Schedules tab of the Gallery currently lists all schedules, 20 to a page, with no option to filter.  I am currently managing 183 active schedules.  In order to find a single schedule, I have to sort by Workflow name, then page through 10 pages of schedules to find the schedule I'm looking for.

Please add an option to filter this list. 

Ideally, I would like to be able to filter on multiple fields at once (example:  Priority = High, Status = Active, Owner = Bob Smith, Times Run > 20).  Barring that, a simple search option on workflow name, similar to the search option on the Collections tab, would be enough.

Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1).   However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)

Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.

CC: @BlytheE 

We use the Server API to manage our server environment - and we recently noticed that the Workflows API (/admin/v1/workflows) ignores any canvasses after the 10 000'th submission.

For example:

• If we don't use any offsets or limits - then we get 10 000 applications
• If we use an offset of 5000 with a limit of 10000 - we get 5000 applications (i.e. anything after canvas 10 000 is being ignored)
• if we use an offset of 9990 with a limit of 100 - we get 10 rows returned (i.e. anything after canvas 10 000 being ignored)

By querying Mongo directly (appinfos collection) we know that we have 18 800 or so unique applications in our environment.

Please can you remove this cap from the API so that it can be used to query any number of canvasses on a larger environment?

cc: 

+  @Hemanth @marydest24 @Shreyasi @Sotoll @Kosi @revathi @Bethanyturner012  @TanyaS 

Could the community receive a comprehensive data dictionary of all the collections in Mongo with:

- Description of each collection

- Description of each attribute (or field) within each collection

- Documentation of joins between the collections

A great example can be seen in how Tableau documents their postgresSQL tables: https://help.tableau.com/current/server/en-us/data_dictionary.htm

This would be extremely helpful as we are determining which collections we need to store, how to construct queries and how to build analytics on our assets. 

Thank you!

We have the Local License Server installed.  Right now, if a Designer user changes roles, or leaves the company, they have to release their license from their client-side machine.  If they don't release it properly, and IT can't get us into their machines, then we have to wait 7 days for that license to roll off the server.  There should be a way for a system admin to forcefully revoke someone's license.

It would be nice to be able to change the Gallery URL from:

• http://localhost/gallery/
• http://alteryx.mycompany.ca/gallery/

to:

• http://localhost/
• http://alteryx.mycompany.ca/

The reason being to make it easier for end users to find the server/content.

Original forum post here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Changing-the-Gallery-URL-on-Alteryx-S...

Would like to see a Notification hierarchy implemented to Gallery. Currently, the settings that control notifications are at the Gallery-level....where only the admin can control, for example, notifying users if a new workflow was added to a collection they belong too. Could this setting be inherited, but then, for example, a Collection owner can implement their own notification settings that overrides the Gallery default? Using the same example as before, perhaps the Collection owner could disable notifying their Users if a new workflow is loaded to the collection.

Nick

Currently the Private Gallery product has 2 authentication options - AD and built in. 

If an organization uses AD, this solution is fine, however there are many origanizations who use other standard directory systems. One of the more common directory/authentication systemsis LDAP due to its wide adoption and cross platform compatibility. 

It would be fantastic to have functionality similar to the AD integration, however with LDAP for Gallery authentication and user management. 

Best regards,

Ryan

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.

It would be great if the admin could change some default settings on the Alteryx Gallery page. For example, where we have the list of apps, show Detail view and sort by App name ascending by default.

 

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

I would like to propose a number of small enhancements to the Gallery:

1. Time format. The 12-hour time format (

    

   ) is confusing to everybody except Americans. Please add support for a 24-hour format. This could be done either by extending the Locale settings or by a separate check box. Please make sure that this time format is used everywhere in the Gallery (last update, last run, schedule, etc.).
2. Date format. Even though using English as GUI language, I prefer the time format according to ISO 8601-1, namely "YYYY-MM-DD". Please add support for this format, independent of selected language.
3. Number of Rows per Page in My Workspace: Each time I open My Workspace, the number of listed workflows per page is set back to 10. Please add support to set the default number of workflows in the user settings or at least preserve the chosen number within the same session.
4. Fully utilize the screen in My Workspace: Even after switching to more than 10 rows per page, nearly half of my screen stays empty. Please add function to utilize the screen completely.
   

Currently, the API V3 endpoints does not have anything for Data Connection Manager (DCM). Create an endpoint to allow users to add/delete/update and list data sources, credentials, and users of DCM data sources. Also include an "admin" endpoint that can list all of the above for the entire server.

The admin screen of Alteryx gallery does not have an admin function for DCM sources, its users, and credentials. This can cause visibility issues during audits of the gallery. An API endpoint can alleviate this issue until it is added to the UI.

It would be nice if the Gallery Admin could download the workflow from the workflow page within the UI, without having to run API calls or having to add himself temporarily to someone else's studio. 

The current setup of Data Connections, as of v11.3, relies on users to have the same aliases or connection strings available to easily share Workflows and publish them to a Gallery. In order to solve this, I propose that a system be created that allows users to establish "Local" and "Remote" connections. The Local connections will be used anytime the developer is creating a Workflow on his own computer, but will be automatically substituted with the Remote connection information once the Workflow is published. Remote connections may be filled with an Alias to a connection from the Gallery.

The primary benefit of this is that an organization will not need all of their developers to standardize their aliases and/or connections strings per connection. Instead, they will create one connection within the Gallery that will be distributed to developers and applied to the Remote column. This will generally reduce difficulties regarding the expansion of an Alteryx user base within an organization. Below I will outline two possible implementations of this:

1) Add a Remote Connection String field when adding a connection in the Data Connection Manager. This optional field will allow the user to set only one connection to an IO transaction, but maintain the Local-Remote functionality described above. Here is a mockup of how that might look within Alteryx Designer. 

2) Add a Remote Connection String field on each IO action within Alteryx. This will give the developers more flexibility in which connections are used where, but will also require more setup and maintenance time. Below is a mockup of how that might look.