Alteryx Designer Desktop Ideas

When training people on the use of action tools, something that I always have to hit on is that when you are telling the tool which piece of the XML that you are adjusting, it's sort of difficult to tell what you have selected, and super easy to accidentally select something else.

Example:

When you initially select the action to take it's this nice Blue Color. However, it still doesn't feel exactly like you have actually selected anything or told the Action Tool what to do, since it's so easy to just select any other one of these actions.

A slightly different problem is that if you are selecting an action that has been previously configured, it is just this light grey color. So it can be easy to accidentally change your settings because you may not realize it's actually set up.

Here is a recent community post that sort of outlines a few of these problems.

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Analytic-App-to-Create-Custom-SQL-Quer...

Similar to previous ideas from @patrick_mcauliffe and @shailesh_patel - would like to request 2 things:

Default on Folder Picker Interface tool

The folder picker tool does not currently allow a default value - this unnecessarily adds work if users have the same value 90% of the time.

Please add a field for the default value that will show when the interface starts up

Similar ideas:

- Default on Date interface: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Default-Date-for-Interface-Tool/idi-p/35770

- Default on File Selector: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Default-file-location-in-file-broswer-Interf...

It would be great if the "fields from connected tool" option pulled fresh data at runtime when used in the gallery and pulling data from non-interface tools. The external source option doesn't have many settings (i.e. I can just point to one file), whereas the possibilities would be endless if I could use the full suite of tools to create a data set, at runtime, to pass to the list box/dropdown.

I'd like to be able to disable a tool container but not minimize it so I can still see what's in there. Maybe disabled containers could be grayed out the way the output tools are when you disable them. We would still need to retain current features in case people like it that way, but it would be nice to choose.

I have some fairly long running analytic apps on my private gallery.  We have many different users who will run these apps and I would like to send them an email when the app is complete so that they don't have to keep checking back for results.

I came across a few different posts that explained how to use a text input named __cloud:UserId to determine the user id of the person running the app and then to query the MongoDB for that user to retrieve their email address.  These posts were very helpful, as I do have it working in my analytic app.  However, I tried putting all of this into a macro so that I didn't have to copy/paste every time I needed the current user's email address.  Unfortunately, the __cloud:UserId text box does not seem to work if it is in a macro. 

I will start off with a story. I have built a process to manage batch API requests. It's an iterative process that checks to see where the export is at by calling an API and then returning some status. It will run and wait and run and wait until the export is ready to be downloaded. However sometimes, the jobs don't finish and a status returns something like "failed" or "cancelled". When this is the case, I have my process (which is a little bit batch macro) kicks off an error message, using the nifty error message tool. After some time I noticed that it was a PAIN to go back and figure out which of my requests failed and I decided that I need to add some messaging around where this was failing, so I could do some easy auditing. So I go back into my tool and much to my chagrin, I cannot pass variables into the message section. I would expect it to have worked something like this:

"Record "+[#2]+" is not 'A'"

Can we please get a change to this. It would save a lot of time and energy if we could create a dynamic error message option.

TL;DR Please allow us to use formulas in the "If expression is true, display error message:" settings area.

It is just a bit of annoyance, really. I'd like to see the option of inputting a hexcode of color and/or a screen color picker in the color dialog. At the moment, you have to change R, G, B separately or play around with the cursor to find the right color.

The color dialog is relevant for the documentation purposes but also reporting tools and I'm sure it would make life easier to some people, especially when branding colours are important.

It would be nice to be able to set a default date for the Date Interface tool.

Props to @KaneG for the workaround ( http://community.alteryx.com/t5/Publishing-Gallery/Set-Default-Date-for-Date-Interface-Tool/m-p/3573... But I'd like to see something built in to the tool rather than use a workaround every time as the standard.  Plus, I enjoy the uniform look of having two date inputs.

Just as a side note while we're on the topic of the Date Interface tool; it is really misleading the way "Today" stays outlined even after you click on a different date.  I always second guess if it took my click or not.

I sometimes find that a workflow would be more efficient if I swapped the order of a couple tools. It would be cool if we could select 2 tools and then right-click or something to swap them.

Can the inputs to app interface tools update other interface tools within the same app?  Right now, I believe the only way to do this is with chained-apps, but I don't wish to go that route again.

Just one example:

Can a Dropdown interface tool update a listbox interface tool with an action?  

Right now, I have two interface tools in an app:

1. Dropdown
2. Listbox.  

For the Listbox tool , it references an external source file for the NAME:VALUE pairs, let's call this file:  Category1.yxdb.

I would like for the resulting dropdown selection to update this external source file to say, Category1.yxdb or Category2.yxdb or Category3.yxdb, etc.

The different .yxdb files here have different name:value pairs within them.

It doesn't seem like this possible at the moment, but please let me know if this is something that's currently supported within Alteryx.

Thanks,

Collin

Pardon the length of this post, but I have been working with Alteryx since version 2.0 (11 years) and have been accumulating a wish list ever since.  Some of these suggestions have been made in the past but have yet to be embraced.  This is the first post for the first 'idea' but, as I said, this is a wish list that has grown since I was first introduced to Alteryx. More posts will follow.

I will break this into sections to hopefully make the suggestions easier to categorize and digest.

Application interface - Since I was introduce to Alteryx, the application interface (what is presented to users) has remained rather stagnant and, with the rumored push to adopt HTML as a replacement for pcxml, could benefit from the following additional settings. I suggest these based on the fact that dot Net classes for interface controls are readily available in Windows which allow for manipulation of each of the controls attributes.

1. The ability to set 'style' attributes for each of the interface tools in the application interface (font-family, font-style, font-size, font-weight, color, etc. This could be presented to the developer as an additional (perhaps optional button) in the Configuration panel for each interface tool as below:

These settings would be specific to the type of interface tool and to how the individual tool would layout and/or be styled relative to the application interface window. One layout option, applicable to most interface tools, would be where the label would be relative to the object itself (top, bottom, left, right). The CSS could be stored in and interpreted from the XML of the yxwz file referencing the ToolID of the Node in a section of the XML hierarchy called <CSS> or something standard.  An option to alter the default CSS could be displayed with a radio button control so that if not selected, the tool would fallback to the default system CSS of the tool.  This default could also be set in System settings so that a consistent interface could be defined across the enterprise.

2. Moving to the actual window that displays when the application is opened, a lot of the same concepts could be applied to the Interface Designer pane.

Attributes that could be set could include position on screen when opened, width and height of the window, and all the attributes of a dot Net form.  The same radio button strategy used for individual interface tools could be employed to use or not use system defaults.

3. In the UI, it would be nice if there was additional flexibility in how the interface tools could be laid out.  Along with the relative position of labels for each control, being able to layout controls horizontally as well as vertically would allow for a more organized interface.

 The Radio buttons would work as normal with the Text Box controls inside each Radio button and only displaying when the button is selected.

I realize a lot of the current development in Alteryx is focused on the new Alteryx Connect and being able to attach to more data files and services. But, if there is still also a concerted effort to move from what could be considered a legacy proprietary mark up language, pcxml, to a more robust and universally accepted mark up, html and css, then, in my humble opinion, expanding the options for developers to design more user friendly and customizable applications to a standard 'style' across the enterprise, both on the desktop and in the gallery, is a worthy endeavor.

Thanks for your attention.  More to follow.

Dan

I would like to see a time interface tool similar to the Date and Numeric Up Down tools. I am working on some macros where the user can select the time they would like to use a filter for the data. 

Example: I want all data loaded after 5:00 PM because its late and needs to be removed.

Example 2: I want to create an app where the user can select what time range they would like to see records for (business hours, during their shift, etc) 

Currently this require 2-3 numeric up downs or a Text box with directions for the user on how to format field with Error tools to prevent bad entries. It could even be UTC time.

Time Interface Tool 

Speed up canvas edits - The Create/Remove Space Tool

Usually day two of working with a canvas I realize that I have been a fool, and I come up with a significantly more elegant or simple solution.  Moving all of the containers or tools to fit my slick new container is cumbersome and slow.  I've created a GIF of a feature several tools have which allows the user to easily move and arrange items on the canvas.

Open source tool used in demo: bpmnJs

Hi,

I would like to be able to modify my connection string in the Alias Manager.

Connection string is greyed out :

If I want to change my connection string, I have to create a new alias.

It would be nice to have functionality similar to the List Box where a user can select all items at once, or deselect all items at once.  The workaround for now would be to roll everything up to an individual Key (maybe called "All").  But it would still be nice to have those two options (again, just like on the list box).

Hello. While working at my company it has come up a few times that An Interface tool that acts like a standard "grid" would be extremely helpful.  

This tool would allow users to update data that has a logical link to each-other like a stanard "row".  Below are a few very simple examples where this would be extremely helpful.

#1) An application is being used as a file System ETL that has an interface that allows users to select what data to pull from a flat file and store in a database.  The users can pick which 'columns' to keep by choosing the following information.  The column name, type, and final database location of that column. 

In this case a user needs to enter 3 key pieces of field information that have to relate to eachother.  

#2) There is a table in a database that has thresholds for a specific law at the state level. (for Example: All loans in Florida must have a loan balance < 300k).  However these laws can be updated, and the end users want the ability to #1: See the data, and then #2: Update it if the laws have changed.

A grid in this case would be perfect, as they could query the data to see the 50 states and specified limits, and then change the data in the "limits" column in order to update the database.

The previous 2 examples are pretty simple examples, but I have run into this request a few times from my personal experience, so figured I would see what everyone thought!

Right now, the List Box interface tool allows end users to select multiple options of fields for selections, filtering, and formatting/formulating. 

However, it doesn't do quite as good when a use case has over 1,000+ columns/fields. This is made even more complicated with each column/field having somewhat similar naming conventions thereby causing confusion. 

Having a search function, as made available in standard Select Tools, Join tools, and other tools that has filtering capacity, will be most helpful for developers to give maximum flexibility to end users.

The ability to limit the number of records (either on a specific input tool, or via the Workflow Properties) is super useful when developing a workflow...

...but how many times do you forget that a record limit was set and then spend ridiculous amounts of time trying to figure out why something isn't working properly? (I can't be the only person this has happened to...).

Wouldn't it be fantastic if a warning/message was shown in the workflow results (e.g. "Input Tool (n) has a record limit set"
or "Record Limits are set on the Workflow Properties")?

This idea is concerned with suggesting values based on text box entry in an analytic app. This would be an autocomplete within the text box interface based on matches to a list of connected values. For example, if someone was posting "805 Wells Road" it would expand the text box window and supply potential matches to click on.

Quick and dirty photoshop image below: