Alteryx Server Ideas

Alteryx Server seems to natively support MicrosoftSQL and Oracle connections on Alteryx Server. It would be helpful to natively support (i.e., a non-ODBC connection) for Cloudera Hadoop as well.

I'd love the ability to have one schedule for a workflow at specific times. 

Currently you have to create 4 different schedules if you'd like a workflow to run at 10 am, 3 pm, 5:30 pm and 11:30 pm and doing this makes the "Scheduled Workflow" section of the server not only cluttered, but a lot more difficult to manage.  (like spotting accidentally duplicated schedules- which also happens more often than i'd like :)

Thanks!

System Administrator should be able to configure portal pages be being able to choose the columns, columns widths, and sort order.  For Example  in the collections view,  there are columns Inight Count, User Count, Studio count which add no value to my user community.  Yet the name column is not wide enought to show the full names. The collect page is sorted by Create Date which does not add value and once you get above 20 collections  

The recommendation would be to allow System Admins to be able to change these settings.  If the definations are stored a json or xml file or some other file that can be edited, allowing for the customizations.  Admins would edit at their own risk working with in parameters and documentation provided. 

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.

Currently, Alteryx Server has a setting for how many days to keep Results from scheduled workflows, which prevents your Results log from getting too large.

Unfortunately, this setting is universal to all workflows, regardless of schedule.  If you have monthly jobs sharing a server with jobs that run every 5 minutes (which we currently do), and you set your limit to 30 days, you get at most 1 result from monthly jobs, but 8,640 results from your 5-minute jobs!

A better option would be to keep the most recent X results from any schedule (where X is user-configurable).

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

Having the option to disable schedules within the Designer application would be advantageous for we support staff.  Especially when multiple service restarts or server reboots are required.  When we perform migrations or restores or even upgrades or when conducting server maintenance actions.   As we know starting of the Alteryx service immediately queues up workflows to be run based against there schedule times.   When maintenance is being performed we do not want workflows to run, and/or having to wait for completions or have the user to rerun the workflow.   The option to temporarily disable schedules globally with a click of a button is far better then changing the parameters of the schedule or even deleting it.   To go a step further = an internal mongodb administration command to disable/enable schedules would also be helpful at the database level 

When a render tool is run on Designer pointed to a temporary file the log gives you a clickable link to access the output.  When deployed to the Gallery unless you have given it a specific output destination with %temp% in the filename you get... nothing.  

What did I expect?  The pdf or other temp file to render on the screen or at least download for me.  Or give me a dropdown selection of the various files render could create for me.

Please consider adding this feature to the Alteryx PRIVATE Galleries.  This is a feature of the Alteryx Gallery and would be useful for our clients too.

Thanks,

Mark

We've noticed on our Server Gallery that users must click 'Run' two separate times when running an app.  The first time they see 'Run', its really taking them to a configuration screen, rather than actually executing the tool.  What if that first 'Run' button was changed to 'Configure'?  We've seen that users hesitate to run apps because they aren't sure what they're getting when they click 'Run' the first time.

Very Simple Request.

Just like how you can search for a collection, we would like to be able to search for a schedule. One team has over 5 pages of schedules and it would be nice for them to search for one to update vs having to scroll through 5 pages to find it

Currently, we have the functionality to set a recurring schedule with daily frequency with an option to 'Run only during work week (Mon-Fri)' I would like to add this 'Run only during work week (Mon-Fri)' option to the Hourly frequency interface. 

No current option to run on weekdays only:

One of our biggest areas of confusion for new users of our Gallery is the Download button. They often click it thinking that will give them their information right away. It would be great if the person didn't see that or the scheduler option if they were not an Artisan, since they can't use the workflow anyway. It would be even better if selecting the workflow took them straight into the question portion.

In any large IT environment - you will have multiple systems which each use different nomenclature to describe the same thing

This relates to products; currencies; customers; suppliers; trade types; etc.

At present - our users are bridging this gap either by:

a) creating a bunch of excel spreadsheets with "Magic Code Translation Tables" - which is unfortunate because these become unmaintainable very quickly and live on people's desktops (and are not reusable assets) or

b) creating a whole morass of one-way-translation tables to translate from each input source to the normalized format - these are all hand-rolled translation tables; with hand-rolled ways of adding translations etc.

What would be very useful is to allow Alteryx users to specify these kinds of domain concepts on the Alteryx server, with a flexible way of adding synonyms.  For example - our master customer list is kept on the server with a master customer ID (call it MID for Master).   If I'm dealing with a new system that uses a different customer ID (call it NsID for New SystemID), then I can map the NsID to the MID centrally so that anyone who wants to do analytics on this data can just drag in a converter from NsID to MID; and also drag in the master customer list with the MIDs.

This would allow all these Magic Translation Tables to become an enterprise asset rather than isolated data islands, and act as an accelerator for every other team using this data.

As we continue to build Alteryx Workflows for the business, there is a continued need for an organizational structure for saving and storing Alteryx Workflows within the Alteryx Gallery. Organizing the workflow repository through a "folder hierarchy" will allow users to quickly navigate and find the appropriate workflow. Currently, the workflows are listed in alphabetical order and requires the user to remember the Alteryx Workflow name and click to the proper page. 

Any enhancements to the Alteryx Gallery organization structure would be greatly appreciated!

Thank you, 

KK

Currently if there is a password change, I have to download my workflows, update the password in the Tableau connector, and reupload the files. 

This would enable groups with a single sign on to ensure scheduled workflows are not interrupted. 

Allow the artisan to turn off the ability of a member to download app results.  Some of the information is highly confidential, and we don't want them to be able to easily print out a list of this information and have that list "floating around".  Or take sensitive client data with them to another job if they leave us and use that to profit their new employer.

Hello,

Currently a workflow sends notifications when is configured to do so (by adding an event in Designer).

I think that there should be an option to add a notification event for a schedule. It makes more sense because:

- I don't need notifications when I run a workflow by myself. I need it for schedules

- Turning on/off a notification is technically a development - it should be a configuration.

Thanks,

Piotr