Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.

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

The V3 jobs API endpoint woefully lacks any usefulness. The current endpoint only has a get jobs/{jobid} method that is not useful because a database admin must query the database to get a list of all job IDs. To add insult to injury, this method is only limited to the user whose job is running or queued.

 

These are new features that I am proposing

1. GET jobs/listThis method must be callable by all users. Parameters such as none (default—full list), running, or queued will display jobs with the appropriate status. The job ID of the running or queued job and the worker it is running on must be included in the resultset.

2. GET jobs/{ownerid} — This method must be callable by all users. Like the GET jobs/list above, the resultset must include the job ID of the running or queued job and the worker it is running on.

3. DELETE jobs/{jobid} This method must be callable by the person who scheduled the job, the owner of the workflow, or the curator. This method is the equivalent of cancelling a job on the Server Admin page - #!/admin/jobs by a curator. All three mentioned people have a vested interest in the running or queued jobs on the server and must be able to cancel those jobs.

4. POST jobs/reassign/{jobid}/{new_job_tag} This method is restricted to the curator and applies to any job in a queued state. It allows a curator to reassign a job to another job tag or the first available worker for reasons determined by the curator.

 

This is an enhancement that I am proposing
1. GET jobs/{jobid} This method must be callable by all users. This will allow any user to get the details of any running or queued job.

 

Logging requirements

All DELETE or POST methods must be logged and purged based on the Persistence OptionDelete queue and results after (days).

 

 

Situation:

As your analytics work grows - you find yourself using the power of Alteryx to create shared macros.    These act as an accelerator for a team because one team member can us a reusable solution created by another team member.   For example - many teams need to get data out of JIRA (or some other system) so you create a connector that everyone can use.

 

That's going well - and now you have 20 teams all publishing canvasses to your server (possibly 100s of canvasses running in production) which make use of your JIRA connector - all good so-far!

 

Problem:

BUT THEN - you discover an issue with the JIRA connector and you need to fix it and publish a new version!

 

It's at this point that you realise that the canvasses on your server which use your JIRA connector are NOT pointing to it, but they have made a copy and included this inside their canvas.   So when you fix the problem with the JIRA connector - no-one gets the fix!

 

This is because every application uploaded to the server is a yxzp file, which zips up a COPY of all the shared macros and uses this in an isolated way.

So - in order to get the new JIRA connector (with the defect repaired) used instead of the old one you now need to:

- Download EVERY canvas on your server

- Unpack them all to expose the sub-macros being used

- Inspect them to see if they are actually an instance of the JIRA Macro

- Make a list of the owner and application IDs

- reach out by e-mail or phone to every one of these folk to ask them to republish their Alteryx workflow with your new version of the JIRA connector.

 

 

Proposal:

Please can we revisit this - we really do need the power of shared macros - and we also need the ability to fix and manage these like a product over time.   This will have an impact on the engine (hence copying @AdamR_AYX ) 

 

Desired end-state:

- When you build a canvas using a shared macro - it doesn't store the macro itself, but rather a reference to the version on the server - unless you explicitly decide to break the connection and take a copy.

- When you check this canvas into the server - your application / yxzp does NOT include a copy of the shared macro - instead it has a reference link

- this means that Alteryx Server can now track which canvasses use this shared macro very simply

- When I fix this shared macro - I can then do an in-place update; or if the interface is not the same (i.e. different inputs or outputs) then this has to be a new version and the users will stay pointing to version 1.

 

This is how shared assets are managed in a micro-service world, which is the way that all of our architecture is going - and it seems important that we build this thinking into the Alteryx infrastructure too.

 

 

 

 

 

 

 

@AdamR_AYX ; @Treyson ; @SteveA @DerekK ; @BlytheE 

Hello all,

According to https://openlineage.io/ 

 

image.png

 

 

 

An open framework for data lineage collection and analysis

Data lineage is the foundation for a new generation of powerful, context-aware data tools and best practices. OpenLineage enables consistent collection of lineage metadata, creating a deeper understanding of how data is produced and used.

 

 

 
This is typically the open standards needed for lineage analysis and I think it will become more and more a differenciator with your competitors. As of today, DBT or Apache Airflow already supports it (as producer), Egeria or Marquez already support it (as consumer) and guys from Datahub are working on it  (as consumers)https://feature-requests.datahubproject.io/p/openlineage
So I think Alteryx should implement this standard API as a producer, it's the next big thing in Data Governance and you don't want to stay behind !

Best regards,

Simon

Currently, the API V3 endpoints does not have anything for Data Connection Manager (DCM). Create an endpoint to allow users to add/delete/update and list data sources, credentials, and users of DCM data sources. Also include an "admin" endpoint that can list all of the above for the entire server.

 

The admin screen of Alteryx gallery does not have an admin function for DCM sources, its users, and credentials. This can cause visibility issues during audits of the gallery. An API endpoint can alleviate this issue until it is added to the UI.

The AlteryxService internal authenticated API that the nodes use to communicate with each other for status is not accessible to customers because it is using an undocumented authentication method. The data this appears to provide would be useful to server administrators to determine the true health of the individual nodes and for reporting purposes.

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.

 

 

Given the need for administrators to be able to perform analysis and monitoring on server performance; user usage etc - it is necessary to provide full documentation for both the API and the database underlying the server so that admins can use this to good effect.

 

Ref: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...

 

Although very limited documentation is available on the server API (https://gallery.alteryx.com/api-docs) what we're looking for is a much more fully formed and navigable experience like some of the examples below.

 

This will make building helper processes substantially easier; as well as allow admins to fully manage their environment.

 

Many thanks

S

cc: @HeatherMHarris @revathi @AshwiniChezhiyan @LizaNemchynova

 

Currently, in order to run an app via the API, you have to have uploaded the app to your private studio. Frankly, I don't find this function useful because you have to download then re-upload an app in order to gain access to the API. The API would be more useful if when an app is shared with you (or a collection is shared with you), then it would also allow for that app to be run via API by the user it was shared with. Right now, the only person who can run the app via API is the user who originally uploaded said app. 

Hi

In a heavily used server environment, and depending on how workflows are deployed, it is possible to accumulate a vast number of "one off" workflows that could/should be deleted  as they would never be used again. In one of our environments we have over 1 million of these.

 

Currently we are manually deleting them 500 at a time but have asked if there is a way to script the delete process to make it more efficient. We have been told that to really delete a workflow you would need to touch at least 4 collections.

 

Can we have a Delete workflow API in one of the next releases in order to address this issue?

 

Thank you

 

Tom Diroff

There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.

 

I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.

 

APIs I am requesting be released:

  • PUT .../gallery/api/collections/{collectionID}/apps/{appID}/
  • POST .../gallery/api/scheduler/

My team currently uses the API to call a large number of workflows via a Python based scheduler process.  We use this currently by having ~10 users in a single subscription (Private Studio).  

 

All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.  

 

From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.  

 

Are there plans to adjust the API endpoints in the future to better account for this?

 

Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.

 

Thanks

API that allows to specify the workflow version to download.

Hi, 

 

I think it would be extremely useful to be able to trigger an Alteryx workflow using Power Automate. 

 

The main benefit I see at the moment is automatically triggering an Alteryx workflow when the input data has been refreshed.

 

This would also enable a Power App to be added directly to Power Bi which can simply be clicked to re-run an Alteryx workflow then refresh the Power Bi dataset. 

I’ve had a query from a Team here at my organisation regarding OAuth2. They are trying to investigate whether a Robotic Process Automation Tool can be integrated with the Alteryx Gallery API.

It uses OAuth2 but my understanding is Alteryx Gallery uses OAuth1. 

 

Can Alteryx Gallery API be enhanced to use OAuth2? A plan to support OAuth2 authentication for a REST API in a future release?   

The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections.  The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.

 

Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.

 

This might be considered a subset of the Idea Server API to extract / submit workflows.

 

 

Thank you for your consideration.
Sincerely,

David

 

Hello Alteryx Developers,

 

It would be great if you develop a way to connect the Alteryx Designer to AWS Redshift by SSO. When i try to set this type of connection at the Simba ODBC Driver it opens the connection several times with AWS at the browser and that ruin the customer experience.

 

Best Regards

 

Danilo Benjamin

Our company has workflows where we use the Gallery API to kick off executions on server.  The user kicking off the workflow has setup API access using his account, but when he kicks off his jobs, it does not show up under his Gallery so he is unable to view the results.  In the admin panel, it shows the owner as (None) so it does not appear that workflows kicked off via the API get assigned to the user tied to the API key.

 

Conversations with Alteryx support revealed that these results are available via an API call, but not within the Gallery web UI.  It would be great if the user tied to the API key were added to the workflow execution so they could see results within the Gallery rather than going back through the API.  

 

api_execution.png

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 

 

 

 

DeleteEndpoint1.jpg

 

DeleteEndpoint2.jpg

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 

Hello,

We use external corporate scheduler and we would like to start scheduling Alteryx workflows in this way. However, collections don't have API which would simplify our way of running workflows which we are shared by the users. Are you planning to enable such feature?

 

Best,

Piotr Zawistowski

Top Liked Authors