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.
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 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.
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.
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.
Hello Alteryx Team,
we would like to customize SAML login with additional claims (departement)?
We want to grant authentication based on claims we are using in addition of firstname, lastname, email.
So we need custom code as well, is this possible to integrate or merge with alteryx code ?
simple example would be:
we add city to the claims and on user with from city "New York" will be accepted all others will get access denied page.
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.
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.
The admin (aka curator) needs to be given more control. The admin should have greater control than the users of the system.
My organization is in the Healthcare industry and we have HIPAA laws to abide by when it comes to data. Not all users should be able to see all data. Developers should not have complete control over the data they publish.
Get tips from Tableau as they have admin controls down with their permissions process.
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.
When installing and configuring Alteryx, the wizard allows the administrator to select the Gallery authentication to be used among:
Integrated Windows authentication
Integrated Windows authentication with Kerberos
The note states:
Once an authentication type has been selected, it should not be changed. Changing it may cause technical problems.
The gallery manual states "Once an authentication type has been selected it should not be changed or Gallery functionality may be compromised."
If you are reading this idea suggestion, I hope it is not too late for you. Why allow the user to change the authentication method once the install is completed? What are the options to solve this?
One option would be to grey-out the "Authentication Type" section in the "Gallery Authentication" screen, so the user is not able to change authentication methods once after the first configuration is set. This would still allow the user to change SAML settings.
Another option, if somehow there is a reason why a user would want to change authentication types even though it is not supported, what about changing the layout to make it more difficult to change the authentication type.
What are your other suggested changes?
This is not relevant if this idea is implemented https://community.alteryx.com/t5/Alteryx-Server-Ideas/Allow-changing-of-Gallery-Authentication-witho...
However, I would imagine that a UI change would be a lot easier to implement that supporting overhauling the user management in the MongoDB.
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
We Should be able to use the Published macro in the server/ Gallery in any Designer workflow and Re-use it Multiple Times in Different Workflows.
It would be great if each user could persist their gallery UI sorting/view changes and leave them as default. When I log in I nearly always immediately switch to list view and sort by most recent modified. This means everytime I access a set of workflows there are at least 3 click actions before I can even start working.
Current Data Connections options are limited to db connections: MSSQL, Oracle and Others.
In my opinion, it should be expanded by at least:
- FTP/SFTP addresses
- URLs to webservices or resources
- Cloud resources like AWS S3
The server should manage resources as much as possible
I've used a standard configuration to set up an Alteyx server. The gallery is available at https://alteryx.samplecompany.com/gallery
I'd would be really helpful if you enable to create a landing page at https://alteryx.samplecompany.com/ and add a possibility to host add extra pages. The easiest way to do this is to add an option to the Alteryx Server configuration wizard and read the pages from Alteryx workspace location.
Additionally, such landing page should have redirection from HTTP to HTTPs.
I would like to have the ability to configure my company's Gallery to display more than five applications/workflows to a page. This is a waste of screen space and creates unnecessary clicks for browsing.
The ability to create multiple fields in the Multi-Field Formula and Multi-Row Formula tools. Currently I have to drag 3 tools to the canvas which can become cluttered. We should be able to create multiple formulas in one tool, similar to how the formula tool works.