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
Hi
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?
Thank you
Tom Diroff
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:
Currently, this is completely manual with whoever is assuming the schedule creating it under their profile and then the old schedule being deleted.
This can happen often in organization where a user leaves the company or assumes a new role requiring some else to maintain those schedules. It would be convenient if there was an option to reassign the owner of a schedule to simply this process.
Hi,
We have more clients that would like to prioritize their scheduled jobs based on run time and importance.
It could be a simple priority number, that decides which job that need to run next. Further it could be nice to be able to allocate certain workers to certain jobs.
I am looking forward to your feedback.
Daniel
I wish Alteryx would allow more control over user access to scheduling workflows. Currently there is only a radio button that globally allows users to access the scheduler. I wish we had another layer where we could limit access by Permissions. For example, we would like all Artisans and Curators to have access to the scheduler, but not viewers.
Hi
My idea is to facilitate scheduling through Gallery vs the separate scheduler built into Designer. The reasons for this:
Thanks,
Ryan
I’m facing issues with scheduling workflow in Europe/London timing. I’m trying to schedule jobs to run at 10pm UK hours everyday (except Fri and Sat) starting from today i.e. 26th Jan (as per UK timing)
However since I’m in India and my local desktop is showing India time (which is 00:15hrs on 27th Jan), the Alteryx Gallery scheduler is picking India hours but not as per the region we selected. The 26th Jan date is greyed out and unable to select.
The workaround for this to change local time on desktop which is not in our control in our case.
Could you please bring a change in this behavior. If I am am scheduling on x date a workflow for a timezone which is x-1 the scheduler should allow me to set up the schedule.
User | Likes Count |
---|---|
10 | |
8 | |
5 | |
4 | |
4 |