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
Given the security requirements of our company collections need to be created centrally, which is fine for sub-organizations that only require one collection. However, the large sub-orgs require more than 1 collection, ideally we would create the top-level collection and give the sub-org the access to create their own sub-collection within that collection, but not the ability to create collections at the top-level.
In an enterprise multi-node Alteryx Server deployment that has existed for many years and many upgrades, there are artifacts within the MongoDB that are unknown to Gallery Administrators. I envision a workflow or app that is developed by Alteryx that queries the MongoDB and looks for orphaned documents in the MongoDB across all collections. With 2022.3 there is a pre-upgrade check, however, it does not find all unexpected items within the MongoDB. Regular ongoing MongoDB health helps with overall management of the environment and could prompt for support cases before it becomes a problem during pre-upgrade activities.
When you add a workflow you have to add its schedule to share the results in collection menber's.
A workflow can be in several collections and therefore different users can schedule it. (why not)
This results in multiple schedules for the same workflow. There is no reason why a workflow cannot have multiple schedules.(mandatory in some cases)
Automatically adding schedules to the collection would allow users to see that there is already a schedule on the workflows in question and not to recreate one!
it should also be possible to create a schedule from the collection.
Hi Alteryx support team,
We would like to use the search functionality available in the schedules tab of Alteryx gallery and when anyone searches the schedule by typing the name in search box on schedules tab, he/she should get list of the results along with the schedule information such as frequency of schedule, times run etc.
As of now, when one searches results are displayed as jobs and their run history.
Case reference - Alteryx, Inc Case # 00606791
Regards,
milan
Hello all,
According to wikipedia https://en.wikipedia.org/wiki/Webhook
"A webhook in web development is a method of augmenting or altering the behavior of a web page or web application with custom callbacks. These callbacks may be maintained, modified, and managed by third-party users and developers who may not necessarily be affiliated with the originating website or application. "
An example : whoever publishes an asset, I receive a notification on Teams and when a scheduling task fails, it creates automatically an analysis task on Trello.
Seems cool, huh?
Guys at Tableau have implemented it (https://help.tableau.com/current/developer/webhooks/en-us/ ) and so do the guys for Qlik Cloud.
Best regards,
Simon
Idea: Option to receive an email notification when a schedule gets disabled (could be added in the user settings, see attached picture)
Business Impact: The implementation of this idea would reduce delays that might even have a financial impact because
not receiving any notifications when a schedule was disabled could lead to
I would be glad if you could implement this idea because I think it would be useful for a lot of people!
Hello all,
Nowadays, chatting, commenting, having a discussion on assets that are published on a server is a very common feature, and a useful one !
Here an example on Tableau :
Collaboration is not a luxury item !
Best regards,
Simon
Today, when you share a workflow with someone else through the collection, you cannot see the manual run that the person will do, neither the person will see yours.
This is really annoying as this is not helping collaboration between colleagues.
Since we use an external scheduler and the server api, only the job owner will see the job execution results within the gallery.
Idea here would be to let the sharing of job execution result as an option in the collection.
When scheduling an analytical app on Gallery, there is no UI for submitting app values. This significantly limits the value of scheduling workflows and using analytical apps. With this feature, it would allow our users to have more flexible scheduling while also simply maintaining one workflow. Because this feature doesn't exist, we have had to build workarounds by either creating multiple workflows or utilizing APIs.
Since this feature is already available for manual runs and APIS (shown below), it shouldn't be a reach to also have this feature when scheduling a run.
Manual Method:
API Method: GET /workflows/{appId}/questions
Scheduling Method (no app questions):
We want to share direct links to analytics apps with our users. However this does not work with our current SAML login. This the use case.
1. User clicks on direct link URL for the app
2. User is required to click log-in button
3. After login user is taking to the gallery home page not to the app
The end effect is that we cannot share links to apps with our casual users, instead we have to instruct them to go to the gallery log in and then search all public workflows for the specific app they are looking for. Not a great user experience, especially because we did not have this issue before single sign on support.
personally I think this is bug more than a feature request, but was asked to create it as a request by support
This is an issue that has been marked as solved, however it isn't.
The problem still persist. When you have a macro with a gallery data connection, the workflow containing the macro gives an error when run on the server: 'Unable to translate alias'
If you select manage assets, then include any macros when you publish, this bug is gone. That's the fix.
But this is not a solution because if someone updates the macro, the containing workflows will still use the old, included version of the macro. You will somehow need to remember which workflows use the modified macro, download them all, include the new version of the macro and republish the workflow.
Well, I can't see how this is a fix to the problem. It's probably better to just keep using the old disabled container 'fix', which is also quite painful.
When I manually execute a wf on Gallery, I sometimes have a tinge of regret that I don't have email events set for the workflow. In most cases, it's just THIS time that I want to receive an alert and not every time. At any point while the workflow is executing, allow the option to request an email event to be sent out for this execution.
I'd like to request the ability for the Curators to change the priority on Apps in the Gallery.
Today we have a system where users are not allowed to set the priority on workflows. The Curators change the priority of scheduled workflows based on workflow runtime/ business need by going to Gallery Admin> Jobs> Scheduled Workflows, and then editing the schedule priority.
The problem that that we have a numbers of Gallery Members/ Viewers that run Apps through the day that are very fast to run, but depending on how big is the queue they can several minutes/ hour until a spot is free to run.
If would be very helpful to get a better UX if the curator can choose which apps should have a higher priority to run.
Thanks,
Mauricio Estevez
I manage a server with 200 + Artisans. Some of them tend to abuse the Scheduler by having workflows running every hour or every x hours. This can penalize other users creating big queues thought the day. Currently I monitor the queue and schedule often and then contact these individuals to better accommodate their needs.
Having the possibility to disable hourly workflows, or enable to only specific users, would help a lot to deter the abusers.
Thanks,
Mauricio Estevez
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.
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.
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.
Currently it's impossible to tell which worker a job is running on. Add a column to the jobs view that shows what worker a job is currently running on.
Currently, if we want to assign a worker node it has to be done at the workflow level. It would be very helpful to be able to make a rule that auto-assigns the type of workflows to a specific node, so all apps go to one, all schedules go to another, etc.
At the very least, if there was an API endpoint to update specific items on a workflow (such as node), this would work as well as we could then build a process that auto-assigns.
Thanks!
User | Likes Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |