You seem to disallow Custom Values from being blank (not even a blank space) but I think that's naive. You should ALLOW Custom Values to be blank. You should also allow Conditional Logic inside of Funnels so that we can do things like: If a Custom Value is "Yes", display "This is a Yes Value", etc. | Funnels

You seem to disallow Custom Values from being blank (not even a blank space) but I think that's naive. You should ALLOW Custom Values to be blank. You should also allow Conditional Logic inside of Funnels so that we can do things like: If a Custom Value is "Yes", display "This is a Yes Value", etc.

David Ramos

use case, there's many; a simple use case is sometimes I want the Custom Value to not be displayed within a paragraph in a Funnel whereas on other sub-accounts I want it to display something within that same paragraph/funnel. Fuad

HIGHLVL-I-3147

March 16, 2021

Zack Herman

I think conditional or default custom values would be killer. So either:
1) Another field in the CV editor for default value (this should carry over on snapshots.  - or -
2) Conditional OR statement within the brackets. This wont break anything and can simply be used by advanced users. Example: {{ custom_values.whatever || "Some default text otherwise." }}

John Mohr

Want the feature, don't like the poster's rude attitude tho, geezzz.

Joe Solano

I agree there are other posts on the ideas board describing the need to have exactly this. If you want workflows to behave differently for different clients without having to have different sets of code then blank values and conditional logic should be allowed on custom values

Ryan Hasiak

Some times clients want to send emails and sms and some just want to send sms. If we had a custom value "Send SMS?" set to yes or no we should be able to condition on that and send them down correct path in the workflow. and simply set that custom value on install to whatever the client has chosen to do

Ryan Hasiak

Yes Please! Why is this not a thing yet?!