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
Use case: I need to schedule a workflow to run every 2 hours each day, with the first run at 7am and the last run at 7pm
Current solution: I need to create seven daily schedules for each hour that i need the workflow to run
Idea: Add an intraday "Start Time" and "Stop Time", or "Between" to the "Minutes / Hours" schedule type, so i can create one schedule that meets the use case requirements
Example schedule with new parameters that meets use case requirements:
Start Time = 7:00 AM
Stop Time = 7:00 PM
Repeat Every = 2 hours
Start Time could default to 12:00 AM
Stop Time could default to 11:59 PM
As Alteryx leans more into the Data Science space - it becomes more important to be able to keep rich documentation of the project along with the Alteryx Asset. This does also require the concept of a "project" on the alteryx server, which would allow for meta-tags; and various different documents to be added with the project.
This would include things like Requirement documents; test evidence; test data sets etc.
This would extend Alteryx from a data prep engine to more of a data-science workbench as different user groups can participate in a specific project.
It would be helpful to have a central Logging tool for large & complex environments.
This would be useful to allow teams to have a central way of logging data transformation errors by error-type; severity; alteryx Canvas; etc.
Right now, there's a message tool, but this doesn't provide a way to create well structured central logging across a team; especially once deployed to a server environment.
CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh
Hi,
The schedules page on server needs an overhaul. Sorry to be so blunt but it is awful. It is by far the worst aspect of Alteryx and one of the most important at the same time.
Here are a few points about it...
1.) Sorting needs to be fixed as it doesn't work correctly (sorting on the first column, "Workflow", returns items that start with 'L', 'S' and a zero as the first three on the list), so looking for 1 scheduled item across 10+ pages of schedules becomes a "needle in a haystack" endeavor.
2.) There are no search and/or filter capabilities which would help alleviate the pain-point mentioned above.
3.) [Missing] items automatically removed from schedule when the workflow is removed from the server. It just jumbles up the screen with useless information.
4.) The 'Schedule' column doesn't need to reflect the name again like the 'Workflow' column. is a hyperlink and the other isnt. I cant tell you how many times I have clicked on the wrong hyperlink only to have to go back and deal with point #1 all over again. Can't it just be a simple calendar icon or something like that next to the Workflow name?
5.) While not as critical, but more of a 'nice to have' function. An ability to export the list of schedules would be helpful. If we ever need to divy up work for an employee that leaves the company it would be a good way to see all of the work they have out there and mark up the list to distribute info for reassignment purposes, etc.
I am sure there are other aspects I am missing, but here are the most important ones to me as an end-user (Not an Admin)
Thanks for listening. 🙂
Today, if I want to save a job onto the Alteryx Gallery, I need full permissions to do so and it is a manual process. For some organizations, this level of access is deemed excessive, which can make properly leveraging the Alteryx Gallery difficult. Having the ability to write a "deployment" script that could publish a workflow to the Gallery, and potentially add a new workflow to a Collection would be incredibly helpful in these cases.
Alteryx Server does not presently support any file encryption systems. Many people need to encrypt there Fileshare as a secure measurement and use safeguard lan encrypted. Please provide a solution so workers are able to read and write encrypted files through safeguard lan encrypted.
It should be possible to schedule chained apps. Particularly useful when the first workflow in a chain runs a check and if the check returns true then the next workflows run and if the check returns false then the next workflow should not run.
Possibly related to:
Schedule Configured Analytic Apps - Alteryx Community
When posting an app to the Gallery, if the app has, say, one PCXML output for the user to see, and one Excel file for the user to download, it would be helpful for to be able to specify which shows first to the user. For example, I have a PCXML that gives the user summary tables, and instructions on how to go to the drop down above and select the second report, click on the Excel icon, and download it. But if the Excel report shows up first, then there is no ability to give them instructions and many simply won't be savy enough to go find the PCXML in the drop down.
Hello Alteryx Developers,
It would be great if you develop a way to connect the Alteryx Designer to AWS Redshift by SSO. When i try to set this type of connection at the Simba ODBC Driver it opens the connection several times with AWS at the browser and that ruin the customer experience.
Best Regards
Danilo Benjamin
Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful.
Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline. I’ll share both files soon.
Here are the top 5 features for the Scheduler.
Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field.
Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning. Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows.
FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.
Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db.
Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx.
Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows.
Big time user of the Gallery API. In fact, I wrote an R package for it (shameless plug: https://cran.r-project.org/package=alterryx).
It is great that you can queue a job for an application using the Gallery API but it would be great if I could also cancel a running job.
I would like to collaborate with my team, but also maintain my own personal private studio.
Is that on the road map?
-Dan
In order to migrate workflows from our UAT environment to a Production server environment, we are looking for an API capability to work with the server:
- Query canvasses by name or ID (to get a list of canvasses)
- Extract Canvas to a particular location (by ID)
- Upload canvas including dependancies (with parameters for team; collection; etc)
This would assist with automating the UAT to Prod process until Alteryx Promote can step into this gap.
CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh
Hello,
We recently upgraded our on-prem instance of Alteryx Server/Gallery to version: -
We have noticed that the search functionality in various areas (top and right-side) no longer return results using a "contains" but rather it is doing an "exact" or "starts with" keyword search. This is very frustrating to many users as we can't easily find our workflows quickly compared to previous versions.
Please improve search functionality.
If a job fails it would be perfect if we could set something in the workflow settings so that the job would retry again in X number of minutes for the next Y number of times. We have jobs that connect to external resources and sometimes the network will reset and will cause the connections to all drop. An example would be I want a workflow to try again in 10 minutes for a maximum of 5 times so over the next 50 mins it will retry every 10 mins if it fails
It would be nice to have an inbuilt function(s) that return an identifier (NTLogin for instance when the gallery is setup with windows auth) of the user running the app on the gallery.
Functions like - USERNAME(), DOMAINNAME() etc., helps.
I know that it can be achieved via the "__cloud:UserId" call , which is not officially supported by alteryx. It adds value if it is inbuilt within the product itself.
Regards,
Sandeep.
Our company has workflows where we use the Gallery API to kick off executions on server. The user kicking off the workflow has setup API access using his account, but when he kicks off his jobs, it does not show up under his Gallery so he is unable to view the results. In the admin panel, it shows the owner as (None) so it does not appear that workflows kicked off via the API get assigned to the user tied to the API key.
Conversations with Alteryx support revealed that these results are available via an API call, but not within the Gallery web UI. It would be great if the user tied to the API key were added to the workflow execution so they could see results within the Gallery rather than going back through the API.
User | Likes Count |
---|---|
6 | |
3 | |
2 | |
2 | |
1 |