I'm a new product manager at Marketo and am currently addressing these issues. The direction we are leaning is to enable a "no-draft" capability to essentially not create a draft each time a change is made to a shared asset (template, snippet, form.) For example:
So, step #1 is to reduce the number of drafts being created in the first place, and often unnecessarily! Step #2 is a better way to mass approve assets. So in my example above, you'd still technically need to approve the 20 drafts that include the updated form. The latter is another problem I'm working to solve.
Just curious to see if this has progressed from "addressing" to predicting a release date yet.
I'm a UX Designer working on this project. We are currently tackling the "no-draft" capability for snippets and we're hoping for a November release! After that, we'll be working on the rest of the shared assets. The target release for these (templates and forms) should be early next year. Christina and I will keep you updated
Hi Christina Fuentealba,
I am a little concerned about the risk of publishing errors with this "no draft" capability, unless :
For instance, on old free form templates, adding a couple of fields or changing the dynamic profiling rules on a form can make it too long to fit in the page.
Hi Scott K. Wilder,
This idea should me marked "already have it"
Thank you for letting me know. Will look into this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.