Request/Briefing Form Templates: Ability to add hidden, pre-filled fields
When creating form templates, I need to add fields that are hidden and pre-defined/selected so the requester doesn't see them, but they get added to their request. (In an ideal world, if some logic could be applied to them - e.g., if the user selects this field: choose X value for hidden field, else: choose Y).
For example, if people fill in the 'Email' form, I would like to add the field 'emailField1' with the value True pre-selected. This means the user doesn't have to fill it in each time and it allows us to use the field for planning views, etc
Matthew Ward
shared this idea
-
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