I've seen various solutions/workarounds but this seems to be a table-stakes ask? When scheduling a workflow I should be able to specify which parameter values to run with. Just two of many use case examples -
Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business
Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials. When their credentials change all they would have to do is update the schedule parameters
(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)
I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.
SQL Server Management Studio
Schedules on Alteryx Gallery/Server
Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1). However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)
Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.
I would like to set a retry count when scheduling a job, and also to specify to duration in between retries, e.g. job fails, but then will retry to run 3 times with a 5 minute wait in between each retry.
Also would like a radio button next to all workflow results, so when you get a list of failed jobs you can click all the jobs and then hit rerun. This should be complimented with select all functionality. This will prevent me from having to go into each job and rerunning, i.e. save me loadsa clicks!
Open Custom Group management internal API's for Curators (or those with Admin Secret/Keys)
If your server is on SAML, you can't leverage any AD group for granting access to resources. The new custom group feature is a help, but still requires you to manually add groups and member users, so it doesn't scale for large organizations (too much management overhead).
Having the internal APIs exposed would allow me to do my own group sync tool, synching members between Custom and AD groups of the same name.
As a server Admin, I'd like to be able to do via APIs all that I can do via the Server Admin UI. This other idea was recently accepted for opening the collections APIs for Admin, it would be great if both Collections and Groups management were opened on the same upcoming release.
Currently, to allow a user to schedule jobs, prioritize jobs, assign jobs, create collections, or have API access, toggles must be set at the user level.
As a server administrator, I want to configure these toggles at the group level, so that a) I don't have to modify a large number of users individually to grant them such permissions, b) I ensure consistency across groups of users that doesn't rely on humans clicking all the right things for each of the relevant people, and c) I can easily change these settings for multiple people, if needed.
If two users sit in the same studio and have multiple scheduled workflows in that studio, both users can see the results of those schedules under "Workflow Results" -> "My Jobs"/"Jobs Shared with Me"
It gives both users in the studio good visibility of all the workflow results they have access to.
Now if we move to a 1 studio-1 user environment and share workflows and schedules via collections, this "Workflow Results" -> "Jobs Shared with Me" functionality is empty. Instead users have to go to each schedule individually to see the results from them there.
So if you're in a 1 studio-many users environment, there is a single place to go to see all workflow results. But if you're in a 1 studio-1 user environment and sharing via collections, you have to go to infinitely many places to see the results of all the schedules shared with you.
So my idea is to have results from schedules shared via collections appear in Workflow Results.
It would be great if you could overwrite an existing workflow when saving to the gallery from designer. It could be a simple popup with a yes/no option to overwrite/save a new copy. Currently, you would have to
1) Save your workflow to the Gallery.
2) Click on ok and be taken to that workflow.
3) Go back to your private studio.
4) Search for the app you want to replace.
5) Realize you have 7 copies of the same workflow with the same name and try to determine which one you want to replace. (this could just be a "me" problem)
6) Select that app
7) Click on replace workflow.
😎 type the name of the workflow in the box.
9) Look through your list of 7 workflows and choose the one that was just uploaded. Usually the first in the list I think.
10) Lament that it took way too many steps.
I recognize that you can open workflows from the gallery in designer which does allow overwriting, but I've run into issues with 1) external dependencies not working as expected (ie packaged assets don't quite work the way I want) and 2) about half the time it will simply give you root errors and then your only option is to save to a folder and then go through the process above.
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration
Moreover, Alteryx Server Additional Capacity license should be 4 cores.
It would be good to have a new field with the owner of the data connection, when users asks to be part of a data connection, we should know who is the identified owner to contact and ask for approval.
We leverage Active Directory groups to manage user permissions to most of our company's resources like databases, file shares, applications, etc. This idea is for the ability to manage a Gallery Data Connection via an Active Directory group. In many cases, our AD group membership actually dictates what permissions a gallery connection should have, but we must manually add/remove users to the Alteryx connection to keep it synched with AD.
I think there are several ways Alteryx could be enhanced to support this; i.e. the AD group could be specified on the connection itself or it could be inherited from a Studio where the subscription is enhanced to support assigning AD groups to it (which could benefit other areas of Alteryx).
I'm told by Alteryx support that this functionality is unsupported but to post the idea here. If anyone knows of workarounds to this limitation I'd certainly be interested!
In prior versions, Gallery Admins could easily and quickly reactivate users that were deactivated (e.g., and employee leaves the company so we inactivate their Gallery account, but then they come back to the company in a few months with the same name and email).
Now, the only way to do this is to edit the Mongo page.
We need a way via the UI to reactivate users, like we did in the old UI.
I suggest adding an option in the current User List/Grid to be able to filter for Inactive users.
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 would like a built-in process that would search or, and resolve, workflows that are stuck in the "initializing" state. These seem to happen for various reasons but communication problems between the controller and workers .. usually a socket timeout.. which appears to be most problematic. It seems that these type of errors should be expected in all but the most stable environments,
Currently, the only tool that we have to solve this problem is to restart the Alteryx Service on the controller and while this works there tendency to cause some collateral damage in workflows ...erroring or restarting from their beginning.
There may be a way to solve this without restarting the service by editing Mongo using a tool like Robo 3T but that is unproven and has its own risk.
After dealing with this issue and struggling for quiet some time we think that the best option is to implement a "clean up" DB process that will run every 5 min or so, capture a list of workflows in the "initializing" state , then compare that list to one in the next 5 min cycle and fix any workflows that appear in both lists. We think that returning any stuck workflows to the queued state would be the best Fix option.
We just don't want to continue to use Restart the Service process to solve this issue and accept the collateral damage.
Thank you for your consideration
Hello, I would like improved user management features and/or training
Add Admin ability to place the Alteryx Service (Engine) into Maintenance mode allowing current workflows to complete, but all new workflow processing moved into Queue to allow for server configuration and/or maintenance.
Currently, if I want to make a small configuration change (like a memory setting in the Runtime settings) I have to hunt for a quiet window or the lowest level of activity to kill the service (and the running jobs).
It would be helpful to flip a 'switch' and have all new jobs go into 'Queue' allowing for the change and service stop/restart ... then pick right back up with the queue in configured order. (execution time, priority level, etc...)
The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections. The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.
Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.
This might be considered a subset of the Idea Server API to extract / submit workflows.
Thank you for your consideration.
I am in the process of migrating apps from the old gallery to the new. I have screen captures of the results from the same app in both. In the older gallery version, if there is only a single file type available, it defaults to that file type and you click the icon for the type. In the new gallery version, you must select a file type before you can download the file, even if there is only a single type available. The dropdown makes sense for one that you have multiple types (like pcxml), but it makes no sense to require the user to go through an extra step to select a type before downloading when that's the only type they can download. Please see all the screen captures. The blue-ish background is from the new gallery.
Issue: When Workflow names have similar beginnings on server a user cannot distinguish between them because the columns on this GUI are not expandable as would be expected. A user has to make their browser larger and all columns open proportionately.
Solution: Change column settings so users can drag column widths to make changes. A bonus would be to allow a user to set a default along with an option to always auto expand all.
We have situations where some workflows that are scheduled end up having intermittent connection issues to other databases that result in the workflow running to timeout. The timeout settings are set in the server, but it would be nice if you could set an override value for a lesser timeout in the runtime settings for individual workflows and basically use the server setting as a not to exceed value. We have a multi-node environment with multiple worker nodes and about 250 artisans. We have some regularly scheduled workflows taking the full amount of time in the timeout setting and obviously if a couple of normally quick running workflows ran to timeout that causes issues with the queue.
When saving to our company's gallery, we must deselect dozens of assets for our numerous workflows every time they need to be resaved, which is very frequent.
I would like to suggest a select/deselect all button under manage workflow assets. This would save a considerable amount of time.
Ability to change the default workflow settings when to also include [Others may view this workflow's history] in a similar way to the other attributes in workflow settings that are set by default. This would prove beneficial for workflows which are shared across a large team and need to be run on a consistent frequency and are not run headless. The inability to set this by default leaves a risk that the setting remains unchecked and more than one user triggers that workflow in a given month which could result in a material impact if the output of that workflow is posting to another system in the firm.
Hello Alteryx team,
I would like to propose idea that was mentioned on the community but there is no solution either.
The issue is related to Qlik Analytics Samples and error that it is causing with wrong path error for default macros like eg.CountRecords.