SanfordWhiteman

I don't think such a "code generator" is feasible. Anybody using COs should have a dev who can write VTL. Now, having Velocity tokens work in web pages and webhooks -- and having tokens as a whole be interpreted in flows -- that's an idea I can get behind!

Velocity tokens can access COs for dynamic email content. That's their most common use.

But it does not say we have to ask for their consent to just store the data. I wouldn't trust a lawyer who said this. Your call, but the people on this thread have worked with hundreds of companies in total and frankly, I trust us more.Provisions for withdrawal of consent make no sense without a c...

Read Article 17 and Recital 65 again.In fact GDPR explicitly covers erasure of data upon withdrawal of consent.

customObjectName, filterType and we get an appropriate error if we enter invalid values against those fields.These are enumerations of property names, not data values in the database. There's no comparison.

It's neither a bug, nor is it "good to have" — because you're not understanding how the Marketo database works.It's a terrible to have feature that would break the system. It would, in fact, become the bug.Let me repeat: the string "123" is a valid value for the email field.Here's an actual lead in...

in all other scenarios we have worked beforeReally? In all other databases with an email column, a query against that column is validated? Against what regex?Don't think so. Anyone designing such a thing would have no idea how to validate email addresses.

That makes no sense whatsoever."123" is a valid email value in Marketo. It can't be a blocked filter value.This is not a bug.

"123" is a valid Email value. Nothing wrong there."abc" may not be a valid hyphen-grouped GUID format but I've never seen a single system that does format validation on this datatype. That's overengineering, like validating if a SHA-1 hash is 40 characters and throwing a different error -- why bothe...

Like add the inside the RTA, like any other HTML element.