Alteryx Server Ideas

Currently there are certain locations on server that are paginating content results:

• /gallery/#!apps/studio
• /gallery/admin/#!apps
• /gallery/admin/#!subscriptions
• /gallery/admin/#!users

Each of these pages require users to either know exactly what they want to find by using keyword filtering or know exactly what page they want to go to and use the bottom arrows/page numbers to navigate to that page. Ditching pagination for something more intuitive helps users that may not be as acclimated with the depth of content when there are a lot of results, and also saves users multiple click interactions to find what they want.

There are tons of solutions for this, but infinite scroll is the most user-friendly & least taxing server & client side.

https://infinite-scroll.com/ has code & examples, and jquery seems to be the most widely used implementation.

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. 

Option to update ownership to any other valid license holder as needed.

Use Case: Currently the canvas owner is marked by default as the user publishing the canvas to production.

However, we have seen instances where the person moves teams and would like to hand it over to another person.

The Admin Gallery api needs to have the ability to get questions,execute jobs, get outputs. Currently I can only get questions, execute jobs and get outputs of my private gallery flows, I need to be able to do this for other Artisan flows without having to have their key/secret.

Enhance the USER tab in Gallery for showing the active user status, last login time

Easy to filter out the active user

Allow Admin to kill user session 

One of our biggest areas of confusion for new users of our Gallery is the Download button. They often click it thinking that will give them their information right away. It would be great if the person didn't see that or the scheduler option if they were not an Artisan, since they can't use the workflow anyway. It would be even better if selecting the workflow took them straight into the question portion.

As we continue to build Alteryx Workflows for the business, there is a continued need for an organizational structure for saving and storing Alteryx Workflows within the Alteryx Gallery. Organizing the workflow repository through a "folder hierarchy" will allow users to quickly navigate and find the appropriate workflow. Currently, the workflows are listed in alphabetical order and requires the user to remember the Alteryx Workflow name and click to the proper page. 

Any enhancements to the Alteryx Gallery organization structure would be greatly appreciated!

Thank you, 

KK

This idea covers 2 things:

- Disabling certain tools for users

- Pushing out other tools

Disabling;

- If we want to disable a particular tool for everyone or for specific users - then we need to go to every single deployed machine and adjust settings or delete some DLLs.

- What we would need is to be able to take a user / group of users - and de-select certain tools or apply limits

- In our corporate environment - every designer needs to check in with the server before fully starting up.   If it cannot connect to the server, it needs to terminate gracefully

- As the designer logs in - the first negotiated conversation is "What tools and capabilities and standard default settings should I have"

Pushing Out:

- If a useful tool is brought into our environment (like the JIRA connector here: https://gallery.alteryx.com/#!app/JIRA-Connector/58d87c2feffc2a0dd0b5ed8f or the CREW macros) - we want to be able to push these out to all the users

- Again - every designer checks in with the server first

- Then negotiates tools

- then downloads any missing tools or updates new versions of existing tools.

This kind of central server capability is essential in any enterprise deployment of several hundred seats.

Hi there,

Currently, when we download a version of Alteryx - we need to download a very large number of binaries across many different download locations.    Once we get these in, they need to go through InfoSec audits; then be packed for deployment etc.     this creates a very large admin overhead in that folk need to check for updates across multiple binaries and also create a significant number of different installs which then need to be rolled out across hundreds of workstations.

The request would be to change the approach to downloads for enterprise customers:

- Admin logs into the download portal

- They then select the components which they need (Designer; predictive; CREW macros; Microsoft starter pack; Tableau starter pack; JIRA connector from the gallery; additional predictive tools from the gallery)

- this then becomes the defined selection set.

- When any of these items are updated - the admin is notified

- When they download - these are then all built into a single installer binary which we can then download and roll out to all our workstations.

Many thanks

Sean

cc: @dataMack @adrianloong

As users change roles; or possibly even leave the firm - we need to automatically manage the ownership of their and their permission.

- We need to be able to export all permissions and ownership of assets by user using an API

- We then need to be able to revoke permissions using an API (we have a central entitlement management process that this can be tied into)

- we also need to trigger a revoke on all licenses via API.

If done within Alteryx server:

- When a dept code on a user changes; or user leaves - trigger an invalidate on all assets.

- Workflow to both the primary and secondary owner to ask for a new owner

- Also automatically trigger a revoke on all licenses

In order for us to manage the large number of canvasses on our server - we need to add the ability for Admin teams to require additional attributes on every canvas:

For us, these mandatory attributes would be:

- Which team do you belong to (dropdown)

- What business process does this serve (dropdown - multiselect)

- Primary & secondary canvas owner (validated kerberos)

For the ones that have dropdown lists - we can provide the master data into a drop location or into a manually configured list on the server.

For a given DB connection - there's a need to be able to specify the owner for this specific connection.

Reason for this is that the credentials for a given DB are not all managed by the central admin team - so we'd want to say that a given DB connection is owned by a particular person so that this can be updated frequently as passwords change.

For resilience - our particular policy would be to have 2 owners so that if one person resigns or changes roles, it invalidates the primary and reverts to the secondary - and then asks the new Primary to create a backup owner.

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

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.

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.

It is currently (Alteryx Server 2018) not possible to delete Districts one created - we can only disable them. See also: https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Deleting-Gallery-Districts/m-p/32684

Frankly, this is rather inconvenient if one wants to restructure a Gallery. Renaming them is an option, but there might still be a number of districts we want to delete. Would appreciate if this could be considered for a future update.

We've purchased a server license and several designer licenses to publish analytics apps to customers via our internal/company gallery. Whether a user signs in or not, users should not be subjected to corporate Alteryx ads. This is a terrible user experience and detracts from our ability to deploy self-serve solutions.

This may be more from an admin standpoint but once I add workers into a cluster (controller token added), I have no way of knowing if the worker is now added to the cluster unless a workflow starts getting serviced and I view it from the 'View schedules' tab.

This causes issues specially when we have to add multiple of them and need to keep a track of which ones are added to the cluster or not.

On the admin page, I should be able to view the list of the workers that is currently existing on the cluster.

This idea is to allow users to configure the file view option for a workflow running in the gallery that produces file outputs. Today, there are two views that a user can toggle between (see attachment), but I don't believe there's a way to change the default view. This idea is to change the setting as either a global gallery setting, on a workflow-by-workflow basis, or both.

We have end users that miss the drop down menu (and the file count next to the drop down, and the label we've added in the analytic app that says there will be two output files, and...), so they sometimes miss the second file entirely. Setting the default view to the "list view" rather than the drop down view could help alleviate that pain.

Note: The screenshots in the attachment show two Excel files that could be combined into one file with multiple tabs. This is a pain point for other workflows, as well, that produce outputs in multiple file formats.