Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

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.

 

 

There is no good way to get server user credentials into a workflow without asking them for it in an App interface.  It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.

Currently the server diagnostics (http://localhost/gallery/admin/#!diagnosticscovers a narrow time window (from what I can see - only the last few hours)

 

Current Server Window.jpg

 

.... 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

 

zoomAndPan.jpg

 

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.

 

Thank you 

Sean

 

 

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.

Hi,

 

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.

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.

 

Best regards,

Ryan

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. 

I was reading a post on the Community (http://community.alteryx.com/t5/Publishing-Gallery/Macro-sharing-Best-practice/m-p/38330) which reminded me of an idea that I had.

 

It would be really nice if a Gallery location could be used as a "Macro Search Path" so that macros don't need to be downloaded from the Gallery and saved locally to be used in a workflow.

 

So in addition to going to Options>User Settings>Edit User Settings>Macros and adding a local/network path, you could add your internal gallery information...

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.

 

  1. Workflow priority ranking. When two or more workflows are scheduled to run at the same time, ‘priority’ sets the order of execution. Priority is set at the time of scheduling the workflow. Values range from 1 to 100. If a priority is not set the default is 50. The ‘priority’ field can be read from Mongo db. 

 

Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field. 

 

  1. Restrict which controller and workers a specific workflow can run on. Default is to run on all servers. At the time of scheduling a workflow can designated to restrict which server to execute on. This creates a field called ‘restrict’ which server it cannot execute on. 

 

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. 

 

  1. Set sequence of successfully completed 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. 

 

  1. If a workflow fails you can set the number of attempts to run successfully. Report attempts greater than 1 in a new field called ‘attempts’ that can be read from the 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. 

 

  1. If a workflow runs more than X minutes the scheduler kills the workflow and reports a workflow error with a unique code called ‘execution-limit’.  This code can be read in the mongo db. The defaut is 90 minutes and can be set to any number of minutes. Each workflow can have it’s own limit. 

 

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. 

Hi

 

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.

 

Regards

Haribabu Muppaneni

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!

 

brian

 

If a job fails it would be perfect if we could set something in the workflow settings so that the job would retry again in X number of minutes for the next Y number of times. We have jobs that connect to external resources and sometimes the network will reset and will cause the connections to all drop. An example would be I want a workflow to try again in 10 minutes for a maximum of 5 times so over the next 50 mins it will retry every 10 mins if it fails

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?

 

-Dan

 

 

When upgrading dot releases to designer desktops, allow for compatibility to the server without the mandate to update the server.

Currently there are certain locations on server that are paginating content results:

 

  • /gallery/#!apps/studio
  • /gallery/admin/#!apps
  • /gallery/admin/#!subscriptions
  • /gallery/admin/#!users

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.

 

pagination.png

 

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.

  1. It will generate trust about the workflow/app. If I see that something is rated higher and has been used and commented by a lot of users I am more inclined to use it
  2. It will provide a lot of ideas on how a particular workflow/macro can be used in different ways 
  3. Review/Feedback will help the author to make changes as required or suggested by users.
  4. The macro's will probably show up in google search based on key words provided by users in their reviews.

......

 

I had initiated a thread some time ago related to this, there is some useful information in there if someone has same concerns.

 

 https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Can-Apps-and-Macros-in-Alteryx-public-Galle...

 

Thanks,

Ashish

 

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. 

 

 

Best regards,

Ryan

Allow LDAP COnfiguration on Alteryx Server ,Right now its only AD ,but LDAP will be for for SSO ,SAML . 

Top Liked Authors