Alteryx Server Ideas

It seems from my own experiences and other community posts (e.g. https://community.alteryx.com/t5/Alteryx-Server-Discussions/Scheduled-worklfow-not-picking-up-the-qu...) that when scheduling a workflow in the gallery, the gallery will run whatever version was most recently uploaded, regardless of which one has been labeled as "Published". Since naturally the intent is for the Published workflow to be the only version running, it would be nice (adnd would me much more logical and intuitive) for the scheduler to run that version.

It would be nice having the ability to alter the timeout of the file upload on Alteryx Analytic Apps uploading to the Gallery.  Having it restrained by time and not file size makes it so that users with poorer internet speeds will not even be able to upload moderate sized files.  

Is Alteryx looking at implementing some kind of feature to provide a preview of impacted objects (lineage view) & understand dataconnections' changes impact before it's implemented ?

Benefits:

• Help users understand the ramifications of any changes they make on other cards, DataFlows, or DataFusions.
• Search and explore data lineage.
• Easily find broken dataflows.
• Quickly determine the impact of dataconnection changes on the rest of your Site, Collections, Application etc.

DOMO has this well done in their platform, check it out rather than me explaining here..

Search for Data Lineage & Impact Analysis.

https://knowledge.domo.com/Connect/Managing_DataSets/Viewing_the_Impact_of_Changes_to_DataSets_-_BET...

Hi, our analytics team has dozens of workflows saved to Gallery and scheduled to refresh at regular intervals--or at least we did up until this weekend when the scheduled refreshed terminated for some unknown reason.  We currently have a team investigating the cause. 

The last run for the workflows took place between 10 PM on Friday 3/6 until 2 AM Saturday 3/7.  We didn't notice the refreshes getting terminated until start of business Monday morning.  Immediately our internal customers started asking us why things were out of date and we quickly found the issue and we're now going back and refreshing the data and re-initiating the scheduled refreshes.  However, some of our workflows can't be retroactively restated, so we'll just have a gap in the data from this point on. 

Needless to say, this is unfortunate for our org, so I'm trying to think of ways to avoid it in the future.  Having a notification set to send an e-mail when a workflow errs is helpful only if the workflow gets kicked off to run to begin with.  However, this will not help in cases when something has gone wrong to prevent the running of the workflow to begin with.

What I think we need is a system to auto-generate an e-mail to a person/group whenever a schedule is termed for any reason whether if it's by a person actively terming it, or for any other reason.  Just as you get a confirmation e-mail whenever you term an e-mail subscription, getting a confirmation whenever a scheduled refresh is ended, would be extremely useful.  

Thanks, Kurt

Hi Team,

     Just like the workflow upload API, could you please provide an API end-point for deleting the workflow,Job results and it's related information. In a scenario we might use gallery for one time execution of workflow, once the output was generated there is no point to have some workflows in the Gallery hence in this scenario the Delete API helps as a clean up activity on the Gallery to avoid the Junk/Unused information (Workflow/Job/Outputs). 

When looking at a Workflow in the Gallery there is no way to tell if it currently resides in a collection. As a suggestion, a good place to have this information would be in the header block of a workflow where the version information and number of times a workflow was run is stored.

We have a usecase where we want to check how often a workflow runs via the API so we can automate the consumption reporting we do internally. Right now the API only reads out workflows that were scheduled using said API. That doesn't make a whole lot of sense. Enabling it to also read out all the other workflows would really make this a powerful feature for us and I suspect others.

HI,

I could not find any possible way to send an email if the Alteryx workflow is taking more than expected time.

I was wondering if any such feature is available

In my organisation, Alteryx workflow keeps running sometime due to memory issues. It will be great to know about these delay and handle them.

Regards,

Vish

In our private studios and in our home page we see our workflows in grid view by default and can toggle that to list view if we want. 

BUT we can only see our collections and the workflows in them in list view.

Please can you add the ability to view our collections in grid view?

 Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted. 

so every time there is a java version upgrade,  users have to be notified of the downtime  (even though they could move into 7 day grace period) and then the flexnetls.settings file has to be updated with Java home path.  

Local License Server settings has to pick up the latest Java installation and not require manual Config change and service restart. 

@Kosi @SeanAdams 

 Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted. 

Product should be capable of using the newly installed configuration and not require manual Config change and service restart. 

so every time there is a java version upgrade,  users have to be notified of the downtime  (even though they could move into 7 day grace period) and then the flexnetls.settings file should be updated with Java home path.  

@Kosi @SeanAdams 

Password is required to execute any command on LLS. Last time we forgot the password, only way to retrieve it was to reinstall the LLS ! 

A command to reset password in LLS should do.

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

Password entered during installation is changed to LLS default password after the following sequence of events.

LLS Service start -> Settings update -> Service restart (to let the settings change take effect). 

Avoiding this behavior will save server admin's time in changing password every time setting is changed. 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

Installation/upgrade of java in all servers are usually firmwide Tech team activity - which are outside of Server admins control. 

Java support by Alteryx - is version 8.0.212 - while the latest version available in our premise is 8.0.241. support for latest version of java - which is required for functioning of Local License Server should be prioritized. 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

In stead of having to create an event to notify me when workflows are failing, I would like to easily enable that option from gallery after scheduling a workflow.

regression

Judging by the Community, it seems like the Alteryx business model is to crowdsource documentation. Do the same for a QA checklist. The 2019.4 release of Server shipped with some major regressions, notably:

DE21143 Workflow events no sending Email

DE22751 32-bit OCI connections not working in 2019.4 release

The QA team should publish the QA checklist and allow feedback from the community. The entire point of the community is to make the users and the product better. Let the users see which scenarios are tested and add ideas here for the QA team to utilize.

We're looking to use the worker setting that cancels jobs that run over a certain amount of time. However, In testing we noticed when the server kills the job it does not trigger the workflow event for 'after run with errors'. That said, it does trigger the 'after run without errors' event, but there is no detail in the email as to what happened. This behavior seems counter-intuitive. We primarily use 'after run with errors', so our users could potentially have their workflows cancelled and never hear about it. 

is it possible to do one of the following:

• Trigger the 'after run with errors' workflow event if the server cancels a job
• Have a server notification that emails users when a job is cancelled due to run length

We're currently running server 2019.1, so please ignore this idea if this issue has been resolved in later releases. 

Here is the server setting I am referring to

Have the Alteryx Server send a notification when the license is within a configurable amount of days to being expired via SMTP

Currently we have built-in authentication for Alteryx Server.
In that state, the Default user role of Gallery is set to "Artisan",
If you sign up to create a new user and log in,
It will be registered as "Viewer".

I want the default user to be valid even with the built-in authentication.