Alteryx Server Ideas

As a Curator, I need Artisans to be able to create & maintain their own Gallery connections (rather than only Curators)

- My Artisans use their own credentials in their connections

- Their credentials are subject to a periodic reset policy, so they need a self-service capability to update their connection credentials (and sharing settings)

Right now, with LSS, the only thing you can query who has taken seats on licenses (you get user's email and host name).  This is OK, but it would be great if we could get more information than that.  Primarily

• What was the date/time that the user first grabbed that license
• When was the last date/time the user connected to the license

As you know, there is no way to forcefully remove a license from the LLS (you either have to have user deactivate from Designer, or wait 7 days).  Knowing this information would help admin's know who is actually using the licenses and if someone leaves the company, you can get a countdown until that license is released.

For historical tracking and auditing, I would also like to setup an Alteryx Workflow that puts licensed user information into a table or DB so we have a log of who is using the licenses.

I'd love the ability to have one schedule for a workflow at specific times. 

Currently you have to create 4 different schedules if you'd like a workflow to run at 10 am, 3 pm, 5:30 pm and 11:30 pm and doing this makes the "Scheduled Workflow" section of the server not only cluttered, but a lot more difficult to manage.  (like spotting accidentally duplicated schedules- which also happens more often than i'd like :)

Thanks!

Having the option to disable schedules within the Designer application would be advantageous for we support staff.  Especially when multiple service restarts or server reboots are required.  When we perform migrations or restores or even upgrades or when conducting server maintenance actions.   As we know starting of the Alteryx service immediately queues up workflows to be run based against there schedule times.   When maintenance is being performed we do not want workflows to run, and/or having to wait for completions or have the user to rerun the workflow.   The option to temporarily disable schedules globally with a click of a button is far better then changing the parameters of the schedule or even deleting it.   To go a step further = an internal mongodb administration command to disable/enable schedules would also be helpful at the database level 

Idea:

Using a few designers and registering to the Alteryx Gallery are good fits for micro and small enterprises, from investment vs capability stantd point.

Alteryx Server is suitable for medium to large enterprises with at least 45K USD budget yearly and many alteryx users possibly more than 20...

Don't you think there is a need for something in between? I propose Alteryx mini-server (well we can find a better name hopefully :)

Rationale:

Many Alteryx clients seem to utilize Alteryx designer for ETL,

then some of them further enrich data and model forecasting or predictive modelling.

Before even considering a server they output to a BI server like

• Qlik server or
• Tabelau server or
• PowerBI

If there is a need for automation Alteryx designer + Scheduler does all the trick needed.

Once you update everything in a repetitive fachion 100s to 1000s of Qlik or Tableau users can reach to the most uptodate content and discover dashboards...

I believe we can do a similar thing with a mini server...

What to do:

Currently, many of our most useful apps in the gallery utilises blocked tools (download tool, R tool etc). Every deployment or even minor updates to these apps require emailing the Alteryx Curator account for exception requests. This process is quite cumbersome, although the need for it is understandable. However, given that not a single app from us was ever rejected (and we submitted dozens of requests) , it would be great to have a process in place to apply for a permanent whitelisted status. This would give trusted app authors the ability to deploy apps with blocked tools without emailing the Curator. 

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

Hello,

Maybe it's time to have a better licensing model. In addition of the current and restricted core-base model, why not having a user-based model?

Best regards,

Simon

We have the need to bulk-add users, and to bring in their information (full name; location; etc) from Active directory.

Right now, adding users is a 1:1 process which is highly painful.

Desire is to be able to take a list of Kerberos IDs, and bulk add them as users - and then select a group of them and permission either for the gallery; or for designer licenses.

cc: @revathi @avinashbonu @Deeksha

The workflow result window shows the Name/workflow, AMP, Priority, Assigned worker, Run as, Completed at, Runlenght, and Runtyp of the workflow. The following feature would also be useful on the page.

1. Showing the creation date of the workflow without taking queue time into consideration
2. The option to change the time zone would make it easier to analyze the logs
3. Detailed insight about the particular workflow results, such as average execution time, failure count, and success count with date filtering. 

Hello!
I found a weird bug in my travels today.

The TL:DR is that when a date input tool within the interface tool is used within a collapsing radio button, it defaults to "dd/mm/yyyy", breaking any app when this is not filled out: 

Both values are default - i have not edited these values. The weirdest part is, this is Server/Private Gallery specific. When this workflow is downloaded and run within Designer:

And the workflow runs fine.

I have not tested this with any of the other interface tools, however I suspect this to not be the only tool this issue resides within.

I have attached the workflow I used (not that it would take long to recreate) for testing.

I would like to see some functionality in the Alteryx Gallery in which you can select multiple schedule workflows to disable/enable. Currently as an admin if I have many schedules I need to enable/disable I need to go into each schedule manually to disable or enable. This is okay for one or two, but I have about 20-30, it is very time consuming. I would like to see maybe some checkbox functionality next to the workflow to select and then an option to either disable all selected or enable all selected.

On Server Version 2019.4 I was able to use a SQL query as an external data source for my analytic app options for a drop down menu, tree, list, etc. When we upgraded to 2022.4, this capability was lost and according to the article below a chain analytic app is the best, but unnecessarily complex work around.

Tool Mastery | Drop Down Tool - Alteryx Community liste déroulante dropdown

While in a workspace or collection, it would be great to be able to select multiple workflows and perform a bulk action on them (e.g. delete). This would help cleaning up unused workflows quicker.

Thank you

Hello Alteryx Devs - 

So, I'm poking around the Atlerxy Gallery API stuff with an eye toward building a set of classes that can interact with workflows without exposing Gallery proper to the community at large.  That being said, I was a little dismayed to find that all interactions require inclusion of *user specific* API Keys and Secrets.  It can be dealt with, but ultimately it means that configuring a middleware tier between the real world and Alteryx server requires an additional hierarchical level; i.e., understanding which of the developers came up with workflow X and having *their* API Key / Secret attached at configuration time.  

Anyways, it might be easier to just have a global trusted key / (super) secret.  If you get that, you can execute a workflow.  

Maybe we have a special studio that people could clone to, and in this way, you'd only have to track a single key/secret outside.  

I mean, the existing system works OK for one offs, but if you wanted to have a (semi) modular system in place, dependence on understanding publishing entity specifics seems to muck things up for no discernible benefit.  Of course, maybe in some places there is benefit to this scheme (?), but it is causing me to craft some weird work arounds early in development, which gives me a sinking feeling.

Or am I doing it wrong? 

Thanks for listening. 

brian

We have at the moment our server configured to work with SAML credentials. Whenever a user sets the credentials option to be "User must specify own credentials" the validation is performed using the servers own local user, giving out an error whenever some workflows with SSO data access are uploaded.

It would be great if a window would pop up or credentials could be configured for the validation to aviod seeing the error to show up.

When a user publishes and schedules a workflow on the gallery, they have the option to specify their time zone to ensure that the execution of the workflow occurs at the appropriate time. However, if the workflow invokes the DateTimeNow() function, the captured time is in UTC. If it is important for the end-user to have that time that is captured be in their local time zone, they will need to manually (either within the workflow or as a user input for an Analytic App) specify the offset from UTC.

Instead, there should be an Engine variable that captures the offset (or the time zone) that the workflow was executed from (or scheduled in), which can dynamically adjust the DateTimeNow() output appropriately.

Idea:

To create an IoT district for the Alteryx Gallery...

Rationale:

Many vendors are now focusing on the IoT wave,

having some examples on IoT use cases would be a nice resource for many...

• Please star the idea if you like it,
• Comments are more than welcome

Best