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
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.
*This is an idea from @cneivam from the Portuguese Community*
It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).
My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events. On a large implementation, this becomes very difficult to manage.
Currently the e-mail settings for the server are set up using a wizard and are not available within the admin UI.
Please could you add an explicit section to the Admin UI to allow the admin team to set up approved SMTP settings, allowing this all to be managed in one admin console.
Further: Can you allow the admins to push these settings down to the desktop users. This would allow the admin team to control the SMTP usage and prevent data leakage. It would also reduce complexity for the user since the SMTP settings are all pre-set making eMail tools; and Events easier to set up.
Could the community receive a comprehensive data dictionary of all the collections in Mongo with:
- Description of each collection
- Description of each attribute (or field) within each collection
- Documentation of joins between the collections
A great example can be seen in how Tableau documents their postgresSQL tables: https://help.tableau.com/current/server/en-us/data_dictionary.htm
This would be extremely helpful as we are determining which collections we need to store, how to construct queries and how to build analytics on our assets.
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.
Given the need for administrators to be able to perform analysis and monitoring on server performance; user usage etc - it is necessary to provide full documentation for both the API and the database underlying the server so that admins can use this to good effect.
Although very limited documentation is available on the server API (https://gallery.alteryx.com/api-docs) what we're looking for is a much more fully formed and navigable experience like some of the examples below.
This will make building helper processes substantially easier; as well as allow admins to fully manage their environment.
As the Server Admin I'd like to have the ability to view ALL "Workflow Results" for all Subscriptions.This will give the highest level admin the ability to monitor all schedules (on the entire server instance) and monitor if they are unable to complete successfully (example- unable to allocate memory) and any other errors are occurring.
Knowing this information will help the server administrator understand if there are issues with the server itself (e.g. if we need more workers or to simply adjust actual server system settings..etc..)
Now, gallery does not support AD group , need to setup user one by one.
If gallery support AD group synchronization, it is more convenient for gallery admin to manage large number of users.
By assigning AD users to AD group, it will reduce the maintenance task of gallery admin, since gallery admin don't need to grant rights in the gallery directly.
This idea covers 2 things:
- Disabling certain tools for users
- Pushing out other tools
- If we want to disable a particular tool for everyone or for specific users - then we need to go to every single deployed machine and adjust settings or delete some DLLs.
- What we would need is to be able to take a user / group of users - and de-select certain tools or apply limits
- In our corporate environment - every designer needs to check in with the server before fully starting up. If it cannot connect to the server, it needs to terminate gracefully
- As the designer logs in - the first negotiated conversation is "What tools and capabilities and standard default settings should I have"
- If a useful tool is brought into our environment (like the JIRA connector here: https://gallery.alteryx.com/#!app/JIRA-Connector/58d87c2feffc2a0dd0b5ed8f or the CREW macros) - we want to be able to push these out to all the users
- Again - every designer checks in with the server first
- Then negotiates tools
- then downloads any missing tools or updates new versions of existing tools.
This kind of central server capability is essential in any enterprise deployment of several hundred seats.
Right now, if you are using Windows Authentication, you can map AD group and users on the Permissions and Collections tab. But for some reason, you can't use AD groups on the Data Connections tab. Most of our databases are already secured by in-house AD groups in which you have to be a member in order to access that database. Instead of managing a 2nd, most likely duplicate, list of users in the Data Connections tab I would like to be able to map the pre-existing AD group to that data connection. That also means I don't have to service access requests. If someone wants access to a database, they talk to the database owners, get added to the group and then they automatically can pull that data into Alteryx.
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.
Would like to see a Notification hierarchy implemented to Gallery. Currently, the settings that control notifications are at the Gallery-level....where only the admin can control, for example, notifying users if a new workflow was added to a collection they belong too. Could this setting be inherited, but then, for example, a Collection owner can implement their own notification settings that overrides the Gallery default? Using the same example as before, perhaps the Collection owner could disable notifying their Users if a new workflow is loaded to the collection.
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.
As users change roles; or possibly even leave the firm - we need to automatically manage the ownership of their and their permission.
- We need to be able to export all permissions and ownership of assets by user using an API
- We then need to be able to revoke permissions using an API (we have a central entitlement management process that this can be tied into)
- we also need to trigger a revoke on all licenses via API.
If done within Alteryx server:
- When a dept code on a user changes; or user leaves - trigger an invalidate on all assets.
- Workflow to both the primary and secondary owner to ask for a new owner
- Also automatically trigger a revoke on all licenses
Currently on Alteryx it is possible to add visibility of a subscriptions scheduled workflows to all members of that subscription.
What we would quite like is for the ability to turn on or off the ability to edit workflows within that subscription for all members.
As in if a member goes on leave, or leaves the company, or is ill, other members can edit, update and cancel the scheduled workflow as needed without needing to go through an admin for it.
Now, under the Job Tab, it is only show the status of running job.
Suggest to add one new page for showing the run history of each workflow/job.
1. Workflow name
3. Assigned Worker
4. Start time
5. End time
8. Job Type (schedule or manual tracker)
10. Message ( e.g. error log)