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.
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.
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.
I would like to be able to see which collection(s) a Workflow is in since in future users will access the majority of workflows via a Collection - so if a user asks me about access to a certain workflow I can find out how they would get access to it i.e. which Collection(s) it was available in and who owns those.
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.
We recently upgraded our on-prem instance of Alteryx Server/Gallery to version: -
We have noticed that the search functionality in various areas (top and right-side) no longer return results using a "contains" but rather it is doing an "exact" or "starts with" keyword search. This is very frustrating to many users as we can't easily find our workflows quickly compared to previous versions.
Please improve search functionality.
As we look at upgrading Alteryx Server - one of the challenges is that it's an all-or-nothing approach; and there doesn't seem to be a guided wizard approach to upgrading.
The upgrade process would be much less intimidating if we could create a Migration tool which can work across versions - similar to Microsoft SQL Server which has the. This would allow us to:
- Migrate a subset of assets up or down versions
- Migrate across servers to do consolidation or to split loads into different servers for the purpose of segregation
- Progressively migrate over time to limit the risk.
There is no good way to get server user credentials into a workflow without asking them for it in an App interface. It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.
Wanted to grab some attention here regarding the Alteryx gallery search engine (which also bleeds over into searching for schedules and jobs when troubleshooting).
Since a picture is worth a thousand words, I'm pasting two pictures (one attachment) of searching our gallery for the word "Contour" and the word "Signal". Both of these words are in the title of a single workflow - when I search for the word "Contour", the workflow pops up. When I use the first word in the workflow, which is "Signal", it doesn't pop up.
I appreciate all that Alteryx does, but I wouldn't think this should be a difficult issue to fix, and I would imagine there are other frustrations with the functionality here.
I have three team members all in the same private studio. We can see each others' workflows. However, when looking at a workflow that another team member has published to the gallery, it looks like:
This is a massive impediment to collaboration because my team handles ETL for most of the company. If a user complains that their data isn't up to date, whoever receives that support ticket needs to be able to see if the workflow is actually running and whether it was successful or had an error during the last run.
Preventing a team from seeing this for each others' workflow schedules and results means that the only person who can deal with an issue is the person who originally made the workflow. Which makes the idea of a shared private studio wholly pointless as we may as well be operating in different universes.
Please create a studio-level setting where all members of a studio can see all schedules and results of all workflows in that studio.
A nice to have is a connector for Microsoft Flow to trigger workflows. With Microsoft Flow, users can automate processes, or set conditions that can trigger services across many different providers.
Having the ability to use a Microsoft Flow can enable alteryx users to run workflows and feed in data that could be used by Microsoft Flow to feed into other processes.
This would be a game changer for many users.
There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.
I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.
APIs I am requesting be released:
2019.4+ Server now prompts users to select an Encoding Type when downloading a csv on the gallery. Unfortunately there is no way to disable the prompt of which encoding option to utilize or an ability to select a system default. Please provide these server options as this is causing confusion across departments.
(many users like the preview provided by yxdb but want excel download)
During development in Designer, when the workflow is configured to output to csv it already has the encoding configured, please provide the option to at least default this at output on the gallery:
The only alternative at this time is to republish all workbooks configured to output .csv or .yxdb to be .xlsx. This is not ideal.
Note: Scheduled jobs are not affected - I tested a scheduled run and csv files were successfully written out to a file share on the server. Content format appears to not be impacted.
The schedules page on server needs an overhaul. Sorry to be so blunt but it is awful. It is by far the worst aspect of Alteryx and one of the most important at the same time.
Here are a few points about it...
1.) Sorting needs to be fixed as it doesn't work correctly (sorting on the first column, "Workflow", returns items that start with 'L', 'S' and a zero as the first three on the list), so looking for 1 scheduled item across 10+ pages of schedules becomes a "needle in a haystack" endeavor.
2.) There are no search and/or filter capabilities which would help alleviate the pain-point mentioned above.
3.) [Missing] items automatically removed from schedule when the workflow is removed from the server. It just jumbles up the screen with useless information.
4.) The 'Schedule' column doesn't need to reflect the name again like the 'Workflow' column. is a hyperlink and the other isnt. I cant tell you how many times I have clicked on the wrong hyperlink only to have to go back and deal with point #1 all over again. Can't it just be a simple calendar icon or something like that next to the Workflow name?
5.) While not as critical, but more of a 'nice to have' function. An ability to export the list of schedules would be helpful. If we ever need to divy up work for an employee that leaves the company it would be a good way to see all of the work they have out there and mark up the list to distribute info for reassignment purposes, etc.
I am sure there are other aspects I am missing, but here are the most important ones to me as an end-user (Not an Admin)
Thanks for listening. 🙂
The idea is to have tabs on separate pages in the Gallery (or the option to allow that type of behavior). Right now, if you created an analytic app that has questions on different tabs they will be on separate pages in Designer, but when you push the workflow to the Gallery all the questions will be on the same page. The tabs act as a navigation bar instead of taking you to separate pages.
Here's two different discussions that ask about this in case there is any confusion:
In a heavily used server environment, and depending on how workflows are deployed, it is possible to accumulate a vast number of "one off" workflows that could/should be deleted as they would never be used again. In one of our environments we have over 1 million of these.
Currently we are manually deleting them 500 at a time but have asked if there is a way to script the delete process to make it more efficient. We have been told that to really delete a workflow you would need to touch at least 4 collections.
Can we have a Delete workflow API in one of the next releases in order to address this issue?
When rerunning a failed manual job, the same Priority is used, but the Optional Job Name is not and cannot be re-entered on submit. User has to go to Workflow results page and Edit to add the Optional Job Name for a rerun.
I suggest the Optional Job Name text box be added to the rerun submit page.
Prefill using the original job's value if one exists.
Some of our artisans are unable to publish straight from designer and it would be great if there was an "Upload workflow" button in the private studio just like there is for curators in the admin panel.
My team currently uses the API to call a large number of workflows via a Python based scheduler process. We use this currently by having ~10 users in a single subscription (Private Studio).
All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.
From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.
Are there plans to adjust the API endpoints in the future to better account for this?
Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.
We need a way to read a workflow log file while the workflow is running .. we want to peek inside the log file to see what is happening in the workflow, especially for the case when the workflow seems to be "hung". This would be an invaluable troubleshooting tool.
Currently these worklfow log files are locked by Windows and are inaccessible by all but unapproved 3rd part utilities .. if at all.
Often these logs disappear if the workflow needs to be deleted in order to save the environment
It is noted that the service logs do not exhibit this behavior, so the request is to
1) allow the running workflow logs to have the same behavior as the service logs
2) provide a work around to allow reading of the running workflow logs
Thank you for thinking about this