I've found something that will most likely need to be addressed in a future update. This applies specifically for custom form results emails. (In other words, the issue does not occur when using the default [_form_results_] variable in the form results email. It only occurs when creating a custom HTML layout using specific field "names" to display inputted information.)

Normally, if a particular form field is left blank, the corresponding item in the form results email is also blank. However, when using the new "conditional" fields, if a particular form field is not completed (left blank), the corresponding item in the form results email shows the field "name" within brackets. (Ex: If a form field named "extension" is left blank, the form results email will show "[extension]".) Interestingly, while this occurs on all but one of our "conditional" form fields, one "conditional" form field does not have the same behavior. I'm not sure why, though.

Anyway, here's my question: Is there some kind of code (PHP possibly) that I can use to hide the bracketed variables if there is no input? Or, will we just have to wait for an update. I know our client is not going to be pleased that this extra text is showing up on the form because it adds confusion to the reading of the information. (They process many, many lengthy form submissions and any nonsense input gets in their way.)

Thanks, in advance for any help anyone can provide.

Kindest regards,
Jeremy

I would open a support topic as this something that the cc gurus should be looking at.
https://www.coffeecup.com/help/myroom/opentopic/

Thanks Eric! I opened a support topic. Hopefully there's an easy fix. :-)

Regards,
Jeremy

Post back when you get an answer.

Will do. :-)

Hey Eric!

Just wanted to follow up and let you know that my ticket was responded to. It was forwarded to the techs and they said a fix will very likely be in the next update. Woohoo! :-)

What a great group of software developers! :-)

All the best,
Jeremy

This is why I stick with CC. They listen. Really puts all other companies customer service to shame.

This issue has been fixed in Build 5191. How is that for turnaround Jeremy!