Alteryx Server Ideas

At some point we would like Alteryx Gallery to support SSO via SAML and Authorization via AD groups. The way I want is to have Authentication via SAML and Authorization via AD groups. For instance one of our apps Tableau: It does authentication via SAML (SSO) and for authorization, we import AD groups into Tableau thrice a day(stores the groups in a .xml file), once the groups are in the Tableau, we secure the objects within Tableau using that LDAP groups (which kind of become local groups after import). Basically the userid after the successful authentication step is used by the app for authorization.

I just stated Tableau as one of the ways to implement Authentication and Authorization for an enterprise app. If Alteryx Gallery needs to be an enterprise app, you will need to look into this idea. 

Thanks
Raj

We currently have the ability to store connections on the server which protects the credentials - however this capability does not exist for APIs for Sharepoint sites etc.

Please could you extend this to cover authentication for ALL connectors?

Many thanks

Sean

cc: @revathi

*This is an idea from @cneivam  from the Portuguese Community*

• Being able to control the workload in Alteryx Server (for example, making sure that a workflow can run only when another set of workflows finish running)

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.

CC: @BlytheE 

Can we make API function available to assign specific worker node while submitting job request using api.

Good Day.

We would like a built-in process that would search or, and resolve, workflows that are stuck in the "initializing" state. These seem to happen for various reasons but communication problems between the controller and workers .. usually a socket timeout.. which appears  to be most problematic. It seems  that these type of errors should be expected in all but the most stable environments,

Currently, the only tool that we have to solve this problem is to restart the Alteryx Service on the controller and while this works there tendency to cause some collateral damage in workflows ...erroring or restarting from their beginning.

There may be a way to solve this without restarting the service by editing Mongo using a tool like Robo 3T but that is unproven and has its own risk.

After dealing with this issue and struggling for quiet some time we think that the best option is to implement a "clean up" DB process that will run every 5 min or so, capture a list of workflows in the "initializing" state , then compare that list to one in the next 5 min cycle and fix any workflows that appear in both lists. We think that returning  any stuck workflows to the queued state would be the best Fix  option.

We just don't want to continue to use Restart the Service process to solve this issue and accept the collateral damage.

Thank you for your consideration

Tom D  

I'm really enjoying the new Save As functionality to push to the gallery, but had a request that would make it even more useful for me. 

I saw that you can open workflows directly from the Gallery and edit them with version control, but it would be nice if it was possible to do a Save As on a local workflow and point it at an existing copy on the server.  I need to maintain a local copy of my workflow for dev/prod separation, but currently my way to push to prod is to do a Save As to my Private Gallery, remove the existing copy from the company gallery, and then share my newly created workflow into the company gallery.  This causes some headaches like no version control, switching out icons everytime, and overall just a messy way to push to prod.  

It would be helpful if there was a way to overwrite an existing workflow in the gallery rather than editing it directly.  

Can we add an ability to manually adjust the order of workflows in a collection? I don't think we should have to go and click the column to sort each time if we want them in alphabetical order. It looks better for the end user to have everything nice an arranged when you have multiple processes in each collection.

Hello,

Tableau has a nice Postman Collection available... it's really easy to use since you can download or forkt it on Postman and all you have to do is to write the variable values.

I would like the same thing but for Alteryx.

Best regards,

Simon

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 Alteryx has a timeout setting at a worker level which applies to all of the workflows/schedules that run on that node. 

It'd be great and very useful is that setting is made available at a granular level like at the Collection/User Group or workflow level. 

I've been told by Alteryx support that this is not a feature that is currently available. Hence proposing an Idea on the community requesting for such an ability!

We use the Server API to manage our server environment - and we recently noticed that the Workflows API (/admin/v1/workflows) ignores any canvasses after the 10 000'th submission.

For example:

• If we don't use any offsets or limits - then we get 10 000 applications
• If we use an offset of 5000 with a limit of 10000 - we get 5000 applications (i.e. anything after canvas 10 000 is being ignored)
• if we use an offset of 9990 with a limit of 100 - we get 10 rows returned (i.e. anything after canvas 10 000 being ignored)

By querying Mongo directly (appinfos collection) we know that we have 18 800 or so unique applications in our environment.

Please can you remove this cap from the API so that it can be used to query any number of canvasses on a larger environment?

cc: 

+  @Hemanth @marydest24 @Shreyasi @Sotoll @Kosi @revathi @Bethanyturner012  @TanyaS 

Hi,

I have described my issue in the Community post here:

https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Version-Management-in-Gallery/m-p/120319#M3...

Is there a way to retrieve an exact date when new version of a workflow was uploaded to Gallery? I know it works when it is today, yesterday or couple days ago but after that you can only see "2 months ago" etc. in Creation Date, which is not sufficient for any version management.

Thank you

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.  

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.

Use Cases:

1. As a server admin, planned PM outages should be scheduled.  These outages should prevent jobs from beginning execution (window of time) prior to the outage.  Jobs running at the time of the cut-off should be system-cancelled.  
2. As a server admin, unplanned outages should cause running jobs to stop.  At the conclusion of an outage, jobs that are system cancelled should be restarted.

Currently, we use Task Manager to control Alteryx Service (or command line).  An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities.  While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't.  Other admins have asked what is "hanging" alteryx service up for a STOP command.  I have explained that all jobs must be stopped in order for a quick restart of the service.  

We're using a single server today (this client) and plan to add workers to the configuration.   It would be helpful to know where work is running and be able to use admin functions across the servers.

Cheers,

Mark

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. 

Thank you!

The workflow result window shows the Name/workflow, AMP, Priority, Assigned worker, Run as, Completed at, Runlenght, and Runtyp of the workflow. The following feature would also be useful on the page.

1. Showing the creation date of the workflow without taking queue time into consideration
2. The option to change the time zone would make it easier to analyze the logs
3. Detailed insight about the particular workflow results, such as average execution time, failure count, and success count with date filtering. 

Hello!
I found a weird bug in my travels today.

The TL:DR is that when a date input tool within the interface tool is used within a collapsing radio button, it defaults to "dd/mm/yyyy", breaking any app when this is not filled out: 

Both values are default - i have not edited these values. The weirdest part is, this is Server/Private Gallery specific. When this workflow is downloaded and run within Designer:

And the workflow runs fine.

I have not tested this with any of the other interface tools, however I suspect this to not be the only tool this issue resides within.

I have attached the workflow I used (not that it would take long to recreate) for testing.