Alteryx Server Ideas

The idea is to have tabs on separate pages in the Gallery (or the option to allow that type of behavior).  Right now, if you created an analytic app that has questions on different tabs they will be on separate pages in Designer, but when you push the workflow to the Gallery all the questions will be on the same page. The tabs act as a navigation bar instead of taking you to separate pages. 

Here's two different discussions that ask about this in case there is any confusion:

https://community.alteryx.com/t5/Alteryx-Server-Discussions/Interface-Designer-with-TABS-in-the-serv...

https://community.alteryx.com/t5/Alteryx-Server-Discussions/Analytic-App-Tabs-in-Gallery/m-p/846477/...

Good Day

We need a way to read a workflow log file while the workflow is running .. we want to peek inside the log file to see what is happening in the workflow, especially for the  case when the workflow seems to be "hung". This would be an invaluable troubleshooting tool.

Currently these worklfow log files are locked by Windows and are inaccessible by all but unapproved 3rd part utilities .. if at all.

Often these logs disappear if the workflow needs to be deleted in order to save the environment

It is noted that the service logs do not exhibit this behavior, so the request is to

1) allow the running workflow logs to have the same behavior as the service logs

2) provide a work around to allow reading of the running workflow logs

3) ?????

Thank you for thinking about this

Tom D

Greetings Server friends!

I was talking with @KevinP in the Solutions Center at Inspire and we talked a lot about how Server has been evolving over the last several versions. I'd like to request that end users be able to select workflows or applications shared with them as "Favorites." It would be great for ServerUI to offer a separate section for these selected "favorites" so that the end users can have a single go-to place to access their most frequently used apps.

 @JohnPelletier 

Hi all,

For a user to know if a schedule was successful or not, they need to go schedule by schedule to check each of them.

I suggest adding one additional column to show the status of the last run. 

Something like this:

Thank you,

Fernando Vizcaino

When restoring an Alteryx Gallery instance to a second box for test & dev it's highly likely that you don't want all your workflows scheduled from your production instance to run in your secondary instance.

However there doesn't currently seem to be a kill switch that you can implement up front to stop your scheduled workflows from running. The only way to disable scheduled workflows in your test gallery is to manually delete them all, which is annoying when you have hundreds.

It would be great to have a config flag to disable scheduled workflows before the service is started.

If two users sit in the same studio and have multiple scheduled workflows in that studio, both users can see the results of those schedules under "Workflow Results" -> "My Jobs"/"Jobs Shared with Me" 

It gives both users in the studio good visibility of all the workflow results they have access to.

Now if we move to a 1 studio-1 user environment and share workflows and schedules via collections, this "Workflow Results" -> "Jobs Shared with Me" functionality is empty. Instead users have to go to each schedule individually to see the results from them there. 

So if you're in a 1 studio-many users environment, there is a single place to go to see all workflow results. But if you're in a 1 studio-1 user environment and sharing via collections, you have to go to infinitely many places to see the results of all the schedules shared with you.

So my idea is to have results from schedules shared via collections appear in Workflow Results.

Submitting this idea based on the Case #00361430.
 

We are trying to do alteryx workflow chaining based on workflows available in alteryx gallery, but this option is not currently available in alteryx right now and we are raising this idea to enable this feature in upcoming release or existing version patches.

Currently couple of methods available; saving the workflow in network share drive and chain the alteryx workflow based on events or run another analytical app on success.

The disadvantage of these methods are,

1. We cannot have version history maintained for the workflows in network share drive.

2. We cannot able to run a specific workflow in chaining as the workflows are packaged together.

Add Admin ability to place the Alteryx Service (Engine) into Maintenance mode allowing current workflows to complete, but all new workflow processing moved into Queue to allow for server configuration and/or maintenance.

Currently, if I want to make a small configuration change (like a memory setting in the Runtime settings) I have to hunt for a quiet window or the lowest level of activity to kill the service (and the running jobs).

It would be helpful to flip a 'switch' and have all new jobs go into 'Queue' allowing for the change and service stop/restart ... then pick right back up with the queue in configured order. (execution time, priority level, etc...)

At my organization, we have many workflows on our server that take data from one database and store it on another. We would love the ability for an alert system that warns us when a job fails so that we can solve it immediately and not risk the chance of not noticing until a few weeks or months later.

Along with setting a schedule for an app in the gallery, the user should also be able to set the different interface values for each schedule he/she makes.

My main use case is regarding having generic templates for ETL processes, that have multiple different types of runs based on configuration values, but I'm sure there are plenty others.

Best,

dK

It would be a very pleasing user experience if we could enjoy the Server usage with a true dark mode. The customization in the Theme-Panel isn't advanced enough to do it ourselves - unless we deep dive into the css-files. The CSS already has a good structure and the dark mode could be enable with just a few changes. 

Here is a comparison of my server in light and dark mode.

It's probably noticeable that I haven't studied Design, but it should give a rough suggestion how it could look.

Obviously not everyone wants a dark mode, therefore every user should have toggle in the user settings to switch between light and dark mode.

So - one of the biggest challenges that we have with the MongoDB used by Alteryx Server is that we continually have issues with locking (where our admins have to go in and undo locks)

Additionally - the current implementation of MongoDB connectivity does not support full Kerberos authentication which means that we're on a non-compliant install (which in a large enterprise is an uncomfortable place).

Given that a very large amount of what the server does is transactional - it would make sense to have an option to use a large-scale SQL server instead of using Mongo.   For large enterprise customers, there must be flexibility to allow the databases that they have large supported instances of (my strong preference would be MS SQL 2016).

MS SQL natively supports XML so all the canvasses can be stored in native format.   Additionally, MS SQL allows very fast query across XML, and given the clustering and reporting capabilities in MS SQL, this would dramatically increase our ability to self-manage our infra.

Given that Alteryx is looking more and more at large Enterprise customers - a move to a large-scale clustered SQL env as the back-end would be a very positive move.

NOTE: as we consider DB options for a SQL backend - please consider your large-scale enterprise customers.   For example - MS SQL or Oracle or DB2 are all much more prevalent in enterprises than databases like Postgres - so it's important to focus on the enterprise support for the DB that you choose.

+ @Deeksha @avinashbonu @revathi @BenBu

The current Alteryx user interface is displayed in a vertical orientation without the option for customization. To optimize space efficiency, it would be highly advantageous if the filters could be arranged horizontally, as depicted in the attached figure.

Additionally, there is a usability issue with the options list for interface tools like the list box. Currently, all options are displayed without utilizing a dropdown, requiring users to scroll extensively when multiple tools with numerous options are present within a single analytic app. Implementing a dropdown functionality for improved navigation would significantly enhance the overall user experience.

Currently, only users themselves are able to setup the default worker tag in their My Profile page. To ensure efficient management of worker nodes, Server Admins or Curators should be allowed to set the default worker tags of gallery users, preferably in bulk. This will help avoid workflows to be executed using the wrong worker node.

API that allows to specify the workflow version to download.

For whatever reason a schedule is disabled, whether a Studio expires, or for any other legitimate reason, a notification email should be sent to the Admin and the one that created the schedule in advance of it being disabled. When a scheduled workflow is not executed, it leaves us scrambling for answers. A sudden disablement of the schedule is disappointing to discover after all other stones have been turned. Notify us in advance of a schedule being disabled. 

An example would be where a user has a scheduled workflow that runs at regular intervals and they might want to look at the logs from the results from a specific date. Having the ability to filter the date column would help with this, as the only other alternative at the moment is manually working through the pages.

It would be useful if the Admin of a Private Gallery (in house server) could delete studios and/or members.  Also, it's confusing that a member who's added also gets a Studio automatically set up.  Members (for my purposes) are only supposed to be able to run apps in collections that I grant them access to.  They should not get their own studio.  Even if they can't use the studio (or even know that they have a studio), it's not very efficient to have all these studios show up on the subscriptions screen.

Please could all log file paths on Server have the option to change their location, including 

C:\ProgramData\Alteryx\ErrorLogs\AlteryxE2

To enable all log files to be written to an alternative drive than the installation.

The benefit it to prevent excessive space usage on the C: drive

Support have advised there is no way to alter the path or limit these log files by number or size.

Many thanks.