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 ability to select a workflow or app within the Gallery web interface and change its name. This would maintain its historical run data, version control revisions, placement in collections, etc.
Use case: As a workflow or app continues to be developed over time, the name may need a revision to continue reflecting the workflow's function.
Best regards,
Ryan
It would be nice if the Gallery Admin could download the workflow from the workflow page within the UI, without having to run API calls or having to add himself temporarily to someone else's studio.
Currently, Alteryx Server lacks rich job scheduling functionality to other products like Control-M and Informatica's Scheduler
Feature Requests:
1) Ability to configure job retries on failure without having to rerun the workflow based on a event trigger: https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/How-to-run-a-workflow-from-an-event...
There are common occurrences where a workflow may fail to connect to Input sources and a retry would normally resolve the issue.
2) More user friendly way to setup dependencies between scheduled workflows. For example, if workflow A fails it triggers workflow B to run. If workflow B runs without errors, it triggers workflow C to run. Currently, we would need to configure this based upon events. A complex chain of scheduled workflows becomes difficult to manage and scale.
Currently when scheduling workflows, there is an option to schedule based on the calendar day but not on business day. For example, if I want to run a workflow on Business Day 1 of every month, it is not necessarily the first day of every Month. For the month of June 2019, Business Day 1 is June 3rd, since the 1st and 2nd fall on the weekend. Many departments run their processes on Business Days rather than Calendar days. Also factoring Holidays into consideration would be a plus since January 1st for example is a Holiday, Business Day 1 would fall on the 2nd.
See following article for background reference: https://community.alteryx.com/t5/Alteryx-Server-Discussions/workflow-exceeded-maximum-runtime-of-30-...
I have a support case (#00278355) advising unsupported changes to the alteryx.config file, involving an undocumented setting for chainedTimeout, as in:
<engine enableAutoLicensing="true" useServiceLayerComposer="true" chainedTimeout="10800"
This setting should be documented, supported, and made user-configurable through the System Settings GUI.
Hi there,
On the server product you have the ability to set up timeouts to avoid server resources being hogged by any one canvas.
Currently this setting only applies to scheduled canvasses - however this leaves a gap where users can just run this manually.
Please can you extend this setting to also cover manually initiated jobs too?
Greetings Server friends!
I was talking with @KevinP in the Solutions Center at Inspire and we talked a lot about how Server has been evolving over the last several versions. I'd like to request that end users be able to select workflows or applications shared with them as "Favorites." It would be great for ServerUI to offer a separate section for these selected "favorites" so that the end users can have a single go-to place to access their most frequently used apps.
Open Custom Group management internal API's for Curators (or those with Admin Secret/Keys)
If your server is on SAML, you can't leverage any AD group for granting access to resources. The new custom group feature is a help, but still requires you to manually add groups and member users, so it doesn't scale for large organizations (too much management overhead).
Having the internal APIs exposed would allow me to do my own group sync tool, synching members between Custom and AD groups of the same name.
As a server Admin, I'd like to be able to do via APIs all that I can do via the Server Admin UI. This other idea was recently accepted for opening the collections APIs for Admin, it would be great if both Collections and Groups management were opened on the same upcoming release.
The idea is to have tabs on separate pages in the Gallery (or the option to allow that type of behavior). Right now, if you created an analytic app that has questions on different tabs they will be on separate pages in Designer, but when you push the workflow to the Gallery all the questions will be on the same page. The tabs act as a navigation bar instead of taking you to separate pages.
Here's two different discussions that ask about this in case there is any confusion:
I would like to set a retry count when scheduling a job, and also to specify to duration in between retries, e.g. job fails, but then will retry to run 3 times with a 5 minute wait in between each retry.
Also would like a radio button next to all workflow results, so when you get a list of failed jobs you can click all the jobs and then hit rerun. This should be complimented with select all functionality. This will prevent me from having to go into each job and rerunning, i.e. save me loadsa clicks!
Currently, to allow a user to schedule jobs, prioritize jobs, assign jobs, create collections, or have API access, toggles must be set at the user level.
As a server administrator, I want to configure these toggles at the group level, so that a) I don't have to modify a large number of users individually to grant them such permissions, b) I ensure consistency across groups of users that doesn't rely on humans clicking all the right things for each of the relevant people, and c) I can easily change these settings for multiple people, if needed.
API that allows to specify the workflow version to download.
An example would be where a user has a scheduled workflow that runs at regular intervals and they might want to look at the logs from the results from a specific date. Having the ability to filter the date column would help with this, as the only other alternative at the moment is manually working through the pages.
Hi
In a heavily used server environment, and depending on how workflows are deployed, it is possible to accumulate a vast number of "one off" workflows that could/should be deleted as they would never be used again. In one of our environments we have over 1 million of these.
Currently we are manually deleting them 500 at a time but have asked if there is a way to script the delete process to make it more efficient. We have been told that to really delete a workflow you would need to touch at least 4 collections.
Can we have a Delete workflow API in one of the next releases in order to address this issue?
Thank you
Tom Diroff
I work at a large organization where Security and Privacy are of utmost importance. The ideology that we need to follow is Least Privilege and Need to Know.
We (Curators) do not want all the Artisans to publish workflows to Home Page, either knowingly or unknowingly. We however do want to allow a few power users to publish their work in Home Page, but currently the Gallery does not provide the ability to pick and choose who can share workflows publicly. We are educating users to not share any contents publicly, but as we scale up, it will be difficult to manage and govern this.
I'm suggesting to implement a global Yes/No feature that will Enable/Disable Artisans to publish contents in Home Page (just like the way we have for Jobs/Scheduling feature). Further, in Users section, Edit User setting needs to have a Yes/No button that will allow Curators to let certain Artisans place workflows in My Company's Gallery.
Organizations that never want any workflow to be shared publicly can disable this feature using global Yes/No button. Organizations (like the one I work at) that want to enable this only for certain Artisans, can set the Global Yes/No to No, and then in Users tab, they can pick and choose the Users that need this functionality (which will override the global default). Finally Organizations that do not really care about this functionality can just set the global setting to Yes.
Hoping other organizations find value in this functionality as well. Thanks.
Hello!
Currently one of the pain points when looking at integrating Alteryx Server into an organisation, is the role of a Curator, and who should be given that role. Of course, from an IT perspective, they want governance and control over data connections, users, and configuration - as it is important that users aren't simply able to change the default role to Curator and give all users access to the Administration portal, for instance. On the other hand, a Super User is typically given Curator access to allow for adjustments to all other sections of the Administrator Portal, that IT quite frankly don't care about.
What would be useful, is for a new role to be created, elevated from Curator. Let's call them 'Super Curator'. These 'Super Curators' (or, User-Curators, for a less exciting name) have access to all of the Admin portal as usual. 'Curators', would now only have access to the following (Highlighted yellow for Curator access):
This would aid the conversation from an IT perspective, allowing them to take control of user, data connection, and credential administration, whilst leaving the rest of the control to the other Curators. As this wouldn't always be a requirement, it would be useful to allow for a toggle of this setting within the Configuration on the Gallery. This would also not effect pre-existing setups of curators, as in the update of implementation, all current Curators should be adapted into 'Super Curators'.
Thanks,
TheOC
There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.
I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.
APIs I am requesting be released:
My team currently uses the API to call a large number of workflows via a Python based scheduler process. We use this currently by having ~10 users in a single subscription (Private Studio).
All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.
From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.
Are there plans to adjust the API endpoints in the future to better account for this?
Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.
Thanks
As large enterprises continually strengthen security around their system and data assets, we're seeing adoption of products like CyberArk's Enterprise Password Vault (https://www.cyberark.com/products/privileged-account-security-solution/enterprise-password-vault/ )
The system is essentially a central repository that secures and automatically rotates passwords for privileged accounts- things like a functional account you would use to run workflows against a certain database or set of systems.
It would be great if Alteryx could build both Server (Run As Account) and Designer (for individual database connections) integrations with a tool like that.
Hi Server users,
It is amazing to know the permissions we have when accessing our own profile, but sometimes that is not enough. Knowing your server role is needed to perform a few tasks and it would be fantastic to have something simple like the example below.
User | Likes Count |
---|---|
5 | |
2 | |
2 | |
2 | |
2 |