Email 2.0: List variables should only accept list values

[Grégoire_Miche2]

With the new email editor, it is possible to create a picklist variable.

Problem: the enduser is not restricted to the list of values! So we cannot use this to restrict the values the user can input, which is very dangerous. Furthermore, we discovered this inadvertently, playing with it, as the doc does not say anything about this.

Although, I understand in some cases, it's better to let the possibility to add a custom value.

So please Marketo add a mktoAllowCustomValues property, that when set to false, would prevent the user to enter a value that is not in the list.

Default value for the property should be "False".

Use cases:

• Have the user choose amongst various Google ID
• Have user choose amongst some predefined branded colors

All of which situations where a 'custom" value could create a serious issue.

-Greg

[Grégoire_Miche2]

Justin Cooperman​,

Another one for you

-Greg

[SanfordWhiteman]

I totally agree and when we built this enhancement (for LP Editor, but same idea) there was never a thought of allowing outside links, since the whole idea is to focus marketers on established channels:

[Anonymous]

Regarding the branded colors list example, it would be great to have values as well as names for the values, like the boolean. Most people can't tell what color they're choosing by looking at a hex number.

[Anonymous]

Is the list variable coming to the LP editor?

[SanfordWhiteman]

We built this ourselves as an extension to the GLP Editor. It's not official.

[Grégoire_Miche2]

Hi My,

Vote here:

-Greg

[Grégoire_Miche2]

Hi My,

Many of the email enhancements should be replicated to the LP's.

See

-Greg

[Anonymous]

Voted!