Alteryx Server Ideas

Hey Team,

With 2020.3, the new Groups feature came into light, which is great, but seems like it was only half-thought.

It would have been nicely complemented with some API endpoints that would allow managing the groups' members - add, remove, list members, etc.

Seems like the API on Alteryx is like 100 steps behind and seems like the new developments are not considering adding APIs for the new released features. I feel this is a product roadmap issue.

As an admin, I would like far more ways to automate managing the Server/Gallery than the ones currently provided by Alteryx.

Integration with AD would be nice as well, we use SAML, and would like to have the option to import AD groups that would sync automatically in Alteryx - same way Tableau has those groups that are imported directly from AD.

Thanks,

Alex

Today the v3 api requires curator access.  V3 has Getters that should work for users with API permission.  The Getter should return the objects that user has access to.   Example:   GetCredentials for a normal user with API access should return credentials that the user has access to.  Today they get a 401 auth error.

We don't want to make these users curators just to let them access the V3 api.

in the current alteryx gallery if we need to disable of enable the schedules workflows we need to manually enable or disable them.

example if we have 100 scheduled workflow. and we want to disable all of them and then enable them later. currently we spend hours to manually disable and enable each of them.

By adding a feature to select the workflows in scheduled to enable of disable the selected one at one which will save hours of time.

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

Please keep in mind that this is a suggestion from a container novice! 🙂

However, our situation is such that our release upgrade deployments are taking significant time to install, test and sign-off from DEV through PROD for the four main life-cycles involved in our server environment. Even if we script the deployment to save time, there's still manual configuration needed to confirm the new version works in the next server environment.

Similar to how Promote can deploy from DEV through PROD using images/containers, my suggestion is to package the Server components into images/containers that can be similarly deployed through the life-cycles. While the container with mongoDB doesn't need to move to the next life-cycle, the containers with the web server, load balancer, and engine nodes could move with the click of a button. And if needed, reverted to prior version with similar ease.

I forgot to ask about this idea at the UX lab during Inspire, but would be very happy to hear if it's already in the pipeline!

Thank you for your consideration!

Currently , once a user have SetPriority access ,he can select from Low, Medium, High or Critical priority levels to ensure certain jobs always take priority over others.  

This feature can be misused as users can upgrade their priority levels to jump up the queue and later downgrade the levels. It's difficult to justify and ask each others when you have 1000+ jobs running in a day and it makes administration tough and gives unbiased Gallery to all end users.

It would be nice to have on Admin console, global option to set max priority level so that no user can jump up level beyond this.

The AlteryxService addtoqueue command is great, but it leaves me wanting more.  My simple use case is to run WorkflowB via the addtoqueue command in an after run event from WorkflowA, which is run daily.  The result is that i end up with a cluttered scheduler with many instances of WorkflowB that i need to manually clean up, since addtoqueue creates a new record in AS_Applications each time it runs

It would be useful if there was an AlteryxService command for each of the subroutines already built in to the scheduler front end app: schedule workflow, update workflow, add workflow, remove workflow, edit schedule, etc

MongoDB objects could be identified by oid which the user can get from querying the AlteryxService database

I don't want to rebuild what you've already built, just need a little more control over it 🙂

Hello!
Currently when administrating the Alteryx Server, within the 'users' page, I can see that new users will be setup as 'default'. 

This will display as 'default', which can be confusing, as I need to navigate to the configuration page to remind myself what the default role is. Additionally, they may be part of a group, either in AD or within the server, that upgrades their default rank, for instance if they are part of a group set to be curators. They will still always display as 'default'.

I would like to suggest the following:

This would allow me to see much more clearly who is set as what rank on the Server, but also which users are set to different ranks as part of an AD group.

This is a real flaw in the product (almost a bug), you cannot search for a schedule.  We have about 150 jobs scheduled to run daily.  If you want to amend the schedule you have to page next through all the schedules to find it.  If you search for the workflow name, you get the workflow screen which does not contain a link to the schedules.

Also add a link to the schedules for each job on the workflow page.  I.e. search for job ABC, see that it has 3 different schedules associated with it and be able to edit, or delete any of its schedules.

As Alteryx Admin, we want to understand what our users are doing in their workflows as much as possible to ensure best user experience. In order to do this we would like to scan through User workflow XML in order to breakdown everything going on. We understand that their are many posts on workflows already doing a lot of this but:

Our Ask:  is to release XML DTD or similar documentation that can help us breakdown workflows at individual tool levels (as well as differences between tool versions)

This would allow us to further build out solutions to admin visibility of user workflows.

We have a usecase where we want to check how often a workflow runs via the API so we can automate the consumption reporting we do internally. Right now the API only reads out workflows that were scheduled using said API. That doesn't make a whole lot of sense. Enabling it to also read out all the other workflows would really make this a powerful feature for us and I suspect others.

HI,

I could not find any possible way to send an email if the Alteryx workflow is taking more than expected time.

I was wondering if any such feature is available

In my organisation, Alteryx workflow keeps running sometime due to memory issues. It will be great to know about these delay and handle them.

Regards,

Vish

In our private studios and in our home page we see our workflows in grid view by default and can toggle that to list view if we want. 

BUT we can only see our collections and the workflows in them in list view.

Please can you add the ability to view our collections in grid view?

Password is required to execute any command on LLS. Last time we forgot the password, only way to retrieve it was to reinstall the LLS ! 

A command to reset password in LLS should do.

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

Many organizations have IT applications (Splunk, OSIsoft PI, etc.) that can consume, historize, and monitor Windows Performance Monitor items.  If would be great if Alteryx wrote application-specific information to PerfMon.  Things like: number of engines running, number of workflows in the queue, number of people logged into gallery, time it takes for data to pass between DB/Controller/Gallery, etc. This would go a long way in helping admins to properly size systems and monitor them for upsets.

In the example given, there are four scheduled jobs running in the server at the moment and one manual job is being triggered by the user and is in a queued state for more than 30 minutes to start running. However, in MongoDB, when a job is triggered, that time is captured as the start time (not considering the queue time). If we consider the start time of As_Queue in our workflow, we ended up with a mess. Since that manual job is queued for 30 minutes and running for only 3.30 hours, it is being killed by our workflow. It should only be killed after 4 hours.  

• How did we determine the total queue time & the execution start time for the running/queued jobs? 
• How do I kill this job automatically after four hours while taking queue time into consideration? 
• Is there any other way to kill the manual jobs after four hours? Please note that scheduled jobs will be killed automatically by the system after four hours.

If you run an Alteryx app on your desktop or hard drive, a help button will appear in the bottom right. This button defaults to sending you to help.Alteryx.com, but you can adjust it to send you to any location by adjusting the app in the interface designer. This means that you could use the help button to send users to a location detailing how to actually use the app built. The issue comes that when you upload an Alteryx app to the Alteryx Gallery, the "help" button disappears. I propose that the help button be made available in the Alteryx gallery for apps so that designers can use it to direct users to locations detailing how to use the apps.

My question is, is there a way to see after a job is executed how much memory it consumed in total? Today we have monitoring set at server level that records memory consumption over time but it doesn’t tell which job caused the spike unless we manually go and check list of jobs executed around that time frame. Even with that we cannot know for sure which job is causing the spike.  

Today there is no realtime inbuilt job monitoring tool that can answer questions like above. 

The mongo db back is a working process but I would like to replace individual workflows and not the entire server state.