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
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
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
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.
As a Gallery Admin I would like to be able to add and remove a user from local groups on the User page.
I realise that this would only work for local groups and that AD groups would need to be excluded (and indicated as unavailable for editing)
On the Users page it is quick and easy to see what Role each user has - UNLESS they have been assigned the "Default" role in which case it will depend on Gallery Default Role and which Group(s) they are assigned to.
I propose an additional column be added to the page to show the Effective Role for each user. The purpose of this change is to allow an administrator to quickly and easily confirm the effective Role of any Gallery use by viewing the User page, without having to check the user's group membership and the Role assignment that those groups provide.
For those users with a assigned Role other than "Default" that value will obviously match the assigned Role.
For users assigned the "Default" Role the page should show the result that would be returned by the appropriate permission resolution code when determining their effective Role from the Group membership and the Gallery Default.
[Screen image is from 2020.4 - with my suggested positioning for Effective Role added]
As a further enhancement a set of checkboxes showing the value of the special permissions e.g. Create Collections, would be good but might require a more significant re-design of the page and would only be saving a single click. I suggest instead that it might be useful to have an enhanced filter view of users which allows an administrator to view e.g. all users who can Create Collections etc.
The AlteryxService internal authenticated API that the nodes use to communicate with each other for status is not accessible to customers because it is using an undocumented authentication method. The data this appears to provide would be useful to server administrators to determine the true health of the individual nodes and for reporting purposes.
Hi all,
For a user to know if a schedule was successful or not, they need to go schedule by schedule to check each of them.
I suggest adding one additional column to show the status of the last run.
Something like this:
Thank you,
Fernando Vizcaino
At the moment when you give the "assign job" permission the user can choose any worker, it would be great if there was a way to assign workers to users or groups.
Example 1 (worker 3 is assigned to one group):
Worker1 - Assigned to ALL
Worker2 - Assigned to ALL
Worker3 - Assigned to ArtisansGroup1
In this scenario, all Gallery users have access to Worker 1 and Worker 2 and the ArtisansGroup1 has access to Worker1, Worker2 and Worker3.
Without a doubt, Schedule Forecast is a great feature. I feel Schedule Forecast feature should be enabled for Artisans as well who usually create new schedules on Alteryx Server. Artisans can look up the existing schedule details at a specific time and decide if it is best time for their workflow to run. It will be counter productive otherwise in my opinion as curators have to inform the artisan to move their schedule to some other time as there are several other workflows running at the exact time and impact execution time.
Currently you can only view the workflow results / history for other users workflows that are scheduled and the schedule is shared in the collection.
A lot of our workflows are set up to run on-demand, some as analytical apps and some as standard workflows.
The first point of reference when a user experiences an issue should be to view the workflow results, but currently this is not possible and just gives an error "Access Denied" even when the tick box is selected within Workflow settings.
My suggestion is that you should be able to see the workflow results of any workflow that is shared with you (regardless of whether it is scheduled or run on-demand) as this would make fault finding and user support much easier.
Thanks
Rob
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.
Thank you,
Daniel
Currently the default 'Rows Per Page' is set to 10 when within various pages on the Gallery.
As we add more and more Apps to our Gallery it would help to be able to increase the default so it is higher than 10.
This will help ensure users do not forget about or miss tools that are available to them which are hidden on other pages. Additionally, they will not need to remember what page to jump to if the App does not pull through to the first 10 rows, or prevent the need for them having to increase the number of 'Rows Per Page' themselves.
The workflow result window shows the Name/workflow, AMP, Priority, Assigned worker, Run as, Completed at, Runlenght, and Runtyp of the workflow. The following feature would also be useful on the page.
1. Showing the creation date of the workflow without taking queue time into consideration
2. The option to change the time zone would make it easier to analyze the logs
3. Detailed insight about the particular workflow results, such as average execution time, failure count, and success count with date filtering.
Hello!
I found a weird bug in my travels today.
The TL:DR is that when a date input tool within the interface tool is used within a collapsing radio button, it defaults to "dd/mm/yyyy", breaking any app when this is not filled out:
Both values are default - i have not edited these values. The weirdest part is, this is Server/Private Gallery specific. When this workflow is downloaded and run within Designer:
And the workflow runs fine.
I have not tested this with any of the other interface tools, however I suspect this to not be the only tool this issue resides within.
I have attached the workflow I used (not that it would take long to recreate) for testing.
I would like to see some functionality in the Alteryx Gallery in which you can select multiple schedule workflows to disable/enable. Currently as an admin if I have many schedules I need to enable/disable I need to go into each schedule manually to disable or enable. This is okay for one or two, but I have about 20-30, it is very time consuming. I would like to see maybe some checkbox functionality next to the workflow to select and then an option to either disable all selected or enable all selected.
Currently, only users themselves are able to setup the default worker tag in their My Profile page. To ensure efficient management of worker nodes, Server Admins or Curators should be allowed to set the default worker tags of gallery users, preferably in bulk. This will help avoid workflows to be executed using the wrong worker node.
We have at the moment our server configured to work with SAML credentials. Whenever a user sets the credentials option to be "User must specify own credentials" the validation is performed using the servers own local user, giving out an error whenever some workflows with SSO data access are uploaded.
It would be great if a window would pop up or credentials could be configured for the validation to aviod seeing the error to show up.
The current Gallery API executes a job until it reaches a completion state with either success or failure. Once reaching that state, the callout to /v1/jobs/{jobId}/ will return an array of messages that can then be parsed to gather information about the execution of the job, similar to the output you see in designer or via the CLI when running a job directly.
It would be nice if the callout to the jobs endpoint would constantly update and return the messages array with each callout. With jobs that take longer to execute, our Gallery API wrapper could then report back to us and let us know what messages have come out as the jobs runs. For example, if a process takes 2 hours to execute, we might want to know how far along the job is or if it has met a special condition that will cause it to run longer, etc. To do that, we could add in message tools that report info messages to us. Unfortunately, these messages are ineffective if we are running via the API because we won't see them until the job has fully completed.
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.
User | Likes Count |
---|---|
3 | |
3 | |
2 | |
2 | |
2 |