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)
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.
Currently the server diagnostics (http://localhost/gallery/admin/#!diagnostics) covers a narrow time window (from what I can see - only the last few hours)
.... and if you attempt to zoom out or pan to see a broader time window - the graph gets smaller, but the data does not grow to fill the remaining space
Please could we request 2 changes:
a) add a time axis on the bottom of this chart so that the user can understand the time dimension
b) Increase the time available for analytics to an arbitrarily broad set of data (which the admin can configure as a server setup parameter - retention period). For us - we'd want to keep at least 3 months of data, and be able to view this analytically.
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.
Currently when scheduling workflows, there is an option to schedule based on the calendar day but not on business day. For example, if I want to run a workflow on Business Day 1 of every month, it is not necessarily the first day of every Month. For the month of June 2019, Business Day 1 is June 3rd, since the 1st and 2nd fall on the weekend. Many departments run their processes on Business Days rather than Calendar days. Also factoring Holidays into consideration would be a plus since January 1st for example is a Holiday, Business Day 1 would fall on the 2nd.
We have more than 100 workflows scheduled in different intervals for a day. Inorder to monitor this we have to manually check in the workflow results if the workflow ran successfully or not.
Say a workflow is scheduled every 30mins then we have to check this 48times in a day manually in the Gallery results if it ran successfully or not.
Similarly we will have N number of workflows scheduled with different intervals.
We feel its too time consuming to manually verify this.
It will be good if there is a notification when there is a failure in the run, so we can check it only then rather than checking it every 30mins.
It will be great to make visibility of workflow execution results to other users in same subscription.
As of now, only schedules are visible to all users in a subscription, but not the workflow execution results executed by a user to other users in same subscription.
This will avoid duplicate execution of same workflow by multiple user in a team as it will provide option to cross check the execution results by other users, if executed already, before execution of same workflow.
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.
Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful.
Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline. I’ll share both files soon.
Here are the top 5 features for the Scheduler.
Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field.
Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning. Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows.
FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.
Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db.
Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx.
Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows.
Many people maintain valuable information in Excel files, and many organizations, like ours, also use SharePoint to store and share structured and unstructured information. We see most user-generated and maintained data in Excel files in SharePoint document libraries, and one of the great benefits of Alteryx is the ability to join that Excel data with other data sources. Unfortunately, the v11.0 Scheduler cannot resolve the UNC-style ( \\server@SSL\DavWWWRoot\site-name\document-library\filename ) addresses, so workflows that access this valuable SharePoint Excel data must be run manually. The SharePoint List Input tool can read the list-style metadata for Document Library files, but does not access the file content.
The Scheduler should be enhanced so that scheduled workflows can read Excel data stored in SharePoint Document Libraries.
Hey Alteryx Dev Gurus -
I've got a situation wherein the user runs something in Gallery, and complains. I have to log in as that user to view the output files that came back out. As a super user, I should be able to have all seeing ability! Thanks!
Currently there are certain locations on server that are paginating content results:
Each of these pages require users to either know exactly what they want to find by using keyword filtering or know exactly what page they want to go to and use the bottom arrows/page numbers to navigate to that page. Ditching pagination for something more intuitive helps users that may not be as acclimated with the depth of content when there are a lot of results, and also saves users multiple click interactions to find what they want.
There are tons of solutions for this, but infinite scroll is the most user-friendly & least taxing server & client side.
https://infinite-scroll.com/ has code & examples, and jquery seems to be the most widely used implementation.
I have been trying to scan all of the workflows that are stored in the gallery and wrote this community post about it. Some Alteryx employees reached out to me directly to see if they could help solve my problem. We ended up with a somewhat wonky roundabout solution (that I haven't implemented yet) by downloading yxzp files through the Gallery API, unzipping them, then scanning the workflows as xml. I think the process could be greatly simplified if Alteryx had a set of Introspective tools.
The introspective tools would use similar, if not the same, processes that Alteryx already has in place to pull data from the gallery/server itself. The set of tools would be most useful for Server admins or people that are trying to build meta-workflows for Alteryx to make things easier for their users. Similar to the solution to my problem above, most of this functionality can be worked around by querying the Mongo and/or scanning engine logs. The Introspective tools would simplify this process greatly, especially when it comes to joining records from the Mongo and collecting workflow-internal data.
Since the tools will have direct access to the gallery/server it would make sense that they would only be available to machines with server licensing or could be made available if the user has a high enough permission level in the gallery they are trying to obtain data from.
I would like to collaborate with my team, but also maintain my own personal private studio.
Is that on the road map?
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.
I need to monitor which applications are shared with who on regular basis. We follow the 19.2 subscription model to share applications.
Can you extend server usage reports to include such data?
The idea here is that it would be very beneficial to allow general users to publish .YXZP packages to their server gallery (and/or the pubic gallery!!!). Currently, this can only be accomplished by a server administrator through the 'Admin' page on the server. It is also a completely different process than that of publishing Apps, Workflows, Macros etc., which can be done easily from the desktop designer.
For instance, I have developed an Adobe Analytics - Connector Toolkit, which is a .yxzp package, and is located HERE (check it out!). However, I do not have the ability to upload it to gallery.alteryx.com because I am obviously not an admin on the public gallery.
The neat thing about publishing packages to the server is that they appear just like Applications in the gallery. Descriptions can be added and you can even disable the default 'Run' button and provide a 'Download' or 'Save' button instead.
Hopefully, this is a feature that may be available in a future server release!
P.S. - the Adobe Analytics - Connector Toolkit is also attached below.
We get a lot of comparisons with DataStage ETL and what Alteryx can do. DataStage has the capability to partition queries and run on multiple worker nodes to allow the execution to be more efficient and faster than if it ran on one worker. We want similar capability on Alteryx as our case study shows right now that Alteryx is 10X slower than a query ran on DataStage through the GRID.
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.