Show/Hide logic for Work Request forms
We would like the ability to show or hide different fields in a Work Request form based on a user selected drop down.
For example, if a user selects Website Update from the Request Type dropdown, only fields in section Website Update would display and all others would be hidden.
In current state, you can choose to jump to a certain section, but other sections remain visible so the jump logic doesn't provide much value as users still have to scroll past irrelevant sections of the form to submit it. I did confirm with one of the IT engineers there is no way to execute this desired functionality with the currently available form logic.
-
Richard Jones
commented
I wanted to add some more details.
Specifically I need to be able to reference a field without showing that field.
Eg: If I have a template where I have a multi select option, which is either A, B or C - and someone selects A AND B AND C, I want to be able to show a field for more details about A, AND then another field for more details about B (and C) (but I don't want to have to reshow the original field again.
I also want to be able to limit options on fields without needing to have a field selected or a condition met. eg: I have a template for a certain type of photo shoot which only used options D, E or F (and not A, B, C etc) so I just want to say 'Limit the field values' without needing 'IF' and a reference to a field.
This also applies to jumping to a section, if I select an option and I jump to a section, I don't necessarily want to continue down the rest of the form, I want to have an option at the end of the section, to jump (without an IF) to another section of the form.
The current implementation is tantalizing, but largely ineffective for complicated forms. I am struggling to see how I can use it as it stands.
I also posted this on https://feedback.optimizely.com/forums/964812-cmp-content-marketing-platform/suggestions/51008743-enhanced-template-logic
-
Steven Kim
commented
Having the ability to show/hide different sections would be incredibly helpful for web update requests. We'd like to keep a work request form for CMS updates to a single form, and having to alert users to ignore lower sections of forms for different types of updates is not very user friendly and can cause confusion.