I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.
SQL Server Management Studio
Schedules on Alteryx Gallery/Server
Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1). However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)
Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.
I've seen various solutions/workarounds but this seems to be a table-stakes ask? When scheduling a workflow I should be able to specify which parameter values to run with. Just two of many use case examples -
Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business
Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials. When their credentials change all they would have to do is update the schedule parameters
(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)
A nice to have is a connector for Microsoft Flow to trigger workflows. With Microsoft Flow, users can automate processes, or set conditions that can trigger services across many different providers.
Having the ability to use a Microsoft Flow can enable alteryx users to run workflows and feed in data that could be used by Microsoft Flow to feed into other processes.
This would be a game changer for many users.
We have several clients that operate in a Multi-Forest environment due to mergers and acquisitions. Currently with Alteryx Server the only option we can offer them is to use Built-In authentication. A lot of corporate and particularly finance institutions prefer a single sign on approach and utilise Windows authentication to do this.
Would it be possible to add support for Multi-Forest organisations into Server to support organisations going through mergers and acquisitions?
This would really benefit us in selling Server in to organisations with complex structures and reduce friction in publishing or preparing workflows.
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.
*This is an idea from @cneivam from the Portuguese Community*
Can we make API function available to assign specific worker node while submitting job request using api.
For scheduled jobs, there should be an option to include performance profiling in output logs globally. Basically we are looking at how we can understand which custom macros are in use, and in which workflows, and one way to do this would be to get the output logs into another tool (i.e., splunk), and then set up some queries there. It would work, but I would have to tell N developers to go set performance profiling on, re-upload their workflows, ect.
But why not have a switch on server / gallery that just turns this feature on globally for every scheduled workflow?
Thank you for attending my TED talk on why performance profiling should have an option to be set globally.
Please Enable OAuth 2.0/OpenID Support for Alteryx Server & Connect. Currently, it supports only AD , SAML .
Current SAML has limitations, Unable to import Security groups from LDAP/AD if SAML is enabled.
My company uses R Shiny and maybe in the future Python Dash to create multiple analytic apps, dashboards, etc for multiple people to run across our company. One thing that would be nice to to have these R Shiny workflows run off of the Alteryx Server as that would allow us to use Alteryx Server to keep permissions and ease of use.
I propose an update to the Alteryx Server that would allow for R Shiny apps to be run in the Alteryx Server with all functionality of custom R interactive plots, etc etc just like what you'd see in one hosted on a R Shiny Server.
The benefits of this would allow for my company to only have to manage one server instance (Alteryx) to run all of this. Since R/Python is allowed/used in Alteryx workflows already, can you add the ability to visualize R Shiny code/plots/interactions/etc within Alteryx Server itself?
Below you can see few of my suggestion to improve Alteryx Server.
Idea for Alteryx Server monitoring:
Give server more functionality with:
Hopefully you will find these suggestions interesting and useful.
Our corporation has multiple private studios set up (depending on various teams within our infrastructure); when we provide a user access to one private studio, they cannot be part of another private studio (to update/add/remove their workflows); they can view/see them within the collections, but cannot action them.
If possible within the Alteryx Server interface, could users be added to multiple/different private studios (and be authorized for all), and have a toggle that would allow them to switch back and forth? This would alleviate a lot of our issues we have with users reporting/being involved with multiple teams (who are requiring access to different private studios).
I could not find any possible way to send an email if the Alteryx workflow is taking more than expected time.
I was wondering if any such feature is available
In my organisation, Alteryx workflow keeps running sometime due to memory issues. It will be great to know about these delay and handle them.
Currently, even if Alteryx Server is installed in E drive, RuntimeSettings.xml is generated in C¥programdata¥alteryx. Users cannot replace RuntimeSettings.xml to other folders.
It would be nice if a feature that users can specify place to save RuntimeSettings.xml.
Or, it would be nice if this specification is put in the documentation.
We are looking for the ability to use Alteryx as PaaS in the Azure cloud similar to how Databricks is working on Azure. So servers spin up when demand shows up and then they spin down. Where we are not on the hook for server patching etc., but instead, we lease processing power/time from Alteryx in the cloud on an as needed basis. The licensing model will also need to be a scalable to support this type of usage.
Please keep in mind that this is a suggestion from a container novice! 🙂
However, our situation is such that our release upgrade deployments are taking significant time to install, test and sign-off from DEV through PROD for the four main life-cycles involved in our server environment. Even if we script the deployment to save time, there's still manual configuration needed to confirm the new version works in the next server environment.
Similar to how Promote can deploy from DEV through PROD using images/containers, my suggestion is to package the Server components into images/containers that can be similarly deployed through the life-cycles. While the container with mongoDB doesn't need to move to the next life-cycle, the containers with the web server, load balancer, and engine nodes could move with the click of a button. And if needed, reverted to prior version with similar ease.
I forgot to ask about this idea at the UX lab during Inspire, but would be very happy to hear if it's already in the pipeline!
Thank you for your consideration!
I think there should be option to test save data connection during setup and after. Perfectly, if there was possibility to schedule connectivity check, however, just adding option to test it manually will be the step forward.
I can't find an option in Alteryx Server wizard to enable redirection from http to https. Alteryx Service occupies both ports so I can't (and I don't want) to deploy a redirection on port 80. Such feature would be really helpful if it comes out of the box.
We have installed Server on Azure VM and have looked into options such as a replica AD Domain Controller in the Azure environment for authentication, however, we would like to have Server authenticated using Azure AD.
As a system admin, I need a simple, reliable way to back up the Alteryx Server without shutting it down first. A hot-backup (and restore) utility that includes a consistent copy of MongoDB plus any other server config files would allow me to do this.
Having the option to disable schedules within the Designer application would be advantageous for we support staff. Especially when multiple service restarts or server reboots are required. When we perform migrations or restores or even upgrades or when conducting server maintenance actions. As we know starting of the Alteryx service immediately queues up workflows to be run based against there schedule times. When maintenance is being performed we do not want workflows to run, and/or having to wait for completions or have the user to rerun the workflow. The option to temporarily disable schedules globally with a click of a button is far better then changing the parameters of the schedule or even deleting it. To go a step further = an internal mongodb administration command to disable/enable schedules would also be helpful at the database level