When we create a shared macro on the Gallery, the desire is that we are able to:
- publish this down to users simply and seamlessly
- Allow them to use these assets in their canvasses
- Allow them to simply update to the latest version of the asset on an existing canvas.
Unfortunately - right now the only way to distribute shared macros is to create a shared folder; and the only way to manage version upgrades of a shared macro is to manually find every single usage and manually upgrade.
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.
I have been looking at the content in Alteryx Public Gallery for some time and I have had some concerns about the safety and usability of the macros/workflows in the gallery.
I think there should be an option to rate, review and provide feedback on stuff that is out there on the public gallery. This will be helpful in many different way.
I had initiated a thread some time ago related to this, there is some useful information in there if someone has same concerns.
For a given DB connection - there's a need to be able to specify the owner for this specific connection.
Reason for this is that the credentials for a given DB are not all managed by the central admin team - so we'd want to say that a given DB connection is owned by a particular person so that this can be updated frequently as passwords change.
For resilience - our particular policy would be to have 2 owners so that if one person resigns or changes roles, it invalidates the primary and reverts to the secondary - and then asks the new Primary to create a backup owner.
We are taking an incremental feed of all server canvasses in order to look for patterns - however there is no option on the server admin APIs (the Workflow API specifically) that allow you to filter by date.
Please can you add to this API to allow API users to specify an upload/updated date filter and only take items after this date.
As Alteryx makes more and more use of the Public gallery - it would be valuable for Alteryx to explicitly have a section devoted to items that are certified by Alteryx so that we can be safe bringing them into our corporate env.
The assets created by Alteryx are currently listed with Alteryx as the author, however it would be useful to have a completely separate section with Alteryx assets only, and with these broken down by type.
We've confirmed with @KevinP that the Alteryx Gallery / Server API does not currently support downloading canvasses in unzipped data-stream format. (https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...)
Please can we add an API end-point that allows the following:
Current API only allows this to be downloaded to a zipped file; which then needs to be unzipped; and then loaded back into a data stream.
The default view at gallery home page time will not support long titles for your workflows. I have several that get cut off with . . . . . and you need to hover over in order to get the full title. You can select a list view, which helps, and gives you more metadata, but you have no mechanism to save your table / list view as a default. Administrators should have the option to define a default view (tabular / list) and have it default that way for everyone who gets there, authenticated or not.
If you goto a private studio, you get the list view option. If you go to a collection, you get the list view option. If you goto a district, you don't get a list / table option set, just table set. Why?
There does not seem to be a way to set a (list of) favorite(s), even as an administrator. There should be a quick-hit button option to get you there, add it to a favorites collection, something. It seems like we went a long way to generate three different builds of ways to organize workflows, but left out the one that is most universal in similar tools. 'My favorites'.
The search criteria for adding a workflow to a collection *mandates* that you have a space, but doesn't tell you that is why you are not getting any hits; i.e., 'Water' and 'Water ' will give you 'no results found', or anything with water in the title respectively. Ugh.
The gallery has the ability to create specific districts for things like reusable macros, which is a tremendous help.
Unfortunately - when a user actually uses one of these macros - it looses it's connection / dependence to the macro that's stored on the gallery - so if the macro on the gallery is updated or repaired, this update has to be done on every single workflow that uses the macro because they all carry their own copy.
We need to make the dependence to a macro that's downloaded into a strong dependence - otherwise reusable macros can quickly become a liability rather than an asset because we will end up with dozens of different copies of the macro being used in different places - just like if we had a reusable web API that we built, everyone would be on the latest version unless they explicitly made the call to break version.
While there are cases where you may want to not follow along with the version upgrade - this should be an explicit decision (just like in a code repository where you deliberately decide to fork code). There are also some arguments that doing this will create more risk because an upgrade to a macro could break several flows if there's a defect. This is true, but that's the reason that we should be testing reusable macros very robustly before pushing them into usage with an automated harness.
each canvas in our environment goes through initial dev; then a testing phase; then into production usage after completing testing & peer review.
Currently the server environment has no concept of progression or promotion so we have to set up our own Dev; UAT; and Prod gallery & server - this really is very clunky because assets have to be manually copied across.
What would be more effective is:
- Allow a single asset to have a lifecycle (like you do in GIT) - so that it can go through dev and testing as a branch of the main code
- Once ready - user then changes the lifecycle type to "testing" or "UAT" and pushes it to users
- Once signed off, the user then promotes this to a production flow, and it replaces the current production version
There are a few areas where we'd need to do some thinking (dependancy tracking; branching; changing connection details as you promote so that you can hit the prod data stores etc) - but fundamentally this would go a VERY long way towards eliminating much of the admin involved in running the gallery.
One needs to obtain a designer license in order to have a server license.
It may be a good idea to package those two don't you think, and now it's ok to install designer on a Server OS.
It would be awesome if you automatically have a virtual desktop environment to connect to...when you get a server license,
The following is a slide from Inspire 2016 and the client's are already doing this
1. For keeping the running workflows unaffected by docking undocking workstations
2. It also increases the performance by getting the designer closer to the data
3. It would also be safe to share company analytics capabilities with outsider without giving them direct access to downloadable data etc.
There needs to be a means for Server Admins to delete/clean up subscriptions and users from the system.
Ref: https://help.alteryx.com/server/11.0/admin/index.htm#Administration/Users.htm%3FTocPath%3DAdminister..., “To revoke a user's access to Gallery, deactivate their user account. You cannot delete a Gallery user's account.”
While testing with version 11.0, default permissions set to NO ACCESS, Security using Windows Active Directory, I gave the gallery URL to a random teammate to see what they could access. While permissions prevented the individual from most activities, the server still created a USER and SUBSCRIPTION for the individual. Once testing was completed, there was no means possible to clean up these entries., or at least to do more than set them to NO ACCESS.
For most enterprise applications, it is common practice to be able to purge a user account from a system if they are no longer a member of the company.
Currently the only filtering available in the Results tab in View Schedules is by Workflow Name. It would be nice to be able to filter by Status, so we can just look for potential problems, like warnings or errors. Currently, I have a job that runs every 5 minutes. That means I have to scroll through hundreds of rows, or about 12 pages using the default 25 rows per page, just to scan for potential problems in the last 24 hours.
Would it be possible to specify whether a worker handles scheduled jobs, ad-hoc jobs or both? Right now it seems that the workers treat both types of jobs the same, meaning that a slew of ad-hoc jobs initiated from the Gallery could slow down jobs that are scheduled to run on a regular cadence. It'd be great if those scheduled jobs could have a dedicated worker (or workers) and have any ad-hoc jobs handled by a separate worker (or workers) so that the scheduled jobs (which might be more important) are not held up by one-off jobs.
Can we make the ability for a developer using Alteryx Designer and having a workflow using in-DB tools to pass along their credentials with the workflow when scheduling to run on Alteryx Server. An individual user may have access to only certain tables in Teradata for example and the ODBC connection on Server may not have access to the same tables so we need to be able to pass along the encrypted credentials. THanks!
In order for us to manage the large number of canvasses on our server - we need to add the ability for Admin teams to require additional attributes on every canvas:
For us, these mandatory attributes would be:
- Which team do you belong to (dropdown)
- What business process does this serve (dropdown - multiselect)
- Primary & secondary canvas owner (validated kerberos)
For the ones that have dropdown lists - we can provide the master data into a drop location or into a manually configured list on the server.
We need a way to figure out at which tool alteryx workflow is currently at (i.e., workflow execution progress log) when the workflow is running on the alteryx server scheduler.
This is very useful especially if you have analytical workflows that take long time to run (say 4-6 hours) and at the moment there is NO WAY to figure out at which stage the execution is at from the scheduler.
We can't open the log file on the server as the workflow is IN PROGRESS (we get the standard The process cannot access the file because it is being used by another process) . We can't see the underlying progress log under Scheduler Queue tab either.
It will be useful to capture that information in MongoDB or somewhere so that we can read the In progress log in the real time..
I think it would be a great feature to include the performance tuning logs as an optional output in Alteryx Server.
- This would allow me the ability to leave performance logging turned on, so I could see what was happening during an automated scheduled run of the workflow.
Performance Log : <Link> (or attachment)
I would also like to see a tool (or tools) as optional outputs such as:
<List of Files: <Link to Files> <Size of File>
These type of outputs would be greatly beneficial options instead of "This Workflow produced No Output"
Thanks for reading
For large implementations of Alteryx - you'd want to have a live control-center view that allows you to see:
- The state of health of all the server components
- the depth of the queue in the controller
- Jobs failing vs. succeeding.
While this can be done by running alteryx jobs, and by going and looking for problems - what we'd want is to have a heads-up control center view which is self-refreshing all the time so that administrators can be notified when there are issues. And this should not be e-mail notification (it's too easy to miss an e-mail or an SNMP alert)
Think about a 40 inch monitor on a wall (like in a traffic control center) that allows the server management team to see the state of health of the plant at a glance, and dive into issues without having to constantly be looking for them. this is a critical capability for enterprise install-base and would be a very useful capability to add to the platform.