Alteryx Server Ideas

The Users, Workflows, Collections & Schedules tabs all have hyperlinks to the relevant sections of administration. However, this only shows the current 'as-is' active state. What would be useful is for each number show to have its own drillthrough to that subset of data, i.e. clicking on Inactive under users takes you to a list of inactive users, similarly clicking on Active Jobs under Schedules takes you to the list of actively running jobs etc.

This would provide a more intuitive navigation for admins.

Hi all,

In an enterprise environment - DB connections need to be set up from the server and pushed down to your users; and they need to be managed across the various servers in your software lifecycle.

In other words - you may have a sandpit / dev server env; a UAT env; a pre-prod; and a prod env - and each of these need to have the same DCM credential IDs so that users can access these.     

(before you say "you can do this from the desktop) - that is true, however that's not a workable solution in an enterprise env because that means that users can change the password from their desktop into a prod env which is a breach of IT General Controls)

The solution here is to break DCM out in to a separate service - where

- all your servers (dev; UAT; Pre-Prod; Prod) can all point to one instance of DCM

- users can maintain their own connections and credentials

        - Each needs to have up to 2 owners so that you can deal with people moving jobs / leaving the firm

- users can also entitle these connections and credentials to their team members so that when the team member logs in, it shows a popup saying "you've just been given access to new credentials / connections"

- A particular connection may have multiple different variants - depending on the environment.

        - HR Data may point to a UAT version of HR data if you're on the UAT server; and to Prod if you're on the Prod server

        - if a connection is environment specific - then it also needs to have segregated credentials (since the login to your UAT HR Data may not be the same as prod).

Thank you all

sean

cc: @wesley-siu @_PavelP 

We previously had 2020.4 and had the Shared with Me tab on the Gallery Workflow Results.  Now that is missing on 2022.3 that we are on now.  This made it easy to see all scheduled flows that were shared with you that you did not schedule.  It help those that monitor flows and their progress during the day.  It is cumbersome to go to collections and look for them.  As well as not fun to add the schedules to each collections as you have to search for them instead of just picking from the list.

Enhancement request that there is an ability to limit collection naming rights to the collection owner and/or collection admins. Currently anyone with access to a collection can rename it.

Enhancement for the ability to trap errors at the tool level, take actions, and direct workflows based on error messages. If a tool presents an error, check for additional handling instruction in the configuration panel.

Hi all,

I would like to suggest the idea to make the ability to add a graphic to an Interface on the server as well. 

Currently, the function only seems to work on Desktop, but having it work on the Gallery as well would be very nice.

Especially if we could have the image be horizontally oriented as well as vertically, depending on our other interface tools. 

Would love to hear any other related comments or ideas!

As we have more and more users onboarded to the Server, and many users share similar names, it is getting more and more complicated to manage. 

It will be great if we have a management console that allows us to create User Groups, Tags, set User Departments, and more controls alongside their curator, designer, etc status on Server.

Groups like User Groups gives a group of people access into certain workflows, districts, collections, etc. It will also be helpful as it can also be an audit trail of who ran what - with a feature that allows users or groups of users to run certain tasks or schedules. 

Sometimes, a workflow posted to the Server is calling from a source data that has dimensions which are specific to certain users based on departments, divisions, countries, regions, states, or etc. depending on the level of granularity. 

Although Alteryx developers can create Analytical Apps that have the option for end users to select these dimensions, a more seamless experience for end users (and better for security as well) is to have the ability to configure such filters for existing users on the Alteryx Server itself.

So, if Person A belongs to State 1 and Person B belongs to State 2, by default when both Person A & B enter the Server to that specific workflow in a collection or district, they will automatically be filtered for State 1 and 2 respectively. 

This is similar to Section Access configuration - whereby users have already been pre-filtered the moment they enter.

The current workaround is to create multiple workflows and store them in different collections or districts specific to end users, and to make any changes will require a change to the workflow itself. 

It will be great to have a dashboard that allows for Alteryx Server admins to configure on their own without hassle.

When running an analytical app in designer desktop, the user has the ability to choose the location they want the output saved.  However, when you move that same app to the gallery, they no longer have that option.  They have to download the file and move it to the intended location.  Being able to specify the location would save the end user time.  I also have an app that uses a formula tool to save the output to the same location as the input, but moving to gallery does not allow the user to do this.

Currently there is no way to clear historic notifications, it would be good to add this functionality.

Linked to this is system messages do not work as expected, as system message should either be present or not. However, when cleared it persists in the notifications and the clearage also shows as a blank entry, which is a poor user experience.

Having the ability to clear notifications would help with this, but ideally system messages should be separate from the notifications, as in whilst it is active it should appear as a banner in the UI as per the documentation and not be clearable by the user and when it is not in place, i.e. the event has occurred, it should not be present, there is no need to refer back to this system message.

Given the security requirements of our company collections need to be created centrally, which is fine for sub-organizations that only require one collection. However, the large sub-orgs require more than 1 collection, ideally we would create the top-level collection and give the sub-org the access to create their own sub-collection within that collection, but not the ability to create collections at the top-level.

Currently users have to be manually added to groups and those groups linked to collections.

For large organizations this is time consuming, it would be better if users could automatically be assigned to the relevant collection based on matching an attribute of the collection with an attribute of the user/group.

To take this further, when using SSO the information, such as group could automatically be passed in by the claim and so fully automate the process.

Currently SAML configuration can only pass First Name, Last Name & Email Address. It would be useful if additional attributes could be configured, such as group information. This would link to another enhancement that is automatically linking new users to a given collection based on this additional attribute.

Currently any pages or links that you create are displayed as uppercase, which is a poor user experience.

Anyone with access to a collection can see the Users & Groups tabs, which show information that is no appropriate for non administrators to see and prompts unwanted questions. Users no not need to know who else has access to the collection and what rights they have.

It would be useful if there was a configuration option to hide these tabs from roles below Curator.

Currently pages you add to server when opened via the link icon open in a new window. If you are using SSO authentication, such as SAML this essentially logs the user out in that window. This is not a good user experience.

Ideally there should be an configurable option to open pages within the current window, thereby maintaining login and provided a better navigation experience.

Hello all,


Alteryx Designer Cloud is quite young, somehow incomplete, not compatible with Alteryx Desktop etc... but I'm very optimistic than in a few years it will become a killing app !

That said, I'm more skeptical on this race to the cloud : from my experience, Cloud should just be one way of selling a product, not the only one. It has a lot of cons and a lot of pros and customers should have the possibility to choose between "on-premise" and "cloud"  product, and change from one to the other very easily.

My main customer on Alteryx is a government agency that deals with highly confidential, personal data. They won't go to cloud. Not in the next ten years. But they would love to have the Alteryx Designer Cloud on their own server.

Best regards,

Simon

Allow Collection owner to be a point of contact rather than a sub-Curator. We want a ticket process to control access to collection workflows and users in a SOX-dedicated gallery and giving those permissions outside the ticket process would be a hole in our control environment. Currently we make a service account the owner, but that means we need a list of contact people on the side.

In an enterprise multi-node Alteryx Server deployment that has existed for many years and many upgrades, there are artifacts within the MongoDB that are unknown to Gallery Administrators. I envision a workflow or app that is developed by Alteryx that queries the MongoDB and looks for orphaned documents in the MongoDB across all collections. With 2022.3 there is a pre-upgrade check, however, it does not find all unexpected items within the MongoDB. Regular ongoing MongoDB health helps with overall management of the environment and could prompt for support cases before it becomes a problem during pre-upgrade activities.