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 V3 jobs API endpoint woefully lacks any usefulness. The current endpoint only has a get jobs/{jobid} method that is not useful because a database admin must query the database to get a list of all job IDs. To add insult to injury, this method is only limited to the user whose job is running or queued.
These are new features that I am proposing
1. GET jobs/list—This method must be callable by all users. Parameters such as none (default—full list), running, or queued will display jobs with the appropriate status. The job ID of the running or queued job and the worker it is running on must be included in the resultset.
2. GET jobs/{ownerid} — This method must be callable by all users. Like the GET jobs/list above, the resultset must include the job ID of the running or queued job and the worker it is running on.
3. DELETE jobs/{jobid} — This method must be callable by the person who scheduled the job, the owner of the workflow, or the curator. This method is the equivalent of cancelling a job on the Server Admin page - #!/admin/jobs by a curator. All three mentioned people have a vested interest in the running or queued jobs on the server and must be able to cancel those jobs.
4. POST jobs/reassign/{jobid}/{new_job_tag} — This method is restricted to the curator and applies to any job in a queued state. It allows a curator to reassign a job to another job tag or the first available worker for reasons determined by the curator.
This is an enhancement that I am proposing
1. GET jobs/{jobid} — This method must be callable by all users. This will allow any user to get the details of any running or queued job.
Logging requirements
All DELETE or POST methods must be logged and purged based on the Persistence Option > Delete queue and results after (days).
I would like the ability to "favorite" Public flows that are on the server and then have a separate "Favorites" section. As the volume of Public flows on the server increases, It would allow for users to be able to navigate to frequently used flows much faster.
Add entered parameter into the result panel. It helps to debug process and audit.
sometime users save file in different way, and it not directly related to the interactive question
(e.g. Question: "SAP FBL5N Data" Input: "EXPORT (2).XLSX")
when error happen, I need the source file and the parameter.
if this idea is implemented, i just need the screenshot, which faster, without user to re-run the workflow to screenshot and share the parameter setup.
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.
When scheduling workflows in the gallery that are recurring, it would be beneficial to have start and end times also. For example, when setting the frequency to hourly, if there is an option to run between 9 AM and 5 PM that would be great. This would prevent us to schedule workflows for all 24 hours and take up systemic resources when other important workflows could run instead
Commas save lives! With large numbers, it's difficult to see what number was actually entered without commas present, and the wrong number can easily be entered as a result:
Is this number
It's hard to say without taking a really close look!
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.
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,
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
I am noticing what I think it's a big gap in terms of turnover and job changes. Even though you can add workflows to a Collection for development and update purposes. Only the original owner/publisher can see the version history for a workflow. At least that appears to be the case in 2020.1
Is there any discussion for the road map to include a way to transfer the ownership of a workflow from one user to another? this would alleviate the need to publish a brand new version and then reset all the scheduling.
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.
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
After a job is run on Alteryx Server, Gallery lists Job Results with a Status column containing with one of 2 values:
If any WARNING messages are generated by the workflow, the operator/user is unaware unless they take the time to expand the message log details, then scroll through the long list of messages that typically appear in the log.
Because the Success Icon appears whether there are Warnings or not, the user must dutifully spend extra time scrolling through the list looking for Warnings even if there are none to be found.
My Idea: provide additional information under the Status column in one or more of these ways:
I think that the user would benefit from a filter where they could focus on errors, warnings, or other types of messages in the same spirit as the Designer interface, but I recognize that would be a lot of work and I am not asking for that now.
Current State:
Currently, all workflows and applications are in list-form within "My Workspace" (formerly Private Studio) and Collections. In My Workspace, I might have workflows and applications that support a broad range of domain spaces and audiences. As the developer (or Artisan), they're all in My Workspace, but shown as an exhaustive list with no categorization unless I name them to represent not only the function of the workflow/application but also the domain.
Once those same workflows/applications are moved to collections, there can exist confusion over whether the workflow/application is intended for a schedule, manual run, or application. Separating by naming convention gets messy and degrades clarity for non-developer roles.
Proposed Solution:
I would like to see folders, only one or two levels deep, be added to My Workspace and to Collections. This proposed solution would not alter permissions, as those would be common for the parent collection and any assigned roles would function the same for that entire collection. The solution is simply adding organization to enhance the user experience.
For example: I might have a Collection that is intended for my Finance team....
Finance_Collection / Scheduled_ETL_Workflows / Workflows
Finance_Collection / Scheduled_Analytic_Workflows / Workflows
Finance_Collection / Applications_for_AccountingDepartment_ReceivablesTeam / Workflows
Finance_Collection / Applications_for_AccountingDepartment_PayablesTeam / Workflows
Finance_Collection / Manual_ETL_Workflows / Workflows
Finance_Collection / Manual_Analytic_Workflows / Workflows
Finance_Collection / etc...
All persons who have been assigned the role connected to the "Finance Collection" will still see everything in all of the folders but would have a better sense of what "workflows/applications" are intended for their use according to the folders the workflows/applications are organized into.
Value Added (Why This Matters):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I welcome input and feedback from the community and would appreciate your support if you find this suggestion useful for your Alteryx experience!
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.
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
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
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.
It would be great if you could overwrite an existing workflow when saving to the gallery from designer. It could be a simple popup with a yes/no option to overwrite/save a new copy. Currently, you would have to
1) Save your workflow to the Gallery.
2) Click on ok and be taken to that workflow.
3) Go back to your private studio.
4) Search for the app you want to replace.
5) Realize you have 7 copies of the same workflow with the same name and try to determine which one you want to replace. (this could just be a "me" problem)
6) Select that app
7) Click on replace workflow.
😎 type the name of the workflow in the box.
9) Look through your list of 7 workflows and choose the one that was just uploaded. Usually the first in the list I think.
10) Lament that it took way too many steps.
I recognize that you can open workflows from the gallery in designer which does allow overwriting, but I've run into issues with 1) external dependencies not working as expected (ie packaged assets don't quite work the way I want) and 2) about half the time it will simply give you root errors and then your only option is to save to a folder and then go through the process above.
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.
User | Likes Count |
---|---|
7 | |
3 | |
2 | |
2 | |
1 |