Hey everyone,
Wondering what experience people here have with managing forms across multiple workspaces?
I'm in the process of setting up a centre of excellence workspace for an organisation that has teams in a few locations globally, each with their own workspace. The CoE workspace will cover off a lot of key program templates - just trying to figure out the best solution within this for handling forms. I'd like to be able to set up some global forms within design studio for a few of the program templates, but you can't share forms across workspaces.
I'm not keen on the idea of not specifying any form within each program and having "global" forms within each workspace where the reference needs to be updated each time. But nor am I particularly keen on local forms for every program...
Thoughts?
Solved! Go to Solution.
Grace, this is one of those major limitations in Marketo today. Especially when, today, you can share email/LP templates, smart lists, and images. To have a proper CoE/Global Demand Center environment in Marketo, all key assets should be sharable across workspaces. Vote here:
Until this is "fixed", we now include the forms at the program template level for some of our templates (primarily events).
While this creates an unnecessary number of forms in our instance, it's the most scalable approach we have - especially for those users that aren't savvy enough to leverage some of the advanced alternatives - like the Forms 2.0 API.
Grace, this is one of those major limitations in Marketo today. Especially when, today, you can share email/LP templates, smart lists, and images. To have a proper CoE/Global Demand Center environment in Marketo, all key assets should be sharable across workspaces. Vote here:
Until this is "fixed", we now include the forms at the program template level for some of our templates (primarily events).
While this creates an unnecessary number of forms in our instance, it's the most scalable approach we have - especially for those users that aren't savvy enough to leverage some of the advanced alternatives - like the Forms 2.0 API.
Thanks for that screenshot, Dan. This is helpful to know - I suspect that this is how I will need to handle it until forms can be shared!
You could use the REST Asset API (not the client-side Forms JS API) to replicate form descriptors from workspace to workspace. For example, on the hour, copy the primary form definition to all secondary spaces.
Thanks Sanford, that's a really good thought to keep in mind. I think local is probably going to be the best solution for this client right now, but I will be looking into that option when they get a little more comfortable with the technical skills!