Allow Display Rules for Static Elements

It would help to hide/show Static Elements based on form values. Sometimes the “static elements” / instructions need to change based on the user input.

When the fields are being hidden/shown based on form values, we need the option to hide/show the static elements that contain the instructions for the user.

Hey Roman,

By elements I guess you mean other views? You can easily to this with JavaScript and jquery you can use the change or keyup function and then call the hide or show based on the value of the input.

If you need help with this Message me
Johnny@appknowledged.co.uk

Hi Johnny, thanks for your reply. By “static elements” I meant Title text and dividers. Currently the rules only seem to apply to other fields, not objects that arent fields. I’m not a coder, so I’m only using the drag and drop features.
Screenshot 2021-11-11 115936

Hi Johnny,

Thanks for your reply.

By “static elements” I meant Title Text and Dividers. Currently the rules only seem to apply to other fields, not objects that aren’t fields.

I’m not a coder, so I’m only using the drag and drop features. Perhaps you can teach me how to code this.

Screenshot 2021-11-11 115936.png

image002.png

I would also love to see this feature added. The “Instructions” option for individual questions can be one alternative, but those appear underneath the question itself, and I wanted my instructions to appear before the users gets to the answer selection. The workaround I found that works pretty well is to basically take all of the text I wanted to be in the static field and add it to the “Label” field of the question it goes with. Knack will automatically make all of this text in to a bolded “header”-type text, but you can make it look and read like basic text in a static field using some simple HTML formatting codes (e.g. add <br /> to create line breaks, or put in <span style=“font-weight:normal;”> and all the text that appears after the > will look like normal text. This is a bit clunky and difficult to edit because the “label” boxes are one-liners, but it gets the job done for now.

@HGSU thanks for your input here. What field type do you use when you do your suggestion? Since it’s really the label that matters, I don’t want the form field to confuse the user. Thanks!!