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*

[DavidP]

Great idea Chris!!! The gears in my head are already moving wrt all the things this could unlock!

[Kenda]

I feel like this is one of those ideas that we've all lived with and found workarounds for but makes so much sense to add it to the product! I will gladly hop on this bandwagon 

[Thableaus]

I support this idea, but going a bit further, it would be interesting to enhance the whole Chained App structure. I still think using containers to define window interfaces would be tricky, we should be able to link apps in a clear way.

[marcusblackhill]

That would be very helpful. It would simplify the way we do Apps, how we test them, control the flow, etc. Great idea!

[JagdeeshN]

Would indeed be very helpful. Especially while building complex analytical apps that might need different interfaces according to the audience using it.

[Taylor_S]

Yes!! This is so needed!!

[hansfinesse]

This should be actually implemented! The container when disabled should not show the interface tools associated with it. This can be great with conditional logic

[hansfinesse]

This is required