Alteryx Server Ideas

Hi,

It would be nice if scheduled workflow credentials could be linked to the workflow and not the individual versions of the workflow.

It is problematic for the user that they need to remember to reschedule the workflow, whenever they publish a new version of the workflow.

Best,

Daniel

I have been looking at the content in Alteryx Public Gallery for some time and I have had some concerns about the safety and usability of the macros/workflows in the gallery. 

I think there should be an option to rate, review and provide feedback on stuff that is out there on the public gallery. This will be helpful in many different way.

1. It will generate trust about the workflow/app. If I see that something is rated higher and has been used and commented by a lot of users I am more inclined to use it
2. It will provide a lot of ideas on how a particular workflow/macro can be used in different ways 
3. Review/Feedback will help the author to make changes as required or suggested by users.
4. The macro's will probably show up in google search based on key words provided by users in their reviews.

......

I had initiated a thread some time ago related to this, there is some useful information in there if someone has same concerns.

 https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Can-Apps-and-Macros-in-Alteryx-public-Galle...

Thanks,

Ashish

Hello all,

It appears that every time we have a talk about the gallery organization, people bugs around the difference between district and collection. Adopting a new semantic with less confusion would lead to

: -a more intuitive product for everyday life

-less question and less confusion during pre-sales/POC/Training.

Best regards,

Simon

Organizations using Alteryx Server with an embedded MongoDB can benefit from an option to change the MongoDB User and Admin User passwords.

Current deployments of Alteryx Server allow regeneration of the Controller Token, and for many of the same reasons, the ability to change the MongoDB passwords would be beneficial to customers.

Many organizations rely on a centralized team for daily administration of the Alteryx Server and MongoDB. With the current functionality, when members of this team change positions, they continue to know the MongoDB authentication information indefinitely. Providing organizations with this capability allows them to make the determination of how/when a change is required to mitigate any risk of misuse.

At some point we would like Alteryx Gallery to support SSO via SAML and Authorization via AD groups. The way I want is to have Authentication via SAML and Authorization via AD groups. For instance one of our apps Tableau: It does authentication via SAML (SSO) and for authorization, we import AD groups into Tableau thrice a day(stores the groups in a .xml file), once the groups are in the Tableau, we secure the objects within Tableau using that LDAP groups (which kind of become local groups after import). Basically the userid after the successful authentication step is used by the app for authorization.

I just stated Tableau as one of the ways to implement Authentication and Authorization for an enterprise app. If Alteryx Gallery needs to be an enterprise app, you will need to look into this idea. 

Thanks
Raj

Can we add an ability to manually adjust the order of workflows in a collection? I don't think we should have to go and click the column to sort each time if we want them in alphabetical order. It looks better for the end user to have everything nice an arranged when you have multiple processes in each collection.

With Alteryx Server 2019.4, new users cannot create Collections by default. 

As Alteryx Server admin this causes much manual effort on my side, because I need to configure new users manually. 

Alteryx claims to be a tool for automatization and I do not see how this new feature fits into Alteryx's vision.

I wish that there were tools, which allow me to automatize the management of users on the Alteryx Server. 

With a growing number of users on the Alteryx Gallery, manual user management is not an option!

I wish there was a way to create custom roles on the Gallery and assign them to AD groups, similar to "Permissions".

Those custom roles could include the privilege to create Collections, schedule Jobs, etc.

I would also love, if there was a way to give granular access to the Data Connection menu to users. 

I have already addressed this topic to the Alteryx product manager in Q1 2019 and I hope this feature will be implemented in the future. 

Hello,

We use external corporate scheduler and we would like to start scheduling Alteryx workflows in this way. However, collections don't have API which would simplify our way of running workflows which we are shared by the users. Are you planning to enable such feature?

Best,

Piotr Zawistowski

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.

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 opening a canvas - it is possible to open from the gallery, which is important in a team environment.

However - as you work on this canvas - if you hit save, it does not save a new version to the server and increment the original (as would happen on sharepoint) - instead it asks you to create a new file.    

Please can you change this behaviour as follows:

- If I open from the gallery then when I save I'm updating the same Gallery asset and incrementing the version ID by 1.

- The only time I would save in a new file is if I use Save As; and explicitly pick a new file.

 cc: @jalvarezv

There are two key APIs that we use for extracting canvasses for governance & surveillance:

- the Workflows API which lists all canvasses on the server;

-  and the API call which returns a packaged version of the application by AppID

Unfortunately - when we query for all workflows to get the first list - there is no flag to indicate that a subset of these are actually deleted.   The result is that you need to make the second call to find this out which is wasteful.

Please add a "deleted" flag to the Workflows API so that we can identify which applications have been deleted without having to call the specific App ID post.

CC: @jalvarezv

We are taking an incremental feed of all server canvasses in order to look for patterns - however there is no option on the server admin APIs (the Workflow API specifically) that allow you to filter by date.

Please can you add to this API to allow API users to specify an upload/updated date filter and only take items after this date.

cc: @jalvarezv

@SteveA did an article about server logging a few years ago which was very helpful.

https://community.alteryx.com/t5/Engine-Works-Blog/A-deeper-dive-into-Server-logging/ba-p/22389

... and in the training events at Inspire this year there was a session on how to find and interpret server logs.

it would be very useful for large server environments to move away from discrete log files as much as possible, and instead move towards a world where the logs are stored in a data format, and one logging infra is used for all so that an admin team can see these all in one place.

Granted - the initial boot-up of a server, where it needs to connect to the logging DB is going to be a challenge - but after this initial primary boot sequence it would be great if all server logs and logging events were stored in a database of some kind so that we can analyze and collect events.     That way, server admins can have a great UI experience; as well as a great analytical experience without having to regex through multiple different .LOG files.

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.

As a system admin, I need a simple, reliable way to back up the Alteryx Server without shutting it down first. A hot-backup (and restore) utility that includes a consistent copy of MongoDB plus any other server config files would allow me to do this.

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.

When a process is running in foreground, the GUI does an excellent job of giving feedback to the user as to which "step" the job is running and how much data is processing through the active tools.  When that same job is scheduled, the amount of information is limited to when the job began execution.

If a tool was able to give checkpoint status out to the user, we could better monitor the progress of scheduled jobs.  The visibility to the job is most important for long running jobs.  We've unfortunately had instances where we have had to cancel jobs and to restart them not knowing how close or how far from finishing they were.

Thanks for your consideration,

Mark