Alteryx Server Ideas

Currently it takes four clicks and three displays (including the current scheduler display I'm attempting to post as well) just to temporarily disable a job.  It would be so much more convenient if there were a one touch icon on this display that allowed you to do that function.  

When using In-DB with iSeries over Generic ODBC everything works fine in Designer however when executing via Gallery process fails because a semi-colon ";" is added to the SQL statement as a terminator character and iSeries rejects this SQL0104 - Token ; was not valid. Valid Values < END OF STATEMENT > 

We have a MongoDB connection string that we plug in to RuntimeSettings.xml during install.  Upon startup, the Mongo connection fails because RuntimeSettings.xml expects the connecting string to be encrypted.  The fix for this, is for someone to manually update the MongoDB connection via the Alteryx UI.  We would like a way to encrypt the MongoDB connection string for RuntimeSettings.xml before we start Alteryx for the first time.

Hi Alteryx Team,

I understand that the Timeout feature on all Workers is only available for the workflows scheduled on Alteryx Server.

In a heavily used server environment and depending on how workflows are configured, can we have a timeout feature available for non-scheduled workflows (adhoc workflow runs/manually triggered workflow runs) as well on all the Workers on Alteryx Server ?

Thank You,

Nishi Jain

It would be great if we can set the priority of a job when scheduling a workflow through either the Designer UI or through AlteryxService addtoqueue command

In my organization we primarily schedule jobs through these avenues and this would bring them up to par with the scheduling capabilities of Gallery

For example:

AlteryxService https://help.alteryx.com/current/server/alteryxservice-commands

addtoqueue=path,host[:port],secret[,true]

^ add an optional parameter that takes enum value {Low, Medium, High, Critical}

Designer UI

Add a dropdown that takes an enum {Low, Medium, High, Critical}

Alteryx Server API should be allowed to publish the workflow in the gallery. 

Hello,

Looks like the user inputs (check boxes, free text fields, drop downs, file uploads etc., ) to the app are "temporarily" stored during the course of the app "Run" time. These - especially the "uploaded files" get deleted from  the temporary folder after the successful run of the workflow.

Ex: user uploads 2 files to the app as inputs. see attached interface.

It is important that the user selections are persisted on the alteryx server for debugging, investigation, audit trail purposes.

Of-course - there are workarounds by some extra code/logic within the app. But - in-order for the "server" tool to be considered as robust/industrialized - it is critical to "log" the user interactions on the server side.

Is it something already looked into?

Regards,

Sandeep.

The search for replacing a workflow is poor (and I get that it is probably challenging to write on the back end) but as a result even if I type in the exact title of the workflow (aka copy and paste) Alteryx replace can't find it. Not only does this mean I have multiple workflows with the same name running around (loads of fun with lack of version control) but it also makes this entire thing more frustrating every time I update a workflow (as normally this also means the scheduling of said workflow breaks).

It would be awesome if instead of having to search by title for your workflow that you wish to replace with if you could instead use the URL where Alteryx Gallery put the workflow and then there wouldn't be any confusions about which workflow and you wouldn't have to type.

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

- Gallery in all supported languages

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

• Can’t use CReW macros in Server

Hello Alteryx Devs - 

So, I'm poking around the Atlerxy Gallery API stuff with an eye toward building a set of classes that can interact with workflows without exposing Gallery proper to the community at large.  That being said, I was a little dismayed to find that all interactions require inclusion of *user specific* API Keys and Secrets.  It can be dealt with, but ultimately it means that configuring a middleware tier between the real world and Alteryx server requires an additional hierarchical level; i.e., understanding which of the developers came up with workflow X and having *their* API Key / Secret attached at configuration time.  

Anyways, it might be easier to just have a global trusted key / (super) secret.  If you get that, you can execute a workflow.  

Maybe we have a special studio that people could clone to, and in this way, you'd only have to track a single key/secret outside.  

I mean, the existing system works OK for one offs, but if you wanted to have a (semi) modular system in place, dependence on understanding publishing entity specifics seems to muck things up for no discernible benefit.  Of course, maybe in some places there is benefit to this scheme (?), but it is causing me to craft some weird work arounds early in development, which gives me a sinking feeling.

Or am I doing it wrong? 

Thanks for listening. 

brian

Hi,

I have missing this functionality in alteryx gallery where we can see the runtime status of running app.

In Workflow result option we can view only post completion of app run.

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

I know that the documentation shows that you can setup a worker to a specific QoS so that it will only pick up work for a particular workflow or app, but there could be a greater use for it.

For example if the Admin could control what QoS means for each definition.

I.E. Application, vs a workflow that runs over an hour, vs in-database tools. Then it will allow the admins to self guide where the work is going.

Right now there is only three levels

• Normal workflow execution: QOS = 0
• Chained application execution: QOS = 4 (all apps in the chain aside from the last)
• Workflow validation requests: QOS = 6

This was great for Alteryx public, but for private Galleries we need to distribute the work better than FIFO.

 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 

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 

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