Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Indeed, I call it the Fieldset-at-a-Time (FsaaT) method and there’s a blog post and some demos out there. The JS can be even tighter now than a few years ago due to browser built-ins, it’s really quite easy. If you don’t care about giving somebody a Back button, just use multiple forms. The user doe...
I would have those tokens be Velocity {{my.tokens}}. Then each can access any $variables set in earlier tokens.
Well, using Velocity output as part of links isn’t generally supported. Instead, output the whole link including the and from Velocity,
Is it a Velocity {{my.token}}? I don't understand any other way that what you're saying could be true -- that the {{my.token}} reflects lead-level values.
There's no reason a {{my.token}} won't be sent with a webhook, as long as the Call Webhook step is inside/inherits from the place the {{my.token}} is defined. is it really a {{my.token}} though? A person-specific history field would be a {{lead.token}} (which also will be sent in a webhook).
Sure, that would be interesting, although the thing is it totally changes the idea of where Dynamic Content can go.
Something like a country-specific footer can be easily done in Velocity (which can be on the template).
Couldn’t you use the id of the to simulate this?
But I'm saying it's not specific to labels or values or any datatype. It's a lack of escaping so the Idea would benefit by being generalized.
Robb, {{my.tokens}} aren’t properly escaped to serve as any form field values in Marketo (they need to be both JSON-escaped and HTML attribute-escaped, but they are not).You may not have run into a problem with other datatypes/values, but the form descriptor breaks with any tokens crafted in such a ...