Featured Ideas
Hello 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 a user saves an APP and that APP contains macros with embedded macros (2 to N layers deep). Make package with ALL subroutine/macros included an option. This is a PAIN for users to try to manage otherwise.
cheers,
Mark
- Enhancement
- Scaling
- Settings
Hello Community!
I really enjoy the concept of the Data Connection Manager, but we have controls in place that don't allow our users to share database connections with each other - the official data source owner needs to approve. We have been able to do this with the typical Data Connections through Active Directory groups that we load into Gallery custom groups.
It would be nice to be able to allow users to create their own data connections to be shared but we would like to add a couple of governance features:
- When an Artisan wants to publish a data connection to Gallery, they publish it to a shared space (could be within collections). For example, they could share to the HR Data Connection space.
- That shared space is governed by custom groups in Gallery, similar to assets in a collection for workflows (who can access, who can add, who can modify, who can remove, who is the owner)
- Ideally, we would also like to have more of a submission process - someone can submit a data connection, and then a data owner can "accept" the data connection. The data owner would then check to see if they are connecting properly before it is added to the shared space.
- AdminUI
- New Request
- Permissions
- Scaling
sometime the schedule workflow is too heavy and take few hours.
it impact the normal workflow run. as it take all workflow slot.
so my idea is to limit the schedule workflow and always leave space for manual workflow.
to avoid delay of both work.
- New Request
- Scaling
More of our customers (we are a premier partner) have Servers with multiple worker nodes. If a custom macro is needed, currently it has to be added manually on each worker node.
Would love to see a feature in the Admin portal that allows for the upload and distribution of custom macros to all or select workers.
- New Request
- Scaling
- Server
I am an Artisan but not the Owner of the studio - I uploaded the workflow and would like to see all the jobs (including manually triggered) that run for my workflow so I can track any issues i.e. when workflow fails. I checked with the Owner of the studio and he also can see only the runs he triggered.
I understand from the Support team in my company that option to see all the jobs that run is currently available only for the Curator role but would be extremely helpful if you would make it available to all the users that have access to the Private Studio.
- Enhancement
- Scaling
- Server
I would like to see ability to limit the number of versions a user can save of a workflow. As a server environment ages we start to see the database become unnecessarily larger because the number of version of workflows. For servers related to DEV and QA environments as an Admin I would like to be able to say users can keep their 10-25 most recent versions of their workflows. Then anything over that will start to auto-delete just like the auto save feature in Designer.
- Database
- New Request
- Scaling
- Server