When an artisan moves positions (within or external) away from their current responsibilities, their collections and workflows should be able to be transferred via an administrator to another user.
So - one of the biggest challenges that we have with the MongoDB used by Alteryx Server is that we continually have issues with locking (where our admins have to go in and undo locks)
Additionally - the current implementation of MongoDB connectivity does not support full Kerberos authentication which means that we're on a non-compliant install (which in a large enterprise is an uncomfortable place).
Given that a very large amount of what the server does is transactional - it would make sense to have an option to use a large-scale SQL server instead of using Mongo. For large enterprise customers, there must be flexibility to allow the databases that they have large supported instances of (my strong preference would be MS SQL 2016).
MS SQL natively supports XML so all the canvasses can be stored in native format. Additionally, MS SQL allows very fast query across XML, and given the clustering and reporting capabilities in MS SQL, this would dramatically increase our ability to self-manage our infra.
Given that Alteryx is looking more and more at large Enterprise customers - a move to a large-scale clustered SQL env as the back-end would be a very positive move.
NOTE: as we consider DB options for a SQL backend - please consider your large-scale enterprise customers. For example - MS SQL or Oracle or DB2 are all much more prevalent in enterprises than databases like Postgres - so it's important to focus on the enterprise support for the DB that you choose.
My company, a very large organization, is in the early implementation phase of Alteryx right now. My company requires frequent password changes and we plan on making heavy use of Shared Connections since there are also many shared data sources. Unfortunately, this would mean that every time a credential has changed that affects a workflow, the credential holder would have to contact Server Administration (me), and I would have to update any Shared Connections or other assets that use those credentials. This problem is exacerbated by also having to manage user permissions and which users belong in each Subscription Right now, that is not much of a big deal, but as the number of users begins to scale, this could become a very daunting task.
My current solution is to create Subscriptions for each Department, Group, or Team and give one person from that Subscription Curator permissions. This enables each Department to work more autonomously and reduces the load for Server Admin. The issue is that there is no permission level between the publishing rights of an Artisan and the ubiquitous acces of a Curator. So, with my solution, any one of the Subsription Curators can start using connections they're not supposed to have access to or deleting/stopping scheduled flows, intentionally or otherwise.
I propose that we find a middle ground between Curator and Artisan, a (Studio) Moderator. This person can be assigned one or more subscriptions by a full Curator and will have Curator-like permission, but only to the assigned Subscriptions. This means that they will be able to add/modify Credentials, Connections, and/or Scheduled under the envelope of their Subscriptions, but they won't have access to any others. I believe that this solution will mitigate the possible overflow of tedium to the true Curators while allowing the powerful communal features of Alteryx be used to their full potential.
The shared data connections from the Gallery have been very helpful in centralizing data connection information between desktop users and their workflows when saved to the Gallery. The In-DB tools currently cannot take advantage of the Gallery Data Connections and require a completely separate setup that is both confusing and adds additional connection management work for creation/password changes.
It would be a great enhancement to Alteryx if all connections for the different types of tools could be centrally managed from the shared Data Connections manager found in the Gallery.
As a server administrator, I would like to have more control over collections. I have a user who is in charge of a collection out of office, and we have some users who need to get to be added to the collection to run workflows. As admin of the server, I would like to be able to add users to this collection, modify permissions, modify workflows, etc. This would be necessary both for when users are temporarily out of the office as well as if someone were to leave the company.
Along with setting a schedule for an app in the gallery, the user should also be able to set the different interface values for each schedule he/she makes.
My main use case is regarding having generic templates for ETL processes, that have multiple different types of runs based on configuration values, but I'm sure there are plenty others.
Suggested information to be included in audit logs.
A secure audit record of all activities on the system:
At minimum the logs should include the following:
I believe many customers could benefit from this type of audit logging, especially those who are required to obtain specific security certifications for their alteryx deployments. From what I can see online there does not seem to be out of the box functionality for this. If anyone has implemented any type of audit logging like this please feel free to comment.
Is there any plan to create an automated way of publishing apps/workflows to the gallery. This has been a common painpoint for me on several different projects when I explain how manual of a process this is.
I'd imagine this could easily be solved by adding an additional API call to their library. Ideally, you'd be able to point the gallery to a shared folder with workflows you want to push (git repo functionality would even be better), and have it just move the .xml scripts to the server/mongoDB.
It would be useful if the Admin of a Private Gallery (in house server) could delete studios and/or members. Also, it's confusing that a member who's added also gets a Studio automatically set up. Members (for my purposes) are only supposed to be able to run apps in collections that I grant them access to. They should not get their own studio. Even if they can't use the studio (or even know that they have a studio), it's not very efficient to have all these studios show up on the subscriptions screen.
I would like to collaborate with my team, but also maintain my own personal private studio.
Is that on the road map?
As we continue to build Alteryx Workflows for the business, there is a continued need for an organizational structure for saving and storing Alteryx Workflows within the Alteryx Gallery. Organizing the workflow repository through a "folder hierarchy" will allow users to quickly navigate and find the appropriate workflow. Currently, the workflows are listed in alphabetical order and requires the user to remember the Alteryx Workflow name and click to the proper page.
Any enhancements to the Alteryx Gallery organization structure would be greatly appreciated!
Currently the Private Gallery product has 2 authentication options - AD and built in.
If an organization uses AD, this solution is fine, however there are many origanizations who use other standard directory systems. One of the more common directory/authentication systemsis LDAP due to its wide adoption and cross platform compatibility.
It would be fantastic to have functionality similar to the AD integration, however with LDAP for Gallery authentication and user management.
We've purchased a server license and several designer licenses to publish analytics apps to customers via our internal/company gallery. Whether a user signs in or not, users should not be subjected to corporate Alteryx ads. This is a terrible user experience and detracts from our ability to deploy self-serve solutions.
In larger organizations or organizations with global coverage, it is possible for users to be in different time zones from each other and the Alteryx server.
WIth our implementation of Alteryx server, we have the server time zone set to that of our data warehouse, but this time zone is different than my own by -2 hours. In the case of scheduling a workflow in the future, I normally correct for this by setting the scheule in the time zone of the server and things work alright.
It falls apart is when I want to schedule something in the future, but it is within the timespan between my time zone and the server time zone. For example: It is 6PM my time, and 4PM server time. I want to schedule a workflow to run at 5PM server time (7PM my time). When I try to set this up with the Version 10 scheduler built into Alteryx desktop, it overides the date field upon saving to run the following day instead of today as it thinks im trying to schedule the run at a time that has already passed (which it has in my timezone, but not in the server time zone). Upon trying to edit this schedule to reset the date to today, it again reverts upon saving.
The only way I have found to get around this is to reset the time zone of my computer to match the server time zone, then set the schedule, then reset the time zone of my machine back to local time again. This is not the best experience, and will likely be required more frequently for users as their time zone difference increases.
When wanting to run something server side immediately (I do this in cases where the runtime will be long, or im mobile and on a machine with a lower amount of processing resources) the "Once" option can be used in scheduler to push something to server and run it. In my case, due to the timezone difference, the default time set when trying to do this is the current time in my time zone, but 2 hours ahead of the current server time.
I have two proposed resolutions:
1) Transmit Server time zone information to the local scheduler to have everything involving scheduling in Server time. Also for any timestamp fields, include the time zone designation so its clear to the user.
2) Use information from the user's machine and information from the server to do timezone conversions behind the scenes so whenever scheduling or viewing schedules, all timestamps are in local time to the user. I feel this is the prefered solution for the best user experience, but would also be the more complex to implement.
We have the need to bulk-add users, and to bring in their information (full name; location; etc) from Active directory.
Right now, adding users is a 1:1 process which is highly painful.
Desire is to be able to take a list of Kerberos IDs, and bulk add them as users - and then select a group of them and permission either for the gallery; or for designer licenses.