Interface tools to be allowed to be deactivated in containers

[mceleavey]

Currently it's not possible to "switch off" interface tools in the same was as we can with the other tools. This limits the functionality especially within chained apps. If we could switch these tools off it would be much easier for us to tailor the experience by allowing selections to be activated by logic, rather than simply the data therein.

Please Alteryx Gods. I beseech thee!

*lights candles*

[patrick_digan]

Great idea!

[TheOC]

Love the idea!

[cgoodman3]

I’ve always wanted to be able to put interface tools inside tool containers so you can turn off a container which also deactivates those questions from appearing in the app interface.

[clmc9601]

Cool! How would you want it to impact the interface itself? For those options to completely disappear, or would it be more like a radio button that hides everything nested beneath it?

[clmc9601]

Aha same thought as @cgoodman3 

[mbarone]

YES PLEASE!!!!!!  I too have had to complicate my designs to work around this - what @cgoodman3 talks about is exactly what I could use (put an interface tool in a container and if the container is disabled, then so is the tool's appearance in the UI).

[mceleavey]

@cgoodman3 exactly. Think chained apps. I would be able to tailor the second app not only to change the data in dropdowns etc. but to actually remove a question/option according to logic.

@clmc9601 more of a dynamic thing. If you select X in app 1 then chain to app 2, then option five doesn't exist as it's logically mutually exclusive.

I have a LOT of use cases in a single project where this would be very helpful. Currently, we're hacking the XML to apply the suppression.

[mceleavey]

Exactly @mbarone .

We're doing it via the flat ASCII method at the moment, which is not for everyone.

[Jean-Balteryx]

Even though it's your idea @mceleavey, I love it and support it !

[mceleavey]

@Jean-Balteryx  😁