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
The current Enterprise Utility Workflow does not have a match/look-up in place between the two environments for user ID's. Thus, the migration workflow doesn't work without adding in a couple extra API calls. When we upgrade to a new version of the utility, I have to add this back in.
It would be nice if the workflow would come with this already configured.
Hello,
Could you make it possible for curators to administer DCM connections created by other users?
Currently if one of the curators creates a connection, then only that person can modify it and give other people access to it.
Therefore if the person who created the connection isn't available then nobody can be given access to the connection.
Any curator can manage legacy gallery connections so to be able to move away from legacy connections and use DCM connections instead we need the same administration capabilities for DCM connections.
Thanks.
Hello all,
Right now, we can choose either MongoDb or Microsoft SQL Server as a backend. I would suggest to add Postgresql. Why ?
-it's open-source
-it's reliable
-it's free
-it works well on many environments
-it's popular
-it's already used as backend for Tableau or Qlik and many others
-it respects SQL norm and doesn't have a lot of specificity
Best regards,
Simon
Workflows which are scheduled and continuously failing in a row 5 times need to stop/disable the schedule. Sent a mail to the workflow owner stopped schedule due to continuous error.
For Administrating the schedule workflows this feature helps a lot. Many users create workflows and dump into server and schedule it and forgot it if we implement this strategy, it will be helpful to both users and Admin team.
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.
Please could all log file paths on Server have the option to change their location, including
C:\ProgramData\Alteryx\ErrorLogs\AlteryxE2
To enable all log files to be written to an alternative drive than the installation.
The benefit it to prevent excessive space usage on the C: drive
Support have advised there is no way to alter the path or limit these log files by number or size.
Many thanks.
Alteryx DCM has been an incredibly useful addition that supports key security concerns from companies. Currently, only three external key vaults are supported:
Hashicorp Vault (KV secrets engine) - supported for Designer 22.3 and later.
CyberArk Conjur - supported for Designer 22.3 and later.
AWS Secrets Manager
https://help.alteryx.com/current/en/designer/tools/dcm---designer/dcm-external-vaults.html##
I propose that we also include Delinea Secret Server.
Thank you and hopefully we can start to add more to make this feature widely useable and support security compliance.
Maintaining multiple workers (five currently, soon, six) with identical setups is challenging when dealing with In-Database (InDb) connections. I must log in to each worker, start Alteryx Designer, go to In-Db settings, and create the connection. This also becomes tedious when trying to update passwords, which occurs every 90 days in my company.
The suggestion is to set up an In-Db connection on one worker and have it propagate to the other workers.
Propagates to other workers → |
This would save time maintaining workers in the gallery and help prevent errors during setup on each worker (e.g., typing in the wrong password).
As an "extra credit" mission, expose In-Db connections through an API that can list, create, update, or delete an In-Db connection.
Hello! We just upgraded to 23.2, and I see in v3 an endpoint to start a job (v3/workflows/{id}/jobs) and then another to get that job's status (v3/jobs/{jobID}). Compared to v1, I think the outputs endpoint is missing (v1/jobs/{jobID}/output/{outputID}). I'd love for this to be added so we can upgrade from v1 to v3.
The dcm admin apis look promising. I would love if they could add put endpoints for sharing/execution and sharing/collaboration for admins. There is already a delete command for those two endpoints
I want to let my artisans choose the collaboration option when sharing dcm sources. Currently they'd have to be promoted to curators to do this.
On the Job page, in addition to seeing the worker tag that a job is running on, it would be great to see which server the job is running on to ensure the work is being spread out and look for bottle necks. We have a group on servers broken down into Small , Medium and large with several servers in each group. Looking at the current screen, you can not tell what server a job is running on within the group. Example, 'Large' has 3 servers with 4 jobs running on it. But you can not identify which server the job is running on.
I just underwent an exercise of recovering my controller in the event of a catastrophic failure. One of the steps is to recover the DCME keys (DCM Encryption keys) - which is documented here: https://help.alteryx.com/20221/en/server/install/server-host-recovery-guide/dcme-keys-to-backup.html...
This DCME recovery needs to be revisited. This document assumes that the previous controller is running. In a disaster recovery situation, this is not possible. What, if any, can be done to recover the DCME keys if the host has is completely irrecoverable?
For context, having an irrecoverable host has happened. Complete hard drive failure (showing my age), nuked virtual machine and its backups (no one paid attention to the notices that the data center was shutting down), and fire.
I develop workflows or analytical apps in the Designer and save them in a Gallery. If I need the setting "Always run this workflow with these credentials", I have to type in my username and password every single time I want to save it, even in the same Designer session. This is very annoying and results in saving the workflows much more seldom than I would do if I did not have to type in the credentials every single time.
My idea is to cache the credentials (login name and password) for one Designer session. It would be perfect if it was for the entire Designer session for multiple files. But even if it was specific to the opened file it would help.
Result would be:
Currently, we see the Districts and Collections now compressed into a list view.
Previously, the Server had the widgets feature which really showcased the self-service nature of the Sever. Losing that just made decreased the emphasis on user experience.
It would be great to allow Server Admins to decide whether they want lists or widgets to be available toggles as a design feature for both districts and collections will be of great help.
In addition, regardless of the option, the image size and wording size should be much larger - easier for people to see. Right now, we have to zoom to 150% to make it easier for ourselves to see. Having the ability to control font size, font control with bolds, italtics, etc. will be very helpful as well.
Admin option to restrict certain tools to not be used on the Gallery - Run, Python, Email, and R - without Safe or Semi-safe mode
Enhancement request to add the ability to restrict the ability to make workflows public
Admin ability to put restrictions specifically on the Designer email tool.
The Users, Workflows, Collections & Schedules tabs all have hyperlinks to the relevant sections of administration. However, this only shows the current 'as-is' active state. What would be useful is for each number show to have its own drillthrough to that subset of data, i.e. clicking on Inactive under users takes you to a list of inactive users, similarly clicking on Active Jobs under Schedules takes you to the list of actively running jobs etc.
This would provide a more intuitive navigation for admins.
As we have more and more users onboarded to the Server, and many users share similar names, it is getting more and more complicated to manage.
It will be great if we have a management console that allows us to create User Groups, Tags, set User Departments, and more controls alongside their curator, designer, etc status on Server.
Groups like User Groups gives a group of people access into certain workflows, districts, collections, etc. It will also be helpful as it can also be an audit trail of who ran what - with a feature that allows users or groups of users to run certain tasks or schedules.