Alteryx Server Ideas

Given some jobs are scheduled / can take a while to run it would be useful if Server provided the option to notify the submitting user when it has been completed, which a link to the results.

If you look at post: Re: How do I extract Server Job Run ID at runtime - Alteryx Community amongs others you can see there have been various attempts to create workarounds for this using a combination of API's & Mongo DB calls to build up the information to provide a URL in an email at the end of the flow. However, it feels like this should be an out of the box notification that can be enabled/disabled at the flow level with Alteryx Server.

It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).

My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events.   On a large implementation, this becomes very difficult to manage.

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.

Hello all,

According to https://openlineage.io/ 

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

Maintaining multiple workers (five currently, soon, six) with identical setups is challenging when dealing with In-Database (InDb) connections. I must log in to each worker, start Alteryx Designer, go to In-Db settings, and create the connection. This also becomes tedious when trying to update passwords, which occurs every 90 days in my company.

The suggestion is to set up an In-Db connection on one worker and have it propagate to the other workers. 

Propagates to other workers →

This would save time maintaining workers in the gallery and help prevent errors during setup on each worker (e.g., typing in the wrong password).

As an "extra credit" mission, expose In-Db connections through an API that can list, create, update, or delete an In-Db connection.

My team has started using an Alteryx Gallery 2022.1 instance and we have workflows that take a few minutes to run. Whenever we run a workflow, we are presented with a blank screen instead of the progress bar that we are used to in previous versions of the Gallery. I was wondering if there is a way of enabling the progress bar or at least setting up a load screen to notify the user that the workflow is in progress to avoid them wanting to re-run the application because “nothing is happening”.

This is what we are seeing:

This is what we are used to and would want to see when running our applications:

One of our Server customers has a need to disable all schedules temporarily across all worker nodes.  I do not see an easy way to do this unless we go into each worker's settings and disable from there, but this is not ideal.

The reason is for scheduled maintenance windows during a large upgrade or migration.  Currently stopping the Alteryx Service on each worker is time consuming.

Thank you! 

I have three team members all in the same private studio. We can see each others' workflows. However, when looking at a workflow that another team member has published to the gallery, it looks like:

1. The workflow has never been run
2. The workflow is not scheduled to run

This is a massive impediment to collaboration because my team handles ETL for most of the company. If a user complains that their data isn't up to date, whoever receives that support ticket needs to be able to see if the workflow is actually running and whether it was successful or had an error during the last run.

Preventing a team from seeing this for each others' workflow schedules and results means that the only person who can deal with an issue is the person who originally made the workflow. Which makes the idea of a shared private studio wholly pointless as we may as well be operating in different universes.

Please create a studio-level setting where all members of a studio can see all schedules and results of all workflows in that studio.

When adding jobs to the queue via API call, you currently cannot specify the name of the job.

Running the job directly from gallery allows this as in the picture below, but there is no setting to do so in the API.

When a workflow is used in many different situations, being able to specify a name for the individual run will make tracking and troubleshooting easier.

Wanted to grab some attention here regarding the Alteryx gallery search engine (which also bleeds over into searching for schedules and jobs when troubleshooting). 

Since a picture is worth a thousand words, I'm pasting two pictures (one attachment) of searching our gallery for the word "Contour" and the word "Signal". Both of these words are in the title of a single workflow - when I search for the word "Contour", the workflow pops up. When I use the first word in the workflow, which is "Signal", it doesn't pop up. 

I appreciate all that Alteryx does, but I wouldn't think this should be a difficult issue to fix, and I would imagine there are other frustrations with the functionality here. 

Hello,

Maybe it's time to have a better licensing model. In addition of the current and restricted core-base model, why not having a user-based model?

Best regards,

Simon

As the Server Admin I'd like to have the ability to view ALL "Workflow Results" for all Subscriptions.This will give the highest level admin the ability to monitor all schedules (on the entire server instance) and monitor if they are unable to complete successfully (example- unable to allocate memory) and any other errors are occurring. 

Knowing this information will help the server administrator understand if there are issues with the server itself (e.g. if we need more workers or to simply adjust actual server system settings..etc..)

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.

In prior versions, Gallery Admins could easily and quickly reactivate users that were deactivated (e.g., and employee leaves the company so we inactivate their Gallery account, but then they come back to the company in a few months with the same name and email).  

Now, the only way to do this is to edit the Mongo page.

We need a way via the UI to reactivate users, like we did in the old UI.

I suggest adding an option in the current User List/Grid to be able to filter for Inactive users.

Previously, Alteryx Gallery had a progress bar when the job is running. However, it has been removed in the newer version and the screen only appear blank when the job is running. This could lead to confusion in users as they might be wondering what is happening when the screen goes blank when it actually is running the job. Users might also attempt to click the run button repeatedly due to this.

Hence, I hope Alteryx could bring back the old UI that showed progress bar or anything similar when the job is running so users will aware of what is happening. 

Most companies work on a period level basis and that is every 4 weeks.  There is no way in Alteryx currently to schedule workflows to run only every 4 weeks, the monthly options do not match this cadence.  If the option was added to select "every X week(s) on X day" this would also encompass biweekly scheduling as well.  Outlook currently has exactly what would be needed (screenshot attached.)

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.

When an artisan moves positions (within or external) away from their current responsibilities, their collections and workflows should be able to be transferred via an administrator to another user.

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.

• https://onlinehelp.tableau.com/current/server/en-us/data_dictionary.html
• https://onlinehelp.tableau.com/current/api/rest_api/en-us/help.htm#REST/rest_api.htm%3FTocPath%3D___...
• https://community.lithium.com/t5/Developer-Documentation/bd-p/dev-doc-portal?section=commv2

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