Hiding elements by default

Ask the Community
1

Hello, I’m might not be alone but when we have a lot amount of datas, workshop page can be long to load and element (like buttons for exemple) which are managed by submission criteria can be long to get their correct state (disabled/hidden/enable) making them all showing off then hiding step by step. I’ve found a way by adding some variables used in “conditionnal visibility” but it can become hard to maintain because we have 2 separates ways to manage the visibitlity of the button so it can increase the risk of making an error if modification is needed.

The question is: Is there a way to make the opposite like hidding by default and showing depending of the submission criteria ? Or I get no choice to use conditionnal visibility ?

Thanks in advance.

2

I don’t know if there’s a way to change that in settings. That being said, if your module is slow to load, there might be solutions that can speed it up by splitting it up into multiple modules and then embedding those into a main Workshop module or Carbon workspace. It’s interesting that you’re noticing it loading slowly, and it might be helpful to get a sense of how complex your module is. Do you have a lot of tabs (or nested tabs)? How many variables and source object types are you using?