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
currently, there isn't any way to fully delete (safely) a user from the gallery. So if there is a previous client or previous employee in gallery, we cannot clean up the gallery settings - only "disable". It would be great to have a "trash can" symbol next to the users where we can remove them from the server and keep all of the users clean.
As the single user who upload workflow MYWorkspace ends up being very crowded. I move them to collections to be able to share but on My workspace, I can not see which collection they are associated to. It would be nice if there was a column displayed that showed associated collections. As well as being able to have some different types of category classification. I would want something like a development stage: (In-progress, UAT level, deployed, retired) If they are retired a way to remove them off my general workspace area.
As the title says: please make the date modified data more granular e.g. yyyy-mm-dd HH:MM:SS and not 6 months ago
The current behaviour is the same in designer & browser, but is more important in browser (first screenshot) as there isn't an indicator or method or sorting the order.
Given some jobs are scheduled / can take a while to run it would be useful if Server provided the option to notify the submitting user when it has been completed, which a link to the results.
If you look at post: Re: How do I extract Server Job Run ID at runtime - Alteryx Community amongs others you can see there have been various attempts to create workarounds for this using a combination of API's & Mongo DB calls to build up the information to provide a URL in an email at the end of the flow. However, it feels like this should be an out of the box notification that can be enabled/disabled at the flow level with Alteryx Server.
Hello all,
According to https://openlineage.io/
An open framework for data lineage collection and analysis
Data lineage is the foundation for a new generation of powerful, context-aware data tools and best practices. OpenLineage enables consistent collection of lineage metadata, creating a deeper understanding of how data is produced and used.
This is typically the open standards needed for lineage analysis and I think it will become more and more a differenciator with your competitors. As of today, DBT or Apache Airflow already supports it (as producer), Egeria or Marquez already support it (as consumer) and guys from Datahub are working on it (as consumers)https://feature-requests.datahubproject.io/p/openlineage
So I think Alteryx should implement this standard API as a producer, it's the next big thing in Data Governance and you don't want to stay behind !
Best regards,
Simon
after run workflow in server, it has to download output files one by one. it very annoying when the number is huge.
please change like other platform like SharePoint etc. enable select all options and/or download all options.
Improve Gallery scheduling to allow the end user to specify company denoted Holidays when scheduling a workflow. If the workflow is scheduled on a Holiday the schedule would not run. This should be configurable per workflow schedule. Example: A daily report Monday through Friday would be able to skip Holidays based off a Holiday exclusion list.
We leverage Active Directory groups to manage user permissions to most of our company's resources like databases, file shares, applications, etc. This idea is for the ability to manage a Gallery Data Connection via an Active Directory group. In many cases, our AD group membership actually dictates what permissions a gallery connection should have, but we must manually add/remove users to the Alteryx connection to keep it synched with AD.
I think there are several ways Alteryx could be enhanced to support this; i.e. the AD group could be specified on the connection itself or it could be inherited from a Studio where the subscription is enhanced to support assigning AD groups to it (which could benefit other areas of Alteryx).
I'm told by Alteryx support that this functionality is unsupported but to post the idea here. If anyone knows of workarounds to this limitation I'd certainly be interested!
Hello,
There are some tools that helps to monitor what happens on a website. Some are even open source (like matomo and open web analytics). Why not including one of those tools on Alteryx Server ?
There are of course a lot of feature but I like this one, an heatmap to show where a user click
Best regards,
Simon
User who share Apps/Workflows with other users in a collection are not able to see the results of the other users executions directly in the gallery.
Could you please add the possibility to share workflow results in the Alteryx Gallery?
My team has started using an Alteryx Gallery 2022.1 instance and we have workflows that take a few minutes to run. Whenever we run a workflow, we are presented with a blank screen instead of the progress bar that we are used to in previous versions of the Gallery. I was wondering if there is a way of enabling the progress bar or at least setting up a load screen to notify the user that the workflow is in progress to avoid them wanting to re-run the application because “nothing is happening”.
This is what we are seeing:
This is what we are used to and would want to see when running our applications:
Today, when you trigger a job using the Server API, it is considered as a manual run type. In fact there are only 2 type of jobs : "Scheduled" and "Alteryx_Run"
I think "Alteryx_Run" should be segregated into "API_Run" and "Manual_Run". This way in future version we could treat those type of job differently.
We could also have more stats around the type of jobs.
This idea has been touted in different flavours over the years (but not implemented), but I'd like to push it a little further:
1. Create the ability to collaboratively edit an Alteryx workflow - e.g. like you can edit Microsoft documents collaboratively. If the front-end is primarily an XML interface, this should in theory be possible?
2. Version control (not version tracking) - i.e. automatically state the differences in scripts between versions and allow for checking in and checking out of code
3. Power BI & Tableau Prep have the ability to see exactly what changes were made and to reverse steps to get back to a specific stage of development: it would be great to have a panel that tracks all the edits you've made since you started editing the workflow
In simple terms, a modern, interactive way for multiple developers to work together, but also to encourage the use of Server to "check in" your application and to avoid developers saving the same file over & over again locally.
Previously, Alteryx Gallery had a progress bar when the job is running. However, it has been removed in the newer version and the screen only appear blank when the job is running. This could lead to confusion in users as they might be wondering what is happening when the screen goes blank when it actually is running the job. Users might also attempt to click the run button repeatedly due to this.
Hence, I hope Alteryx could bring back the old UI that showed progress bar or anything similar when the job is running so users will aware of what is happening.
It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).
My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events. On a large implementation, this becomes very difficult to manage.
When adding jobs to the queue via API call, you currently cannot specify the name of the job.
Running the job directly from gallery allows this as in the picture below, but there is no setting to do so in the API.
When a workflow is used in many different situations, being able to specify a name for the individual run will make tracking and troubleshooting easier.
There is no good way to get server user credentials into a workflow without asking them for it in an App interface. It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.
One of our Server customers has a need to disable all schedules temporarily across all worker nodes. I do not see an easy way to do this unless we go into each worker's settings and disable from there, but this is not ideal.
The reason is for scheduled maintenance windows during a large upgrade or migration. Currently stopping the Alteryx Service on each worker is time consuming.
Thank you!
Hi all,
Having all the schedules/results centralized in the same place would be neat!
Option 1: Have all on the same page and have an additional column to describe the shared source.
Option 2: Have a separation between my own schedules and the ones shared with me.
Best,
Fernando Vizcaino
I would like to propose a number of small enhancements to the Gallery:
) is confusing to everybody except Americans. Please add support for a 24-hour format. This could be done either by extending the Locale settings or by a separate check box. Please make sure that this time format is used everywhere in the Gallery (last update, last run, schedule, etc.).
User | Likes Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |