Alteryx Designer Desktop Ideas

When I use the Comment Tool its difficult to select the tools inside it, but when I use the Container Tool the Container Text doesn't support Font Sizes, and doesn't support multiple lines of text so I end up moving the Comment into the Container, but still have problems selecting a group of tools.

So a combined Comment and Container Tools would be wonderful!

Bonus: If the Comment Tool could support Multiple Font Sizes.

Dear Alteryx GUI Gang,

I'll create a container and then customize the colours, margins, transparency, border and then want consistency for other containers.  It would be nice to have a format painter function (brush) to apply the format of one container to another.  This of course could be extended to other tools like comments.  There might be a desire to apply this to more tools too, but the comments and containers would be my focus as they are almost always custom configured.

Cheers,

Mark

I hope that there will be a radio button or a check box where Auto Save on Run can be disabled.  Auto Save on Run is a bad idea.  I often go into workflows and only need one report - so I break a bunch of connections to other reports, maybe I make some other small adhoc or one-off type changes and then Run the workflow.  I get my one, maybe modified, report and close without saving.  So the next time I open the workflow it's as it should be. 

With Auto Save on Run - I'd have to undo everything I changed.  What if it's not my workflow to be changing?  If there is no option to turn it off:  I'd have to make a copy of the workflow, open and make changes, then run, then close, then delete the workflow.

In general, you should never be saving unless it is a deliberate act performed by the user.

Before Designer 2019.4 there was a "bug" in the workflow statistics collection that under the "SampleModule" data from the UsageGallery collection the name of the workflow run from within Designer was available.  We used that information to determine the common workflows run in our community as well as generating a measure of community growth.  The "bug" was removed in 2019.4 and now we can only determine the number of runs, but not the number of distinct workflows that were run.  This idea to do return the workflow name run to the information stored in the Mongo database.