Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello all,
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensing-our-products/ta-p/158030
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 :
https://www.amd.com/en/processors/epyc-7002-series
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.
Best regards,
Simon
Although the connectivity to the eMail infrastructure is set up on the controller and worker nodes - there is no ability to set up automated alerting for errors on workflows from the server.
We would like to be able to set up the gallery as follows:
- Every job is owned by a user or a distribution list
- If that workflow throws an error or warning (this should be configurable on the server, whether warnings are included), then the author should be e-mailed with a link to the specific workflow and the error log.
This can be done in a round-about way, by running an error-reporting alteryx job after the fact - but this kind of alert needs to go out almost immediately given our dependance on Alteryx for specific SLAs.
cc: @avinashbonu ; @Deeksha ; @revathi
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
Currently the Gallery's Admin API is a bit light on functionality. It only works with data connections & workflows and not regular server admin functions. Endpoints I'd love to see, but not limited to, are:
I have been trying to scan all of the workflows that are stored in the gallery and wrote this community post about it. Some Alteryx employees reached out to me directly to see if they could help solve my problem. We ended up with a somewhat wonky roundabout solution (that I haven't implemented yet) by downloading yxzp files through the Gallery API, unzipping them, then scanning the workflows as xml. I think the process could be greatly simplified if Alteryx had a set of Introspective tools.
The introspective tools would use similar, if not the same, processes that Alteryx already has in place to pull data from the gallery/server itself. The set of tools would be most useful for Server admins or people that are trying to build meta-workflows for Alteryx to make things easier for their users. Similar to the solution to my problem above, most of this functionality can be worked around by querying the Mongo and/or scanning engine logs. The Introspective tools would simplify this process greatly, especially when it comes to joining records from the Mongo and collecting workflow-internal data.
Since the tools will have direct access to the gallery/server it would make sense that they would only be available to machines with server licensing or could be made available if the user has a high enough permission level in the gallery they are trying to obtain data from.
We are hoping to move to Mongo Enterprise as the backend for our Alteryx server, however we may not be able to given that Alteryx does not currently support Kerberos & Keytab authentication.
Please could you add this to the server so that larger clients with Enterprise Mongo can scale upwards?
One of the issues that we have with Alteryx jobs in prod (and also Tableau, coincidentally) is that often a canvas is built to serve a need at the time, but after a while it's no-longer needed but it continues to run and consume server resources.
Can we add the option to our server environment to request recertification that a particular job is still needed every X months.
This will achieve 2 useful purposes:
- if the job is no-longer needed then the user hits "No thank you" and it's then taken off the scheduler which reduces server loads
- Alternatively - the user may realize that this should have been handed over to a new team or owner, and they can then make this change based on the recertification prompt.
I'm pretty certain that this would help to manage the inevitable build-up that happens on server environments where jobs build up until the server starts thrashing and the admin team then need to go out to all the users to do this recert process manually.
CC: @rijuthav; @jithinmony; @HengHe; @RajK; @ydmuley; @revathi; @Deeksha; @MPistone; @Ari_Fuller; @Arianna_Fuller; @JoshKushner; @samN; @avinashbonu; @Sunder_Sriram; @Rahul_Thakur; @Rahul_Singh
It is currently (Alteryx Server 2018) not possible to delete Districts one created - we can only disable them. See also: https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Deleting-Gallery-Districts/m-p/32684
Frankly, this is rather inconvenient if one wants to restructure a Gallery. Renaming them is an option, but there might still be a number of districts we want to delete. Would appreciate if this could be considered for a future update.
Hi Team,
The Alteryx API documentation for Audit was only available for certain entities(workflow, collection, etc.,) and not available for Schedule entities
If you create a schedule in Gallery, information about the schedule like creation date time, frequency, owner, type, last run, next run, etc. will be updated in MongoDB. If a user edits or modifies a schedule in the gallery, the edited/updated information is only available in MongoDB. There is no possibility of seeing audit information like old value(before change), new value, or operation (update, delete, insert).
We required the Audit information of the entire gallery operation such as schedule, Collection, Workflow creation, updation, and deletion.
Regards,
Ariharan Rengasamy
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.
Thanks,
MJ
Please support GZIP files in input tool in Server. This is related to https://community.alteryx.com/t5/Alteryx-Product-Ideas/Support-for-GZIP-gz-compressed-files-in-input..., but logged in a separate Idea because the staff indicated in the thread that they are planning support for GZIP in Designer only in 2018.2. We need it in Server as well.
We have the Local License Server installed. Right now, if a Designer user changes roles, or leaves the company, they have to release their license from their client-side machine. If they don't release it properly, and IT can't get us into their machines, then we have to wait 7 days for that license to roll off the server. There should be a way for a system admin to forcefully revoke someone's license.
It would be nice to be able to change the Gallery URL from:
to:
The reason being to make it easier for end users to find the server/content.
Original forum post here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Changing-the-Gallery-URL-on-Alteryx-S...
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.
cc: @JohnPelletier
Would like to see a Notification hierarchy implemented to Gallery. Currently, the settings that control notifications are at the Gallery-level....where only the admin can control, for example, notifying users if a new workflow was added to a collection they belong too. Could this setting be inherited, but then, for example, a Collection owner can implement their own notification settings that overrides the Gallery default? Using the same example as before, perhaps the Collection owner could disable notifying their Users if a new workflow is loaded to the collection.
Nick
Isn't it great that we can toggle between outputs from an app in the Gallery, being able to view and download each one? Yes! However, what if an app produces a lot of outputs...such as 1 per state...or 1 per product type...or 1 per month...etc. What is get is something like this:
Now imagine how long it would take to download all of these...ouch. I recommend Alteryx add a "Download All" button to the page that appears after an app finishes running.
Related Community Post here.
Hello,
Tableau has a nice Postman Collection available... it's really easy to use since you can download or forkt it on Postman and all you have to do is to write the variable values.
I would like the same thing but for Alteryx.
Best regards,
Simon
It would be nice having the ability to alter the timeout of the file upload on Alteryx Analytic Apps uploading to the Gallery. Having it restrained by time and not file size makes it so that users with poorer internet speeds will not even be able to upload moderate sized files.
In the gallery you have the ability to replace a workflow with another, however when doing so the version history only indicates "Package Replaced" (see image below)
Would it be possible to change the default text and input something more meaningful, since in my case I use this field for version control/auditing so it would be good to know what changes came with the replaced version.
Second ask, but maybe not as important as the first.
Sometimes the package we are replacing with itself might have several versions, but these are completely lost when the files are combined.
Would it be possible to keep that version history when the package is replaced.
Eg. Original File is at Version 10. This will be replaced by a package that is at Version 3.
Possible solution would be to have the new version be Version 13 which includes the 10 versions from the original file and the 3 from the new.
Thanks!
I have Designer Apps that work really well using the Browse tool to provide the outputs to display and download in the Apps.
This does not work when I push the Apps to Server.
I find this very restricting and would like to suggest that the Browse Tool be enable to generate its outputs in Server Apps.
I would like the Browser outputs to be enabled for download into Excel, PDF, etc as well so the Server Apps behave in a similar way to the same Apps in Designer.