Alteryx Server Ideas

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.

Admin settings for the Alteryx server are currently split between the Admin GUI in the gallery (screenshot 1 below) and a tool called "Alteryx System Settings" (screenshot 2 below).

Please could you move all of the system settings into the Admin section of the GUI.   Not only will this allow an admin to administer the settings remotely (rather than having to be logged into the actual server with an interactive login which is needed now) - it will also consolidate them into one place which makes things easier for admins to ensure that all settings are set up correctly.

This could be done progressively - a little bit in every release - over the next couple of releases, it does not need to be done in a big reengineering or a massive big-bang release (in fact - progressive release is much more favourable since you learn along the way and big-bang releases are well known to be failure prone).

cc: @TanyaS 

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 

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 

2019.4+ Server now prompts users to select an Encoding Type when downloading a csv on the gallery. Unfortunately there is no way to disable the prompt of which encoding option to utilize or an ability to select a system default. Please provide these server options as this is causing confusion across departments. 

.csv output

.yxdb output, csv format

(many users like the preview provided by yxdb but want excel download)

During development in Designer, when the workflow is configured to output to csv it already has the encoding configured, please provide the option to at least default this at output on the gallery:

.csv config

The only alternative at this time is to republish all workbooks configured to output .csv or .yxdb to be .xlsx. This is not ideal.

Note: Scheduled jobs are not affected - I tested a scheduled run and csv files were successfully written out to a file share on the server. Content format appears to not be impacted. 

Thanks!

Hello everyone,

I created before a post about managing chained workflows using the API.
After reaching out the support, it turns out to be impossible, which is unfortunate.

So I post this idea here, in case anyone is needing it too.

Feels free to ask me details if needed.

Thanks.

It would be good to have these table headers sizable, so that it can be expanded to display complete Name (and other fields).

The mongo db back is a working process but I would like to replace individual workflows and not the entire server state.

Currently the e-mail settings for the server are set up using a wizard and are not available within the admin UI.

Please could you add an explicit section to the Admin UI to allow the admin team to set up approved SMTP settings, allowing this all to be managed in one admin console.

Further: Can you allow the admins to push these settings down to the desktop users.   This would allow the admin team to control the SMTP usage and prevent data leakage.   It would also reduce complexity for the user since the SMTP settings are all pre-set making eMail tools; and Events easier to set up.